Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

Dell PowerProtect Cyber Recovery 19.14 Alerts Reference Guide

PDF

Critical storage alerts

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.
  1. Review alerts to determine when the vault was secured
  2. Contact the Cyber Recovery admin who secured the vault to coordinate the release of the vault
  3. Run the synchronization again
2002 Unable to initiate a Data Domain replication synchronization job. An attempt to start a Data Domain replication synchronization job is unsuccessful.
  1. Verify that Data Domain credentials were not updated
  2. Verify the health of the Data Domain storage system: DD Boost, Network, Filesystem status
  3. Verify connectivity from the Cyber Recovery Management Host to this Data Domain storage system.
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.
  1. Verify that the Data Domain DD Boost license is enabled.
  2. Verify that the DD Boost feature is enabled
  3. Ensure that the maximum limit of MTrees on this Data Domain has not been reached
  4. Verify that there is enough storage available to complete the point-in-time copy
  5. Verify the replicated mtree is not empty
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.
  1. Verify that the Data Domain storage system username and password are correct
  2. Verify that the storage system is accessible.
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.
  1. Verify that the amount of time specified is within the retention lock minimum and maximum settings for the policy
  2. Verify that the Data Domain Retention Lock license is enabled and is not expired
2013 Unable to create the recovery sandbox. Cyber Recovery was unable to create the requested recovery sandbox.
  1. Verify that DD Boost is enabled
  2. Verify the Data Domain storage system credentials.
  3. Ensure that the maximum number of MTrees has not been reached
  4. Determine if a sandbox with the same name exists on the Data Domain Storage system.
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.
  1. Check the alerts on the Data Domain system for any related alerts.
  2. Check network and storage status on the Data Domain system.
  3. Retry the synchronization.
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.
  1. Determine if there are any permission issues removing the contents.
  2. Verify the filesystem mounts on the Cyber Recovery system.
  3. Verify that NFS network ports are available on both the Data Domain and Cyber Recovery systems.
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.
  1. Verify that Data Domain credentials were not updated.
  2. Verify the health of the Data Domain storage system: DD Boost, Network, Filesystem status.
  3. Verify connectivity from the Cyber Recovery Management Host to this Data Domain storage system.
2024 Possible malicious behavior has been detected. It is possible that someone is doing something to cause harm to your system.
  1. Please contact your security officer to remediate the issue.
  2. Fingerprint is required to be reset if Data domain FQDN changes
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.
  1. Check the alerts on the Data Domain system for any related alerts.
  2. Check network and storage status on the Data Domain system.
2031 Unable to initiate a stop-replication job. An attempt to start a stop-replication job is unsuccessful.
  1. Verify that start-replication job is running.
  2. Verify the vault is not in secure state.
  3. Verify connectivity from the Cyber Recovery Management Host to this Data Domain storage system.
2032 Unable to initiate a start-replication job. An attempt to start a start-replication job is unsuccessful.
  1. Verify the vault is not in secure state.
  2. Verify connectivity from the Cyber Recovery Management Host to this Data Domain storage system.
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
  1. Check network status on the DD system.
  2. Check the alerts on the DD system for any related alerts.
  3. Verify network connectivity between the Cyber Recovery system and the DD system.
  4. Verify that password has not been locked out on DD.
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.
  • Any active sandboxes or recovery sandboxes that are no longer needed.
  • Any policies that are no longer being used; you can delete policies when copies age out and are removed.
  • Replication targets that are not being used in policies and are not planned to be used.
  • Sandbox MTrees that are no longer in sync with Cyber Recovery.
  • Test MTrees that are no longer being used.

Consider:

  • Moving replication targets (policies) to another existing vault DD system with additional MTree capacity.
  • Adding capacity to the Data Domain.
  • Adding a new vault DD system.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\