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
Related Articles
Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error
Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error: Error - snapshot of independent volume vol-0123456789abcdef failed to start. Reason: The volume 'vol-0123456789abcdef' does not exist This error may ...Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into CPM server log during the tag scanning operation
The following may be printed into the CPM server log during the tag scanning operation: ERROR: manage_account_tagged_resources(.\cpmserver\cpm\backup_tag.py:336) Policy_Name doesn't exist/attached to account To resolve: Find error in CPM server logs, ...Resizing the cpmdata volume
Resizing the cpmdata volume is done like any other ec2 instance. The general procedure can be found here - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html IMPORTANT - Before extending a file system that ...cpmdata volume disk usage growth due to binlog
Background: In version 4.2.x, we have upgraded MySQL DB from version 5 to version 8, this changed the default parameter that determines how many binlog file to keep from 10 days to 30 days. This might result in increase in the size the MySQL DB take ...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 ...