vRanger 7.8.3 - User Guide

Starting the restore job

Starting the restore job

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

This task is a procedure in Performing a full restore from manifest for a physical machine.

To start the restore job:

1	On the Summary page, review the data displayed in the tree view.

2	If you want to begin the job automatically after completing the wizard, select Run the Job after Finish is clicked.

 

NOTE: If this option is not selected, the job is saved and begins at the time determined during the Setting the Recurrence Schedule procedure.

3	Click Finish.

4	If you did not opt to begin the job automatically after clicking Finish, and this job is an on-demand job, do the following:

 

NOTE: If this job is not an on-demand job, the job begins at the scheduled time.

a	In the main vRanger UI, in the My Inventory view, select the server or host for the server you want to restore, and then select the job from the Working Inventory pane.

b	On the View toolbar, click Run.

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.

Performing FLR from manifest

Performing FLR from manifest

An FLR from manifest lets you move the files that make up a backup to your preferred location restore a VM whose backup files are not in a repository. This process lets you move the files that make up a backup to wherever you want and still perform a restore.

To perform an FLR from manifest:

1	Click My Repositories.

2	On the My Repositories toolbar, click the FLR from Manifest icon .

3	In the File Level Restore from Manifest dialog box, enter the user name, password, and path for the Manifest file of the backup that contains the files you want to restore.

4	Enter the Encryption Password, if the backup was encrypted.

5

Click OK.

6	In the Select the Files/Folders to Restore pane, expand the archive to view the file structure, and then select the file or files to recover.

7	In the Destination pane, select the destination to which the selected files should be recovered.

The Destination pane shows the Windows Explorer view for the machine on which vRanger is installed.

 

CAUTION: vRanger does not check for previous versions of the files you are restoring. Files restored using FLR overwrites any previous files of the same name in the restore destination.

8	Click Restore.

9	In the Restore Status pane, view the status of the restore activity and the value in the Percent Finished column.

10	Verify that the status is Finished and Percent Finished is 100%.

11	To view the restored file or folder, click View in Explorer.

 

Replicate VMs

Understanding replication of VMs

vRanger includes integrated replication based on the proven technology of vReplicator, enabling replication of VMware® virtual machines (VMs) both on site and at remote locations for flexible and efficient disaster recovery preparedness. Combine backup and replication jobs to ensure that you meet your organization’s recovery time and recovery point objectives. Perform fast VM failover and recovery at all your sites, no matter where they are located.

 

NOTE: Replication is not available for Hyper-V® VMs. If you are looking for information on replicating Quest RDA and EMC DD Boost repositories, see Managing repository replication.

A VM is made up of a set of files. Replicating a VM is, in essence, replicating the set of files that make up the VM, with changes to these files that reflect user-specified settings for the source VM.

Be aware of the following regarding the destination that you target for a replication:

•

You can change the storage-destination settings. Although vRanger uses the defaults from the original configuration, you change the host and storage targets. For example, you can replicate from a non-VVol datastore to a VVol datastore. In another example, you can replicate from a datastore that is governed by one storage policy to a datastore that is governed by a different policy, or no policy.

•	You can select different storage for the target of the primary VM file versus the disks.

•	If the target uses DRS, you must select the DRS, which governs which datastore in the cluster is used at replication time; you cannot select a specific datastore.

•	If your environment uses storage policies, datastores are listed under the applicable policy. Any datastores not associated with a storage policy are listed separately.

The following table lists the set of files replicated by vReplicator:

 

Table 1. Files replicated

File extension	Description
.vmx	The VM config file, one per VM.
.vmxf	The extended VM config file, one per VM.
.nvram	The VM BIO file, one per VM.
.vmdk	The VM hard disk file, one per hard disk or snapshot.
-flat.vmdk	The VM hard disk data file, one per hard disk or snapshot.
-delta.vmdk	The VM snapshot data file, one per snapshot.
-ctk.vmdk	The VM hard disk change tracking file when CB is enabled on the disk.

How replication works

Understanding replication of VMs

vRanger includes integrated replication based on the proven technology of vReplicator, enabling replication of VMware® virtual machines (VMs) both on site and at remote locations for flexible and efficient disaster recovery preparedness. Combine backup and replication jobs to ensure that you meet your organization’s recovery time and recovery point objectives. Perform fast VM failover and recovery at all your sites, no matter where they are located.

 

NOTE: Replication is not available for Hyper-V® VMs. If you are looking for information on replicating Quest RDA and EMC DD Boost repositories, see Managing repository replication.

A VM is made up of a set of files. Replicating a VM is, in essence, replicating the set of files that make up the VM, with changes to these files that reflect user-specified settings for the source VM.

Be aware of the following regarding the destination that you target for a replication:

•

You can change the storage-destination settings. Although vRanger uses the defaults from the original configuration, you change the host and storage targets. For example, you can replicate from a non-VVol datastore to a VVol datastore. In another example, you can replicate from a datastore that is governed by one storage policy to a datastore that is governed by a different policy, or no policy.

•	You can select different storage for the target of the primary VM file versus the disks.

•	If the target uses DRS, you must select the DRS, which governs which datastore in the cluster is used at replication time; you cannot select a specific datastore.

•	If your environment uses storage policies, datastores are listed under the applicable policy. Any datastores not associated with a storage policy are listed separately.

The following table lists the set of files replicated by vReplicator:

 

Table 1. Files replicated

File extension	Description
.vmx	The VM config file, one per VM.
.vmxf	The extended VM config file, one per VM.
.nvram	The VM BIO file, one per VM.
.vmdk	The VM hard disk file, one per hard disk or snapshot.
-flat.vmdk	The VM hard disk data file, one per hard disk or snapshot.
-delta.vmdk	The VM snapshot data file, one per snapshot.
-ctk.vmdk	The VM hard disk change tracking file when CB is enabled on the disk.