AWS Glacier inventory is either wrong or asynchronous?Backing up data stored on Amazon S3Server incremental backup to AWS GlacierAnsible AWS dynamic inventory: `./ec2.py --list` unauthorizedHow get back losts archive_ids of AWS Glacier vaultAWS - ELB - Puppet - Must not contain unprintable charactersUpload to S3 bucket slows over timeAmazon Glacier Job Inventory Download Not AvailableAWS Cost for Uploading to S3 and immediately transitioning to glacierMove files between Azure and S3/GlacierCloudberry Glacier items re-appear after deletion
Could a rotating ring space station have a bolo-like extension?
If I arrive in the UK, and then head to mainland Europe, does my Schengen visa 90 day limit start when I arrived in the UK, or mainland Europe?
ifconfig shows UP while ip link shows DOWN
Why is this integration method not valid?
Is it normal to "extract a paper" from a master thesis?
How to deceive the MC
Physical only checkdb is failing, but full one is completed successfully
Visual Block Mode edit with sequential number
Why is std::ssize() introduced in C++20
Why does the painters tape have to be blue?
Who were the members of the jury in the Game of Thrones finale?
How do you earn the reader's trust?
How to find sum of maximum K elements in range in array
Alexandrov's generalization of Cauchy's rigidity theorem
How to remove new line added by readarray when using a delimiter?
Why does Bran want to find Drogon?
Did Game of Thrones end the way that George RR Martin intended?
Navigating a quick return to previous employer
Goldfish unresponsive, what should I do?
Testing using real data of the customer
What did Brienne write about Jaime?
Piping the output of comand columns
Are cells guaranteed to get at least one mitochondrion when they divide?
Is it safe to redirect stdout and stderr to the same file without file descriptor copies?
AWS Glacier inventory is either wrong or asynchronous?
Backing up data stored on Amazon S3Server incremental backup to AWS GlacierAnsible AWS dynamic inventory: `./ec2.py --list` unauthorizedHow get back losts archive_ids of AWS Glacier vaultAWS - ELB - Puppet - Must not contain unprintable charactersUpload to S3 bucket slows over timeAmazon Glacier Job Inventory Download Not AvailableAWS Cost for Uploading to S3 and immediately transitioning to glacierMove files between Azure and S3/GlacierCloudberry Glacier items re-appear after deletion
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Using Boto3, I uploaded 12 files to Amazon's Glacier last night at 21:43 EST.
I received ArchiveID's for all 12 files, so I assume they uploaded correctly.
According the the AWS management console, the most recent inventory was run at 02:53 EST this morning. So about 5 hours after upload.
But the inventory does not show those 12 files. There is only 1 file (that I uploaded 1 week ago).
I know I have to wait another day for the next AWS Inventory to run, but I thought I'd ask if this is expected behavior?
Does the time amazon calculated/reported time of the Inventory not really match when it was run? Is it possible the inventory actually ran before I uploaded those files?
If not, why would I get archiveID's (indicating successful upload) but they aren't listed in an intentory run AFTER they were uploaded?
Edit:
The files did show up on the next inventory.
But I'm still curious why the time of the 'Last Inventory' in AWS Console which was 5 hours after upload reported zero files. My only explanation is that the 'Last Inventory' time of the AWS Console is when the information was uploaded to the AWS Console. But that the ACTUAL inventory could have run hours earlier (hence it missed the recently uploaded files).
amazon-web-services amazon-glacier
asked Feb 2 '17 at 14:02
NertskullNertskull
163
add a comment |
Using Boto3, I uploaded 12 files to Amazon's Glacier last night at 21:43 EST.
I received ArchiveID's for all 12 files, so I assume they uploaded correctly.
According the the AWS management console, the most recent inventory was run at 02:53 EST this morning. So about 5 hours after upload.
But the inventory does not show those 12 files. There is only 1 file (that I uploaded 1 week ago).
I know I have to wait another day for the next AWS Inventory to run, but I thought I'd ask if this is expected behavior?
Does the time amazon calculated/reported time of the Inventory not really match when it was run? Is it possible the inventory actually ran before I uploaded those files?
If not, why would I get archiveID's (indicating successful upload) but they aren't listed in an intentory run AFTER they were uploaded?
Edit:
The files did show up on the next inventory.
But I'm still curious why the time of the 'Last Inventory' in AWS Console which was 5 hours after upload reported zero files. My only explanation is that the 'Last Inventory' time of the AWS Console is when the information was uploaded to the AWS Console. But that the ACTUAL inventory could have run hours earlier (hence it missed the recently uploaded files).
amazon-web-services amazon-glacier
asked Feb 2 '17 at 14:02
NertskullNertskull
163
add a comment |
Using Boto3, I uploaded 12 files to Amazon's Glacier last night at 21:43 EST.
I received ArchiveID's for all 12 files, so I assume they uploaded correctly.
According the the AWS management console, the most recent inventory was run at 02:53 EST this morning. So about 5 hours after upload.
But the inventory does not show those 12 files. There is only 1 file (that I uploaded 1 week ago).
I know I have to wait another day for the next AWS Inventory to run, but I thought I'd ask if this is expected behavior?
Does the time amazon calculated/reported time of the Inventory not really match when it was run? Is it possible the inventory actually ran before I uploaded those files?
If not, why would I get archiveID's (indicating successful upload) but they aren't listed in an intentory run AFTER they were uploaded?
Edit:
The files did show up on the next inventory.
But I'm still curious why the time of the 'Last Inventory' in AWS Console which was 5 hours after upload reported zero files. My only explanation is that the 'Last Inventory' time of the AWS Console is when the information was uploaded to the AWS Console. But that the ACTUAL inventory could have run hours earlier (hence it missed the recently uploaded files).
amazon-web-services amazon-glacier
asked Feb 2 '17 at 14:02
NertskullNertskull
163
Using Boto3, I uploaded 12 files to Amazon's Glacier last night at 21:43 EST.
I received ArchiveID's for all 12 files, so I assume they uploaded correctly.
According the the AWS management console, the most recent inventory was run at 02:53 EST this morning. So about 5 hours after upload.
But the inventory does not show those 12 files. There is only 1 file (that I uploaded 1 week ago).
I know I have to wait another day for the next AWS Inventory to run, but I thought I'd ask if this is expected behavior?
Does the time amazon calculated/reported time of the Inventory not really match when it was run? Is it possible the inventory actually ran before I uploaded those files?
If not, why would I get archiveID's (indicating successful upload) but they aren't listed in an intentory run AFTER they were uploaded?
Edit:
The files did show up on the next inventory.
But I'm still curious why the time of the 'Last Inventory' in AWS Console which was 5 hours after upload reported zero files. My only explanation is that the 'Last Inventory' time of the AWS Console is when the information was uploaded to the AWS Console. But that the ACTUAL inventory could have run hours earlier (hence it missed the recently uploaded files).
amazon-web-services amazon-glacier
amazon-web-services amazon-glacier
asked Feb 2 '17 at 14:02
NertskullNertskull
163
asked Feb 2 '17 at 14:02
NertskullNertskull
163
edited Feb 7 '17 at 12:17
Nertskull
asked Feb 2 '17 at 14:02
NertskullNertskull
163
asked Feb 2 '17 at 14:02
NertskullNertskull
163
asked Feb 2 '17 at 14:02
NertskullNertskull
163
163
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
When you initiate a job for a vault inventory, Amazon Glacier returns the last inventory it generated, which is a point-in-time snapshot and not real-time data.
http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html
Asking for an inventory apparently doesn't trigger the actual generation -- it just preps the last inventory for fetching.
Inventories are updated approximately once every 24 hours, so there's a good chance of those new files not appearing in the timetable you describe.
Unless you're interested in features only available through the Glacier API, like vault locks, you may find the S3/Glacier integration provides a more useful interface. Files uploaded as S3 objects and then transitioned to the Glacier storage class by lifecycle policies are not visble through the Glacier API -- they continue to appear as S3 objects, making it more straightforward to iterate through them and their metadata, all of which is effectively in real time.
answered Feb 3 '17 at 2:15
Michael - sqlbotMichael - sqlbot
16.5k3563
That doesn't answer the question. The inventory generation time reported on Amazon's AWS Console Management was 5 hours after the files were uploaded. This has nothing to do with initiating vault inventory retrievals or downloading inventories. I'm only talking about the Console Management information for the last inventory, which ran 5 hours AFTER the files were uploaded, yet reports zero files. It appears the time reported in AWS Console Management of the 'Last Inventory' may not be the ACTUAL time it was run, but instead the time it was 'posted' to my AWS Console.
– Nertskull
Feb 7 '17 at 12:15
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f830146%2faws-glacier-inventory-is-either-wrong-or-asynchronous%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When you initiate a job for a vault inventory, Amazon Glacier returns the last inventory it generated, which is a point-in-time snapshot and not real-time data.
http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html
Asking for an inventory apparently doesn't trigger the actual generation -- it just preps the last inventory for fetching.
Inventories are updated approximately once every 24 hours, so there's a good chance of those new files not appearing in the timetable you describe.
Unless you're interested in features only available through the Glacier API, like vault locks, you may find the S3/Glacier integration provides a more useful interface. Files uploaded as S3 objects and then transitioned to the Glacier storage class by lifecycle policies are not visble through the Glacier API -- they continue to appear as S3 objects, making it more straightforward to iterate through them and their metadata, all of which is effectively in real time.
answered Feb 3 '17 at 2:15
Michael - sqlbotMichael - sqlbot
16.5k3563
That doesn't answer the question. The inventory generation time reported on Amazon's AWS Console Management was 5 hours after the files were uploaded. This has nothing to do with initiating vault inventory retrievals or downloading inventories. I'm only talking about the Console Management information for the last inventory, which ran 5 hours AFTER the files were uploaded, yet reports zero files. It appears the time reported in AWS Console Management of the 'Last Inventory' may not be the ACTUAL time it was run, but instead the time it was 'posted' to my AWS Console.
– Nertskull
Feb 7 '17 at 12:15
add a comment |
When you initiate a job for a vault inventory, Amazon Glacier returns the last inventory it generated, which is a point-in-time snapshot and not real-time data.
http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html
Asking for an inventory apparently doesn't trigger the actual generation -- it just preps the last inventory for fetching.
Inventories are updated approximately once every 24 hours, so there's a good chance of those new files not appearing in the timetable you describe.
Unless you're interested in features only available through the Glacier API, like vault locks, you may find the S3/Glacier integration provides a more useful interface. Files uploaded as S3 objects and then transitioned to the Glacier storage class by lifecycle policies are not visble through the Glacier API -- they continue to appear as S3 objects, making it more straightforward to iterate through them and their metadata, all of which is effectively in real time.
answered Feb 3 '17 at 2:15
Michael - sqlbotMichael - sqlbot
16.5k3563
That doesn't answer the question. The inventory generation time reported on Amazon's AWS Console Management was 5 hours after the files were uploaded. This has nothing to do with initiating vault inventory retrievals or downloading inventories. I'm only talking about the Console Management information for the last inventory, which ran 5 hours AFTER the files were uploaded, yet reports zero files. It appears the time reported in AWS Console Management of the 'Last Inventory' may not be the ACTUAL time it was run, but instead the time it was 'posted' to my AWS Console.
– Nertskull
Feb 7 '17 at 12:15
add a comment |
When you initiate a job for a vault inventory, Amazon Glacier returns the last inventory it generated, which is a point-in-time snapshot and not real-time data.
http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html
Asking for an inventory apparently doesn't trigger the actual generation -- it just preps the last inventory for fetching.
Inventories are updated approximately once every 24 hours, so there's a good chance of those new files not appearing in the timetable you describe.
Unless you're interested in features only available through the Glacier API, like vault locks, you may find the S3/Glacier integration provides a more useful interface. Files uploaded as S3 objects and then transitioned to the Glacier storage class by lifecycle policies are not visble through the Glacier API -- they continue to appear as S3 objects, making it more straightforward to iterate through them and their metadata, all of which is effectively in real time.
answered Feb 3 '17 at 2:15
Michael - sqlbotMichael - sqlbot
16.5k3563
When you initiate a job for a vault inventory, Amazon Glacier returns the last inventory it generated, which is a point-in-time snapshot and not real-time data.
http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html
Asking for an inventory apparently doesn't trigger the actual generation -- it just preps the last inventory for fetching.
Inventories are updated approximately once every 24 hours, so there's a good chance of those new files not appearing in the timetable you describe.
Unless you're interested in features only available through the Glacier API, like vault locks, you may find the S3/Glacier integration provides a more useful interface. Files uploaded as S3 objects and then transitioned to the Glacier storage class by lifecycle policies are not visble through the Glacier API -- they continue to appear as S3 objects, making it more straightforward to iterate through them and their metadata, all of which is effectively in real time.
answered Feb 3 '17 at 2:15
Michael - sqlbotMichael - sqlbot
16.5k3563
answered Feb 3 '17 at 2:15
Michael - sqlbotMichael - sqlbot
16.5k3563
answered Feb 3 '17 at 2:15
Michael - sqlbotMichael - sqlbot
16.5k3563
answered Feb 3 '17 at 2:15
Michael - sqlbotMichael - sqlbot
16.5k3563
16.5k3563
That doesn't answer the question. The inventory generation time reported on Amazon's AWS Console Management was 5 hours after the files were uploaded. This has nothing to do with initiating vault inventory retrievals or downloading inventories. I'm only talking about the Console Management information for the last inventory, which ran 5 hours AFTER the files were uploaded, yet reports zero files. It appears the time reported in AWS Console Management of the 'Last Inventory' may not be the ACTUAL time it was run, but instead the time it was 'posted' to my AWS Console.
– Nertskull
Feb 7 '17 at 12:15
add a comment |
That doesn't answer the question. The inventory generation time reported on Amazon's AWS Console Management was 5 hours after the files were uploaded. This has nothing to do with initiating vault inventory retrievals or downloading inventories. I'm only talking about the Console Management information for the last inventory, which ran 5 hours AFTER the files were uploaded, yet reports zero files. It appears the time reported in AWS Console Management of the 'Last Inventory' may not be the ACTUAL time it was run, but instead the time it was 'posted' to my AWS Console.
– Nertskull
Feb 7 '17 at 12:15
That doesn't answer the question. The inventory generation time reported on Amazon's AWS Console Management was 5 hours after the files were uploaded. This has nothing to do with initiating vault inventory retrievals or downloading inventories. I'm only talking about the Console Management information for the last inventory, which ran 5 hours AFTER the files were uploaded, yet reports zero files. It appears the time reported in AWS Console Management of the 'Last Inventory' may not be the ACTUAL time it was run, but instead the time it was 'posted' to my AWS Console.
– Nertskull
Feb 7 '17 at 12:15
That doesn't answer the question. The inventory generation time reported on Amazon's AWS Console Management was 5 hours after the files were uploaded. This has nothing to do with initiating vault inventory retrievals or downloading inventories. I'm only talking about the Console Management information for the last inventory, which ran 5 hours AFTER the files were uploaded, yet reports zero files. It appears the time reported in AWS Console Management of the 'Last Inventory' may not be the ACTUAL time it was run, but instead the time it was 'posted' to my AWS Console.
– Nertskull
Feb 7 '17 at 12:15
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f830146%2faws-glacier-inventory-is-either-wrong-or-asynchronous%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
