Tchater maintenant avec le support
Tchattez avec un ingénieur du support

vRanger 7.7.1 - 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

Setting the recurrence schedule

Previous Next


Backup > Configuring a backup job > Setting the recurrence schedule

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.

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.

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

Previous Next


Backup > Configuring a backup job > Configuring email notifications

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.
2
Click Next.

Starting the backup job

Previous Next


Backup > Configuring a backup job > Starting the backup job

Starting the backup job

The final page in the Backup Wizard displays a summary of the selections you made for the job.

To start the backup job:
1
On the Summary page, review the data displayed in the tree view.
3
Click Finish.
c
In the Confirm Run Job dialog box, click Yes.
5
To check progress or confirm completion, click My Jobs, and then click Recent Jobs.

 

Restore

Previous Next



The vRanger restore process

vRanger offers three main options for restoring from backup: restoring the full server from a repository, restoring a file or files from a repository, or restoring the server or file from a manifest. For more information, see the following topics:

If you are restoring a VMware® VM, be aware of the following regarding the destination that you target for a restore:

Full restore

Using vRanger, recovery of an entire virtual machine (VM) — or resource pool, VMware vSphere® vApp(s)™, and so on — is a simple process. A full restore returns the protected objects to the state as of the point in time at which the backup was performed. If the savepoint is for a differential backup, the restore process first restores the matched full backup, and then merges the data from the selected differential archive. For incremental savepoints, the full backup is restored along with each incremental archive taken between the full and the selected savepoint.

When restoring a parent object, such as a vApp, vRanger restores the VM data and the parent object’s metadata, allowing you to restore the entire object state and settings and the actual VM data.

During the normal restore process, information is pulled from the vRanger database to complete the restore job. If the vRanger server is lost, and the database cannot be recovered or is otherwise unavailable, you can reinstall a fresh version of vRanger and import the repository to regain access to your backups.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation