31 Days of Disaster Recovery
- Last Time CheckDB was Run by Jason Brimhall (blog|@SQLRNNR). This post is important because knowledge is power. Especially if you may not be the one directly responsible for the integrity checks at your job. This is a quick way to check the last good DBCC integrity check for the database.
- Automated Backup Tuning by Nic Cain (blog|@SirSQL). You can get some good performance boost by tweaking the backup buffers, but you can also send backup performance in the toilet by tweaking it the wrong way. And it depends heavily on many factors so there is only one reliable way to determine the best settings: trial and error. Nic has automated that process for you and it runs the backup through various settings and graphs the performance differences for you so you can easily see which settings give you the best performance.
- Centralizing and Analyzing SQL Backup Pro Backup and Restore Data by Rodney Landrum (blog|@SQLBeat). It’s absolutely imperative that a DBA know the state of the backups on his servers. If you have a large number of servers, that can be a very daunting task. This process shows one way to automate this process and easily keep on top of a large number of servers.
- The SQL Server Instance That Will not Start by Gail Shaw (blog|@SQLInTheWild). This is a great article about the common problems you may face when rebooting SQL Server and it won’t start. If you haven’t already been there, you will be soon enough. Gail walks you through fixing several different common problems (which believe me is much better than reinstalling production in the heat of the moment).
- Everything by Paul Randal (blog|@PaulRandal). Okay, so I’m not referencing a particular blog post here, but if a week goes by without checking Paul’s blog, chances are pretty good that you missed something important. There’s no better source for learning deep internals on disaster recovery, DBCC, etc. Read it all. And then … read it again.
If you missed any of the earlier posts in my DR series, you can check them out here:
- 31 Days of disaster Recovery
- Does DBCC Automatically Use Existing Snapshot?
- Protection From Restoring a Backup of a Contained Database
- Determining Files to Restore Database
- Back That Thang Up
- Dealing With Corruption in a Nonclustered Index
- Dealing With Corruption in Allocation Pages
- Writing SLAs for Disaster Recover
- Resolutions for All DBAs
- Use All the Checksums
- Monitoring for Corruption Errors
- Converting LSN Formats
- Extreme Disaster Recovery Training
- Standard Backup Scripts
- Fixing a Corrupt Tempdb
- Running DBCC CheckTable in Parallel Jobs
Twitter
LinkedIn
TLF
RSS
WritersCafe
SQLPASS
Facebook
Thanks for the Shout out Robert.
You’re welcome.
Pingback: Day 16 of 31 Days of Disaster Recovery: Disaster Recovery Gems … « Quick Disaster Recovery.com
Pingback: Day 19 of 31 Days of Disaster Recovery: How Much Log Can a Backup Log | SQLSoldier
Hello SQLSoldier,
I really like your blog and the great information on disaster recovery.
Since I starting working as a SQL DBA (over 10 years) I have noticed that most poeple aren’t actually ready for a disaster, be it a SQL Server or the entire site.
I have created a script that will document the entire SQL server so that you have all the information you need. You can view it at my blog (http://sqlsurgeon.blogspot.ca/2012/09/hello-everyone-today-im-putting-up-my.html) and I would like to get your feed back on it. Do you see anything information that is missing? My hope is that this report will have all the needed information for a complete rebuild.
Any comments would be appreciated.
Thank you in advance for your time and for all the great information you have here.
Rudy
Hi Rudy. Very nice script. A couple of thoughts come to mind right away. Log shipping info and replication.
You don’t need to enable Show Advanced Features to query all settings in sys.configurations (which is one of the reasons I prefer sys.configurations over sp_configure).
Are you creating SQL logins with the same password and SID? if not, see my post here: http://www.sqlsoldier.com/wp/sqlserver/transferring-logins-to-a-database-mirror
Pingback: Day 29 of 31 Days of Disaster Recovery: Using Database Snapshots to Restore Replicated Databases in Test | SQLSoldier