N2WS-18084 - Volumes may be excluded from backup unexpectedly

• Related Articles

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

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

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

• N2WS-17670 - Worker volumes might not get deleted after S3 copy job

  Issue: Volume that are attached to a CPM worker might not get deleted after the S3 copy completes. Solution: Patch for v3.2.1 Available and attached to this KB Click here to go back to the Release notes: Release notes for the latest v3.2.x CPM ...

• N2WS-22641 - Backup stuck in progress when permission missing

  Issue: When 'ec2:DescribeNetworkInterface' permission is missing, all backups get stuck in progress ERROR: create_instance_record(record_management.py:507) Could not get primary network interface info ( instance: i-12345678, NIC: eni-9876543). ...