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 contains valuable data, it is a
best practice to create a snapshot of the volume that contains it in case you
need to roll back your changes
Below are the steps for resizing the cpmdata volume.
- Go to EC2
console, Volumes tab.
- Find the CPM
Cloud Protection Manager Data volume
- Click Actions, Modify Volume and change it to the desired volume size.
- SSH into
CPM,
- Type lsblk to see that the volume was modified to the desired size. In
the example below it is named as xvdf and it was changed to 10G.
- Type df -h to see the volume named /cpmdata and its filesystem path.
You should notice that it is still using the former size.
- To
increase the size of fs type the command resize2fs <path of
cpmdata>. In the example that would be sudo resize2fs /dev/xvdf
- Type df -h again to confirm that size changed to the full volume's
size.
Related Articles
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 ASAPBackup 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 ..."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 ...Recommended instance sizes and volume types for CPM Server instances
EC2 Instance sizing guidelines Here are the recommended instance sizes for CPM Server instances: Up to 200 instances - T3.medium Up to 500 instances - M5.large, C5.large, R5.large, C6i.large, R6i.large, M6i.large, C7i.large, M7i.large Up to 1000 ...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 ...