> it shouldn’t be the same as the production database

Why is that?

gregors an hour ago | parent | next [-]

Here's an example from the circleci incident

and a good analysis by a flicker engineer who ran into similar issues

	▲	davidw 21 minutes ago \| parent [-]
		CircleCI and Flickr are both pretty big systems. There are tons of businesses that will never operate at that scale.

zarzavat 3 hours ago | parent | prev [-]

If you need to restore the production database do you also want to restore the task database?

If your task is to send an email, do you want to send it again? Probably not.

	▲	stavros 3 hours ago \| parent [-]
		It's not like I'll get a choice between the task database going down and not going down. If my task database goes down, I'm either losing jobs or duplicating jobs, and I have to pick which one I want. Whether the downtime is at the same time as the production database or not is irrelevant. In fact, I'd rather it did happen at the same time as production, so I don't have to reconcile a bunch of data on top of the tasks.