Setting boot device on VM’s when recovering into SCVMM
Viewed 649 times
To workaround this issue, Zerto has created a method by which the first boot device can be statically assigned when recovering to an SCVMM environment.
**The workaround is applicable only to environments running Zerto 5.0 and above and will not work with any version prior to 5.0 **
To implement this, perform the following actions:
- In the machine running the Zerto Virtual Manager on the SCVMM site, open the file located in "C:Program FilesZertoZerto Virtual Replicationtweaks.txt". (Note: If you installed Zerto in a different drive from "C:", please navigate to the appropriate disk drive/installation directory).
- Note: if the machine has 'Admin Approval Mode' enabled, you may need to open Notepad or your text editor as an administrator to be able to save the file after making changes
- In the file, add a new line below any existing content, and add one or all of the following entries. Tweaks including "Gen2" in the String are for Generation 2 VMs, while ones without are for Generation 1 VMs. Windows and Non Windows Operating Systems have their own tweaks.
- t_firstBootDeviceWindowsVMs = "SCSI,0,0"
- t_firstBootDeviceNonWindowsVMs = "SCSI,0,0"
- t_firstBootDeviceGen2WindowsVMs = "SCSI,0,0"
- t_firstBootDeviceGen2NonWindowsVMs = "SCSI,0,0"
- Save the file
- Perform the recovery operation
Note: You do not need to restart the Zerto Virtual Manager service for this change to take effect.
Additionally: the first boot device string can be changed, but the string should match one of the following formats: "SCSI,BusId(integer),LunId(integer)" or "NIC,SlotId(integer)" (e.g. "SCSI,0,0" or "NIC,0". Any changes made to this value will affect ALL VMs recovered to this environment which match the OS filter named in the tweak.