Chat now with support
Chat with Support

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

Differential replication

In differential replication, vRanger compares the data blocks on the source VM to a data map to identify blocks that have changed since the last replication pass. These changed blocks are sent to the target VM and committed to disk, and the data map is updated to reflect the current state of both VMs.

When using differential replication, consider the following:

Configuring transport failover options

Replication transport actions occur through HotAdd — LAN-free or network. If one transport method is not available, vRanger attempts to perform the replication task using one of the other transport methods. You may configure the order in which vRanger attempts the transport options with the Transport Failover node of the Configuration Options page. For VMware® ESXi™ hosts, configure the transport order to VA-based HotAdd > VA-based Network.

Pre-seeding replication jobs

vRanger replication is intended to replicate changes from a source VM to a remote target. It is often not practical to perform the first replication pass — which sends the full VM) to a remote site over a WAN link. You may use vRanger to “seed” a replication job locally to reduce the amount of data sent over the WAN.

To pre-seed replication jobs, complete the following tasks:

Complete the steps in the following procedure to back up the source VM.

Savepoints are named using a VMname_date_time_UUID format. Copy the entire directory, which contains a .var file and two .metadata files, for the savepoint in question.
5
Using the Restore from Manifest function documented in Performing a full restore from manifest for VMware VMs, restore the backup to the target VMware® ESXi™ Server at the DR site.

Complete the steps in the following procedure to replicate the changes made to the VM.

2
5
In the Select Target Host dialog box, next to Preseed VM UUID, click the browse button, and select the pre-seeded VM.

Creating a replication job

vRanger uses a simple wizard to guide you through the process of creating a replication job. At a high level, the process includes the following steps. Each of the steps is explained in more detail in the topics that follow.

To create a replication job, complete the following tasks:

Complete the steps in the following procedure to select the source VM.

1
Click My Inventory.
3
Enter the Job Name and Job Description, and click Next.

On the Select Target Host page, complete the following steps to select a target host.

Choose a Target Host from the list, and click Next.
If you have pre-seeded the VM on the target host, select the host on the target side to which the source VM has been restored. For more information, see Pre-seeding replication jobs. When selecting the target VM name, ensure that you are using the same name as the source VM. vRanger appends “_VzReplicate” to the VM name on the target side.
2
[Optional] In the Select Target Host dialog box, next to Preseed VM UUID, click the browse button, and select the pre-seeded VM.
IMPORTANT: After a replication job has been saved, you cannot change the target host. If you want to replicate to a different host, you may either use VMware vSphere® vMotion® to migrate the VM to the preferred host, or create a replication job for the preferred target. If you vMotion the VM, the existing replication job should identify the change in host and adjust automatically.

On the Replication Mode page, you can select between differential replication and hybrid replication. For more information, see Replication modes.

1
On the Replication Mode page, under Replication Type, select Differential Replication.
NOTE: Hybrid replication is not supported when replicating to or from VMware® ESXi™. This feature is deprecated for vRanger 7.2 and later.
2
Click Next.

On the Replication Network Mapping page, you specify the network on the target host to which the VM nics should connect.

1
Select the Network Mapping you want to use for this job.
2
Click Next.

The Select which Hard Disk(s) to replicate page lets you include or exclude specific disks from replication.

You may select a Primary Datastore, which is used as the default for all disks in this job, letting you configure only the exceptions.
2
In the Target Datastore column, verify that the Primary Datastore has been populated.
4
On the Select Primary Storage page, review the list of datastores.
6
When the Select which Hard Disk(s) to replicate page appears, click Next.

The Replication Options page lets you configure additional operations performed during the replication job. You may also view the transport failover preferences, and modify them as needed.

Check destination for free space.

This option prompts vRanger to check the destination location to ensure that there is enough space available for the replica VM.

Update notes with latest replication results.

If this flag is selected, vRanger updates the VM Notes in VC with the most recent replication task status.

NOTE: vRanger maintains the existing VM notes in VMware® vCenter™, appending the replication status to the end.

Enable guest quiescing.

This option enables the VMware® Tools when creating a snapshot. Use this flag if you are replicating a database server. During this process, vRanger freezes or pauses writes on supported applications to provide a consistent image of VSS-enabled databases. For more information, see Physical backup transport options.

Enable Active Block Mapping (ABM).

Selecting this option enables ABM, which lets vRanger skip data that recognized as removed on Windows® NTFS — including junk data in recycle bin.

The following ABM settings options are also available:

3
Click Next.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating