The following table lists the Cyber Recovery storage alerts with a Critical severity.
Alert ID | Message Summary | Summary Details | Remedy |
---|---|---|---|
2001 | The vault is no longer in the unlocked state during data synchronization. | The vault is no longer unlocked during synchronization, probably because the Cyber Recovery admin secured the vault. The job status is Critical. |
|
2002 | Unable to initiate a Data Domain replication synchronization job. | An attempt to start a Data Domain replication synchronization job is unsuccessful. |
|
2003 | Unable to create a point-in-time copy. | An attempt was made to create a point-in-time copy in the Cyber Recovery retention lock repository. |
|
2004 | Unable to create a point-in-time copy due to an empty MTree | An MTree on the Data Domain is empty | Verify that the MTree on the Data Domain has at least one file to create a point-in-time copy |
2005 | Unable to connect to the storage system by using SSH. | Cyber Recovery requires the use of the SSH protocol to perform Data Domain operations. |
|
2006 | Unable to apply a retention lock timestamp to the point-in-time copy. | An attempt was made to apply a retention lock to the point-in-time copy. |
|
2013 | Unable to create the recovery sandbox. | Cyber Recovery was unable to create the requested recovery sandbox. |
|
2017 | An error was detected during data synchronization into the vault. | An error was detected while performing a replication status check for this Data Domain replication context. |
|
2018 | Unable to remove the contents of one or more point in time copies. | Cyber Recovery is unable to remove the contents of one or more point in time copies. |
|
2022 | Unable to initiate a job to monitor the Data Domain replication initial synchronization. | An attempt to start a job to monitor a Data Domain replication initial synchronization operation is unsuccessful. |
|
2024 | Possible malicious behavior has been detected. | It is possible that someone is doing something to cause harm to your system. |
|
2025 | Remote host identification has changed. | It is possible that remote host identification has changed due to an upgrade. | If remote host identification has changed due to an upgrade, complete the upgrade procedure. |
2026 | An error was detected during a vault storage validation. | An error was detected while performing a Data Domain status check for this Data Domain replication context. |
|
2031 | Unable to initiate a stop-replication job. | An attempt to start a stop-replication job is unsuccessful. |
|
2032 | Unable to initiate a start-replication job. | An attempt to start a start-replication job is unsuccessful. |
|
2034 | 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. |
2035 | An error was detected while attempting to communicate with the DD system | Unable to communicate with the DD management interface |
|
2040 | File count exceeds 900 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 |
2042 | The DD system uses 90% 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.
Consider:
|