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 for that record.
As a result, a recovery of the archive backup will not be possible.
In addition, while restore is not possible, the data is still stored in Glacier
Affected versions
3.0.0, 3.0.0a
Fix version
3.0.0b - Not Available yet

An announcement will be sent once patch is ready and the release note will be updated.
Workaround
Increase S3 retention time and/or generation to avoid
moving backup to Glacier until 3.0b is available
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 ...
Patch for slow loading of backup monitor after upgrade to 2.4.0
Customers with a large number of backup history records may notice slower loading of the "Backup Monitor" view after upgrading to 2.4.0 If you are seeing this issue, please update to the latest version of CPM, v2.5.0 Reference defect number – ...
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 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. When using ...