2 ms·
After looking at this directly in the control panel, the automation rules are just not going to be good enough. Let's say you have a three day rotation of dail
by ck2 14y ago
After looking at this directly in the control panel, the automation rules are just not going to be good enough.
Let's say you have a three day rotation of daily backups, 1 2 and 3 into S3.
If you wanted to use these controls to archive a weekly on Sunday and/or monthly on the 1st directly into glacier, there is no way to tell which of the rotations is the newest.
So it has to be done directly via the glacier API anyway.
Unless I am missing something or my backup logic could be improved?
What would have been actually useful is if there was a trigger command that could be sent via the S3 api itself. ie. copy|move|restore /backup/1 to glacier
Anyway will just use free inbound on glacier instead. It's a shame because it uses up the sending servers bandwidth to duplicate the exact process it just completed to S3.
added: unless maybe a one-time lifecycle rule can be created via the S3 api to tell it the daily archive it just uploaded (since the sending server knows right then which directory it just used) to copy into glacier - that might work