Working Reports pane
Backup overview
Virtual machine (VM) backup
vRanger protects two varieties of VMs:
•
•For more information on the different types of virtual backups, see the following topics:
Protecting VMware VMs
When protecting a VMware® virtual environment, vRanger uses VMware snapshot technology to store incoming write requests temporarily while the source VMs are being backed up. After a VMware backup completes, the snapshot is deleted, which commits those pending writes to disk. vRanger can back up a VMware VM that already has an open snapshot and can back up the open snapshot, but any secondary consolidated helper snapshots are closed prior to running the backup.
With Inventory Node Selection, you can browse the VMware® vCenter™ or VMware® vCloud Director® inventory and select which VMs, groups, or VMware vSphere® vApp(s)™ you want to protect. You can select a VM, folder, resource pool, vApps, VMware® ESXi™ host, data center, or vCenter, and back up all the VMs located under that node in the tree.
VMware Virtual Volumes and Storage Policies
Protecting VMware vApps
VMware vSphere® vApp(s)™ are containers — similar to a resource pool — that help you manage and control resources for the VMs contained within. vApps are used to group the individual components of a multi-tier application properly, allowing for application-level resource control and portability. When protecting vApps, vRanger backs up both the VMs and the vApp metadata to maintain the vApp settings and structure upon restore.
Protecting encrypted VMs
•Protecting Hyper-V VMs
When protecting a Hyper-V® host, the vRanger Hyper-V Agent is installed on the host. The vRanger Hyper-V Agent works with the VSS writer present on all Hyper-V hosts to back up every VM on the host and send the backups directly to the repository. If the host is on the same network as the repository location, such as a SAN, the client can perform LAN-free backups.
Incremental and differential backups with Resilient Change Tracking
Physical machine backup
For backing up physical machines, vRanger uses a physical backup client, similar to the one used for protecting Hyper-V® VMs, to perform backup and communication operations. The client can be installed when the source server is added to the vRanger inventory, or installed manually to comply with change control requirements.
After it is installed, the physical client does the following:
IMPORTANT: Physical backups are only supported on Windows® machines matching the list of supported operating systems. For more information, see the Quest vRanger Installation/Upgrade Guide.
Reviewing backup transport options
vRanger offers different data transport options for backup tasks.
VMware backup transport options
•
•
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center