Quest® vRanger® 7.6.3
These release notes provide information about the Quest® vRanger® release.
vRanger Backup & Replication is the market-leading backup, recovery, and backup-management solution for VMware® and Hyper-V® virtual environments. vRanger automatically discovers new virtual machines (VMs), reduces backup windows, provides smarter backup options, and offers more scalability through its agent-less architecture and features while using fewer resources.
vRanger 7.6.3 is a maintenance release with minor enhancements and bug fixes. See and for more detailed information.
Table 1. General enhancements
Table 2. Backup and restore resolved issues
Virtual appliance version listed in vRanger Installation and Upgrade Guide corrected.
Table 3. Installation known issues
If the Quest vRanger Service is installed with a user other than the currently logged in user, use mixed-mode authentication for SQL Server® and authenticate with the system administrator (sa) user.
Alternatively, Windows®-only authentication can be used if the following workaround is implemented.
3 Replace VRANGER\vRangerServiceUser with the name of the vRanger service user in the following command:
If you did not remove the vRanger database during a vRanger uninstall, you must use the same credentials as the original install or grant rights to the database for the new user when reinstalling vRanger.
vRanger is available in three versions: vRanger Standard Edition (SE), vRanger Backup & Replication, and vReplicator. Only one version of vRanger can be licensed on a machine at any one time. For example, you cannot license vRanger SE and vReplicator on the same machine.
2 When the Charms bar appears, select the Start icon.
3 Right-click in an empty space on the Start screen, and select All Apps.
4 Using the scroll bar at the bottom, scroll right to the Quest section.
5 Look for the Uninstall tile above the vRanger Backup & Replication tile.
6 Right-click the Uninstall tile, and select Run as Administrator.
When a proxy server is configured on the vRanger machine, vRanger may not be able to connect to VMware® vCenter™ Servers or NetVault SmartDisk repositories.
2 Open Internet Explorer® (IE) while logged-in with the account.
3 Go to Internet Options > Connections > LAN settings; this location varies depending on the version of IE installed on the machine.
4 Make sure that no proxy information is defined, and no proxy server is being used.
5 Clear the automatically detect settings check box, in case your particular environment has an automatic proxy script set up.
During an upgrade, the vRanger Upgrade Installer might not delete the previous vRanger Pro Service event log. This exclusion causes the vRanger user interface (UI) to hang and display a “Could not connect to the service” message after the upgrade. To remove the log manually, complete the following steps:
1 Disable the Event Log service.
3 From the vRanger machine’s %SystemRoot%\System32\Config folder, delete the vRanger *.evt file.
5 Restart the Event Log service.
When the Quest vRanger Service is configured for a delayed start, and the vRanger Upgrade Installer is run before the existing Quest vRanger Service has started, the upgrade fails when the Quest vRanger Service starts.
If vRanger is installed using a local admin account, and that account is changed after vRanger is uninstalled, you must use SQL Server authentication for the database installer for both vRanger and Cataloging when you reinstall vRanger.
Table 4. General known issues
• VM backups encounter 2129 Can’t Write errors to CIFS repositories with any transport type.
• Physical machine backups encounter 2129 Can’t Write errors to CIFS repositories.
• Virtual appliance (VA) backups fail with 2129 Can’t Write errors to CIFS repositories.
• Physical machine shows as Disconnected in Inventory.
• Domain membership: The machine may be part of the domain, as seen when you bring up the computer properties, but the membership may not be active, and may have to be reset. To check the status of the systems domain membership from the machine itself, use the command: netdom verify %computername% /verbose
When vRanger is installed on a VM that contains two paravirtualized (PVSCSI) controllers, mounting of paravirtual volumes by using HotAdd fail, causing vRanger to continue operations using the configured failover method — network for backup, or the configured transport failover option for replication.
By default, this directory is C:\Program Files\Quest\vRanger.
2 Open the Vizioncore.vRanger.Service.exe.config file in Notepad.
3 Search the file for CommitTimeout, and change the timeout value to 450.
5 Restart the Quest vRanger Service to implement the changes.
Backup jobs for Hyper-V® Servers are shown twice in the Backup Job Summary Report.
Table 5. Backup known issues
When performing SAN backups of VMs created in VMware® vCloud Director® from a template, the backup may fail with the “Error: 2760 - <VIXcannotOpenDetails> VIX can’t open…” error.
The VMware SAN mode transport searches for VMs by BIOS UUID. By default, all instances and VMs that are deployed from a given catalog vApps/template in vCloud Director are assigned the same BIOS UUID. For more information, see .
When performing a quiesced backup of a Windows Server 2012 VM without using vzShadow.exe, event log errors are generated for System Reserved volumes during snapshot creation.
The VMware QueryChangedDiskAreas API returns incorrect sectors after extending the VM VMDK file with CBT enabled. This issue causes the CBT filter to become invalid, possibly corrupting vRanger backups. For more information, see .
Ensure that the patches described in are applied, and follow other workaround recommendations documented in the KB as appropriate for your environment.
When using the vzShadow.exe executable to perform application-consistent backups, lettered drives are required. The use of vzShadow.exe to quiesce mount points with databases is not supported.
When backing up Windows Server 2008 R2 VMs with multiple disks, and the Enable Guest Quiescing option is selected, some backup tasks may fail with the “API Call failed with message: A general system error occurred: Protocol error from VMX” error.
When performing full backups with CBT enabled, the CBT operation may fail with the “Change Block Tracking not enabled on <disk>” error. When performing incremental or differential backups of the same VMs, CBT functions properly.
• VMware® ESXi™ host crash
• Storage vMotion® of the VM — while powered off
Sometimes, deleting the *ctk.vmdk file for each disk in the affected VM resolves this issue.
• Change the VM settings to set the StartConnected value of the CD-ROM-image device to True.
• Ensure that the restore job option Force Power On is enabled.
When a standalone ESXi 5 host is added to the vRanger inventory, and that Host is associated with a vSphere® 5 vCenter that is not in the vRanger inventory, restore operations to that host fail with the error:
“<host> is being managed by a Virtual Center. Please disassociate the host from the Virtual Center before continuing a Restore operation or register the Virtual Center in vRanger.”
Association is a new relationship introduced in vSphere 5, whereby some host resources are managed only by an associated vCenter, and not the host itself. The Host, therefore, does not have permission to perform the operations required to restore a VM. If the vCenter is not in the vRanger inventory, vRanger cannot obtain the required permissions.
If you are connected to the vRanger machine using RDP when installing vRanger, some vRanger components required for FLR may be installed in an unexpected location, causing them to be unavailable when requested by vRanger. This issue causes FLR tasks to freeze while displaying “Loading …”
When performing a Linux® FLR operation that recovers files and folders with the following characters in the name, the files and folders are displayed with what look to be randomly generated names, and are restored successfully with same random names. Characters that cause this behavior are:
Windows systems often contain a Microsoft-created hidden partition that is not visible through the Disk Management snap-in. When vRanger catalogs the disk containing this hidden partition, it attempts to catalog this partition and may fail, as the partition is often not formatted with NTFS. vRanger generates a failure message in the log files for this partition which may cause confusion, as this partition is often not known to exist.
Physical backup of Windows Server 2012 and 2012 R2 machines may fail with the “Failed to create VSS snapshot (P_VSSUTIL_WRITER_ERR)” message. This issue is often due to a VSS timeout caused by resource contention on the source server.
If the disk hardware is changed between physical backup or restore tasks, the job should be updated to reflect such changes to ensure that the intended disks are included. In some instances, rebooting the target server causes disks to change IDs — see Microsoft article . This change to the IDs results in a machine whose effective hardware has changed.
When deploying the vRanger physical client to a physical server, the account used to install and run the client must have administrative Log on as a service rights. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, a Group Policy object associated with this node might be removing the right. Check with your domain administrator to find out if this issue is happening.
If a repository was created using the vAPI, and the path to the repository was entered using backward slashes instead of forward slashes, restoring a physical server savepoint fails with the “Error: 2630 - can’t find uuid” error.
The use of dynamic disks are not supported for physical backup. If a physical backup task is performed on a source server containing dynamic disks, the task fails with the “Value cannot be null” message.
1 On the source server, open the Windows firewall, and select Change Settings. In the Exception tab, select Windows Management Instrumentation (WMI).
2 On the source server, verify that the Remote Procedure Call (RPC) service is started and set to Automatic.
3 On the source server, verify that the Windows Management Instrumentation (WMI) service is started and set to Automatic.
When uninstalling the vRanger Physical Client, the following files are not removed from the physical client installation directory —C:\Program Files\Quest\vRangerPhysicalClient by default.
When restoring to a physical server, vRanger does not lock the source or savepoint. This behavior potentially allows the un-supported practice of creating two simultaneous restore tasks to the same server.
When performing physical backups, if the credentials used for authenticating to the source server are changed without updating vRanger, subsequent backup tasks fail with the “Failed to acquire shared resources (Unable to connect to the backup destination.) Failed to connect to the backup destination” error. When this issue occurs, update the credentials in vRanger.
Table 8. Replication known issues
When a standalone ESXi host is added to the vRanger inventory, and that Host is associated with a vSphere vCenter not in the vRanger inventory, replication operations to that host fail with the error:
“<host> is being managed by a Virtual Center. Please disassociate the host from the Virtual Center before continuing a replication operation or register the Virtual Center in vRanger.”
Association is a relationship introduced in vSphere 5, whereby some host resources are managed only by an associated vCenter, and not the host itself. The Host, therefore, does not have permission to perform the operations required to replicate a VM. If the vCenter is not in the vRanger inventory, vRanger cannot obtain the required permissions.
A failover operation performs two key tasks that need to be performed manually if the operation fails: powering on the destination VM, and reversing the direction of replication to ensure that changes to the destination VM are captured when operation reverts to the production site. To replicate a failover task manually, perform the following steps:
When performing a replication task after upgrading the source VM from HW version 4 to HW version 7 or 8, the task may appear to hang, and fail with the “The operation has timed out” message. In this situation, vRanger upgrades the HW version of the replica VM, which triggers a vSphere prompt to update the VMware Tools on the replica VM.
In the vSphere Client, select Continue with the VM Upgrade for the replica VM.
Table 9. Virtual appliance (VA) known issues
4 Run the command: dmesg | grep "rename.*eth"
6 Run the command: cd /etc/sysconfig
7 Run the following command to create and edit the configuration file for the new NIC where <IFname> is the new name for the new NIC card:
9 Restart networking by running the command: /etc/init.d/network restart
Table 10. Third-party known issues
vSphere 5 introduces the vStorage APIs VixDiskLib_PrepareForAccess() and VixDiskLib_EndAccess() to lock and unlock migration for individual VMs. It is observed that on occasion the VixDiskLib_EndAccess fails to unlock the VM and, as a result, that VM is left in a state where vMotion is permanently disabled.
Due to a VMware limitation — as documented in the vSphere 5 Documentation — vRanger cannot support operations against datastores with names containing the characters forward slash (/), backward slash (\), and percent (%).
If the host name of a vCenter server contains a character that Tomcat does not support, retrieving health data fails with the “Unable to retrieve health data from <server>…” error. This error occurs because Tomcat requires that host names are RFC 952 complaint. For more information, see .
When creating or running a backup job, the operation fails with the “Error: 2760 - <VIXcannotOpenDetails> VIX can’t open [XXXXX] XXXX/XXX.vmdk (The host is not licensed for this feature)” error.