Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error

• Related Articles

• Upgrade may fail with the "Failed labeling and mounting after 10 retries, giving up" and "Could not mount the new volume, returned: 256" errors

  Upgrade using AMI may fail with the following error in the file config_shell_commands.log: 2021-02-08 18:07:06,610: perform_shell_commands(:339)  Could not mount the new volume, returned: 256 2021-02-08 18:07:06,610: perform_shell_commands(:349)  ...

• "Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during CPM upgrade

  The following error message may be displayed when trying to upgrade the CPM instance using a new AMI: Could not attach volume vol-1234567890abcdef to instance i-abcdef0123456789. Reason: Cannot attach volume 'vol-1234567890abcdef' with Marketplace ...

• cpmdata policy might fail with error volume does not exist

  Issue: If the volumeID of the CPMDATA volume(EBS) changes (due to restoring CPM from snapshot for example),  This might cause the cpmdata policy to fail, still showing the old VolumeID: Solution: try to run cpmdata policy ASAP

• DR of encrypted snapshots may fail with the “No matching KMS alias” error

  DR of encrypted snapshots may fail with the following error in the Backup log: ERROR: start_copy_region(.\cpmserver\cpm\dr_volume.py:<line number>) Volume DR copy snapshot failed (in Backup account). No matching KMS alias on target region (source ...

• A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error

  A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error: Error - (instance: i-1234567890abcdef) could not get object from aws. Instance probably doesn't exist anymore ... Warning - Finished kicking off ...