Question
Volume Storage or Spaces for backups
- Posted July 9, 2019
- DigitalOceanBackupsBlock StorageObject Storage
I want to store my database backups (.sql exports) & important files backup (which is a .zip) outside my local server. I’ve came across Block Storages & Object Storages. For this task, Block Storage seemed more logical to me as it’s just like a harddrive storage but then when I tried to setup, I realised it’s actually for attaching to an existing server. But if I attach a volume to my actual server, if something goes wrong and I can’t ssh, I won’t be able to access the Volume right? Object Storages’ use-case seemed to me as CDN so I thought it’s not what I’m looking for as obviously they are private data that I won’t share on CDN.
For storing backups, what would you do? I need around 50gb - backup database every X hr (monthly) together as important files (weekly).
For this task, would you use Block Storages or Object Storages?
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.
It makes more sense to store your backups offsite, on a storage that is accessible to you easily. For this reason you should go with the Object Storage (DigitalOcean Spaces).
It is true that you can use DigitalOcean Spaces as a CDN, but that’s just one of the uses of it. Basically you can store and retrieve files and choose whether they are public or private.
Many tools and software give you the option to read and write to your Object Storage (example: on SimpleBackups we allow our users to directly store their backups on DigitalOcean Spaces), unlike a block storage which ties you down and requires first to be attached to a server instance so you can access your files.
If you need to extend your server storage and easily detach and attach drives, you should use a block storage.
If you need to store your backups, then an object storage is the way to go.
Hope this helps.