Best practice for S3 backups' frequency and retention
S3 backups are meant for low-frequency (weekly, monthly, yearly), long-term (over 3 months) retention backups.
You can see our recommendation for S3 backup here: https://n2ws.com/wp-content/uploads/2019/02/N2WS-quick-guide-optimize-backups-S3.pdf
Not following these recommendation will actually cost you money, instead of saving.
Also, running S3 backup daily may cause failures, as S3 backup/cleanup is a time consuming process, which may take over 24 hours.
Related Articles
Best Practices for S3 Backup
We strongly recommend to configure S3 backup according to https://docs.n2ws.com/user-guide/appendix-a-recommended-configuration-for-copy-to-s3 Failure to do so may result in excessive AWS charges, slow backup/restore, or failure to perform one.How cleanup works and why it might not delete snapshots older than the defined retention setting.
Background This KB Article will explain how the cleanup process works and why sometimes cleanup might not delete old snapshots It includes following sections: About the cleanup process Why Cleanup might not delete old snapshots Examples About the ...Copy backup to S3 may fail with the error message "Workers could not be launched"
During backup copy to S3 a worker creation may fail with the error (backup.log): - Error - Workers could not be launched The worker usually fails right after it was started. There are several possible issues that gives you this error. 1) The was an ...Cleanup may not delete snapshots older than the defined retention for the policy
CPM removes the snapshots in accordance with defined retention policies. However, only successful backups are counted towards the retention. It is crucial to understand what a "successful backup" is. A "successful backup" is a backup that has both ...N2WS-21963 - Copy to S3 fails with Failed to stop processor(s)
Issue: Copy to S3 is failing with following error ERROR: add_error(segment_handler.py:322) copy of md table of segment 1 of volume vol-12345678, instance i-0987654321, backup 123 fail : Failed to stop processor(s): not all blocks were processed ...