- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
RDS instances might have maintenance windows or other backup operations (like automated snapshots) that could interfere with AWS Backup if they are scheduled around the same time.
Hello.
Do the tag values and keys set on the RDS instance match the resource selection settings set in AWS Backup?
Tag values are case sensitive and must match exactly.
Hi,
Do you have resource type parametrized in your config in addition to tag? In that case, resource type takes over:
see https://docs.aws.amazon.com/aws-backup/latest/devguide/assigning-resources.html
If both a resource type and tags are specified in a resource assignment, the resource type
specified in the backup plan takes priority over the tag condition. Service opt-in settings
are disregarded in this situation.
Best,
Didier
As a last resort, if Didier's suggestion does not pan out, I'd go back to Riku's suggestion about tag values. I have experienced situations where the tag values look EXACTLY the same, but one somehow has a space or some other thing in it that the display doesn't show. You can always manually re-type the tag value for the RDS that did not backup just to eliminate this possibility. Best.
Thanks all. With some testing, the problem is likely too close to the automated backup window configured in RDS instance.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 10 Monaten
- AWS OFFICIALAktualisiert vor 6 Monaten
Checked. It is all match
By the way, if I directly select RDS instead of the tag, won't a backup be created? If it is not retrieved, try changing the time when you perform the backup.
I try to create a "on-demand backup" for selective RDS. It's working. May I know why changing the time will make it work?
As @Mina Gobrial says, it may not work if it overlaps with the maintenance window. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html