Moving Policy Lifecycles to a Different Repository
Moving Policy Lifecycles to a Different Repository
Overview
This article provides the best procedure for moving policy lifecycles to a different storage repository in N2WS. It also addresses common questions regarding the impact of changing the storage repository linked to a policy.
Procedure to Move Policies Lifecycle
- Identify the Policy: Determine which backup policy you want to move to a new storage repository.
- Create a New Storage Repository (if required): Set up the new storage repository on N2WS where you want to future backups to go. For Steps on how to create a new repository click here: https://docs.n2ws.com/user-guide/21-managing-snapshots-with-lifecycle-policies#id-21-2-1-configuring-an-s3-repository
- Update the Backup Policy:
- Navigate to the "Policys" on N2WS.
- Select the policy you wish to change the storage repository for.
- Select "Lifecycle Management", scroll down until you see Storage Settings change the "target repository" to the one you created in step 2 as shown in the screenshot below:
- Verify the Change: Click "Save" and this will mean any copies to your storage repository going forward will be sent the new one.
Frequently Asked Questions
What will happen if I change a backup policy's storage repository?
When you change the storage repository linked to a backup policy, the policy will start using the new storage repository for any future backups from the time its changed.
What happens to the backups in the old storage repository?
All backups in the old storage repository remain intact and can still be restored, as long as they are not deleted from the storage repository.
Additional Notes
Decommissioning a Storage Repository: If you plan to decommission a storage repository, ensure that all necessary backups are either moved or that you have verified their accessibility from the new repository.
Backup Retention: Be mindful of your backup retention policies to avoid accidental deletion of important backups.
By following these steps, you can seamlessly transition your policy lifecycles to a new storage repository while maintaining access to your existing backups.
Important: never delete an S3 bucket from the AWS console, before deleting it from N2WS UI.
Related Articles
Backup to s3 may fail with error "Amazon REST error: 'S3 error: The operation is not valid for the object's storage class"
Backup to s3 may fail with error "Amazon REST error: 'S3 error: The operation is not valid for the object's storage class" In worker logs you may find this error: Amazon REST error: 'S3 error: The operation is not valid for the object's storage class ...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 ...Does CPM backup ephemeral storage?
The answer is no, CPM does not backup the ephemeral storage. CPM utilizes native AWS snapshots, and they do not support ephemeral storage. Ephemeral storage is not meant for persistent data. That said, in some setups, to leverage the speed of that ...Resolving Snapshot Restore Failures from Cold Storage, Error: "not all blocks were processed"
Issue During the process of restoring a snapshot from cold storage, the snapshot is successfully retrieved from cold storage to the hot tier (S3). However, the restore process may fail when retrieving from S3 to EBS with the following error: Worker ...Volume recovery may fail during File Level Restore with the “exceeded your maximum storage limit” error
Exploring a volume via Backup Monitor may fail with the following error: If you experience this error, you need to increase the total storage limit in this region for the type of storage mentioned in the error. In EC2 console, go to the desired ...