Best Practices for S3 Backup
Failure to do so may result in excessive AWS charges, slow backup/restore, or failure to perform one.
Backup scripts may fail after upgrading to CPM 2.3.0
If you have partially successful backups after upgrading your CPM to v2.3.x or newer, please open the backup log and search for the below: Error - Could not find script "before_<Policy Name>", will continue without backup scripts If you have found ...
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 ...
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 ...
CPM may mark a backup as successful although not all snapshots succeeded
In case CPM marks a backup as successful but not all snapshots succeed, please upgrade to the latest 2.X.X version Reference defect number – N2WS-3578, fixed in v2.4.0 Link to Release Notes and the latest patch – ...
Backups may fail with "CPM Server identified this backup as orphaned: marking as failed" after upgrade to v2.3.x
Backups may fail with "CPM Server identified this backup as orphaned: marking as failed” error after upgrading to 2.3.0X and logs may show the below prints: update_request(agentapi_requests.py:<line_number>) failed calling url ...