지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Application consistency for Hyper-V VMs

Previous Next



Application consistency for Hyper-V VMs

vRanger can provide two levels of consistency for Hyper-V® VM backups: file-system consistency and application consistency.

Crash consistent: A crash-consistent backup is analogous to pulling the plug on a server and then backing up the data. The state of the data that is being backed up with respect to the users of the data is indeterminate. Restoring a crash-consistent image is equivalent to rebooting a server after a hard shut-down.
Application consistent: vRanger engages the Microsoft Volume Shadow Copy Services (VSS) to put supported applications into a consistent state during a backup. This option ensures that all application writes requests in the machines memory are committed to disk before the snapshot is taken, which means that the application and data can be reliably recovered from the backup archive.

To achieve either type of application consistency, you must comply with the following requirements:

The vRanger agent installed on the Hyper-V host uses the VSS native to the Windows operating system to support the truncation of any supported application transaction logs. Log truncation automatically frees space in the logical log for the transaction log to reuse.

Application consistency for physical backups

Previous Next


Backup > Determining application consistency > Application consistency for physical backups

Application consistency for physical backups

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

File-system consistent: File-system consistency is achieved without any additional tools or configurations. File-system consistency ensures that no file system writes were lost during the backup process.
Application consistent: vRanger engages the Microsoft VSS to put supported applications into a consistent state during a backup. This option ensures that all application writes requests in the machines memory are committed to disk before the snapshot is taken, which means that the application and data can be reliably recovered from the backup archive.

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

Previous Next


Backup > Understanding retention policies and space-saving technologies

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.

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.

Full backups: Each savepoint is a complete backup set. Deleting a savepoint has no bearing on the recoverability of any other full savepoint.
Incremental backups: Incremental backup jobs backup only the blocks that have changed since the last backup — full or incremental. Restoring an incremental savepoint requires the parent full and every incremental between the full and the selected incremental.
Differential backups: A differential backup contains the data that has changed since the last full backup. Each differential backup includes the contents of the previous differential, which in retention terms means that only the parent full and the most recent differential are required for a restore.
Full backups

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:

Day 1: A full backup is taken.
Day 2: A full backup is taken.
Day 3: A full backup is taken.
Day 4: A full backup is taken.
Day 5: A full backup is taken.
Day 6: A full backup is taken.
Day 7: A full backup is taken.
Day 8: A full backup is taken. The savepoint from Day 1 is removed.
Day 9: A full backup is taken. The savepoint from Day 2 is removed.
Incremental backups

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:

Table 2. Incremental backup retention example

Day

Action

1

A full backup is taken.

2

An incremental backup is taken.

3

An incremental backup is taken.

4

An incremental backup is taken.

5

An incremental backup is taken.

6

An incremental backup is taken.

7

An incremental backup is taken.

8

A full backup is taken.

9

An incremental backup is taken.

10

An incremental backup is taken.

11

An incremental backup is taken.

12

An incremental backup is taken.

13

An incremental backup is taken.

14

An incremental backup is taken. All savepoints from Day 1 to Day 7 are removed.

15

A full backup is taken.

Differential backups

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%:

Table 3. Differential backup retention example

Day

Action

1

A full backup is taken.

2

A differential backup is taken.

3

A differential backup is taken.

4

A differential backup is taken.

5

A differential backup is taken.

6

A differential backup is taken.

7

A differential backup is taken.

8

A full backup is taken. The differential savepoint from Day 2 is removed.

9

A differential backup is taken. The differential savepoint from Day 3 is removed.

10

A differential backup is taken. The differential savepoint from Day 4 is removed.

11

A differential backup is taken. The differential savepoint from Day 5 is removed.

12

A differential backup is taken. The differential savepoint from Day 6 is removed.

13

A differential backup is taken.

14

A differential backup is taken. The differential savepoint from Day 7 and the full savepoint from Day 1 are removed.

Performing optional configurations

Previous Next


Backup > Performing optional configurations

Performing optional configurations

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

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택