How to Move Amazon S3 Data to Glacier

Amazon S3 is a cloud storage solution from Amazon that provides infinite storage capacity for relatively-low prices. I currently use it to keep a backup of my local NAS (network attached storage) device. However, Amazon S3 isn’t the best option for storing a large amount of data that you won’t access very often.

Amazon Glacier is a solution provided by Amazon that dramatically reduces the cost of storing large amounts of data in the cloud For example, storing 2500 GB of data on S3 cost about $215 a month. That’s quite a bit of money for just backing up your data. However, storing 2500 GB on Amazon Glacier will only cost you only $25 a month. That’s almost 1/10 the cost of S3.

So how do you move your data from Amazon S3 to Glacier? Using Lifecycle Policies. These policies are basically just rules that you can setup to move the data from S3 to Glacier at specific times. Let’s learn how to create a Lifecycle Policy.

Create Lifecycle Policy on Amazon S3

To get started, first go ahead and log into Amazon Web Services (aws.amazon.com) and click on My Account/Console at the top. Then click on AWS Management Console.

Aws console

Now from the list of Amazon Web services listed, go ahead and click on S3.

Amazon s3 service

Next click on the bucket name that contains the data you want to transfer to Glacier. Note that you will be able to either transfer the entire bucket, just folders or even specific files only.

S3 bucket name

When you open a bucket, you’ll see the content of the bucket on the left hand side. Click on Properties at the top right to open the settings for that bucket.

Bucket properties

At the bottom, you’ll see Lifecycle. Go ahead and expand Lifecycle to see your current rules, if any. I have one setup already which transfers everything in the bucket to Glacier after it’s uploaded to S3.

Add lifecycle

To setup a new rule, go ahead and click on Add rule. The new Lifecycle rule dialog will pop up as shown below.

Lifecycle rule

Now let’s go through the different options. Firstly, you can give it a name, which can be whatever you life. The Apply to Entire Bucket check box will apply the rule to all files and folders inside the bucket. If you want to only move a certain portion of the data to Glacier and leave the rest in S3, then do not check the box.

Instead, you can enter a Prefix, which is the name of the file or folder you want to move to Glacier. For example, if I wanted to just move the music folder in my bucket to Glacier, I would type music/ in the Prefix box. To specify a file, you type in the path like music/mymusic.mp3.

Next is Time Period Format. You can either choose from Days from the creation date or Effective from date. This option lets you choose when you want the objects you specified to be moved into Glacier. If you choose Days from the creation date, you can say, for example, that you want to move the data to Glacier after 10 days. This means when the file is data is first uploaded to S3, it will be moved to Glacier after 10 days of being created.

Effective from date will let you just specify a date in the future at which point the data will be transferred to Glacier. You have to click on the Add Transition button in order to specify the time period. My screenshot says “Move to Glacier”, but that’s because I already created a rule. When you click Add Transition, you can type in the number of days or the date. Note that if you type in 0 for the number of days, then the data will be moved immediately the next time the rule is run.

Number of days

There is also an Expiration button, but be careful with this. Again, depending on what you chose from Time Period Format, you can either specify a number of days or specific date in the future. Adding an expiration means the data will be deleted after the time you specify. It’s important to remember that it will be deleted from S3, RRS and Glacier. So basically it’s completely gone if you choose to add an expiration.

Add expiration

If you don’t add an expiration, the data will always remain in Glacier and not be deleted. That’s pretty much it. Once you save the rule, the rule will be run once a day. If your rule matches the criteria you specified, the data will be transferred.

There are a few things to note about this process. Firstly, you can tell your data has been moved to Glacier by checking the Storage Class. If it’s Standard, that is S3. If it’s RRS, that is Reduced Redundancy. The third class is Glacier, which means it’s now stored there.

Storage class s3

Another thing to note is that when you move data from S3 to Glacier, you still have to access it from S3. If you upload data straight to Glacier, it will show up in the Glacier console when you log into AWS. However, moving data using Lifecycle rules means the data will be stored in Glacier and you’ll be charged Glacier prices, but you’ll have to access the data from the S3 console. Kind of confusing, but that’s how it works.

Retrieving Data from Glacier

Getting data back from Glacier is also pretty straight-forward. The thing to remember about Glacier is that data is not immediately accessible like in S3. With S3, you can download any file any time. With Glacier, you have to wait about 3 to 5 hours for the data to be retrieved and put back into S3. That’s also why it’s so much cheaper.

To start a restore, select the file or folder that you want to retrieve and then right-click on it. You’ll see an option called Initiate Restore.

Restore from glacier

If the option is disabled, that means the file is not stored in Glacier. When you restore, you’ll have to choose how long you want the data to be accessible in S3.

Initiate restore glacier

Note that the files are restored to S3 RRS (Reduced Redundancy) storage class, which is a little bit cheaper than S3 Standard. Also note that you cannot permanently restore the data, it will be deleted eventually. I’m not sure what the largest value you can enter for days to keep the data, but it’s not forever. Also, you have to pay the higher fees the longer that data sits in RRS storage class, so it’s better to keep the duration short.

To see the status of a restoration, just click on the file or folder you restored and click on Properties. It will say Restoration in Progress. When the restore is complete and you click Properties again, you’ll see the date that the restore will be kept to.

Overall, getting your data from S3 to Glacier is very easy. Just create one rule and you’re done. Moving data to Glacier can mean big savings if you have a lot of data on S3. If you have any questions, please post a comment. Enjoy!

More posts from the Computer Tips Category

How to Rip DVDs to Your Hard Drive

Google Drive vs. Dropbox vs. SkyDrive vs. Amazon Cloud Drive vs. iCloud

How to Fix "Missing or corrupt NTFS.sys" Error in Windows XP

dynamic-dns-server

How to Pass All iPhone Traffic through an Encrypted VPN

Popular Posts This Month

extract-audio-from-video.png

How to Extract Audio from Video for Free

How to Fix Svchost.exe High CPU Usage

How to Split Your Laptop or PC Screen/Monitor in Windows

ipconfig.png

How to Disable SSID Broadcast on Your Wireless Router

Comments [2]

  1. mohammed m says:

    Very helpful. Keep up the good work!

  2. Thomas says:

    Hey,

    I too use a Synology which is backed up to S3. I was looking to move my data to Glacier instead and stumbled on your page. Thanks for the detailed instructions. I have one question though. What about the incremental backup from the Synology. Will the Syno reupload the whole backup set or will it still “see” the file in S3 and make the incremental back only?

    Thanks

Leave a Reply