Category
产品版本
主题
副主题
Rollback Failure - live recovery access denied (4033022)
--- End of inner exception stack trace --- ... at System.Threading.Tasks ... The page file may be loaded onto the non-OS drive you're trying to roll back. ... There may be insufficient space on the OS drive for the page file.
SQL does not display Metadata in Core UI (4033261)
The SQL does not grant the sysadmin role by default. ... For the agent service to pick up this metadata, the system needs to have the SysAdmin role on each SQL instance installed in the protected agent.
Forcing a SQL Server Attachability Check (4033140)
This article serves as a guide for forcing a SQL server attachability check within Rapid Recovery. ... Rapid Recovery can perform an attachability checks on a protected SQL server. ... The attachability test lets the Core check for the consistency of the SQL databases and ensure that all data files (MDF and LDF files) are available in the backup snapshot.
Mailbox Restore Troubleshooting (4033074)
This article offers several Mailbox Restore error troubleshooting tips. ... When accessing Mailbox Restore, your log files may indicate that a “clean” shutdown did not occur, causing data to become dirty or corrupted.
How to Invite Users and Set User Security Privileges within the License Portal (4033025)
This article provides a step-by-step guide on how to invite users to a group or subgroup and manage their security privileges within the License Portal. ... To invite users and set security privileges, you must have Owner or Administrator rights on the account.
Boot Error: Bootmgr Missing (Windows 7, Server 2008/R2) (4033078)
This article serves as a “How-To” guide that details the steps necessary to resolve the “Bootmgr is missing” error when trying to boot a Windows machine within AppAssure 5. ... When you attempt to boot a Windows machine within AppAssure 5, the “Bootmgr is missing” error displays
Replication Does Not Resume (4033269)
Replication is not running. ... When you go to the Core Console – Replication tab on the target replication Core under State you see Established (paused). ... Replication remain paused even after you click on the toolset icon and select Resume.
Backup transfer fails with error "No such host is known" (4033005)
Backup for an agent may fail with error messages like: ... Job 'Transfer of volumes [C:\] from 'xxxxxxxxx'' failed ... at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
Live Rollback of 20+TB Volume Does Not Allow Access While Rollback is Running (4033001)
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.
ESXi Export Fails with "'VIXDISKLIB_FLAG_NONE' failed" (4032870)
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:
Rapid Recovery Core is producing broadcast storms (4032768)
When Rapid Recovery Core is in use for some operation, network broadcast storms impact LAN traffic. ... A WireShark trace shows a lot of ARP traffic. ... This can be caused by NIC teaming. ... NICs using two different MAC addresses but sharing a single IP address can cause this.
Mount and Export failures with error "There is not enough space on the disk." (4032760)
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.
iScsiPrt errors 129, 39, 27 can 9 indicate that the Repository is not reachable (4032869)
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.
Snapshot Transfers are Failing with Incorrect Function (4032706)
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.
Deleted Machine Returns to Protection List after the Core.Service is Restarted (4032575)
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.
Snapshots Fail with Error - Failed to Delete One or More Log File (4032561)
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
Checksum error failure due to insufficient disk space during repository integrity check (4032693)
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.
Using the Iometer Performance Tool (4018642)
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 very end with "connection was forcibly closed by remote host" (4032529)
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.
Rapid Recovery MSI Patch Install Fails (4032691)
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.
Underscores and other special characters are not permitted in a NAS device name (4032526)
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.
How to rename a Repository (4032649)
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.
Snapshots of very large volumes fail with an error saying "A call to a remote server timed out" (4032507)
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.
Understanding 0% Compression in an AppAssure/Rapid Recovery Repository (4032498)
What is 0% compression when viewing the repository statistics in the UI ... This issue occurs due to accumulation of residual data processed during the backup process which was not properly removed through the normal clean-up process.
Troubleshooting Network Attached Storage (NAS) Issues (4035486)
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.
新产品关联性