When attempting to restore a 23tb data Volume from a protected 2008 agent to a diff 2012 agent with 32tb Volume, the live rollback starts but you cannot access the volume and an "INVALID PARAMETER" error is reported.
When exporting to a ESXi host, the job appears to be progressing, but as soon as the progress bar displays with 0% the job fails with the followoing error: ... Investigating the AppRecovery logs deeper, the following errors are found during the export task leading to the displayed error:
In a Core server, there can be an issue encountered when mounting a recovery point for any volume that is of significant size. ... In case there is a certain amount of free space left on the C: drive that would be insufficient to perform a mount.
After reviewing the Windows System Log to troubleshoot repository issues, reveals iScsiPrt Error Events 129, 39, 27 and 9. ... These errors indicate that the Initiator send either a management command or an initiator task to the target and did not receive a reply.
While transferring a snapshot for the Agent, the jobs continuously fail at what appear to be the exact same spot each time. ... The Core UI reports an error that the transfer failed because it was dropped by the remote host.
A machine is removed from protection in the Core UI and dissapears in the protected machines summary list and in the left frame. ... After the Core.Service or backup server is rebooted, the previously deleted machine returns back to the UI.
When taking a snapshot in AppAssure, it fails with the following error: ... Service Host Error: Service error while handling request [DELETE https://agent_machine:8006/apprecovery/api/agent/transfer/snapshots/7e3ac97b-f7d9-49a8-9689-d08e3819f7f4/volumes/~|~~|~%3f~|~Volume{fac5ef1a-124d-11e2-a86d-806e6f6e6963}~|~/logs]: Failed to delete one or more log files – The system cannot find the file specified
You have run a repository integrity check but it resulted in a Checksum error failure due to insufficient disk space. ... the Dedupe cache size, you have the option of increasing the default 1.5GB value up to 50% of the amount of installed memory on your core server given it has sufficient space.
When attempting to install a patch provided by Quest Support for AppAssure or Rapid Recovery, the installation fails with the error: "The wizard was interrupted before could be completely installed.
How to change the name of an existing repository. ... On cores with multiple repositories you may want to rename them for easier tracking. ... Windows Registry Disclaimer: ... Quest does not provide support for problems that arise from improper modification of the registry.
This article provides guidance on troubleshooting potential network and performance issues for customers using a Network Attached Storage (NAS) device as the location for a Rapid Recovery repository.
Roll up job failed with error message: "Cannot release a buffer that has already been released". ... Logs might include a message indicating an invalid record found on dvm increment refs of dfs_record entry 0x#######
The Rapid Recovery Core can instantly restore data or recover machines to physical or virtual machines from recovery points. ... The recovery points contain agent volume snapshots captured at the block level.
After a base image or especially large backup, subsequent backups also appear to be larger than usual <p>While Rapid Recovery is transferring the recovery point to the core, the VSS snapshot is stored on the agent.
This article describes potential MUP warnings on your Core server. ... Your system logs, as well as your repositories, may show multiple MUP warnings, for example: ... This error may be caused by network connectivity issues.
When attempting a Hyper-V export, the following error message is encountered: ... Please make sure that the proper .Net Framework is installed on ‘#hostname#’ and port ’8010′ is open for incoming HTTP connections and try again.
This article describes the network testing technique and the sequence of steps that need to be taken to perform network connection testing using the Iometer free network test tool. ... In many cases, the replication failure might be due to some environmental or network connection problems.
Jobs fail at the end of the backup with the error message of "connection was forcibly closed by remote host." This can be caused by the data stream of traffic being interrupted during the termination of the backup job.
After a restore, the restored machine fails to boot with stop error 0x0000007B. ... <p style="text-indent: -0.25in;margin: 0in 0in 0pt 1in;mso-list: l0 level2 lfo1;"><span style="mso-list: Ignore;">a.<span style="font: 7pt 'Times New Roman';">
The "User name" and "Password" fields are grayed out (disabled) when trying to open existing repository or to fix repository errors. ... This happens only if repository is located on CIFS share(s) and if the name of one or more NAS devices contains an underscore or any other special characters.
Unable to uninstall a software from "Programs and Features" on a Windows machine with the error: ... Verify that the specified location exists and is writable. ... This is problem can affect any installed software on Windows and is not a Rapid Recovery specific problem.
User receives the following Alert for Virtual Exports when no changes have been made by the user: ... This alert is working as intended. ... The alert is generated whenever a new snapshot is exported to the .vhd location.
The Version Store keeps an in-memory list of modifications made to the database. ... In simple terms, the Version Store is where transactions are held in memory until they can be written to disk.
During backups of systems running DFS replication, VSS backups may cause DFS errors 5012 and 5014 in DFS Replication Logs. ... The DFS VSS Writer (The Component of VSS that controls the quiescing of data related to DFS) works differently than other VSS writers.
Snapshots fail with an error saying "A call to a remote server timed out" ... If you watch the backup, the transfer will sit in "Determining data to send," then fails. ... Very large volumes (in the case I saw, 2 4-TB volumes on a single disk) take a long time to determine what blocks to send, longer than the default timeout and longer than can be configured in the AppAssure GUI.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center