Read the following notes regarding limitations and considerations about installing vRanger in a VM:
Installing vRanger on a physical server provides a method to off-load backup resource consumption from the VMware® ESXi™ host and network. While you can perform Machine-based LAN in this configuration, LAN-free backups are the primary driver for using vRanger in a physical server. For more information, see LAN-free backups (VM backups only) and LAN backups.
The transports available when vRanger is installed in a physical machine include the following:
• |
VA-based HotAdd: This transport mounts the source VM’s disk to the vRanger VA deployed on the source host or cluster. This method allows vRanger — through the VA — to have direct access to the VM data through the VMware® I/O stack rather than the network. In this configuration, data is sent directly from the VA to the repository. |
• |
Machine-based SAN: This transport option uses your fibre-channel infrastructure or iSCSI network to transport backup data to the vRanger machine. |
With vRanger installed on a physical server, the following configurations must be made:
• |
Run the automount scrub command to clean any registry entries pertaining to previously mounted volumes. |
• |
Only one vRanger server should see a set of VMFS LUNs at one time. For backups only, The vRanger server should have only read-only access to the LUNs. To perform LAN-free restores, ensure that the vRanger server has Read + Write access to any zoned VMFS LUNs to which you want to restore. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center