2 ms·
You're right, we could restore each, one by one. However, we have around 30 different databases, each of which take more than a day to restore. We backup datab
by AznHisoka 8y ago
You're right, we could restore each, one by one.
However, we have around 30 different databases, each of which take more than a day to restore. We backup databases every X days, upload them to S3, and delete the previous ones, keeping only the last 3 or so.
So if it takes us 30 days to restore all the databases, those backups might already have been gone in S3 as part of the cleanup operation anyway.
It just gets complicated, and non-trivial when you have multiple databases, each TB's large.
- cheald 8y agoIf you already have the DBs in S3, it seems obvious that you could bring up EC2 instance(s) with gigantic EBS drives attached, restore a DB to it, and run verification measures on it. Parallelize as your budget allows.
- AstralStorm 8y agoEC2 is not an airgapped machine. That's known as cloud backup not offline backup. The solution is to have a tape or disk library and have the other machine take over for restore. If you have TBs of data you can afford a library and another PC to run the recovery test.
- Dylan16807 8y ago> EC2 is not an airgapped machine. That's known as cloud backup not offline backup. Nobody said it was. This subthread is about the importance of testing backups in general. > If you have TBs of data you can afford a library and another PC to run the recovery test. They already explained how that's not enough. Yes, they can add more, but you're missing some info there.