Chat now with support
Chat with Support

vRanger 7.6.3 - User Guide

Introduction Configuring vRanger
Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore
Restoring a physical server Performing a full restore for VMware VMs Performing a full restore for Hyper-V® VMs Performing a full restore for VMware vApps Performing a full restore of a physical machine Performing an FLR on Windows Performing an FLR on Linux Restoring from manifest
Replicate VMs Reports Integrating and monitoring vRanger Using the vRanger Console vAPI Cmdlet details
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-InventoryEntities 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

Transport selection order: VM backup

Previous Next


Backup > Reviewing backup transport options > 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

vRanger: installed on a VM

Previous Next


Backup > Reviewing backup transport options > Transport selection order: VM backup > vRanger: installed on a VM

vRanger: installed on a VM

When installed on a VM, vRanger checks the possible transports in the following order, selecting the first option available to ensure the best performance possible.

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.

 
* 
IMPORTANT: If a VA is configured and HotAdd is not available, a network backup is performed from the VA. No further transport checks are performed.
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.

 
* 
IMPORTANT: If a VA is configured and HotAdd is not available, a network backup is performed from the VA. No further transport checks are performed.
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.

vRanger: installed on a physical machine

Previous Next


Backup > Reviewing backup transport options > Transport selection order: VM backup > vRanger: installed on a physical machine

vRanger: installed on a physical machine

When installed on a physical machine, vRanger checks the possible transports in the following order, selecting the first option available. The preferred transports are checked first, ensuring the best performance possible.

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.

 
* 
IMPORTANT: If a VA is configured and HotAdd is not available, a network backup is performed from the VA. No further transport checks are performed.
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.

 
* 
IMPORTANT: If a VA is configured and HotAdd is not available, a network backup is performed from the VA. No further transport checks are performed.
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

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.

When performing backups of Hyper-V VMs, or backup groups containing Hyper-V VMs, the Transport Selection portion of the Backup Wizard is not shown, as there is only one available option.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating