Chatee ahora con Soporte
Chat con el soporte

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

Restoring a physical server

Previous Next



Restore

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.

Restoring a physical server

Previous Next


Restore > Restoring a physical server > Restoring a physical server

Restoring a physical server

vRanger restores physical savepoints to physical target servers using the vRanger Restore image — by using a CD or USB drive. This restore image provides a temporary boot environment into which the vRanger tools are loaded and run. After the restore is complete, the server can be rebooted into the restored operating system.

After the target server is configured, the process of restoring a physical savepoint is similar to restoring a VM. A full restore returns the server or servers 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.

For the procedures on restoring a physical savepoint, see Performing a full restore of a physical machine.

Restoring a file

Unlike traditional backup solutions that require file-level agents, vRanger can recover a file or files directly from the image-level backup, without mounting the image. Incremental backups are combined with the parent full image as needed.

One of the key problems with file-level restore (FLR) is finding the appropriate files. vRanger includes a cataloging feature that indexes backups of Windows® servers, and records the metadata to enable faster searching. For more information, see Performing an FLR using Catalog Search.

Restoring from a manifest file

Each savepoint contains a manifest file that can be used to restore the savepoint without access to the vRanger database. In addition, the Restore from Manifest function can be used to recover savepoints that are not part of a repository — those savepoints that have been recovered from tape, for example.

The Restore from Manifest function can be used for full restores of VMs and physical servers, and FLR. To restore a savepoint using the manifest file, see Restoring from manifest.

Performing a full restore for VMware VMs

Previous Next


Restore > Performing a full restore for VMware VMs

Performing a full restore for VMware VMs

vRanger performs a full restore of a VM by using a savepoint created from a backup job. A savepoint contains point-in-time data of the VM. If you select an incremental savepoint from which to restore the server, a full savepoint is also restored, along with every incremental savepoint taken between the time of the full backup and the time of the selected incremental backup.

For information about performing a full restore from a savepoint manifest, see Restoring from manifest.

For more information, see Performing a full restore of a physical machine.

To perform a full restore for a VM, complete the following tasks:

Starting the Restore Wizard

Previous Next


Restore > Performing a full restore for VMware VMs

Performing a full restore for VMware VMs

vRanger performs a full restore of a VM by using a savepoint created from a backup job. A savepoint contains point-in-time data of the VM. If you select an incremental savepoint from which to restore the server, a full savepoint is also restored, along with every incremental savepoint taken between the time of the full backup and the time of the selected incremental backup.

For information about performing a full restore from a savepoint manifest, see Restoring from manifest.

For more information, see Performing a full restore of a physical machine.

To perform a full restore for a VM, complete the following tasks:

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación