Chat now with support
Chat with Support

vRanger 7.8 - User Guide

Introduction Configuring vRanger
Configuration overview Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore Replicate VMs Reports Integrating and monitoring vRanger Using the vRanger Console vAPI Cmdlet details
Add-BackupGroupEntity Add-BackupJobTemplate Add-CIFSRepository Add-DdbReplicationRepository Add-DdbRepository Add-EsxHost Add-HypervCluster Add-HypervHost Add-HypervRestoreJobTemplate Add-NFSRepository Add-NVSDRepository Add-PhysicalMachine Add-RdaRepository Add-ReplicationJobTemplate Add-RestoreFromManifestJobTemplate Add-RestoreJobTemplate Add-VirtualAppforLinuxFLR Add-VirtualAppforLinuxFLRVA Add-VirtualCenter Disable-Job Dismount-LinuxVolume Enable-Job Get-AddressBook Get-BackupGroupEntity Get-CatalogSearchData Get-CatalogStatus Get-ConfigOption Get-Connection Get-CurrentTemplateVersionID Get-Datastore Get-GlobalTransportFailover Get-InventoryEntity Get-IsInventoryRefreshing Get-Job Get-JobTemplate Get-MonitorLog Get-Network Get-PhysicalMachineDiskMap Get-Repository Get-RepositoryJob Get-RepositorySavePoint Get-RestoreDiskMap Get-SavepointDisk Get-SavepointManifest Get-Savepoints Get-TransportFailover Get-VirtualApplianceConfig Get-VirtualApplianceDeploymentStatus Get-VirtualApplianceReconfigStatus Get-VirtualMachinesUnderInventory Get-VmDisk Get-VMDKVolume Install-VirtualAppliance Mount-LinuxVolume New-BackupFlag New-BackupGroupMember New-Daily Schedule New-EmailAddress New-IntervalSchedule New-MonthlySchedule New-ReplicationFlag New-RestoreFlag New-SMTPServer New-TransportConfiguration New-VirtualAppliance New-WeeklySchedule New-YearlySchedule Remove-AllMount Remove-BackupGroupEntity Remove-BackupGroupMember Remove-Catalog Remove-DdbStorageUnit Remove-JobTemplate Remove-LinuxVolume Remove-Repository Remove-SavePoint Remove-VirtualAppliance Remove-VirtualApplianceConfiguration Run-JobsNow Run-ReplicationFailover Run-ResumeReplicationFailover Run-TestReplicationFailover Set-Cataloging Set-CBTonVM Set-LinuxVolume Set-MountPath Set-Resources Stop-vRangerJob Update-BackupJobTemplate Update-GlobalTransportFailover Update-HypervRestoreJobTemplate Update-Inventory Update-ReplicationJobTemplate Update-RestoreJobTemplate Update-VirtualAppliance Update-VirtualApplianceConfiguration
About us

VMware backup transport options

Previous Next


Backup > Reviewing backup transport options > VMware backup transport options

vRanger includes support for the VMware® HotAdd disk transport functionality, which permits LAN-free backups from a VM.
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.
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 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.
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.
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.
Click Start > Run, and then 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 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.
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.

Transport selection order: VM backup

Previous Next


Backup > Reviewing backup transport options > 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:
1
VA on source host: vRanger first checks the source host for a VA. If available, that VA is used.
Is VA-based HotAdd available?: vRanger checks the local VA for HotAdd support. If the host is not properly licensed, or the VA cannot access the storage for the source VM, HotAdd is not available.
2
VA on source cluster: If the source host does not have a VA, vRanger determines whether the host is a member of a cluster, If so, vRanger checks for a shared VA on that cluster.
Is VA-based HotAdd available?: vRanger checks the cluster VA for HotAdd support. If the host is not properly licensed, or the VA cannot access the storage for the source VM, HotAdd is not available.
3
Machine-based HotAdd: If there is no VA configured, vRanger determines whether HotAdd is available for the vRanger VM. If the vRanger VM is on a host which is not properly licensed, or if the VM cannot access the storage for the source VM, HotAdd is not available.
4
Machine-based LAN: If a VA is not available, and HotAdd is not supported on the vRanger VM, a network backup is performed from the vRanger machine.
1
VA on source host: vRanger first checks the source host for a VA. If available, that VA is used.
Is HotAdd available?: vRanger checks the local VA for HotAdd support. If the host is not properly licensed, or the VA cannot access the storage for the source VM, HotAdd is not available.
2
VA on source cluster: If the source host does not have a VA, vRanger determines whether the host is a member of a cluster, If so, vRanger checks for a shared VA on that cluster.
Is HotAdd available?: vRanger checks the cluster VA for HotAdd support. If the host is not properly licensed, or the VA cannot access the storage for the source VM, HotAdd is not available.
3
Machine-based SAN: If there is no VA configured, vRanger determines whether the vRanger server is configured for SAN backups.
4
Machine-based LAN: If a VA is not available, and SAN backups are not supported on the vRanger server, a network backup is performed from the vRanger machine.

Hyper-V backup transport options

Previous Next


Backup > Reviewing backup transport options > Hyper-V backup transport options

When backing up Hyper-V® VMs, backup activity is processed by the vRanger Hyper-V Agent on the Hyper-V host. Backup data is read by the agent and sent from the source server directly to the repository.

Physical backup transport options

Previous Next


Backup > Reviewing backup transport options > Physical backup transport options

Related Documents