24
Chapter 5
Upgrading vRanger
Note: If the Instance name on the machine is different, you should change the sever name to the
instance name on the local machine. “vRangerPro” is the default created instance when using SQL
Express 2005.
14.The installation completes.
5.3.0
Upgrading the vRanger Virtual Appliance
The version of the vRanger virtual appliance for this release is listed in Supported Virtual Appliance
Versions. Review the sections that follow for information on checking the version of your deployed
virtual appliances, and for procedures on updating them if necessary.
Note: The vRanger VA is now bundled with vRanger, and can be found in: C:\Program Files (x86)\Quest
Software\vRanger\Client\Quest_vRanger-Virtual-Appliance_190.ova
5.3.1
Checking the Version of Your Virtual Appliance
To check the version of your virtual appliance:
1. Login to the virtual appliance.
2. At the prompt, enter the command
cat /etc/vzvaversion
5.3.2
Upgrading Your Virtual Appliance
There is no method to perform an in-place upgrade of the virtual appliance. The previous version
must be replaced with the new version. To update your virtual appliance(s), follow the steps
described below:
Deploy the new virtual appliance version according to the instructions in “Deploying the Virtual
Appliance - VA Deployment Wizard” in Chapter 3 of the vRanger User’s Guide.
Note: If you want to maintain the scratch disk from your existing virtual appliances, deploy a virtual
appliance without a scratch disk.
3. Migrate your scratch disk as described in Migrating Your Existing Scratch Disk.
Remove your previous VAs from vRanger. To do this, browse to the Virtual Appliance
Configuration dialog via Tools > Options > Virtual Appliance Configuration. Select the
virtual appliances s to remove, and click Remove.
Note: If you are going to attach your existing scratch disk to your upgraded virtual appliance, do so
before removing the old VA.
5.3.2.a
Maintaining Your Scratch Disk
The second disk (scratch disk) on your virtual appliance(s) contains a hash file for each replicated
virtual machine. vRanger uses this file to identify changed data blocks during replication. When
upgrading the virtual appliance, consider migrating the scratch disk from your legacy VA to the
upgraded version. This will ensure that your hash files are maintained. See Upgrading Your Virtual
Appliance for more information.
Important: If you do not migrate the scratch disk to your updated virtual appliances, vRanger will
need to re-create each hash file which requires a full scan of the replicated virtual machine. While
only the changed data will be sent, the re-scan of the VM may take up to 1 minute per GB of hard
disk space.
For more information abou H