N2WS-18084 - Volumes may be excluded from backup unexpectedly

• Related Articles

• DR may fail due to the “Volume DR Failed getting volumes info” and “RequestLimitExceeded” errors

  If DR fails with the below errors in Backup log ERROR: check_region_copy_state(.\cpmserver\cpm\dr_volume.py:<line_number>) Volume DR Failed getting volumes info in region <Region name> (policy <Policy Name>,in Backup account), Exception: ...

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

• N2WS-23418 - Incorrect display of scheduled exclude time

  Issue: Schedule UI is might show incorrect exclude time In addition, the the enabled/disabled toggle will show off even when enabled, Solution: v4.2.2 - install attached patch: ...

• Error "create multi-volume snapshots of instance i-123456789 failed" may occur during backup

  Error: You might see this error in the cpm server logs or the UI Alerts when running backups in CPM 3.0 and above: create multi-volume snapshots of instance i-123456789 failed. Error: You are not authorized to perform this operation. Encoded ...

• CPM configuration may fail with the error: "Could not attach volume %vol-id% to instance %Id% Reason: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use"

  Issue: CPM configuration may fail with the error: "Could not attach volume %vol-id% to instance %Id% Reason: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use" ERROR:  done(views.py:181)  Could not attach volume ...