サポートと今すぐチャット
サポートとのチャット

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

Performing restore operations

Previous Next


Integrating and monitoring vRanger > Performing vRanger sweep-to-tape using Quest NetVault Backup > Performing vRanger sweep-to-tape using Quest NetVault Backup > Performing restore operations

Performing restore operations

There are two available ways to restore your data using vRanger.

To perform restore operations, complete one of the following procedures:

•
Restoring a vRanger repository from tape using NetVault Backup
•
Restoring from a vRanger repository
Restoring a vRanger repository from tape using NetVault Backup

Use the following steps to export a previously captured vRanger repository from tape.

To restore a vRanger repository from tape using NetVault Backup:
1
In the Navigation pane, click Create Restore Job.

On the Create Restore Job — Choose Saveset page, the saveset table provides a list of available savesets. The table shows the saveset name (Job Title and Saveset ID), creation date and time, and saveset size.

2
Select the saveset that you want to restore, and click Next.
 
* 
NOTE: If the backup index of the selected saveset is offline, the Confirm load dialog box is displayed. Click OK to load the index from the backup media, and then in the Load Index dialog box, type or select the number of days you want to store the index in the NetVault Database.
3
On the Create Selection Set page, select the archive, for example, vRanger_Sweep_to_Tape, that you want to restore, and click Next.

This step restores the entire vRanger repository.

 
* 
CAUTION: It is important that you restore to a new repository and not to an existing repository. Failure to do so can possibly result in corruption of data.
4
On the Create Restore Job page, specify a name for the job.

Assign a descriptive name that lets you easily identify the job when monitoring its progress or restoring data. The job name can contain alphanumeric and non-alphanumeric characters, but it cannot contain non-Latin characters. There is no length restriction; however, a maximum of 40 characters is recommended.

5
In the Target Client list, location to restore the file set from the list of available machines.
6
In the Schedule list, use the default, Immediate, to run the job when it is submitted.
7
In the Source Options list, select the media from which to restore the archive.
8
Click Submit to run the job.

You can monitor the job progress from the Job Status page and view the logs from the View Logs page.

Restoring from a vRanger repository

The following steps detail the process of restoring data from a vRanger repository.

To restore from a vRanger repository:
1
Select the vRanger repository that contains the backup of the VM; for example, Repo-001.

vRanger provides options to restore the complete VM, or individual files or folders.

A list of protected VMs display.

2
Select the VM containing the data to restore, and then click File Level Restore in the top menu to start the process.

A file structure view of the selected VM appears.

3
Locate and select the files and folders to restore to the selected machine.
4
On the right side of the window, select the target location; for example, Desktop.
5
Click Restore to start the recovery, which extracts the files from the vRanger repository for immediate access.

After recovery is complete, you have access to the newly restored files.

Using deduplication with Quest NetVault SmartDisk and vRanger

Previous Next


Integrating and monitoring vRanger > Performing vRanger sweep-to-tape using Quest NetVault Backup > Using deduplication with Quest NetVault SmartDisk and vRanger

Using deduplication with Quest NetVault SmartDisk and vRanger

NetVault SmartDisk delivers data de-duplication that significantly reduces storage costs. With powerful, byte-level, variable block de-duplication, and advanced data compression that packs more protected data in the same storage area than competing solutions, you can reduce your disk backup storage footprint by up to 90%.

vRanger versions 5.3 and later support the use of a NetVault SmartDisk server as a repository. Simply by adding a NetVault SmartDisk server to vRanger as a repository, backups written to that repository are automatically de-duplicated.

 
* 
NOTE: NetVault SmartDisk repositories are only supported by the Professional edition of vRanger. If you purchased a vRanger Standard license, you cannot use a NetVault SmartDisk repository.

For more information about integrating vRanger and NetVault SmartDisk, see the Quest vRanger Integration Guide for Quest NetVault SmartDisk.

Using Data Domain and vRanger repositories

Previous Next


Integrating and monitoring vRanger > Performing vRanger sweep-to-tape using Quest NetVault Backup > Using Data Domain and vRanger repositories

Using Data Domain and vRanger repositories

vRanger and EMC® Data Domain® appliances provide a simple and efficient method for backing up and recovering VMware® environments. vRanger provides significant enhancements regarding architecture, performance, and communications over traditional backup solutions. Data Domain provides superior data de-duplication capabilities. The combination of vRanger and Data Domain Technology dramatically reduces your backup and recovery time for VMs on VMware® ESXi™ hosts.

For more information about integrating vRanger and Data Domain, see the Quest vRanger Integration Guide for EMC® Data Domain® Boost (DD Boost™).

Monitoring vRanger

Previous Next


Integrating and monitoring vRanger > Monitoring vRanger

Monitoring vRanger

vRanger can be configured to log events to the Windows® Event Viewer on the vRanger machine. These events can be filtered and monitored using the Microsoft System Center Operations Manager to monitor replication functions in line with other IT operations. When monitoring is enabled, vRanger creates a vRanger Service node on the local Event Viewer.

The events currently monitored and logged by vRanger include:

•
Replication Events: Reserved ID Range 10000 to 10999

Replication task failure: logged as an error, event ID 10001

•
Virtual Appliance Events: Reserved ID Range 11000 to 11999

VA not powered on: logged as an error, event ID 11001

VA connection failure: logged as an error, event ID 11002

VA credential failure: logged as an error, event ID 11003

VA unknown failure: logged as an error, event ID 11999

VA return to normal: logged as an Information event, ID 11998

•
Datastore Events: Reserved ID Range 12000 to 12999

Datastore threshold exceeded: logged as an error, event ID 12000

Datastore unknown failure: logged as an error, event ID 12099

Datastore return to normal: logged as an Information event, ID 12098

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択