N2WS-20379 - Possible invalid archive configuration
Issue:
Glacier Archive retention is calculated based on the original backup creation time (just like S3 retention), and not based on the time of the archive. This misunderstanding can lead customers to set archive retention lower than S3 retention, leading to backups being deleted immediately after moving to archive storage. For example if both S3 and Glacier are set to 1 year retention, then backup will be deleted immediately after moving to glacier - as the backup is already 1 year old.
Solution:
Patch for v4.0.0c is available and attached to this KB. This patch will check if the backup is configured to be deleted immediately after moving to Glacier by checking for a minimum effective archive period of 1 month(s), If it is below 1 month the patch will stop S3 cleanup and archive from being performed until
the configuration is fixed. The following alert will be raised in CPM:
Title (message subject): 'Invalid archive retention setup
detected'
Body: 'Archive retention setup of policy <policy
name> (delete when backup age > <X> months) is
invalid, because backups archived now will be deleted before a minimum archive
period of 1 month(s). S3 Archive and Cleanup for the policy will not be
performed until the configuration is fixed'
Click here to go back to the Release notes: Release notes for the latest v4.0.x CPM release
Related Articles
N2WS-13434 - Backup archived to Glacier disappears from the Backup Monitor
Issue summary Archive backups records might be deleted before their retention period. Issue description Backup record with archived/Glacier backup may be deleted prematurely by the clean-up operation, once it cleans all the snapshot and S3 backups ...N2WS-16181 - S3 backups may get deleted unexpectedly without being archived to Glacier
Issue summary: S3 backup policies with archive to Glacier enabled, and the S3 backups frequency equal to the frequency of moving expired S3 backups to Glacier (e.g. both set to "1"), may result in deletion of an expired S3 backup instead of archiving ...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 ...Upgrade instructions for v3.x/4.x
This guide outlines the steps required to upgrade to N2WS Backup & Recovery version 3.x/4.x We strongly recommend that you follow every step contained within this guide to ensure version 3.x/4.x is configured correctly and no data loss occurs. ...Patch for cost reduction of copy to S3
Installation of the patch will reduce costs drastically for customers who are using S3 (Between 5 to 20 times less expensive than previous version) The improvements are: For copied volumes which are larger than 512GB, worker’s volume type will be sc1 ...