Chatta subito con l'assistenza
Chat con il supporto

vRanger 7.8 - Installation/Upgrade Guide

Introduction Before you install System requirements and compatibility Installing vRanger Upgrading vRanger

Installing the vRanger server

Previous Next


Before you install > Installing the vRanger server

vRanger can be installed either on a physical server or in a VM. As long as the vRanger machine meets the specifications detailed in System requirements and compatibility, application performance should be similar regardless of which option is chosen.
Virtual machine (VM): When installing vRanger in a VM, you eliminate the need for dedicated hardware while maintaining high performance. Due to the lower cost and increased flexibility, this approach is recommended. For information on installing in a VM, see Installing vRanger in a virtual machine (VM).
Physical machine: The primary benefit of installing vRanger on a physical server is that the resource consumption of backup activity is off-loaded from the virtual environment to the physical proxy. For more information on installing on a physical server, see Installing vRanger on a physical server.

Available backup transports

Previous Next


Before you install > Installing the vRanger server > Available backup transports

VA-based HotAdd: Mounts the source VM’s disk to the vRanger VA deployed on the source host or cluster. This method allows vRanger to 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 allows vRanger to 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.
VA-based LAN: Transfers the source VM’s data from the source disk to the vRanger VA over the network. With this method, the backup processing activity occurs on the vRanger 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 machine over the network. With this method, the backup processing activity occurs on the vRanger server.
Machine-based SAN: If there is no VA configured, vRanger determines whether the vRanger server is configured for SAN backups. This method is a high performance configuration that requires vRanger to be connected to your fibre or iSCSI network. In addition, the VMFS volumes containing the VMs to be protected must also be properly zoned and mapped to the vRanger server.

Installing vRanger in a virtual machine (VM)

Previous Next


Before you install > Installing the vRanger server > Installing vRanger in a virtual machine (VM)

When vRanger is installed in a VM, you can perform backups and restores either over the network or in a LAN-free mode which uses the SCSI HotAdd functionality on VMware® ESXi™. The following topics provide a summary of each method. Replication and physical backup tasks are always performed over the network.
You must use a version of VMware vSphere® that supports VMware vSphere Storage APIs - Data Protection (formerly known as vStorage APIs for Data Protection or VADP).
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.
1
Click Start > Run, and then enter diskpart.
If it is not, set it to online all by typing san policy=onlineAll.
VA-based LAN: This option transfers the source VM’s data from the source disk to the vRanger VA over the network using the VMware® VDDK LAN transport. The backup processing activity occurs on the vRanger VA, and then the data is sent to the repository directly.
Machine-based LAN: If there is no vRanger VA deployed, vRanger transfers the source VM’s data from the source disk to the vRanger VM over the network. With this method, the backup processing activity occurs on the vRanger server. The backup data flows “direct to target” from the source server to the target repository, which means that the vRanger server does not process the backup traffic.
In recent versions of Windows®, volumes are recognized by a serial number assigned by Windows. When VMs are cloned, the serial number for each VM volume is cloned as well. During normal operations, this cloning is not an issue; however, when vRanger is cloned from the same source or template as a VM being backed up, the vRanger volume has the same serial number as the source volume.

Installing vRanger on a physical server

Previous Next


Before you install > Installing the vRanger server > Installing vRanger on a physical server

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.
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.
Click Start > All Programs, and enter diskpart.
Run the automount disable command to disable automatic drive letter assignment.
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.
VA-based LAN: This option transfers the source VM’s data from the source disk to the vRanger VA over the network using the VMware® VDDK LAN transport. The backup processing activity occurs on the vRanger VA, and then the data is sent to the repository directly.
Machine-based LAN: If there is no vRanger VA deployed, vRanger transfers the source VM’s data from the source disk to the vRanger machine over the network. With this method, the backup processing activity occurs on the vRanger server. The backup data flows “direct to target” from the source server to the target repository, which means that the vRanger server does not process the backup traffic.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione