Prior to downloading this Software, you must review the Software Transaction Agreement located here and confirm, by clicking the I agree check box below, that your organization accepts and is bound by the terms and conditions of the Software Transaction Agreement for this Software.
If you purchased the licenses for this Software by executing an order form with Quest or if you have an agreement with Quest that states that all purchases are governed by such agreement, then the terms and conditions of that agreement supersedes and takes precedence over the Software Transaction Agreement.
When backing up Hyper-V virtual machines located in CSV and non-CSV volumes, the tasks created fail immediately with the following message:"VSS_E_Flush_Writes_Timeout".Backing up individual VM's can be performed and complete successfully. The Hyper-V VSS writer is in a failed state.Windows event viewer shows a 12298 Event ID VSS Error.
This article provides a complete listing of network ports required by vRanger to facilitate communication of the various application processes including different repository types, physical server protection and VA.
When vRanger Backup & Replication has been installed using the default embedded database, you may experience the following:Cannot reinstall the application using a different Windows user with administrator rights.Cannot log in to the SQL instance using SQL Management Studio or SQLCMD. The installation wizard may report the following error:"Cannot open database "DB_Name" requested by the login...
The vRanger interface does not open and shows the following message in the event viewer: vRanger Backup & Replication encountered an error during startup. The exact error message was: This access control list is not in canonical form and therefore cannot be modified.
Issue has been identified pertaining to the virtual appliances not getting listed in the Virtual Appliance Configuration wizard after upgrading vRanger to 7.8 versions.There is another issue reported where the repository view goes into 'not responding' state when the repository has large number of savepoints. Both these issues would be present in a fresh vRanger 7.8 deployment.