The following table lists the Cyber Recovery alerts with a Warning severity.
Alert ID | Message Summary | Summary Details | Remedy |
---|---|---|---|
2007 | Data Domain DD Boost license not found. | Cyber Recovery was unable to discover the Data Domain DD Boost license. | Contact your storage administrator or sales representative to acquire a Data Domain DD Boost license. |
2008 | Data Domain Replication license not found. | Cyber Recovery was unable to discover the Data Domain Replication license. | Contact your storage administrator or sales representative to acquire a Data Domain Replication license. |
2009 | Data Domain Retention Lock license not found. | Cyber Recovery was unable to discover the Data Domain Retention Lock license. | Contact your storage administrator or sales representative to acquire a Data Domain Retention Lock license. |
2010 | Unable to locate the Data Domain username that is associated with the production data user ID (uid). | For full access to the recovery sandbox for the application, there must be a user that matches the production data user ID (UID). |
|
2011 | Data Domain DD Boost is not enabled on the system. | To perform operations, Cyber Recovery requires that Data Domain DD Boost is enabled. |
|
2012 | The Data Domain storage system does not meet the minimum version supported by Cyber Recovery. | Cyber Recovery requires Data Domain version 6.2.1.50 or later. | Contact the Data Domain storage administrator to upgrade to Data Domain version 6.2.1.50 or later. |
2016 | There is an attempt to remove a recovery sandbox while a recovery is running. | A recovery of an application in the vault is a manual process that requires the user who initiated the recovery to mark the job as completed. |
|
2020 | The operation is taking more time than expected. | The Sync operation progress has breached the jobwindow timings. | Check the job status or cancel the job, if required. |
2021 | Operation canceled. | There is a request to cancel an operation. | Verify that the cancel operation was requested or successful. |
2023 | Error while restoring NetWorker server to its original state. | NetWorker server returned an error while performing recovery cleanup, the cleanup will continue. |
|
2027 | An error was detected while running PPDM recoverability check. | PPDM server returned an error while performing a recovery. | Verify the PPDM Data copy is recoverable. |
2028 | An error was detected while deleting sandbox. | Failed to delete sandbox completely. | Verify the status of sandbox. |
2029 | The recovery job was canceled by the user. | The recovery job was canceled by the user. | None required |
2030 | The synchronization operation is stopping due to exceeding the replication window limit and will complete the current replication snapshot. | The synchronization operation has breached the replication window limit and is stopping after finishing the current replication snapshot. | Set the replication window to a higher replication window time and rerun the synchronization operation on the policy. |
2033 | The Data Domain protection storage space is running low: | add disk space | Ensure that the Cyber Recovery maintenance schedule is running successfully and the copy deletion jobs are running successfully. |
2036 | A previous error has cleared while attempting to communicate with the DD system. | Connectivity with the DD management interface has been restored. | Investigate possible irregular network activity. |
2037 | Failed to delete copies, a job associated with the same policy already in progress. | Unable to delete copies associated with a policy having an associated job in progress. | Please wait for the job associated with the policy to complete and retry. |
2038 | Failed to delete copies with an active retention lock. | Unable to delete copies with an active retention lock. | Please wait for the lock retention period for the copy to be over and retry. |
2039 | File count exceeds 800 million files. | For optimal DD system performance, the number of files must be under 1 billion. | If the value for Cleanable GiB is sizable, reclaim space in the active tier file system by running clean/garbage collection. Alternatively, delete any MTrees that are not in use. |
2041 | The DD system uses 80% of the available MTrees. | Ensure that the maximum limit of MTrees on this DD system has not been reached. | Run a file system cleaning to purge the already deleted MTrees from your DD system. Identify and use the UI or CLI to delete or clean up:
Consider:
|
2043 | MTree file count exceeds 10 million files. | MTrees with greater than 10 million files can lead to performance issues. |
|