The following table lists the Cyber Recovery system alerts with a Warning severity.
Alert ID | Message Summary | Summary Details | Remedy |
---|---|---|---|
1012 | The policy cannot be modified at this time. | Cannot modify the policy because a job for the policy is running. | Verify that no jobs for the policy are running before you modify the policy. |
1013 | The vault is Secured. | The vault has been secured. No further operations can run at this time. |
|
1014 | Unable to perform the requested action for the policy. | There is already an active job for this action for this policy. |
|
1015 | Unable to remove the repository that is associated with the compliance-mode policy. | The repository that is associated with a compliance-mode policy cannot be deleted as the storage system prohibits deletion of a compliance-enabled repository. | There is no remedy. |
1017 | The Cyber Recovery license is about to expire. | The Cyber Recovery license is about to expire. |
|
1020 | Cyber Recovery Policy removed from the system. | The Cyber Recovery Policy has been removed from the system. |
|
1021 | Unable to start the Cyber Recovery job. | A job for this policy is currently running. | Wait for the current job to finish and then try again. If there is a schedule conflict, allow more time between schedules for the same policy. |
1022 | Unable to start the Cyber Recovery job. | The system is in an unknown state. | Verify all services are running. |
1023 | The system cleaning schedule encountered errors when removing expired resources. | The scheduled system cleanup job failed. The cleaning schedule encountered one or more errors when removing expired jobs, alerts, events, snapshots, copies or DR backups. |
|
1024 | Unable to set an SSH key on this host in the vault. | CR will use user account credentials to connect to the server host. |
|
1025 | The vault lock has been manually released. | The vault lock has been manually released. | Normal vault operations may now resume. Secure the vault if this release was not intended. |
1027 | Could not revert the virtual machine snapshot. | Could not revert the virtual machine snapshot during application recovery cleanup. |
|
1032 | Analysis capacity fully consumed. | Application selected for point-in-time copy analysis has reached licensed capacity for Analysis. | Ensure that the application selected for analysis has the correct licenses. |
1035 | Unable to perform to cancel request for analyze job. | The cancel request cannot be completed. | Analyze job may already completed for this copy. |
1036 | Unable to perform the server DR backup job. | The request to initiate the server DR backup job failed; one or more jobs might be in the Running or Canceling state. |
|
1039 | Unable to start the Cyber Recovery job. A disaster recovery backup is currently running. | Unable to start a Cyber Recovery job because a disaster recovery backup is currently running. | Wait for the current disaster recovery backup job to finish and then try again. If there is a schedule conflict, allow more time between the disaster recovery backup schedule and the policy schedule. |
1040 | Unable to start the Cyber Recovery job. The Cyber Recovery license is invalid. | The Cyber Recovery license is invalid. |
|
1041 | Password is about to expire. | Password is about to expire. | Update the password. |
1044 | Failed to send email due to incorrect configuration settings. | Failed to send email due to incorrect configuration settings. | Verify the mail server settings. |
1045 | The log is not included in the support bundle. | Check the details for more information about the failure log. | Verify that the data is available and that all Cyber Recovery services are up and running. |
1046 | Failed to create the complete support bundle. | Check the details for more information about the failure log. | Verify that the data is available and that all Cyber Recovery services are up and running. |
1047 | Failed to secure the complete support bundle. | Check the details for more information about the failure log. | Verify system permissions. |
1048 | Failed to remove support bundle. | Check the additional details for more information. | Verify the system permissions. |
1049 | The system detected and deleted an inconsistent support log bundle. | Check the additional details for more information. | Contact support if you continue to see this problem. |
1050 | The system cannot access support log bundle. | Check the additional details for more information. |
|
1053 | Unable to perform the multilink configuration job. | The request to initiate the multilink configuration job failed; A multilink configuration job for the same application asset might be in the Running or Canceling state. | Wait for the other multilink configuration job to complete then retry. |
1054 | Unable to create jobs report. | Failed to generate the report as no jobs found in specified time range. |
|
1060 | A multilink object definition, which was missing on the Cyber Recovery system, has been automatically configured on the Cyber Recovery system to match a configuration found on the CyberSense system. | The CyberSense monitoring thread detected that a multilink object definition exists on the CyberSense system but does not exist on the Cyber Recovery system. A multilink object definition was configured on the Cyber Recovery system to match the CyberSense system. |
|
1061 | Report recipient emails have restricted domains. | One or more report recipient emails specified have restricted domains. |
|
1066 | Unable to obtain CyberSense license information. | Failed to obtain CyberSense license information. |
|