LanFree HotAdd Limitations, System Requirements, Advantages and Disadvantages.
When using this Network Mode for ESXi, vRanger must be installed on a virtual machine. The recommended settings for this server are as follows:
Plan on 1 concurrent backup per CPU core. To calculate the maximum number of concurrent backup tasks per proxy server, simply identify the number of CPU cores on that server – that is the maximum number of concurrent backups. For example, a Dual-Socket, Quad-Core system will be able to perform up to 8 concurrent backup jobs
Other Hot-Add requirements:
Required vSphere Licensing Levels
vRanger relies on several vSphere APIs to provide backup and replication functionality. Those APIs are restricted by VMware to certain license editions.
Advantages:
Considerations:
Configuring vRanger VM for HotAdd
Please enable the Hot-Add setting inside the job proerties:
When using HotAdd, make sure to disable automount on the vRanger machine. This will prevent Windows on the vRanger VM from assigning a drive letter to the target VMDK. To disable automount:
Other issues to consider:
VMFS Block Size To use HotAdd, the VMFS containing the Target VM and the VMFS containing the vRanger VM must use the same or larger block size. For example, if you back up virtual disk on a datastore with 2Mb blocks, the proxy (vRanger) must also be on a datastore with 2Mb blocks or above. Its strongly recomended to install vRanger on VM which is residing on 8Mb to avoid any future problems.
With HotAdd and the vRanger VM You cannot use HotAdd to backup the vRanger virtual machine (itself). This may result in the vRanger volume being removed from the VM along with the target VMDK.
For more information, refer to VMware’s VDDK 1.2.1 Release Notes: http://www.vmware.com/support/developer/vddk/VDDK-1.2.1-Relnotes.html#knownissues
Additional Limitations:
http://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.html#knownissues
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center