Amazon S3 Glacier vs. Wolters Kluwer ARKon

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

The performance is quite consistent with what is required, the availability of the software is accessible in all aspects, through the use of architectural design patterns we have been able to have better practices when building software. software coding activities that go according to design. The functional requirements and technical aspects of the system are met

Incentivized

• 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

• Has collaboration with customer power users who contribute solution requirements.
• They approve the effective approach of the analyzed solution

Incentivized

• Sometime due to slow drives there are operation failure noticed by us in testing
• Cost of restoring data is high and if you have regular restoring them it is not good option and slow as well.
• While we were setting up the system we took some support from AWS and in many cases their answers were not up to the mark.

Incentivized

• Everyone has to be trained the right way to use it.
• It is also necessary that it adapts to use it in the correct way.

Incentivized

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

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

Everything that involves a pattern of behavior can be programmed, it is guaranteed that decision-making is always based on the information available at all times. There are different possibilities of action, which gives different options to choose the most accurate, you can create a work plan based on these solutions.

Incentivized

• We seldom need to access our data in Glacier; this means that it is a fraction of the cost of S3, including the infrequent-access storage class.
• Transitioning data to Glacier is managed by AWS. We don't need our engineers to build or maintain log pipelines.
• Configuring lifecycle policies for S3 and Glacier is simple; it takes our engineers very little time, and there is little risk of errant configuration.

Incentivized

• It is possible to have the software installed in the environments, in which it will finally be used
• It has the basic principle to provide information to enable efficient control, improved service levels

Incentivized