vRanger 7.8 - User Guide

Backup overview

Backup

vRanger offers two types of backups: virtual and physical. Each type is described in the following topics. Where information relates to only one type of backup, that restriction is noted in the topic title or as a note in the text.

•	Virtual machine (VM) backup

•	Physical machine backup

Virtual machine (VM) backup

vRanger protects two varieties of VMs:

•

VMware

•

Hyper-V

For more information on the different types of virtual backups, see the following topics:

•	Protecting VMware VMs

•	Protecting Hyper-V VMs

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

When you protect a VMware environment, vRanger records data regarding the setup. This data includes whether the VM resides on a DRS-enabled cluster, if there are storage policies involved, and the datastore configuration — network-attached storage (NAS), storage-area network (SAN), VMware Virtual Machine File System (VMFS), or Virtual Volumes (VVols). When you perform a restore or replication, vRanger uses the default settings from the original configuration but provides the option of changing these settings. For example, you can restore a backup from a non-VVol datastore to a VVol datastore, or you can restore a backup from a datastore that is governed by one storage policy to a datastore that is governed by a different policy, or no policy.

 

IMPORTANT: vRanger cannot back up physical raw device map (RDM) partitions. You should see the warning: Incompatible drive detected.

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

VMware vSphere version 6.5 introduced the ability to encrypt virtual machines, including disks and most VM files. Starting with vRanger 7.8, backup, replication, and restore of encrypted virtual machines is supported. In order to properly protect encrypted virtual machines, the following conditions must be met:

•	Virtual machine encryption must be properly configured and deployed in your virtual environment.

•	When using vRanger with machine based HotAdd to backup encrypted VMs, the vRanger VM must also be encrypted. When using vRanger with VA-based HotAdd to backup and replicate encrypted VMs, the VA must also be encrypted.

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.

 

IMPORTANT: Backing up a Hyper-V VM using a VSS writer requires a minimum of 300 MB free space on the volume being backed up. If there is less than 300 MB of available space on the volume, the backup job fails with an error message.

Incremental and differential backups with Resilient Change Tracking

Hyper-V 2016 introduces Resilient Change Tracking (RCT), a native utility that provides change tracking for Hyper-V virtual machines. RCT maintains a record of block changes over time, enabling vRanger to quickly identify blocks changed since the last backup (for differentials, since the last full backup) and eliminating the need to scan the disk to identify changes.

NOTE: Resilient Change Tracking is enabled by default on Windows Server 2016 and requires no additional configuration in vRanger. Incremental backup jobs for Windows Server 2016 Hyper-V will use RCT by default.

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:

•	Communicates with the vRanger server.

•	Gathers information on the source server configuration.

•	Manages and runs the vRanger backup tools and operations.

•	Manages vRanger VSS snapshot activity on the source server.

•	Transmits backup data directly to the repository.

vRanger physical backups are performed using the direct-to-target architecture. Depending on how the source server is connected to the repository, this process can result in network backups or LAN-free backups. For backups to be LAN-free, the source server and repository must exist on the same SAN.

 

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.

 

NOTE: The backup transport method describes only how data is read from the source server, not how the data is sent to the repository.

•	VMware backup transport options

•	Hyper-V backup transport options

•	Physical backup transport options

•	Transport selection order: VM backup