vRanger 7.8.3 - User Guide

HotAdd

HotAdd

vRanger includes support for the VMware® HotAdd disk transport functionality, which permits LAN-free backups from a VM.

vRanger can use HotAdd for two backup methods:

•	VA-based HotAdd: Mounts the source VM’s disk to the vRanger virtual appliance (VA) deployed on the source host or cluster. This method lets vRanger have direct access to the VM data through the VMware I/O stack rather than the network.

•

Machine based HotAdd: If vRanger is installed in a VM, this method mounts the source VM’s disk to the vRanger VM. This method lets vRanger have direct access to the VM data through the VMware I/O stack rather than the network. With this method, the backup processing activity occurs on the vRanger server.

To use vRanger with HotAdd, the VM — either the vRanger VA or the vRanger VM — must be able to access the target VM’s datastores. In addition, all hosts to which the vRanger VM or VA could be vMotioned using VMware vSphere® vMotion® must be able to see the storage for all VMs that vRanger is configured to back up.

 

NOTE: When using HotAdd, plan on one 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 can perform up to eight concurrent backup jobs.

Configuring vRanger for HotAdd

When using HotAdd, make sure to disable Automount on the vRanger machine. This step prevents Windows® on the vRanger VM from assigning a drive letter to the target VMDK.

To disable Automount:

1	Click Start > Run, and enter diskpart.

2	Run the automount disable command to disable automatic drive letter assignment.

3	Run the automount scrub command to clean any registry entries pertaining to previously mounted volumes.

HotAdd limitations

The use of HotAdd for backups is subject to the following limitations:

•

VMFS Block Size: To use HotAdd, the VMFS containing the source VM and the VMFS containing the vRanger VM must use the same block size. For example, if you back up a virtual disk on a datastore with 1 MB blocks, the proxy must also be on a datastore with 1 MB blocks. For more information, see the VMware® VDDK 1.2.1 Release Notes at http://www.vmware.com/support/developer/vddk/VDDK-1.2.1-Relnotes.html#knownissues.

•

HotAdd and the vRanger VM: You cannot use HotAdd to back up the vRanger VM. This issue might result in the vRanger volume being removed from the VM along with the source VMDK. For more information, see the VMware VDDK 1.2.1 Release Notes at http://www.vmware.com/support/developer/vddk/VDDK-1.2.1-Relnotes.html#knownissues.

•	IDE disks are not supported.

•	Mixed mode clusters are not supported for HotAdd. For example, a VM on a VMware® ESXi™ 6.0 host cannot HotAdd a disk from an ESXi 5.1 host.

SAN backups

SAN backups

To perform SAN backups, vRanger must be installed on a physical system attached to your fibre or iSCSI network. In addition, the volumes containing the servers to protect must also be properly zoned and mapped to the vRanger proxy server.

Configuring vRanger for SAN backups

With vRanger installed on a physical proxy server, the following configurations must be made:

•	Disable automount on the vRanger machine:

Click Start > Run, and then enter diskpart.

Run the automount disable command to disable automatic drive letter assignment.

•	Verify that the SAN policy is set to Online All by typing san and hitting Enter.

If it is not, set it to online all by typing san policy=onlineAll.

•	Run the automount scrub command to clean any registry entries pertaining to previously mounted volumes.

•	On your storage device, zone your LUNs so that the vRanger HBA or iSCSI initiator can see and read them.

•	Only one proxy should see a set of LUNs at one time. For backups only, The proxy server should only have read-only access to the LUNs. To perform LAN-free restores, ensure that the vRanger server has Read + Write access to any zoned LUNs to which you want to restore.

LAN

LAN

If no LAN-free option is available, backups can be processed over the network. LAN backups are supported in all configurations and require no additional set-up to work, but are generally the slowest option. Network backups can be processed one of two ways, depending on the source host configuration.

•	VA-based LAN: Transfers the source VM’s data from the source disk to the vRanger virtual appliance (VA) over the network. With this method, the backup processing activity occurs on the VA.

•

Machine-based LAN: If there is no vRanger VA deployed, vRanger transfers the source VM’s data from the source disk to the vRanger server over the network. With this method, the backup processing activity occurs on the vRanger server. For VMware® ESXi™ servers, data is sent by way of the VMware VDDK transport.

 

NOTE: Generally speaking, network backups and restores are slower than LAN-free backups and restores. If your environment supports LAN-free backups, use that option whenever possible.

Transport selection order: VM backup

Transport selection order: VM backup

When backing up VMs or other virtual objects — hosts, clusters, and so on — the vRanger Backup Wizard includes an Automatic option which lets vRanger select the best available method for your configuration. When determining the best transport, vRanger uses two key criteria:

•	Whether VAs are deployed.

•	Where vRanger is installed.

The logic used to select a transport differs slightly based on whether vRanger is installed in a VM or on a physical server. The following topics describe the steps taken to select an automatic transport.

•	vRanger: installed on a VM

•	vRanger: installed on a physical machine