Top 5 Mistakes when Backing Up

Virtual SQL Servers

Brent Ozar, MCM, MVP

Brent Ozar PLF, LLC

Twitter: @BrentO

Administrative points on this webinar

Today’s topic● Thought leadership topic with brief mention of Veeam solution at the end.

Questions● Use the virtual Q&A panel.

● Upcoming webinar on Veeam advanced SQL backups

http://www.veeam.com/webinars.html

● This webinar is recorded and available for replay after a few days.

● At the end of the webinar, we can raise virtual hand for dialog questions.

● Stick around until the end of the webinar!

− NEW! Expanded choices - Winners will receive a choice of books!

Replay and slide download● You will get a follow-up email in a few days to download the slides and

replay this material.

ABOUT @BRENTO

ENOUGH ABOUT ME.

LET’S TALK ABOUT YOU.

Photo Licensed with Creative Commons: http://www.flickr.com/photos/luchoedu/2453280674/

#5: MISSING THE

NEW

BOTTLENECK.

TYPICAL PHYSICAL SQL

SERVER

TYPICAL PHYSICAL SQL

SERVER

TYPICAL VIRTUAL SQL

SERVER

TYPICAL VIRTUAL SQL

SERVER

QUESTIONS TO ASK

How is the host connected to the network and storage?

How many uplinks are we using?

Have we tested load balancing across all of them?

For both storage and networking, where’s the bottleneck?

Do we even have the capability to improve it?

Who else is using it?

And finally…

HOW CAN WE DO MORE

WITH LESS?

Photo Licensed with Creative Commons: http://www.flickr.com/photos/atoxinsocks/5047247159/

#4: NOT

STAGGERING

SCHEDULES

THE DEFAULTS ARE

EASY.

THE SOLUTION:

STAGGER.

Photo Licensed with Creative Commons: http://www.flickr.com/photos/leoplus/2744390812/

STAGGERING IS HARD.

Photo Licensed with Creative Commons: http://www.flickr.com/photos/taylar/5022649634/

#3: FULL BACKUPS

EVERY DAY

FOR PHYSICAL SQL

SERVERS,

FULL BACKUPS ARE EASY.

Photo Licensed with Creative Commons: http://www.flickr.com/photos/doviende/77324602/

IN VIRTUALIZATION,

FULL BACKUPS ARE...NOT

EASY.

Photo Licensed with Creative Commons: http://www.flickr.com/photos/doviende/77324602/

THE FIX: DIFFERENTIALS

Sunday night: full backups

Monday-Saturday nights: differential backups

To restore:

• Restore the last full

• Restore the most recent differential

• Restore the transaction logs

THAT FULL BACKUP

BETTER BE GOOD.

Photo Licensed with Creative Commons: http://www.flickr.com/photos/ambernectar/4843007369/

#2: SKIPPING

SYSTEM OBJECTS

THINK OUTSIDE

THE DATABASE.

Logins & passwords

Jobs & schedules

DTS/SSIS packages

Linked servers

Master stored procs

SQL Server parameters

Trace flags

Exact patch levels

OS hotfixes

Photo Licensed with Creative Commons: http://www.flickr.com/photos/markhillary/484737335/

#1: TAKING THE

WRONG

SNAPSHOT.

“SNAPSHOTS”

Snapshot isolation

Replication snapshots

Database snapshots

SAN snapshots

VM snapshots

Photo Licensed with Creative Commons: http://www.flickr.com/photos/j_benson/4108358813/

YOUR TAKEAWAYS

Don’t do full backups every night at midnight.

Stagger your schedules and ensure they don’t overlap.

Test database restores and know what’s outside your dbs.

Do VM-level snapshots if possible and offload backup work.

Resources and feedback:

BrentOzar.com/go/virtual

Interactive Demo

vPower SureBackup Verification

Questions and Answers Winners receive a choice of the following books

Thank you for attending!

Resources:● Twitter @Veeam Blog: http://www.veeam.com/blog Eval: Veeam.com