When editing an existing scheduled archive job to add the Glacier option, new data files go to Glacier, and old data files remain in Amazon S3.
On a scheduled archive job with Glacier enabled, the metadata files will remain in S3 storage because Rapid Recovery needs to access those files to attach and import completed archives. However, previously exported data (.bin files ) will still show in S3 after editing the job and adding the Glacier option.
Viewing the existing S3 Storage bucket at Amazon S3/Bucket/Folder/AABackup/ArchiveID, you still see data files:
Recovery points data files already archived before enabling the Glacier option will remain in S3 storage and will not move to Glacier. That allows the existing archives to be imported and attached as was intended on the original archive job.
If you want to modify an archive so that all data moves to Glacier, you will need to create a new archive job from zero and check the Glacier option. Future versions of the software might disable the ability to choose the Glacier checkbox when editing existing S3 archive jobs.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center