Failed backups may not be retried if schedule is limited to certain days of the week

• Related Articles

• Backups may fail without being retried

  If a Backup policy has failed and the following conditions are met: Number of retries defined in the policy is not zero. Start time of the backup is the original scheduled start time. Retry Interval (“Wait between Retries (in minutes)”) has passed ...

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

• Some backups may not run on schedule while other backups still run using the same schedule

  Some backups may stop running on their scheduled time although other backups which use the same schedule do run and Run ASAP works. If you face this issue, please upgrade to the latest 2.3.x version. Reference defect number – N2WS-1633, fixed in ...

• Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error

  RDS DR backup of encrypted snapshots between different regions may fail with the following error in the Backup log: Error - RDS DR, copy snapshot failed (to DR account) due to an AWS limitation regarding default encryption key (source US East (Ohio), ...

• S3 backups may be stored for X days instead of X months

  Issue description: When creating or editing a policy with S3 backup enabled and the default GUI time retention unit in the “Keep backup in S3 for at least” section is not changed, S3 backup retention time will be stored internally as “Days” instead ...