Skip to content

Enabling continuous backup failed, because of the following error: Recovery Point is in state DELETING, and can not be updated

0

Hi,

I have the following status message in some RDS RecoveryPoints for which a continuous backup has been configured.

Here is a anonymized recoverypoint example:

BackupSizeInBytes : 0
BackupVaultArn : arn:aws:backup:eu-central-1:123456789012:backup-vault:swn-bvl-ec1-p-cs-default
BackupVaultName : bak-vault
CalculatedLifecycle : Amazon.Backup.Model.CalculatedLifecycle
CompletionDate : 11.03.2025 20:25:00
CompositeMemberIdentifier :
CreatedBy : Amazon.Backup.Model.RecoveryPointCreator
CreationDate : 11.03.2025 19:00:00
EncryptionKeyArn : arn:aws:kms:eu-central-1:123456789012:key/d4e227a1-b76c-3238-86ede-66a0ad574491
IamRoleArn : arn:aws:iam::123456789012:role/AWSBackupRole
IndexStatus :
IndexStatusMessage :
IsEncrypted : True
IsParent : False
LastRestoreTime : 01.01.0001 00:00:00
Lifecycle : Amazon.Backup.Model.Lifecycle
ParentRecoveryPointArn :
RecoveryPointArn : arn:aws:rds:eu-central-1:123456789012:snapshot:awsbackup:job-29c530cd-fa0b-7206-ed31-c47fa0ef13e5
ResourceArn : arn:aws:rds:eu-central-1:123456789012:db:rds-instance-1
ResourceName : db:rds-instance-1
ResourceType : RDS
SourceBackupVaultArn :
Status : COMPLETED
StatusMessage : Enabling continuous backup failed, because of the following error: Recovery Point arn:aws:backup:eu-central-1:123456789012:recovery-point:continuous:db-ojqofqxmjzrw4anwj4f3qadzyu-5369ecc6, is in state DELETING, and can not be updated
VaultType : BACKUP_VAULT

There are other RDS instances that have been configured with identical backup plans, backup rules, etc. where such a message does not appear.

How can I solve this problem?

Reagrds

Jan

asked 9 months ago268 views
2 Answers
0

The issue you're experiencing with enabling continuous backup for your RDS instance is likely related to a previous deletion attempt of a recovery point that hasn't fully completed. When a recovery point is in the DELETING state, it cannot be updated or modified, which is preventing the new continuous backup from being enabled.

To resolve this issue, you can try the following steps:

  1. Wait for 2-3 days: In some cases, AWS Backup might need additional time to complete the deletion process. Give it a few days to see if the status changes on its own.

  2. Check for expired recovery points: After waiting, look for any recently EXPIRED recovery points that resulted from your first manual deletion operation.

  3. Manually delete expired recovery points: If you find any EXPIRED recovery points, try to manually delete them through the AWS Backup console or API.

  4. Verify IAM permissions: Ensure that the IAM role used for AWS Backup operations has the necessary permissions, particularly the 'iam:CreateServiceLinkedRole' action. This permission allows AWS Backup to perform manual deletions.

  5. Modify the backup rule: If the issue persists, you might need to modify your existing backup rule to target a different backup vault temporarily. This could help bypass the conflicting recovery point.

  6. Create a new backup plan: As a last resort, you could create a new backup plan for the affected RDS instance, ensuring it uses a different backup vault.

If these steps don't resolve the issue, it's recommended to contact AWS Support for further assistance, as they can investigate the specific details of your account and the affected recovery points.

Remember that working with backups and recovery points requires careful consideration to avoid data loss. Always ensure you have proper backups before making any changes to your backup configuration.
Sources
Backup deletion - AWS Backup
RecoveryPointByResource - AWS Backup
AwsBackupRecoveryPointDetails - AWS Security Hub

answered 9 months ago
0

Hello Jan,

The issue you're experiencing with enabling continuous backup for your RDS instance is likely related to a previous deletion attempt of a recovery point that hasn't fully completed. When a recovery point is in the DELETING state, it cannot be updated or modified, which is preventing the new continuous backup from being enabled.

If you find the recovery point in the EXPIRED state, try manually deleting it through the AWS Backup console or by using the AWS CLI/API. You can use the following AWS CLI command to delete the recovery point: $ aws backup delete-recovery-point --backup-vault-name <vault-name> --recovery-point-arn <recovery-point-arn>

Please note that if the recovery point is in the EXPIRED state and not deleted, it can affect newer continuous backups. In such cases, the AWS Backup service will take a regular snapshot backup whenever it is unable to perform continuous backups for the RDS instance.

After the expired recovery point is deleted, the next scheduled backup run will again attempt to perform a continuous backup. At that point, the process should be able to execute successfully.

If these steps don't resolve the issue, I recommend reaching out to AWS Support for further assistance. They can investigate the specific details of your account and the affected recovery points to help you resolve this issue.

Sources https://repost.aws/knowledge-center/backup-recovery-point-expired

AWS
SUPPORT ENGINEER
answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.