RDS Continuous Backup Plan Completed with Warning

0

Backup Job has a status of Completed, with the following warning.

Continuous Backup enable failed due to PITR already configured in backup plan: arn:aws:backup:us-west-1:xxxxxxxxxxxxxx:backup-plan:xxxxxx-xxxx-xxxx-xxxx-464cba39235e

This RDS resource backup was moved from another vault, onto a new backup plan. I thought the issue was the old backup plan still existed (it was unused), so I deleted it "xxxxxx-xxxx-xxxx-xxxx-464cba39235e". A week later, and I'm still getting the above.

Via the cli, I see there are versions of that old backup plan, but they are all tagged with a DeletionDate. I see no way to do a permanent removal of the backup plan versions. Aside from maybe deleting the old vault, which I cannot do, since we need to retain those backups.

This all started as we needed to move to a new unlocked vault to extend the retention period.

Any idea?

Byron70
質問済み 2年前884ビュー
1回答
0

Hello,

The error you are witnessing is expected. This is because at any given point in time, only one continuous recovery can be present for resource. Hence, when you create a new plan with new vault for creating any subsequent continuous backups for your RDS instance and AWS Backup finds an existing continuous recovery point in a different backup vault, it throws the error.

So, as to successfully migrate the recovery point to a new vault with help of backup plan. Apart from modifying the plan, you will also need to dissociate or delete the continuous recovery point present in your previous vault. Detailed steps on the same can be found under the heading "Managing continuous backup settings" in below document.

[+] Managing continuous backup settings : https://docs.aws.amazon.com/aws-backup/latest/devguide/point-in-time-recovery.html#point-in-time-considerations

[+] CLI reference : https://awscli.amazonaws.com/v2/documentation/api/latest/reference/backup/disassociate-recovery-point.html

Thus, you do not need to delete the entire vault but just the previous continuous recovery point. Once the concerned recovery point has been successfully deleted/dissociated from the previous backup vault, you should not witness this error.

AWS
サポートエンジニア
回答済み 1年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン