logo
logo
Sign in

Psst. Hey. Hey you. We have to whisper this in case the cool kidz hear, but... it's OK to pull your data back from the cloud

avatar
Geekz Snow
Psst. Hey. Hey you. We have to whisper this in case the cool kidz hear, but... it's OK to pull your data back from the cloud

While so many orgs shift their bytes off prem, here's why you may want to repatriate your information

Analysis The concept of cloud repatriation – shifting systems back in house from the cloud – is nothing new.

The past few years have served up some high-profile cases: file storage and sharing specialist Dropbox took hundreds of petabytes of customer data off AWS’ and back into its data centers in 2017.

The company saved almost US$75m in infrastructure costs over two years according to an S-1 filing.

Accurate comparisons also require a thorough understanding of owning and maintaining on-premises infrastructure – both direct (hardware, software licenses) and indirect (power supplies, connectivity, air-conditioning, staff salaries etc) costs, which can be equally hard to add up.

Figures compiled by the Active Archive Alliance calculated the relative cost of storing one petabyte of archival data on a flash storage system as $3.5m, network attached storage (NAS) box $2.6m, and Amazon S3 at $1.5m.

collect
0
avatar
Geekz Snow
guide
Zupyak is the world’s largest content marketing community, with over 400 000 members and 3 million articles. Explore and get your content discovered.
Read more