backup: All content tagged as backup in NoSQL databases and polyglot persistence
Tuesday, 22 January 2013
Automating MySQL Backups at Facebook Scale
Eric Barrett (Facebook) describes the process used for backing up Facebook’s MySQL cluster1:
Backups are not the most glamorous type of engineering. They are technical, repetitive, and when everything works, nobody notices. They are also cross-discipline, requiring systems, network, and software expertise from multiple teams. But ensuring your memories and connections are safe is incredibly important, and at the end of the day, incredibly rewarding.
If you’d want to make it sound simple, just enumerate the steps:
- Binary logs and
mysqldump - Hadoop DFS
- Long-term storage
Then start asking how you’d accomplish this. With 1 server. With more servers. With more servers while maintaining the availability of the system. See how far you’d be able to answer these questions. At least theoretically.
-
As a side note, in Fun with numbers: How much data is Facebook ingesting, I’ve guestimated the number of MySQL servers in the 20k range. This post mentions: “thousands of database servers in multiple regions”. ↩
Original title and link: Automating MySQL Backups at Facebook Scale (©myNoSQL)
Sunday, 3 July 2011
Backing Up MongoDB: Single Server, Replica Sets, Sharded Cluster
For single server deployments, backups are a must. But sometimes you might need to backup other deployments too. After the break, Scott Hernandez’ (10gen) talks about backing up a single server MongoDB, MongoDB replica sets, and MongoDB sharded cluster.
