SQL Server Backups with PowerShell

Automating restores and verification to leave more time for

the fun things in a DBA’s job

Started with SQL Server 7 in 1998, 15 years later still working with it, but newer versions as well.

Worked as DBA and Developer in that period. Also work with Oracle, MySQL and Linux

In spare time I’m most likely to be found studying a Mathematics degree with the OU, or sat on a bike saddle somewhere remote.

Email: stuart.moore@stuart-moore.co.uk Blog: http://stuart-moore.com Twitter: @napalmgram

Stuart Moore

Started off as Monad back in 2005 Improved with each version, now on version

3 Lots of support for SQL Server:

◦ SMO – SQL Management Objects◦ SQLPS – Official SQL Server Module, offers

methods for the above ◦ SQLPSX – Unofficial SQL Server Module

PowerShell

Essential part of the job Easy to set up simple backup routines with

maintenance plans, not so easy for complex setups

Automated Backups

Should be as essential as backups:◦ Did the backup really complete properly?◦ How long does a full restore take (how long should

RTO be)◦ How long do the transaction backups take to

restore?◦ Do you have whole backup chain◦ If needed, can you prove it to Auditors?

Automated Restores

SQL Server doesn’t offer an easy means to automate restores.

Tend to need to build a job for each database◦ Not easy with an instance with 100s of DB◦ Differing file layouts also a problem

So why aren’t they?

Demos may not be the best examples of PowerShell.◦ I’ve taken some liberties to make them easier to

read◦ Best practice is to write reusable functions, not

lots of scripts.

Warning!!!!

1. Basic Full backup of single db2. Backup all DB on an instance3. Catch new databases4. Split Database backups

Backup Demos

1. Simple Restore2. Include transaction backups3. Check transaction log order4. Restore with file relocation5. Restore to Random point in Time

Restore Demos

So now we’ve restored the database is that it?

No, we need to check that it’s actually usable and structurally sound.◦ Run DBCC checks against◦ Run our own scripts to check integrity or business

rules

Corrupted DBs courtesy of Paul Randal from here - http://bit.ly/1dEeklT

Verification

Use Invoke-Sqlcmd◦ Problems with query timeouts fixed in SQL Server

2012◦ Versions prior to that, look at Invoke-Sqlcmd from

Chad Miller - http://bit.ly/16GOeL8

Using DBCC

Verification Demo

Nothing other than SQL Server backup and restores.◦ Not a faster method◦ Not a slower method◦ Can be monitored just like all other backups◦ Blocked by exactly the same things

Under the hood

Not the world’s most informative error messages:

◦ Plenty of error checking in production scripts◦ Or get used to stepping through to find the

problems

Problems