跳至內容
使用 AWS re:Post 即表示您同意 AWS re:Post 使用條款
AWS re:Postre:Post
關於 re:Post

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

2 分的閱讀內容
0

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

Short description

AWS Backup creates a job that provides details about the process when you back up your AWS resources. The CompleteWithin parameter is the period of time that your backup must completed. If the data transfer for the backup doesn't complete within this parameter, then AWS Backup stops the backup and shows the EXPIRED status. If this happens, then you get one of the following error messages:

  • "Backup Job did not complete within completion window"
  • "An AWS Backup job failed to complete in time"
  • "Backup job failed because there was a running job for the same resource"

The EXPIRED status is a final status, not a transitional status such as RUNNING. For more information about AWS Backup job statuses, see Backup job statuses.

Resolution

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.
主題
Storage
標籤
AWS Backup
語言
English
AWS 官方已更新 2 年前
3 評論

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.

回答 2 年前

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

AWS
管理員

回答 2 年前

I want to clarify the behavior in more detail:

Let's say you have a scheduled backup "A" that is currently running, and a scheduled backup "B" is scheduled to start at 2:00 PM with a 1-hour completion window.

At2:00 PM, scheduled backup "A" is still running. What happens is that scheduled backup "B" will not start immediately — it will wait for scheduled backup "A" to complete.

When scheduled backup "A" completes — let's say at 2:05 PM — scheduled backup "B" will then start. If it completes within its scheduled window, it will succeed. If it does not complete within the scheduled window, it will fail with the status EXPIRED and the following error:

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

AWS

回答 1 個月前

相關內容