Before posting, and to avoid disappointment, please read the following:

  • This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
  • If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.

Amazon Glacier

For technical support visit
Posts: 2
Joined: Tue Apr 02, 2013 3:31 pm

Re: Amazon Glacier

Post by billc.lange »

I just wanted to follow up on my earlier post.
Originally I thought I'd want to archive directly to Glacier.
Now I'm actually thinking of going the other way which is to backup to S3 and then let amazon transfer the files to Glacier with a life cycle rule.
I did some testing with going to Glacier using S3 and thought I'd share what I've done.
I've been using SyncBack Pro to backup to S3 Standard/RRS.
After uploading the files using a SyncBack profile I added a lifecycle rule using the Amazon S3 Management Console to transfer the whole bucket to Glacier.
From my perspective, all that happens is that the storage CLASS of the files changes to "GLACIER". All the file listings are still there in my original S3 bucket but the storage is now GLACIER at the lower cost.
The result besides cost is that you cannot just copy the files out even though they show in the bucket listing.
If you want access to your files you have to initiate a "Restore" (I used the S3 Management Console) which gets a copy of the data into RSS storage where it will stay for a duration of days that you specify. It takes about 4 hours after your restore request to get access to the data.
The storage in my S3 bucket still shows GLACIER but the file properties indicate the RSS storage and the expiration date of the restore.
I found I can copy the restored data by reversing the source/destination of the SyncBack profile and specifying the same or different source as to where to place the data from the S3 bucket.
Downside is that for the number of days of the restore you will be charged for the copy of the data in RSS storage in addition to the GLACIER charges and some additional transfer charges if you restore a large percentage of your data.
At least that's my understanding from the pricing page. I haven't confirmed my personal charges as I'm using a small number of files for my testing just to test the process and I don't anticipate restoring a large portion from Glacier unless for disaster recovery. Anyway you would want to check the costs on this based on your data use plans.
I'm using SyncBack for the file transfer to/from S3 storage and the S3 management console for the life cycle and restore from Glacier functions for my S3 evaluation.
So if I go this direction I would be looking for SyncBack to implement the life cycle rule and the restore functions in addition to the supporting S3 in the backup profile.
Posts: 13
Joined: Sun Jan 17, 2016 9:08 pm

Re: Amazon Glacier

Post by keithl »

Any updates on Glacier support?
Posts: 1011
Joined: Mon Apr 13, 2015 6:22 am

Re: Amazon Glacier

Post by Swapna »


We have answered via your parallel support ticket.

Thank you.
Post Reply