# Host setup for databases with Amazon FSx for NetApp ONTAP Host setup This section walks you through an example host setup for deploying a database system on AWS using Amazon FSx for NetApp ONTAP as the primary storage solution. **Topics** + [ ## Linux kernel parameters ](#linux-parameters) + [ ## Network File System (NFS) ](#nfs-setup) + [ ## Create mount points ](#mount-points) + [ ## Mount file systems ](#mount-filesystem) + [ # Host setup for MSSQL ](mssql.md) ## Linux kernel parameters See the following tabs for details. **Example** Use the following steps to setup the Linux kernel parameters. 1. Create a file named `91-NetApp-DB2.conf` with the following configurations in the `/etc/sysctl.d` directory. ``` net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_rmem = 4096 131072 16777216 net.ipv4.tcp_wmem = 4096 16384 16777216 net.core.netdev_max_backlog = 300000 net.ipv4.tcp_slow_start_after_idle=0 net.ipv4.tcp_no_metrics_save = 1 net.ipv4.tcp_moderate_rcvbuf = 1 net.ipv4.tcp_window_scaling = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_sack = 1 ``` 1. Increase the max sessions slots for NFSv4 to 180. ``` echo options nfs max_session_slots=180 > /etc/modprobe.d/nfsclient.conf ``` 1. Set `sunrpc.tcp_slot_table_entries = 128` in `/etc/sysctl.conf`. 1. Reboot your instance for the kernel parameters and NFS settings to take effect. Use the following steps to setup the Linux kernel parameters. 1. Create a file named `91-NetApp-MaxDB.conf` with the following configurations in the `/etc/sysctl.d` directory. ``` net.core.rmem_max = 16777216 net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_rmem = 4096 131072 16777216 net.ipv4.tcp_wmem = 4096 16384 16777216 net.core.netdev_max_backlog = 300000 net.ipv4.tcp_slow_start_after_idle=0 net.ipv4.tcp_no_metrics_save = 1 net.ipv4.tcp_moderate_rcvbuf = 1 net.ipv4.tcp_window_scaling = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_sack = 1 ``` 1. Increase the max sessions slots for NFSv4 to 180. ``` echo options nfs max_session_slots=180 > /etc/modprobe.d/nfsclient.conf ``` 1. Reboot your instance for the kernel parameters and NFS settings to take effect. Use the following steps to setup the Linux kernel parameters. 1. Create a file named `91-NetApp-ASE.conf` with the following configurations in the `/etc/sysctl.d` directory. ``` net.core.rmem_max = 16777216 net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_rmem = 4096 131072 16777216 net.ipv4.tcp_wmem = 4096 16384 16777216 net.core.netdev_max_backlog = 300000 net.ipv4.tcp_slow_start_after_idle=0 net.ipv4.tcp_no_metrics_save = 1 net.ipv4.tcp_moderate_rcvbuf = 1 net.ipv4.tcp_window_scaling = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_sack = 1 ``` 1. Increase the max sessions slots for NFSv4 to 180. ``` echo options nfs max_session_slots=180 > /etc/modprobe.d/nfsclient.conf ``` 1. Reboot your instance for the kernel parameters and NFS settings to take effect. Use the following steps to setup the Linux kernel parameters. 1. Take a backup of `/etc/sysctl.conf` file by using the following command. ``` sudo cp /etc/sysctl.conf /etc/sysctl.conf.bak ``` 1. Open the `/etc/sysctl.conf` file in a text editor, add the following entries to it, and save the file. ``` net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.core.optmem_max = 16777216 net.core.somaxconn = 4096 net.core.netdev_max_backlog = 300000 net.ipv4.tcp_tw_reuse = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_slow_start_after_idle=0 net.ipv4.tcp_rmem = 4096 131072 16777216 net.ipv4.tcp_wmem = 4096 16384 16777216 net.ipv4.tcp_max_syn_backlog = 16348 net.ipv4.tcp_slow_start_after_idle = 0 net.ipv4.tcp_dsack = 1 net.ipv4.tcp_sack = 1 net.ipv4.tcp_no_metrics_save = 1 net.ipv4.tcp_moderate_rcvbuf = 1 net.ipv4.tcp_window_scaling = 1 net.ipv4.tcp_syn_retries = 8 ``` 1. Increase the max sessions slots for NFSv4 to 180. ``` echo options nfs max_session_slots=180 > /etc/modprobe.d/nfsclient.conf ``` 1. Reboot your instance for the kernel parameters and NFS settings to take effect. ## Network File System (NFS) Network File System (NFS) version 4 and higher requires user authentication. You can authenticate with Lightweight Directory Access Protocol (LDAP) server or local user accounts. If you are using local user accounts, the NFSv4 domain must be set to the same value on all Linux servers and SVMs. Set the following parameters in the `/etc/idmapd.conf` file on the Linux hosts. ``` Domain = Nobody-User = root Nobody-Group = root ``` **Note** You must restart the `nfs-idmapd.service` service after making changes to the domain. **Oracle Direct Network File System (dNFS)** SAP only supports deployment of Oracle database on Amazon FSx for NetApp ONTAP using Direct NFS with NFSv3, NFSv4 and NFSv4.1. You must setup the `oranfstab` file before enabling dNFS client control of NFS. For more details, refer [Deploying Oracle Direct NFS](https://docs.oracle.com/en/database/oracle/oracle-database/19/ladbi/deploying-dnfs.html#GUID-D06079DB-8C71-4F68-A1E3-A75D7D96DCE2). On configuration completion, query the `V$DNFS_SERVERS` view to verify that the server name, NFS mount points, and NFS version shown in the output match the configuration in `oranfstab` file. ## Create mount points See the following for details. **Example** Create the following mount points on your Amazon EC2 instance. ``` mkdir -p /sapmnt mkdir -p /usr/sap mkdir -p /db2/db2 mkdir -p /db2/ mkdir -p /db2//sapdata1 mkdir -p /db2//sapdata mkdir -p /db2//saptmp1 mkdir -p /db2//saptmp mkdir -p /db2//db2dump mkdir -p /db2//log_dir mkdir -p /db2//log_arch mkdir -p /db2backup ``` Create the following mount points on your Amazon EC2 instance. ``` mkdir -p /sapmnt mkdir -p /usr/sap mkdir -p /sapdb//sapdata mkdir -p /sapdb//saplog mkdir -p /backup mkdir -p /sapdb ``` Create the following mount points on your Amazon EC2 instance. ``` mkdir -p /sapmnt mkdir -p /usr/sap mkdir -p /sybase mkdir -p /sybase//sapdata_1 mkdir -p /sybase//saplog_1 mkdir -p /sybase//sapdiag mkdir -p /sybase//saptmp mkdir -p /sybasebackup ``` Create the following mount points on your Amazon EC2 instance. ``` mkdir -p /oracle mkdir -p /oracle/ mkdir -p /oracle//sapdata1 mkdir -p /oracle//sapdata2 mkdir -p /oracle//sapdata3 mkdir -p /oracle//sapdata4 mkdir -p /oracle//origlogA mkdir -p /oracle//origlogB mkdir -p /oracle//mirrlogA mkdir -p /oracle//mirrlogB mkdir -p /oracle//sapreorg mkdir -p /oracle//saptrace mkdir -p /oracle//saparch mkdir -p /oracle//sapcheck mkdir -p /oracle//oraarch mkdir -p /oracle//sapbackup ``` ## Mount file systems The created file systems must be mounted as NFS file systems on Amazon EC2. See the following for details. The following table is an example recommendation of NFS options for different IBM Db2 file systems. **Example** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sap/latest/sap-AnyDB/host.html) **Example** Add the following lines to `/etc/fstab` to preserve mounted file systems during an instance reboot. You can then run `mount -a` to mount the NFS file systems. ``` :/-sapmnt /sapmnt nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-usrsap /usr/sap nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-db2dbsid /db2/db2 nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-dbpath /db2/ nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-sapdata1 /db2//sapdata1 nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=8 :/-sapdata /db2//sapdata nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=8 :/-saptmp1 /db2//saptmp1 nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-saptmp /db2//saptmp nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-logdir /db2//log_dir nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-logarch /db2//log_arch nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-db2dump /db2//db2dump nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-backup /db2backup nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 ``` The following table is an example recommendation of NFS options for different SAP MaxDB file systems. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sap/latest/sap-AnyDB/host.html) **Example** Add the following lines to `/etc/fstab` to preserve mounted file systems during an instance reboot. You can then run `mount -a` to mount the NFS file systems. ``` :/_sapmnt /sapmnt nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/_usrsap /usr/sap nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/_backup /backup nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/_sapdb /sapdb nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/_log /sapdb//saplog nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/_sapdata /sapdb//sapdata nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=8 ``` The following table is an example recommendation of NFS options for different SAP ASE file systems. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sap/latest/sap-AnyDB/host.html) **Example** Add the following lines to `/etc/fstab` to preserve mounted file systems during an instance reboot. You can then run `mount -a` to mount the NFS file systems. ``` :/-sapdata_1 /sybase//sapdata_1 nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=8 :/-saplog_1 /sybase//saplog_1 nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-sapmnt /sapmnt nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-usrsap /usr/sap nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-sybase /sybase nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-sapdiag /sybase//sapdiag nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-saptmp /sybase//saptmp nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-backup /sybasebackup nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 ``` You must assign a virtual hostname to each SVM NFS IP address in `/etc/hosts` file. These hostnames are used in the `oranfstab` file for values of the NFS server `(server: )` during Oracle dNFS configuration. The following table is an example recommendation of NFS options for different SAP Oracle file systems. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sap/latest/sap-AnyDB/host.html) **Example** Add the following lines to `/etc/fstab` to preserve mounted file systems during an instance reboot. You can then run `mount -a` to mount the NFS file systems. ``` :/-oracle /oracle nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-oracle /oracle/ nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-oraarch /oracle//oraarch nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-saparch /oracle//saparch nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-sapreorg /oracle//sapreorg nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-sapbackup /oracle//sapbackup nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-saptrace /oracle//saptrace nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-sapdata1 /oracle//sapdata1 nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=8 :/-sapdata2 /oracle//sapdata nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=8 :/-origlogA /oracle//origlogA nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-origlogB /oracle//origlogB nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-mirrlogB /oracle//mirrlogB nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 :/-mirrlogA /oracle//mirrlogA nfs rw,bg,hard,timeo=600,noatime,vers=4,minorversion=1,lock,rsize=262144,wsize=262144,nconnect=2 ``` are the values that you have assigned in the `/etc/hosts` file for each SVM NFS IP address. + Changes to the `nconnect` parameter take effect only if the NFS file system is unmounted and mounted again. + Client systems must have unique host names when accessing FSx for ONTAP. If there are systems with the same name, the second system may not be able to access FSx for ONTAP. + For RHEL operating system, the `nconnect` parameter is supported only on RHEL 8.3 or higher. # Host setup for MSSQL Use the following procedure to create volumes and LUNs for MSSQL server. 1. Connect to your FSx for ONTAP system using SSH. For more information, see [Managing FSx for ONTAP resources using NetApp applications](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/managing-resources-ontap-apps.html). 1. Use the following SSH command to create the required volumes: ``` vol create -vserver -volume -aggregate aggr1 -size -state online -tiering-policy snapshot-only -percent-snapshot-space 0 -autosize-mode grow -snapshot-policy none -security-style ntfs volume modify -vserver -volume -fractional-reserve 0 volume modify -vserver -volume -space-mgmt-try-first vol_grow volume snapshot autodelete modify -vserver -volume -delete-order oldest_first ``` 1. Start the `iSCSI` service with PowerShell using elevated privileges in Windows servers, and set the startup type to *Automatic*. ``` Start-service -Name msiscsi Set-Service -Name msiscsi -StartupType Automatic ``` 1. Install Multipath-IO with PowerShell using elevated privileges in Windows servers. ``` Install-WindowsFeature -name Multipath-IO -Restart ``` 1. Find the Windows initiator name with PowerShell using elevated privileges in Windows servers. ``` Get-InitiatorPort | select NodeAddress ``` 1. Connect to Storage virtual machines (SVM) using putty, and create an `iGroup`. ``` igroup create -igroup -protocol iscsi -ostype windows -initiator ``` 1. Use the following SSH command to create LUNs inside each volume. To achieve I/O alignment with the operating system partitioning scheme, use `windows_2008` as the recommended LUN type. ``` lun create -path /vol// -size -ostype windows_2008 -space-allocation enabled ``` 1. Use the following SSH command to map the `igroup` to the LUNs that you just created: ``` lun show lun map -path -igroup ``` 1. Get the iSCSI endpoint IP addresses (preferred subnet and standby subnet) from the FSx for ONTAP console. Choose your SVM on the Storage Virtual Machines page. The iSCSI endpoint IP addresses are used as iSCSI targets in the next step. For more information, see [Provisioning iSCSI for Windows](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/mount-iscsi-windows.html). .. On the Windows server, go to iSCSI initiator settings, and connect to your iSCSI targets (FSx for ONTAP iSCSI endpoints). Go to **Discovery** > **Discover Portal**. Enter the iSCSI IP address from previous step, and select **Advanced**. From Local Adapter, select **Microsoft iSCSI Initiator**. From Initiator IP, select **IP of the server**. .. From iSCSI Initiator Settings, select **Targets** and choose **Connect** and **Enable muti-path**. .. For best performance, add more sessions. NetApp recommends creating five iSCSI sessions. Select **Properties** > **Add session** > **Advanced**, and repeat the previous step. For further details, see [SQL Server on Amazon EC2 using Amazon FSx for NetApp ONTAP](https://docs.netapp.com/us-en/netapp-solutions/databases/sql-aws-ec2.html#introduction). 1. Initialize disks with the following PowerShell command: ``` $disks = Get-Disk | where PartitionStyle -eq raw foreach ($disk in $disks) {Initialize-Disk $disk.Number} ``` 1. Run the partition and format commands with PowerShell. ``` New-Partition -DiskNumber 1 -DriveLetter F -UseMaximumSize Format-Volume -DriveLetter F -FileSystem NTFS -AllocationUnitSize 65536 ``` LUNs can also be created using SnapCenter. You can also automate volume and LUN creation using the PowerShell script provided in the Appendix B of [SQL Server on Amazon EC2 using Amazon FSx for NetApp ONTAP](https://docs.netapp.com/us-en/netapp-solutions/databases/sql-aws-ec2.html#introduction).