SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Critique: SQL Server Backup and Restore for the Accidental DBA


Critique: SQL Server Backup and Restore for the Accidental DBA

Author
Message
Grant Fritchey
Grant Fritchey
SSC Guru
SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)

Group: General Forum Members
Points: 98787 Visits: 33014
You’ve either volunteered or had the position thrust upon you, but here you are. You’re the DBA. You are being looked to as the person who will protect the companies’ data and you really don’t have a clue where to start. Let me suggest that one of the first things you should do is put together a good plan for backing up your database. This session will focus on the best practices, standards and methods that you can employ to ensure that you have a solid backup process for the databases under your charge. You’ll also learn how to restore these databases, because your backups are only good if you can restore them. At the end of the session, you should be able to go back to your office with confidence that you can begin to protect the data for your organization.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
bitbucket-25253
bitbucket-25253
SSCoach
SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)

Group: General Forum Members
Points: 15853 Visits: 25280
Having been in the position you describe, wish I had heard your talk before my hair turned grey. Nice clear description of the position many are thrust into, with a clear description of what I will learn from your presentation, how I and my company would benefit. If I could have attended your presentation I certainly would have done so. In fact even now I most likely would learn something, that I should know and may be overlooking.

If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read

Before posting a performance problem please read
Jim Murphy
Jim Murphy
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1219 Visits: 1265
Grant,

Nice description; down to earth and understandable.

I would guess (perhaps wrongly) that almost all people in the room have probably backed up a database. A full backup at least. Perhaps never tried to restore before. Perhaps mentioning terms like "point in time" restore and what is needed for that to work (log chain).

Issues that I have seen in the wild (leading to companies calling me) include:
1) Restore over top of the production database rather than making a 'copy' to sit on the same server. I know, restoring to another server is best, but I get calls after folks think this is going to be easy and blow away production.
2) Backup files ending up on the same physical drives as the .mdf/.ndf or .ldf's (backup to same logical drive letter, to different logical drive which is a partition of the same physical disk, to a shared SAN, or on VM drive which maps to the same physical disks).

This may not be in scope for your talk perhaps, and all of this detail should not end up in the description. However, maybe the description can hint at "no, your backups may not really be ok" with a buzzword or two to catch the attention of people who know super basic backups, but that's it.

Jim

Jim Murphy
http://www.sqlwatchmen.com
@SQLMurph
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search