How redundant/safe is object storage with "spaces"?

I’m looking at using the new “Spaces” object-storage solution for a project. Just wondering, what kind of redundancy is in place for data stored in this system? I want to be able to tell clients that their data is backed up and quite safe from hardware failures. Is this already the case with “Spaces”, or will I need to implement my own redundancy?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

If DO expects Spaces to compete with S3, they’ll need to provide similar durability guarantees. (From Amazon’s documentation, “Amazon S3 Standard and Standard - IA are designed to provide 99.999999999% durability of objects over a given year.”)

As far as I know, no such guarantee has been documented for Spaces. (Please correct me if I’m wrong.) Given this and Spaces’ early-access status, I’m working under the assumption that objects in Spaces could go up in smoke at any moment.

It’s up to you to back them up. You could probably write a script that uses the API to back these up.