Chatee ahora con Soporte
Chat con el soporte

vRanger 7.8.6 - User Guide

Introduction vRanger overview Configuring vRanger
Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore
Restoring an encrypted VMware VM 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

Creating an incremental backup job

For incremental backups, vRanger performs a full scan of the source VM, but copy only blocks that have changed since the last backup.

Incremental backups are typically the fastest backup option and consume less storage space per archive. It is important to note, however, that to restore from an incremental backup, each incremental archive between the full backup and the preferred restore point must be available. When creating incremental backup schedules, use caution to minimize the risk introduced by long incremental chains.

Restoring an incremental backup can take longer than restoring a full or differential backup, because each previous incremental archive needs to be restored as well.

Incremental backups can be modified with the following operations:

•
Active Block Mapping (ABM): ABM scans the disks on a VM and detects the blocks actively used by the disk, as opposed to blocks that were deleted by the Windows® operating system. With ABM enabled, vRanger only backs up the part of a virtual disk that has active data on it. ABM also provides the following settings options:
•
Do not include the Windows page file.
•
Do not include the Windows hibernation file.
 
* 
NOTE: In vRanger 6.1, page files and hibernation files were not backed up by default. In vRanger 7, page and hibernation files are backed up by default. If you are upgrading to vRanger 7 from version 6.1, page files are backed up unless you edit each job and explicitly select the option to skip the page file or hibernation file, or both.
 
* 
CAUTION: ABM does not back up deleted data. If a VM backed up using ABM is restored, undelete operations are not possible.
•
Changed Block Tracking (CBT): 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 durations for backup operations, and reduced resource consumption on network and storage elements.
 
* 
NOTE: CBT does copy deleted blocks if ABM is not also enabled. CBT is a VMware® feature, and does not apply to physical machine or Hyper-V® VM backup.

For more information about selecting the ABM and CBT operations, see Configuring backup options.

To create an incremental backup job:
1
On the Retention Policy Selection page, select your Savepoint Count — the default setting is 7, the maximum value is 1000.
2
In the Space Saving Technology section, select Incremental.
The Options section appears.
3
Configure your incremental options by selecting one the following:
•
Threshold Count: This option defines the number of incremental backups to perform before a full backup is done.
Use the up and down arrows to select a threshold count — the default is 6.
•
Full Backup Days: Select the day or days on which you want vRanger to take a full backup of the server.
 
* 
NOTE: To run full backups only on the selected days, the Threshold Count must be set to a value of 8 or higher. A threshold count of 7 or less causes a full backup to run seven days from the date the job is scheduled, even if that day is not a selected day.
4
Click Next.

Creating a differential backup job

For differential backups, vRanger performs a full scan of the source VM, but copies only blocks that have changed since the last Full backup.

Differential backups are typically slower than incrementals and can consume more storage space. They are faster to restore, however, and require only one differential backup and the parent full backup to restore.

Differential backups can be modified with the following operations:

•
Active Block Mapping (ABM): ABM scans the disks on a VM and detects the blocks actively used by the disk, as opposed to blocks that were deleted by the Windows® operating system. With ABM enabled, vRanger only backs up the part of a virtual disk that has active data on it. ABM also provides the following settings options:
•
Do not include the Windows page file.
•
Do not include the Windows hibernation file.
 
* 
NOTE: In vRanger 6.1, page files and hibernation files were not backed up by default. In vRanger 7, page and hibernation files are backed up by default. If you are upgrading to vRanger 7 from version 6.1, page files are backed up unless you edit each job and explicitly select the option to skip the page file or hibernation file, or both.
 
* 
CAUTION: ABM does not back up deleted data. If a VM backed up using ABM is restored, undelete operations are not possible.
•
Changed Block Tracking (CBT): 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 durations for backup operations, and reduced resource consumption on network and storage elements.
 
* 
NOTE: CBT copies deleted blocks if ABM is not also enabled. CBT is a VMware® feature, and does not apply to physical machine or Hyper-V® VM backup.

For more information about selecting the ABM and CBT operations, see Configuring backup options.

To create a differential backup job:
1
On the Retention Policy Selection page, select your Savepoint Count — the default setting is 7, the maximum value is 1000.
2
In the Space Saving Technology section, select Differential.
The Options section appears.
3
Configure your incremental options by selecting one the following:
•
Threshold Count: This option defines the number of incremental backups to perform before a full backup is done.
Use the up and down arrows to select a threshold count — the value is 6.
•
Full Backup Days: Select the day or days on which you want vRanger to take a full backup of the server.
 
* 
NOTE: To run full backups only on the selected days, the Threshold Count must be set to a value of 8 or higher. A threshold count of 7 or less causes a full backup to run seven days from the date the job is scheduled, even if that day is not a selected day.
•
The Threshold Size refers to the percentage of the hard disk of a VM that must be captured in differential backups before performing a full backup. Using the Threshold Size value might cause your full backups to be taken on unexpected days.
 
* 
NOTE: The Threshold Size setting is still applied if one or more Full Backup Days are set. To prevent the Threshold Size setting from triggering an unwanted full backup, set the Threshold Size to 100 or higher.
4
Click Next.

Setting the recurrence schedule

The Recurrence Schedule Selection page lets you indicate whether the job should be done on demand — at this moment — or at a future time. To schedule a future occurrence, you must define the start time, recurrence pattern, and range of recurrence.

 
* 
NOTE: When using the Full Backup Days option, ensure that the selected recurrence schedule causes backup tasks to run on the configured Full Backup Days.
To set the recurrence schedule:
1
On the Recurrence Schedule Selection page, select from the options described in the following table.
 
 

This will be an on demand job …

There is no need to define a schedule. The job runs on demand.

Start Time

The time of day at which to run the job.

Recurrence Pattern

In this section, you establish how often the report should be generated. There are five options within this section:

•
Daily: The daily option can be scheduled to run the report every weekday or every x number of days.
•
Weekly: vRanger can be configured to run on weekly intervals, from every week to every 99 weeks. The day of the week on which to run reports can be configured.
•
Monthly: The monthly option offers the following configurations:
•
Day [x] of every [y] month:
x can be any value from 1 to 31. This value determines the day of the month on which the job occurs.
y can be any value from 1 to 99. This value determines the monthly interval — for example, every two months sets the job to run every other month.
•
The [f] [d] of every [y] month(s):
f can be either: first, second, third, fourth or last.
d can be: weekday, weekend day, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
y can be any value from 1 to 99. This value determines the monthly interval — for example, every two months sets the report to run every other month.
•
Yearly: The yearly option offers the following configurations:
•
Every [m] [x]:
m is any month of the year. This value determines the month of the year in which the report occurs.
x can be any value from 1 to 31. This value determines the day of the month on which the report occurs.
•
The [f] [d] of [m]:
f can be either: first, second, third, fourth, or last.
d can be: day, weekday, weekend day, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
m is any month of the year. This value determines the month of the year in which the report occurs.
•
Interval: The interval option lets you select the number of days, hours, and minutes that should pass between backup jobs.
NOTE: The interval selected must be greater than or equal to five minutes.

Range of Recurrence

Select the starting date and ending date:

•
No end date: The job recurs until it is stopped.
•
End after: Select the number of occurrences.
•
End by: Select the date by which to end the recurrence.
2
Click Next.

Configuring email notifications

The Email Notification Selection page lets you select the email addresses to which notifications should be sent for this job. You can also request that a report be sent to the recipients identified after the job is complete.

To add or edit email addresses, see Setting up the SMTP server.

To configure email notifications:
1
On the Email Notification Selection page, in the Selected column, select the address to which notifications should be sent.
 
* 
TIP: To select all email addresses, select the check box in the Selected column header.
2
Click Next.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación