If you decided to go with disk mirroring inside your guest operating system across two SAN LUNs for whatever reason (e.g. you want to bring another level of the protection for your application and your SAN environment does not support “stretch cluster” implementation, no support for synchronous mirroring, budget constrains etc.).
There are special configuration parameters which you should add into your virtual machine configuration file (*.vmx) to have your setup working correctly and fault tolerant (from storage perspective).
It will work even without applying them, however in case of a failure of the one storage device you won’t have desired behavior (Your failed disk will be running in memory, so VM will be somehow “frozen”).
Note: source vSphere Storage Guide. I would say the same applies for mirroring inside Linux VMs as well.
Use a Windows virtual machine that supports dynamic disks.
Required privilege: Advanced
- Create a virtual machine with two virtual disks. Make sure to place the disks on different datastores/arrays.
- Log in to your virtual machine and configure the disks as dynamic mirrored disks. See Microsoft documentation.
- After the disks synchronize, power off the virtual machine.
- Change virtual machine settings to allow the use of dynamic disk mirroring.
a. Right-click the virtual machine and select Edit Settings.
b. Click the VM Options tab and expand the Advanced menu.
c. Click Edit Configuration next to Configuration Parameters.
d. Click Add Row and add the following parameters:
Name Value scsi#.returnNoConnectDuringAPD
True scsi#.returnBusyOnNoConnectStatus False
- Click OK.
Latest posts by Dusan Tekeljak (see all)
- Enabling agentless Guest (VM) RAM monitoring with vRealize Operations 6.3+ - February 14, 2017
- Just Another ESXi 6.0 Storage APD Handling Bug - November 15, 2016
- Broadwell ESXi 6.0 Exception 14 PSOD and Lenovo support fail - August 30, 2016