Volume/instance restore may fail with Exception "The volume vol-12345678 does not exist"
If Volume/instance restore of an existing volume fails with the following exception in the Recovery log:
"Exception: The volume '<volume-id>' does not exist", please upgrade to latest 2.X.X to resolve the issue.
defect number - ff4e8ae447, fixed in v2.1.3.
Instance restore may be marked "successful", despite failing to restore a volume
Issue: A cross account restore of an encrypted volume or instance may be marked successful, however a Volume has failed to restore. Fix: If you face this issue, please upgrade to latest 2.X.X version Reference defect number – N2WS-1168, fixed in ...
Volume Snapshot may fail with error "The maximum per volume CreateSnapshot request rate has been exceeded"
Volume Snapshots may fail with the following errors in the log files. backup log 02-12-20 11:07:22 - Error - create snapshot of instance volume vol-xxxxxxxxxxxxx failed. 02-12-19 11:07:22 - Error - snapshot of instance ec2-xxxxxxxxx-xxxx-xx, volume ...
CPM may restore "AMI only" snapshots with wrong volume type
When restoring a snapshot from an "AMI only" policy, CPM may restore the snapshot with a wrong volume type. If you face this issue, please upgrade to latest 2.X.X version Reference defect number – N2WS-1711, fixed in v2.3.0c Link to Release Notes and ...
Exception may occur when trying to recover an instance using CPM CLI
When trying to recover an instance, volume or DB using CPM_CLI, recovery mail fail with an exception If you face this issue when performing non-DR recovery, please upgrade to latest 2.X.X version Reference defect number - 83ec3dd251, fixed in ...
File-level restore may fail with the "Could not get CPM instance info" error
File-level restore may fail with the "Could not get CPM instance info" error: The following error is printed in the CPM server log: ERROR: explore_backup_init(.\cpmserver\cpm\filemanager\views.py:317) Could not get CPM instance info ...