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 年前檢視次數 882 次
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 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南