1 |
VA on source host: vRanger first checks the source host for a VA. If available, that VA is used. |
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. |
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. |
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. |
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. |
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.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center