PVS clients always failover to server side cache during boot when the vDisk mode is set to Cache in device RAM with overflow on hard disk.
1. In a PVS target device booting in private vDisk mode or maintenance vDisk version, open a command prompt with administrator privileges.
2. Run the diskpart utility, using the following command:
3. To verify the SAN policy, run the command:
The SAN policy should be Online All for PVS target devices to function correctly in while in Cache in Device RAM with Overflow on Hard Disk mode.
4. To change the SAN policy, run the command:
5. Shutdown the PVS target device and change the vDisk mode to standard image or promote the maintenance version to test or production version.
When creating a machine template, ensure that it has a similar hard disk drive structure and that it can boot from a vDisk in Private Image mode. For example:
- To PXE boot a VM with write cache, create a VM with 1 hard disk drive.
- To use Boot Device Manager (BDM) to boot a VM with write cache, create a VM with 2 hard disk drives.
- To use BDM to boot a VM that uses a personal vDisk and write cache, create a VM with 3 hard disk drives.