Chat now with support
Chat with Support

vRanger 7.8.5 - Installation/Upgrade Guide

Introduction Before you install System requirements and compatibility Installing vRanger Upgrading vRanger

Upgrading your VA

You can upgrade the vRanger virtual appliance using the Virtual Appliance Configuration dialog box. If your existing VAs have replication scratch disks configured, they are migrated to the upgraded VA as part of this process.

Click Tools, and then click Options.
Under the Virtual Appliance node on the Configuration Options page, click Configuration.
In the Configure Existing Virtual Appliance section, select the VAs to upgrade, and click Upgrade.
If not automatically populated, click Browse, and browse to the location of the latest Open Virtual Appliance (OVA) file.
If you want to maintain the existing VAs, select Do not delete the old virtual appliance. Selecting this option deploys a new VA in parallel.
Click OK to begin the upgrade process.

Maintaining your scratch disk

The second disk — scratch disk — on your VA contains a hash file for each replicated VM. vRanger uses this file to identify changed data blocks during replication. When upgrading the VA, consider migrating the scratch disk from your legacy VA to the upgraded version. This migration ensures that your hash files are maintained. For more information, see Upgrading your VA.

NOTE: If you are using a VMware® vCenter™ version earlier than 6.0, the ability to change the datastore of the VA scratch disk used for replication is not available.

For more information about the scratch disk, see the Quest vRanger User’s Guide.

Migrating your existing scratch disk

The Virtual Appliance Deployment Wizard gives you the option of deploying a VA with or without a scratch disk. When deploying a new VA to upgrade an existing VA used for replication, do not create a scratch disk during the deployment process. You can add the existing scratch disk to the new VA:

On the Hardware tab, click Add.
Select Hard Disk, and click Next.
Select Use an existing virtual disk.
Restart the VM by typing reboot at the prompt.

Upgrading a previous vReplicator installation

Due to the differences in application architecture, there is no upgrade path from vReplicator 3.x to vRanger 7.8.5. vRanger must be installed fresh — using the full installer — and replication jobs must be re-created.

The high-level process for migrating from vReplicator to vRanger 7.8.5 is as follows:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating