When attempting to perform a virtual export on ESXi, the job fails with the following error: ... Vddk Api Exception: The host is not licensed for this feature ... This error appears when the account used to perform the virtual export lacks sufficient administrator rights to vCenter or root access to the ESXi host.
When moving the Rapid Recovery Core service to a new server and restoring settings from a previous setup using an XML file, some agentless (Rapid Snap) backups may stop working. ... The issue happens because the system retains the old Core server’s hostname instead of updating it to match the new one.
In some cases, you may need to convert a seed drive into an archive. ... This could be for various purposes, such as restoring data, verifying integrity using the Archive Check procedure, or other reasons.
This offering is available to ensure that your Rapid Recovery protection solution is running as efficiently as possible and to train your team to take advantage of its full value. ... The Rapid Recovery Health Check is designed to help you better understand your Data Protection environment.
When attempting to consume a seed drive for replication on the Target Core, the following error message appears:<br><br>“Nothing to consume for this Core on the selected Seed Drive. ... If you specified a path to a mapped network drive, please, use it’s UNC path with valid credentials instead.
To resolve the issue please ensure you first backup the registry file before making any changes.
--- 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.
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.
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.
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.
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.
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 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 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)
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:
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.
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#######
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.
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
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center