Missed Recovery Techniques for SQL Server By Rudy Panigas

Missed Recovery Techniques for SQL Server By Rudy Panigas

My Bio: *Working in the IT Industry for over 25 years *Over 12 years as a Database Administrator with experience including architecting, design, implementation, monitoring, automation and specializing in disaster recovery *Worked in a variety of industries including telecom, retail and financial *Guest author at SQL Server Central http://www.sqlservercentral.com/ *My blog: http://sqlsurgeon.blogspot.ca *Member of Toronto PASS - TORPASS

*Do you know the Secret? *Have you really documented everything? *Restored lately? *Recovery Tips

What is a disaster? *City down *Site(s) down *Server(s) down *Power down *A/C down *Anything that affects the company What can we do? *Have offices in another city *Actually have a disaster recovery site *Redundant servers *UPS and other power management options *Good contracts with vendors including building management *Have everything you need off site for recovery

*SQL Server Clustering *Database Mirroring *Log Shipping *Always On (SQL Server 2012) *3 rd Party replication software *Automated backup and restore to recovery site *SAN replication *And whatever you can dream up

HA/DR = HAmyDR

HA/DR = HAmyDR High Availability/Disaster Recovery = How Are my Documentation availability and Restore capabilities

Create documentation as if you are going to do a complete bare metal build.

*Physical /Virtual server information *Storage/Hard drive information *SQL Server versions and patch levels *IP Address, Port numbers, link connections *SP_CONFIGURE *Jobs information *Replication options used *User list, Reporting, FTP etc.

Document everything!!

Get all your ducks in a row! Ensure you have everything you need to restore servers, databases, user accounts, encryption keys, etc.

*Domain Controller / Active Directory *Tape backup systems *SQL Server backups to restore *Server builds Physical and Virtual *Encryption keys (SSRS) *Rebuilt MASTER database *Recovery of system databases *Restore user databases *Restore additional functions

Restore everything!

*Create batch files / PowerShell commands to start and stop SQL Server services

*Create batch files / PowerShell commands to start and stop SQL Server services *Take a copy of the DATA folder before restoring system databases

*Create batch files / PowerShell commands to start and stop SQL Server services *Take a copy of the DATA folder before restoring system databases *Automate everything you can!

*Create batch files / PowerShell commands to start and stop SQL Server services *Take a copy of the DATA folder before restoring system databases *Automate everything you can! *Bring a bag with water, food, change of clothes, portable radio and anything you won t have at your DR site

HA/DR = HAmyDR Document Everything Recover Everything Recovery tips - Automate anything and bring what s missing DO NOT PANIC!! Be Calm!

PLUGGED! Remember the Secret, test, test and test again!

Thank you for you time Question / Comments Visit my blog: http://sqlsurgeon.blogspot.ca Search for SQL Server Document Generator for Disaster Recovery

1) Physical Server Information - Number of CPUs, memory, IP Address, etc. 2) Hard drive space available - in Megabytes 3) SQL Server Information - Server name, version of SQL server, Patch level 4) SQL Server Port Number Used 5) SQL Server Settings - SP_CONFIGURE 6) Database and Log file Physical Locations 7) Database Details - All database information 8) List of SQL Jobs - What jobs execute 9) Last Backup Dates - What and when the last backups was completed 10) Failed SQL Jobs - Jobs that have failed before 11) Disabled Jobs - Jobs there but not set to execute 12) SQL Server Services Status - What services were installed and running 13) Link Server Details - What other servers is SQL Server linked to 14) Database Mail Details - See if it is installed and running

15) Database Mirroring Details - Databases mirrored status 16) Database Log Shipping Details 17) Cluster Details - Information on cluster configuration 18) Always On Replication Details. SQL 2012 and newer This section below will produce T-SQL scripts as an output. You can execute them to automate the rebuild A) SP_CONFIGURE Script to Reapply Values B) User Database Restore Script C) User Login Restore T-SQL Script D) Link Server Rebuild Script