Copy job failed — retention or cross-account mismatch
What AWS reports
destination backup vaulttarget backup vaultcross account copycross-account copysame organizationcopy job failedMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
A copy job fails when the retention requested is outside the destination vault’s allowed range, or when a cross-account copy is attempted between accounts that are not in the same AWS Organization.
How to fix it
- Set the copy’s retention within the destination vault’s min/max range.
- For cross-account copies, keep both accounts inside the same AWS Organization and share the destination vault/key.
- You are not billed for a failed copy job — no recovery point is created — so fix and retry freely.
What AWS documents
AWS states there is no charge when a copy job fails because no recovery point is created.
Source: AWS Backup Developer Guide — Metering & billing
Stop finding this one failure at a time
BackupLens watches every AWS Backup job across every region, matches each failure against this catalogue automatically, and sends you the cause and the fix — instead of a job list you have to read line by line at 3am.
Start free trial