N2WS-15684 - Cleanup issues using copy to S3

N2WS-15684 - Cleanup issues using copy to S3

Issue summary:

Policies with S3 backup enabled and backing up

(1) Independent volumes, and/or
(2) instances purchased from AWS marketplace

May result in premature deletion of S3 backups

Affected versions: 

  1. v3.1.0a, v3.1.0b 

Patch:

  1. Patch for 3.1.0b attached to this KB
Customer with 3.1.0a version first need to upgrade to 3.1.0b version before applying this patch

Interim resolution until fix is installed: 

  1. Increase the EBS snapshot retention period to be equal to the current S3 retention period.
  2. Increase the current S3 retention period by at least 1 month



    • Related Articles

    • Copy backup to S3 may fail with the error message "Workers could not be launched"

      During backup copy to S3 a worker creation may fail with the error (backup.log): - Error - Workers could not be launched The worker usually fails right after it was started. There are several possible issues that gives you this error. 1) The was an ...

    • N2WS-23140 - incorrect dr cleanup message

      Issue: during DR cleanup, there is an incorrect error message saying there might be issues because all backups succeeded. Cleanup did not mark any AWS dr backup for deletion for AWS policy testing. Only 7 of 7 dr backups completed successfully. ...

    • Copy to S3 fails after upgrade to 4.2.2

      Issue: Backup of snapshots to S3 bucket is failing after upgrade from 4.1 to 4.2.2 Solution: One possible reason for such an issue is the change in default behavior. In 4.2.2 we introduced the option to launch a worker with a IAM role attached to it. ...

    • Daily Summary/Cleanup Log may alert of false Cleanup issues

      You may receive the following warning in Daily Summary or Cleanup Log: Warning - Cleanup did not mark any backups for deletion for policy DailyPolicy, because out of 3 completed backups, only 1 were marked as successful This warning may be triggered ...

    • N2WS-21382 - S3 copy worker issues

      Issues: 1. In some rare cases, worker's volumes are not removed after worker instance is terminated 2. Unnecessary alert is raised when none default worker type is used: Worker i-12345 was launched for FLR as t2.micro, which may not an optimal ...