Placing a life cycle policy on a bucket in AWS causes the S3 backups or recoveries to fail

Issue: 

Placing a lifecycle policy on a bucket in AWS causes the S3 backups or recoveries to fail.

Solution:

Placing a lifecycle policy on bucket in AWS using a bucket policy is not supported for bucket used to store snapshots.

If any object was moved to a different storage class, then you need to move them back to the standard storage class.

If objects were already deleted by the lifecycle policy on the bucket, then you will need to create a new full backup of the objects that were deleted.

To force a Full copy follow the steps below.

1. Open the policy

2. Go to backup targets tab -> select the instance

3. Check the below box to force a single full backup to S3:

• Related Articles

• Objects gets deleted manually from S3 bucket from AWS console.

  Issue: S3 backup objects in a bucket get deleted manually directly from the AWS account. For example, a user logs into AWS and deletes items stored in the bucket manually. Solution: This is not a supported method of deleting backups. You will need to ...

• EBS/RDS DR & Recovery with KMS key

  When copying cross account an EBS/RDS Volume encrypted with custom KMS, a KMS key should also be available in the other account. There are 2 ways that CPM uses for checking KMS key - Alias & Tag KMS Tag When using custom tag, you are telling CPM to ...

• N2WS-19716 - policy fails to load backup targets when region has EC2 with root volume

  Issue: When target region has an EC2 instance with instance-store root type volume, the policy will fails to load backup targets in the UI with following errors in UI: Failed to load some AWS instances data: KeyError: 'RootDeviceName' Solution: Patch ...

• N2WS-19829 - can't create S3 Repository for bucket located in enabled region with assume role account type

  Issue: When the S3 bucket is located in new/enabled region (such as Hong Kong for example), Then creating new S3 Repository will fail with the following error in UI Failed creating repository. Reason: ['Failed accessing the specified bucket ...

• Backups may fail with "CPM Server identified this backup as orphaned: marking as failed" after upgrade to v2.3.x

  Backups may fail with "CPM Server identified this backup as orphaned: marking as failed” error after upgrading to 2.3.0X and logs may show the below prints: update_request(agentapi_requests.py:<line_number>) failed calling url ...