Configure the guest operating systems as follows:
Note: The virtual network interface enumeration starts with ens in the Red Hat Enterprise Linux 7 guest operating system.
The following additional best practices are recommended and implemented in the Red Hat Enterprise Linux based guest operating systems running inside the two database VMs.
Note: In our test environment, we applied best practices in accordance with the information in the Dell EMC XtremIO Storage Array Host Configuration Guide. Refer to that guide for details about how to apply the best practices when using XtremIO storage in a Linux environment.
For optimal XtremIO X2 storage performance in a VMware environment, we recommend using VMware Paravirtual SCSI (PVSCSI) controllers and the PVSCSI driver in the guest VMs. We ensured that the in-box Red Hat Enterprise Linux vmw_pvscsi driver module was loaded and used in the guest operating systems.
Note: The PVSCSI driver is used only when the SCSI controller type is set to VMware Paravirtual in the VM settings.
The following table shows the default and recommended vmw_pvscsi parameter settings:
Table 34. PVSCSI parameter settings in guest operating systems
Parameter |
Default value |
Recommended value |
vmw_pvscsi.cmd_per_lun |
RHEL 7: 254 |
RHEL 7: 254 |
vmw_pvscsi.ring_pages |
RHEL 7: 8 |
RHEL 7: 32 |
The parameters and their respective recommended values in this table were appended to the kernel boot arguments in the /etc/default/grub file for the Red Hat Enterprise Linux 7 based guest operating system.
Follow these steps inside the VM to set up two virtual databases:[5]
Table 35. Recommended design of redo log groups
Redo log group number |
Thread number |
Disk group location |
Redo log file size |
1 |
1 |
+REDO1 |
5 GB |
2 |
1 |
+REDO2 |
5 GB |
3 |
1 |
+REDO1 |
5 GB |
4 |
1 |
+REDO2 |
5 GB |
5 |
2 |
+REDO1 |
5 GB |
6 |
2 |
+REDO2 |
5 GB |
7 |
2 |
+REDO1 |
5 GB |
8 |
2 |
+REDO2 |
5 GB |