vRanger 7.8.5 - User Guide

Application consistency for physical backups

vRanger can provide two levels of consistency for physical backups: crash consistent and application consistency.

For physical backups, vRanger also supports — through VSS — the truncation of any supported application transaction logs when the VSS snapshot is creating. Log truncation automatically frees space in the logical log for reuse by the transaction log.

Understanding retention policies and space-saving technologies

vRanger retention policies define the minimum number of restorable savepoints to keep in a repository for a backup job. The number of savepoints retained depends on the type of backups being performed — full, differential, or incremental — and where in the full-differential or full-incremental cycle the retention check is being performed.

NOTE: vRanger does not retire an expired savepoint if that savepoint is required to restore a differential or incremental savepoint still within the retention period.

A key concept in discussing retention policies is the notion of a “backup set.” A backup set is several savepoints that are grouped for two reasons: The first is to implement the retention policy; and the second is to maintain the parent-child relationships that exist when you choose to use differential or incremental backups. The backup set for each type of backup is different.

A backup job consisting only of full backups is the simplest case for retention policy configuration. Each savepoint is independent of the other savepoints, and can be retired without affecting any other savepoints. In other words, a backup set for full backups is equal to one savepoint — only one savepoint is required for a restore.

The following scenario depicts a daily full backup job, with a Savepoint Count of 7:

Incremental backup jobs back up only the blocks that have changed since the last backup — whether it was full or incremental. Restoring an incremental savepoint requires the parent full and every incremental between the full and the selected incremental.

The following scenario depicts a daily incremental backup job, with a Savepoint Count of 7 and a Threshold Count of 6:

Differential savepoints require the parent full backup and the selected differential savepoint to restore. Each differential backup includes the contents of the previous differential, which means, in terms of retention, that only the parent full and the most recent differential are required for a restore.

The following scenario depicts a daily differential backup job, with a Savepoint Count of 7, a Threshold Count of 6, and a Threshold Size of 50%:

Performing optional configurations

Before you set up a backup job, you may want to make the following optional vRanger configurations:

Enabling VMware Changed Block Tracking (CBT)

VMware® CBT reduces the time needed for incremental and differential backups by only backing up the portions of a disk that have changed since the last backup. By determining which blocks changed within the VMDK file, vRanger only backs up the portions of a disk that have changed since the last backup. This often results in shorter backup operations, and reduced resource consumption on network and storage elements.

VMware vSphere® supports CBT, and most VMs running in this environment can use it. The VMs must be Hardware Version 7 or later, and have been created and hosted in VMware® ESXi™ 6.0 or later hosts. VMs that are created in VMware® ESX® 4 or earlier must be migrated to Hardware Version 7 or later for CBT to be supported. CBT must be enabled for each VM with which CBT is to be used.

NOTE: VMs that have not yet been powered on cannot have CBT enabled. You must have powered on the VM for the CBT option to be available.

Change Block Tracking is enabled or disabled on a per-VM basis. There are two methods to enable CBT:

NOTE: This option is enabled by default. If you are upgrading a previous version of vRanger, existing jobs will use their current settings.

•	In the My Inventory view, right-click the VM for which want to change the CBT setting, and then select Enable Change Tracking. The Changed Block Tracking Icon appears next to any VM on which CBT is enabled.