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
A backup record that contains
- Only archived backup(s), and
- Does not contain AWS snapshots nor S3 backups or cleanup process deleted all the required AWS snapshot (and now the backup records contain ONLY archive backup)
Will be deleted by the cleanup operation, the deletion of the backup record might occur before the archive backup
retention period.
As a result, a recovery of the archive backup will not be possible.
Affected versions
3.0.0, 3.0.0a
Fix version
3.0.0b
Related Articles
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 ...
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 ...
N2WS-22950 - data mismatch between EBS recovered and Glacier recovered volumes
Issue: when recovering a snapshot that has been moved to cold storage (archived), in rare situations, the recovered data may be different than the original data. Note: S3 backups are not affected Solution: v4.2.0 & v4.2.1: Patch is available and ...
Warning - Glacier restoration cost
When restoring backups from glacier, The data must first be copied to S3 (‘retrieved’) before it can be accessed. You need to be careful about the restoration cost, which can be affected by the selected Tier and days to keep From our user guide: The ...
How to upgrade CPM using a patch
Please note: upgrading using patch does not upgrade Apache/OS Upgrade Diagram General 1. It is recommended to deploy the patch when you have no active backup policies, DR or recovery running. as it will restart Apache and require few min downtime. 2. ...