Instance recovery may fail if volume over 1024GB is restored.

• Related Articles

• Error on Instance recovery - Instance recovery failed: Failed checking snapshot availability

  Issue: Error - Instance recovery failed: Failed checking snapshot availability When running a recovery, first CPM downloads the data from the bucket, then it creates a temporary snapshot and then creates the instance. This error occurs when a timeout ...

• A c5 instance recovery from snapshot may fail

  If CPM didn't backup a c5 instance with initial ami (snapshots only), the recovery may fail with the following error: To recover a c5 instance you will need to use the AWS CLI to create an AMI to be used during recovery. The examples below are ...

• Recovery of an encrypted volume may fail: "Not authorized to use key"

  Performing a cross account recovery of an encrypted volume, or of an instance containing an encrypted volume may not work if the target account cannot access the encryption key from the source account. Error may appear in the CPM Server log as below: ...

• 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. Reference defect number - ff4e8ae447, ...

• 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 ...