Quest vRanger
Installation/Upgrade Guide
5.3.2.b
25
Migrating Your Existing Scratch Disk
The Virtual Appliance Deployment Wizard gives you the option of deploying a virtual appliance with
or without a scratch disk. When deploying a new VA to upgrade an existing virtual appliance used for
replication, do not create a scratch disk during the deployment process. You can add the existing
scratch disk to the new virtual appliance, as described below:
1. From the VI Client, right-click on the new virtual appliance, and select Edit Settings.
2. On the Hardware tab, click Add.
3. Select Hard Disk. Click Next.
4. Select Use an existing virtual disk.
5. Browse to the location of your existing scratch disk. Select the VMDK for the scratch disk and
click OK.
6. Using the console in the VI client, login to the virtual appliance. Restart the VM by typing reboot
at the prompt.
5.4.0
Upgrading a Previous vReplicator Installation
Due to the differences in application architecture, there is no upgrade path from vReplicator 3.x to
vRanger 6.1. vRanger will need to be installed fresh (using the full installer) and replication jobs will
need to be re-created.
The high-level process for migrating from vReplicator to vRanger 6.1 is as follows:
1. Request a new vRanger 6.x license.
A new license is required for vReplicator customers migrating to vRanger 6.1. Please request
one using the Quest Software Licence Request form at:
https://support.quest.com/LicenseKey.aspx.
Note: Current vReplicator 3.x customers who are also vRanger customers may want to request a
combined license file that includes backup and replication licensing.
2. Download and install vRanger using the Full installer. See Installing vRanger for the installation
procedures.
Warning: If you will be re-creating your replication jobs, do not uninstall vReplicator 3.x. You may
install and run vRanger on the same machine as vReplicator 3.x without issue.
3. Configure vRanger as appropriate. See “Configuration through the Startup Wizard” in Chapter 3
of the vRanger User’s Guide for more information.
4. Re-create replication jobs to match your vReplicator configuration.
vRanger replication jobs can re-use the existing target VMs created by the vReplicator jobs.
This eliminates the need to perform a full synchronization to start the new replication jobs. When
configuring jobs, ensure that the host and datastore configuration matches the original job.
vRanger will recognize the existing target VM and resume replication without sending the full
VM.
Warning: Disable the vReplicator job before enabling its vRanger counterpart.
5. After validating that all replication jobs have been properly migrated and are working correctly,
uninstall vReplicator.