Amazon S3 Glacier vs. Barracuda Message Archiver

If your organization has a lot of archival data that it needs to be backed up for safekeeping, where it won't be touched except in a dire emergency, Amazon Glacier is perfect. In our case, we had a client that generates many TB of video and photo data at annual events and wanted to retain ALL of it, pre- and post- edit for potential use in a future museum. Using the Snowball device, we were able to move hundreds of TB of existing media data that was previously housed on multiple Thunderbolt drives, external RAIDs, etc, in an organized manner, to Amazon Glacier. Then, we were able to setup CloudBerry Backup on their production computers to continually backup any new media that they generated during their annual events.

Incentivized

This is the perfect solution for a quick implementation of archivation. You configure it once and it keeps on going. Users do not need to interact to archive, only to find things back.

• Cheap storage of backup data.
• Can be used as a part of the entire suite of tools from Amazon, without requiring you to leave the familiar stack.

Incentivized

• Archiving with journaling.
• Search with WebClient.
• Search with Add-In.
• Stubbing.

Incentivized

• Accessing data stored in Glacier is slow. That shouldn't be a surprise, but it is undesirable nonetheless.
• Retrieving a large amount of data can be expensive; Glacier's intended use is as an archive of rarely-accessed data.
• Some users regard Glacier with fear and uncertainty. Slow retrieval time and high retrieval cost are the greatest risks of using Glacier, and they are also the Glacier interaction that most users have the least experience with.

Incentivized

• the folder structure of the mailbox is harder to keep up with
• it is a bit confusing when you search for non email items, like contacts.

I would give a ten...but I don´t know the benefit in 2 years between Barracuda in Cloud and Microsoft in Situ Mailarchive. Lets see then!

Incentivized

It is difficult to delete the data as you have to wait for inventory and then bucket modification has to expire.

Incentivized

The product is good but for this specific product there are often some technical problems. Mostly support in Vienna can solve them soon. The development is very, very slow. I have asked for some changes. They gave the okay to make it with a feature request...but 3 years later there is still no code for my problems. Not even one feature request was done.

Incentivized

The support in Vienna is very, very great. They are fast and can support almost all problems by themselves. Especially Mr. Michael Holzer is a very high specialist and you can ask him almost everything. Just write a mail to emeasupport and you will be sure, that some minutes or hours later you will get a kind and professional call.

Incentivized

Think about using offline archives. They make a lot of trouble. Better train your users to use the Outlook Addin Search without using offline archives, which need a lot of power, network and harddrive space. Headers only functionality was promised years ago but is still not implemented.

Incentivized

Since the rest of our infrastructure is in Amazon AWS, coding for sending data to Glacier just makes sense. The others are great as well, for their specific needs and uses, but having *another* third-party software to manage, be billed for, and learn/utilize can be costly in money and time.

Incentivized

It was a lot cheaper, i mean a awfull lot.

• Helped us meet compliance requirements while minimizing costs.
• Simple integration with almost no changes required to our existing S3 management policies.

Incentivized

• i had no negative impact.