A database server crash is one of those scenarios that can haunt your dreams. However, if you plan ahead and know you're prepared, you'll sleep better at night.

Brent Ozar posted a fantastic article about what to do if your most important production database server crashed today and listed these steps:

  1. Identify where the most recent backups are kept
  2. Make sure the backup schedule and frequency lines up with what the business wants
  3. Make sure the backups are getting offsite
  4. Make sure the monitoring software is watching this server, and sending you alerts

Be Prepared

Here are our articles on each of these topics to help you be prepared for the day your most important production database server crashes:

Before Disaster Strikes

PowerShell Lets You Back Up SQL Server Your Way

Keep Track of Your Backups

See Backup Date and Time

Off-Box Backups and Luke-Warm Standby Servers, Parts I-III

Don't Forget about Backup Compression

Step-by-Step Approach to Differential Backup and Recovery

Transaction Log Corruption and Backups

The Smart DBA's Guide to SQL Server Disaster Recovery, Part 1 & 2

SQL Server Database Corruption, Part VII: Backups

Intelligent Transaction Log Backups

Back Up Your SQL Server Databases with CloudBerry Backup

My Favorite Tool of 2013: CloudBerry Backup - Server Edition

Create Alert-Based Log Backups with PowerShell

Free Tool: SQL Server RestoreChecker Utility

SQL Server Database Corruption, Part V: Storage Problem Alerts

Checking Backup Status on Multiple SQL Server Systems

Troubleshooting Transactional Replication

SQL Server Backup and Recovery

After the Crash