Tchater maintenant avec le support
Tchattez avec un ingénieur du support

vRanger 7.8 - Release Notes

Known issues

Previous Next



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:
3
Right-click in an empty space on the Start screen, and select All Apps.
5
Look for the Uninstall tile above the vRanger Backup & Replication tile.
6
Right-click the Uninstall tile, and select Run as Administrator.
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.
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.
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.
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.
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.
Ensure that the patches described in VMware KB article 2090639 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.
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.
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:
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.
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 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.
In the vSphere Client, select Continue with the VM Upgrade for the replica VM.
4
Run the command: dmesg | grep "rename.*eth"
6
Run the command: cd /etc/sysconfig
vi ifconfig.<IFname>
9
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.

System requirements

Previous Next



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.

Supported operating systems for installation

Previous Next


System requirements > Supported operating systems for installation

Windows Server 2008 R212

1

2

3

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:
Updates for Windows Server 2012 R2: Before installing vRanger on Windows Server 2012 R2, ensure that the Windows updates listed below are installed:

Minimum hardware requirements

Previous Next


System requirements > Minimum hardware requirements

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation