Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws backup describe-backup-job BackupSizeInBytes and BytesTransferred are always 0 (short issue description) #330

Closed
orifinkelman opened this issue Aug 14, 2022 · 7 comments
Assignees
Labels
backup bug Something isn't working service-api This issue pertains to the AWS API

Comments

@orifinkelman
Copy link

orifinkelman commented Aug 14, 2022

Describe the bug

I am using aws-cli/2.7.22
Backup S3 buckets.
All my S3 backup jobs always show BackupSizeInBytes and BytesTransferred always show 0, even the first backup job shows 0.

Expected Behavior

I expected to get the full size of the bucket for BackupSizeInBytes for all backup jobs and the number of bytes transferred BytesTransferred according to the actual change in the bucket.

Current Behavior

When using describe-backup-job I am getting 0 for both fields. All other fields come out correct.
$ aws backup describe-backup-job --backup-job-id xxxxxxx-xxxx-xxxx-xxxx-xxxxxxx --output json
{
"AccountId": "XXXXXXXXXX",
"CreationDate": "2022-08-10T12:29:12.700000+03:00",
"CompletionDate": "2022-08-10T12:45:13.952000+03:00",
"State": "COMPLETED",
"PercentDone": "100.0",
"BackupSizeInBytes": 0,
"ResourceType": "S3",
"BytesTransferred": 0,
"StartBy": "2022-08-10T13:29:12.700000+03:00"
}

Reproduction Steps

  1. Create S3 bucket
  2. Upload a file to the bucket
  3. Create on-demand backup job for the s3 bucket and wait for it to complete.
  4. run aws backup describe-backup-job --backup-job-id --output json

Check the output

Possible Solution

none.

Additional Information/Context

No response

CLI version used

2.7.22

Environment details (OS name and version, etc.)

Reproduces on:
MacOS version 12.4

And on AWS Linux
NAME="Amazon Linux"
VERSION="2"
Architecture: aarch64

@tim-finnigan
Copy link

tim-finnigan commented Aug 15, 2022

Hi @orifinkelman thanks for reaching out. Do you mind sharing your debug logs (with any sensitive info redacted) by adding --debug to that command? That could give us more insight into what's going on.

I also saw this related issue on re:Post: https://repost.aws/questions/QUXJTlW8s2SfaAni037N04hA/how-to-see-s-3-backup-size. (Which you may have posted since that was also just created recently.) It's good to ask about service-related issues there too since someone more familiar with this topic might know the answer, so we can monitor the responses there as well.

@tim-finnigan tim-finnigan added response-requested This issue requires a response to continue service-api This issue pertains to the AWS API and removed needs-triage labels Aug 15, 2022
@orifinkelman
Copy link
Author

orifinkelman commented Aug 16, 2022

Hi @tim-finnigan attahced is the output with the --debug flag. Indeed I have posted to question on re:post, but didn't get any answer so I tried here as well. From playing around with other interfaces, I think this is not coming from the CLI as the log events emitted to CloudWatch are also showing 0. For example this is the completion log event for the same backup job I have sent the CLI output for. Note also that the same happens for the restore. The restore job describe and log event shows 0 bytes even though the restore itself is uccessful.

{
"version": "0",
"id": "7fb58f69-bcee-b03e-f967-dd22b841c4bd",
"detail-type": "Backup Job State Change",
"source": "aws.backup",
"account": "xxxxxxxxxx",
"time": "2022-08-14T11:23:32Z",
"region": "us-east-1",
"resources": [
"arn:aws:backup:us-east-1:xxxxxxxx:recovery-point:orif-just-for-test-xxxxxxxxx"
],
"detail": {
"backupJobId": "xxxxxxxxxxxx",
"backupSizeInBytes": "0",
"backupVaultArn": "arn:aws:backup:us-east-1:xxxxxxxxx:backup-vault:Default",
"backupVaultName": "Default",
"bytesTransferred": "0",
"creationDate": "2022-08-14T11:07:27.417Z",
"iamRoleArn": "arn:aws:iam::xxxxxxxxxxxx:role/service-role/AWSBackupDefaultServiceRole",
"resourceArn": "arn:aws:s3:::orif-just-for-test",
"resourceType": "S3",
"state": "COMPLETED",
"completionDate": "2022-08-14T11:15:28.816Z",
"startBy": "2022-08-14T12:07:27.417Z",
"percentDone": 100
}
}
describe-backup-job-debug.txt

@tim-finnigan
Copy link

Thanks @orifinkelman for following up and providing the logs. I also think this is an issue with the backup service so I'm going to transfer this over to our cross-SDK repository for tracking and reach out to the appropriate team. I'll update this issue when I hear back.

@tim-finnigan tim-finnigan removed the response-requested This issue requires a response to continue label Aug 17, 2022
@tim-finnigan tim-finnigan transferred this issue from aws/aws-cli Aug 17, 2022
@tim-finnigan
Copy link

P70186911

@tim-finnigan
Copy link

Hi @orifinkelman, I heard back from the service team and they said:

The AWS Backup team has investigated the concern raised regarding the recovery point showing Size as 0 bytes, we would like to inform that resources like S3 do not have the capability to show the incremental bytes of data of a specific backup and will display the value backupSizeInBytes as 0. Meanwhile we are working on a fix that would show the BytesTransferred within the Backup job report that will inform the size in bytes transferred to a backup vault at the time the job was queried.

If you have any further questions or comments regarding this matter, please contact us at http://aws.amazon.com/support.

Thanks again for bringing this to our attention. The fix related to BytesTransferred should be out in the near future. Feel free to check back in here for any updates or by pinging AWS Support as mentioned above.

@github-actions
Copy link

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@orifinkelman
Copy link
Author

Thanks @tim-finnigan, that would answer the need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backup bug Something isn't working service-api This issue pertains to the AWS API
Projects
None yet
Development

No branches or pull requests

2 participants