Best Practices for S3 Backup

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.

    • Related Articles

    • 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 ...

    • 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 ...

    • 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 ...

    • 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 – ...

    • Backup may fail after approximately 30 minutes

      If backup fails after approximately 30 minutes, please check the Backup Log for the following prints: ERROR: check_keep_alive_delinquents(.\cpmagent\record_management.py:<line_number>) Found stuck backup of policy <policy_name>, has not responded for ...