The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.
Table 3. Installation known issues When installing vRanger on Windows Server 2008 R2 SP1, the Windows Management Framework 3.0 must also be installed in order for the vRanger Service to run. Options for installing WMF 3.0 are:
2 When installing or upgrading vRanger on a Micrsoft Windows 2012 R2 Server, the vRanger GUI may fail to launch with following error:“FileNotFoundException. Could not load file or assembly 'Vizioncore.vRanger.FLR.dll' or one of its dependencies. The specified module could not be found.”This issue is caused by a corrupted Visual C++ 14.0 installation on the installation server. To resolve this issue 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: When vRanger is installed on Windows 8.1 or Windows Server 2012, using the Uninstall icon to remove the application fails unless the uninstall is performed using the Administrator role.
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.If you are unsure what the account is, use Microsoft Management Console (MMC) to check the services.msc file.
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. During periods of heavy activity on the vRanger machine, HotAdd backup tasks may fail over to LAN backups with the following message. Sometimes, the LAN backups fail with the same error.These errors can be caused by excessive resource contention, which causes vRanger message queues to become out of synch.To avoid task timeout errors, schedule jobs to avoid excessive resource contention on the vRanger machine.If rescheduling jobs is not an option, you may increase the timeout value to allow the vRanger message queues to recover from issues caused by resource contention. To change the timeout value: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. In some circumstances, Changed Block Tracking (CBT) does not show as enabled for some VMs in the vRanger inventory. This issue is due to an error described in VMware KB article 2075984.
Table 5. Backup known issues “mkdir: cannot create directory '/var/tmp/vix/dd57d1da-22ee-4a9b-9988-310e8b608c3f': Read-only file system” 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 VMware KB article 1002403. 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 VMware KB article 2090639. 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 using a Microsoft Storage Spaces Direct (S2D) cluster as a repository, VA-based HotAdd will fail with error “Error 2258: FATAL cifs_cant_mkdir”.
When vRanger is installed on Windows Server 2019, attempting to perform a FLR on an ReFS volume causes the vRanger machine to crash. When restoring a VM that had an ISO connected when the VM was backed up, the restored VM does not have the ISO connected.
• 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 host is added to the vRanger inventory, and that Host is associated with a vSphere® 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 relationship in vSphere, 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.
The vRanger Restore CD is not compatible with UEFI. Physical target servers booting into UEFI will not boot the Restore CD.To restore a backup to a physical server booting into UEFI, change the boot mode to BIOS. To do so, follow the steps below: 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 http://msdn.microsoft.com/en-us/library/windows/desktop/bb968801(v=vs.85).aspx. 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. Adding a physical source server to vRanger inventory sometimes fails with the “The RPC server is unavailable” error.
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 of an Exchange 2010 server, the task fails with the “Failed to create VSS snapshot on the target machine (P_VSSUTIL_WRITER_ERR)” error. When performing physical backups, backup tasks intermittently fail with the “Failed to create VSS snapshot on the target machine (P_VSSUTIL_UNEXPECTED)” error. 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 The vRanger replication wizard will allow you to create a job replicating from a higher hardware version to a lower hardware version. When executed, the job will fail with error "Error: API Call failed with message: The virtual machine version is not compatible with the version of the host."VMware ESXi 6.7u2 introduces hardware version 15. This hardware version is incompatible with ESXi versions 6.7u1 or lower. When configuring a replication job from a 6.7u2 host to a host running 6.7u1 or earlier, the VM hardware versions will be incompatible. 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. When performing a failover operation, without synchronizing changes, and the source host is unavailable, the failover task fails and you must manually perform the failover.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:
6 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. Replication with the VA fails if the following characters are used when authenticating a vCenter connection in vRanger:
Table 9. Virtual appliance (VA) known issues When editing an existing VA, changing both the datastore and scratch disk size for a VA fails with an error. When deploying the vRanger VA using the Virtual Appliance Deployment Wizard, only one VA is allowed per host. When creating a VA with the Install-VirtualAppliance vAPI cmdlet, enabling the VADeployStatus parameter may cause failures when used with multiple VAs. In some environments, it may be necessary for a customer to add a second network interface card (NIC) to the vRanger VA.
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:vi ifconfig.<IFname>
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. 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 VMware KB article 1013507. 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. In some cases, VMware backup jobs may fail with the error “Error: -1 Backup process had an unexpected failure”. This is a known issue as documented in VMware KB article 2125497 and the VMware VDDK 6.0 Release Notes.
IMPORTANT: The information in this section is a summary. Review the information below and in the “System Requirements” and “Upgrading vRanger” chapters of the Quest vRanger Installation/Upgrade Guide before installing or upgrading to this version of vRanger.
Table 11. Supported operating systems
Windows 2008 R2 SP1 requires Windows Management Framework 3.0. Refer to Known Issue VR-177 in the vRanger Release Notes for more information.
Before installing vRanger on Windows Server 2012 R2, the updates listed in Additional required software must be installed.
In addition to a supported version of Windows® and a supported VMware® Infrastructure, you may need some additional software components, depending on your configuration.
• Microsoft® .NET Framework: vRanger requires the .NET Framework 4.5. The vRanger installer installs it if not detected.
• SQL Server: [Optional] vRanger utilizes two SQL Server® databases for application functionality. vRanger can install a local version of SQL Express 2014 SP3 or you can choose to install the vRanger databases on your own SQL instance.
• Windows PowerShell 3 or above.If you are installing vRanger on Windows 2008 R2 SP1, you will need to install Windows PowerShell 3 or above before installing vRanger
• vRanger virtual appliance (VA): The vRanger VA is a small, pre-packaged Linux® distribution that serves as a platform for vRanger operations away from the vRanger server. vRanger uses the VA for the following functions:
▪ Replication to and from VMware® ESXi™ hosts.
• Updates for Windows Server 2012 R2: Before installing vRanger on Windows Server 2012 R2, ensure that the Windows updates listed below are installed:
The minimum hardware requirements to run vRanger can vary widely based on several factors. Therefore, you should not do a large-scale implementation without first completing a scoping and sizing exercise.
When backing up from and restoring to a physical server, vRanger uses a client run on that server to perform backup and restore operations. To process the backup workload effectively, the physical server must meet the following requirements: