3 ms·
> Backups are so simple It gets more interesting when you're trying to backup a distributed database. When your durability strategy is to spread your risk acr
by PopeDotNinja 7y ago
> Backups are so simple
It gets more interesting when you're trying to backup a distributed database. When your durability strategy is to spread your risk across a lot of nodes in a cluster, and you're federating your cluster across multiple sites, traditional backups may not be a practical option. However, as I write this, I'm realizing that there's nothing simple about distributed anything, and saying "it's hard to..." may not be all that interesting.
- londons_explore 7y agoPick a data sequence number, and back up each region sperately at the same sequence number. Keep your backups on-site but off-line - you already have many locations. You should practice a location (and it's backups) going offline at the same time as a code bug screws with data in the active system.
- scurvy 7y agoCassandra handles this pretty nicely. Files are immutable, so files are hard-linked to a snapshot directory. Copy out the snapshot directory, delete it, and things are eventually consistent. We restore our MySQL and Cassandra data every day in our production DC from backups in the DR DC. It's the only way to ensure things are working. It's about 100TB of data, but things zip along nicely now that 100gig networks are (more) common.
- PopeDotNinja 7y agoNeat!