This is part of risk management of a company. The company had decided to risk the production setup without a backup at the time. Obviously the downtime of the database is an acceptable risk to them. They could bear the consequence when luck turned against them. It should not be on your shoulder.

People make mistakes all the times. What's important is how they recover and be better. I remember a story where a guy was resigning after screwing up a million dollar venture. His boss told him, you have just learned a million-dollar lesson on the company's dime and you are quitting? The guy stayed on and flourished.

Don't feel bad about this. The decision to launch without backups was a legitimate business gamble. Blaming an engineer for the outcome of a business decision is plain bad management.

"With great power comes great responsibility."

No one is blaming your co-workers - but when your founders take investment money and insist on keeping themselves in charge, they also take on responsibility for the performance of the company and its technology. Just because their legal liability is limited, they aren't off the hook for what we think of them running their product this way.

Blowing the production database is bad, yes - but a LOT of bad days for top shelf programmers start with "rm". It sounds like you owned up to your mistake and put in the late nights to fix it in a way that your bosses didn't...best of luck to you.

You don't have to defend people who made a bad mistake worse. It's nothing personal, competent systems people are in short supply these days.

Only important data is backed up. Only backed up data is important.

Everyone has plans to backup data... it isn't until they actually lose data before they think about a backup. This also means that anyone that actually has backups, has probably lost data in the past...

Never ever plan to backup, just backup.