Why is my backup job in the EXPIRED status in AWS Backup?

3 minuto de leitura
0

I want to know why my backup job is stuck in the EXPIRED status in AWS Backup.

Resolution

When backing up your AWS resources, AWS Backup creates a backup job that provides details about the backup process. A backup job in the EXPIRED status indicates that the job initiated, but didn't complete within the CompleteWithin time. The EXPIRED status also indicates that there's a running job for the same resource. To check the status and details of a backup job, use the AWS Backup console or run the describe-backup-job AWS Command Line Interface (AWS CLI) command.

Note: If you receive errors when running AWS CLI commands, make sure that you're using the most recent AWS CLI version.

CompleteWithin parameter

The CompleteWithin parameter is the period of time that your backup must complete within. If the data transfer for the backup doesn't complete during the CompleteWithin time, then AWS Backup stops the backup and shows the EXPIRED status. You might see an error message similar to the following ones:

"Backup Job did not complete within completion window"

-or-

"An AWS Backup job failed to complete in time."

-or-

"Backup job failed because there was a running job for the same resource"

To update the CompleteWithin parameter, complete the following steps:

  1. Open the AWS Backup console.
  2. In the navigation pane, choose Backup plans.
  3. In the backup rule, choose Customize backup window.
  4. Increase or decrease the Complete Within value.
  5. Choose Save.

Note: The CompleteWithin parameter doesn't indicate that an AWS Backup job is completed within the specified time.

A running job for the same resource

If the backup job fails because of a running job for the same resource, you might see an error message similar to the following one:

"Backup job failed because there was a running job for the same resource."

To see a list of backup jobs in the RUNNING state, run the following list-backup-jobs AWS CLI command:

aws backup list-backup-jobs --by-state RUNNING

Or, to see a list of backup jobs in the RUNNING state by ARN, run the following AWS CLI command:

Note: Replace ResourceARN with your resource's ARN.

aws backup list-backup-jobs --by-resource-arn <ResourceARN> --by-state RUNNING

Review the list for the last completed job, and check if the backup job initiated at the same time.

To prevent backup jobs from running on the same resource, take the following actions:

  • Reduce the frequency of the backups in your backup rules.
  • Increase the time window for StartWithin and CompleteWithin parameters. To update these parameters, see the instructions in the preceding CompleteWithin parameter section.
AWS OFICIAL
AWS OFICIALAtualizada há 9 meses
2 Comentários

Could you clarify whether expired jobs get stopped by AWS?

Your two statements above seem contradictory

  1. The EXPIRED status also indicates that there's a running job for the same resource.
  2. If the data transfer for the backup doesn't complete during the CompleteWithin time, then AWS Backup stops the backup and shows the EXPIRED status.

Also, this is what's written in the info tip popup beside "Complete within" dropdown when you edit the backup rule under "Backup window" section:

If the data transfer for backing up your resource does not complete during this period of time, AWS Backup will display the status Expired. Otherwise, the data transfer portion of your backup job completed successfully. However, for particularly large backups, the rest of the backup process might take up to several days to complete and display the status Completed.

It seems to suggest the "expired" status is informational, the job will run till completion or failure and the status will change to a final status.

respondeu há 12 dias

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

profile pictureAWS
MODERADOR
respondeu há 9 dias