Improve company productivity with a Business Account.Sign Up

x
?
Solved

SQL 2005 Backup to network location, with multiple fulls and tlogs

Posted on 2010-08-27
9
Medium Priority
?
342 Views
Last Modified: 2012-05-10
All,

I am backing up my DB and t-logs to backup devices that refer to a network location (UNC.) They work well.

Each new daily full backup overwites the previous file.  This leaves me in an bad spot if the SQL server catches fire during the backup process, among other weaknesses.

What I'd prefer to do is backup the DB to a different file every day of the week, repeating.  So every Monday I'd back up to the Monday.bak.  If sever catches fire during this process, I restore Sunday.bak. Since the Monday.bak didn't complete, I should still have the t-logs running since Sunday.bak, right?

I am able to do this with multiple backup jobs pointing to multiple backup devices.  This is much work when expanded to include all of our DB across all our servers.

Is there a canned plan that can accomodate what we want?

Thanks in advance.

0
Comment
Question by:AndrewW5
  • 5
  • 4
9 Comments
 
LVL 4

Expert Comment

by:pbarry1
ID: 33547206
Hi,

Yes, just use a Backup Maintenance Plan (use the Maintenance Plan Wizard under "Management / Maintenance Plan) in SQL Server Management Studio.

You can configure the retention period, etc...
0
 
LVL 4

Expert Comment

by:pbarry1
ID: 33547217
One thing to consider: make sure you have the latest SP installed.  Previous versions of SQL 2005 were very messy for these kind of maintenance plans.
0
 
LVL 4

Author Comment

by:AndrewW5
ID: 33547242
I have SP3 installed.  

I couldn't figure out how to apply retention period for my purposes.  In tests it just overwrote the same file.
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
LVL 4

Accepted Solution

by:
pbarry1 earned 2000 total points
ID: 33547273
The trick is to let SQL Server generate the filename (unless you really need to use specific names).  It will track which files it needs to delete or not.  

Do you really need to use specific names?
0
 
LVL 4

Author Comment

by:AndrewW5
ID: 33547286
No, I don't at all.  Let me try that!
0
 
LVL 4

Author Comment

by:AndrewW5
ID: 33547310
It requires me to set a file name.  I can't put a path without a file name in either Backup Devices or in Select Backup Destination. I must be going about this in the wrong way?
0
 
LVL 4

Author Comment

by:AndrewW5
ID: 33547345
I'm in the plan wizard now.  It may be what I needed.
0
 
LVL 4

Assisted Solution

by:pbarry1
pbarry1 earned 2000 total points
ID: 33547372
Yes, don't use a backup device.  It won't do what you want to use.  Here's a summary of what to set in the Maintenance Plan:

Task "Backup Database":
- Backup Type: FULL
- Database(s): All databases (or the ones you want)
- Backup to Disk
- Create a backup file for every database
   - (Personnaly, I use "Create a sub-directory for each database)
   - Enter the root folder where you want SQL to backup your databases
Click OK

Task "Maintenance Clean up"
- Backups files
- File location: "Search folder and delete files bases on an extension" enter the root folder specified above and the extension
- Enter the aging to use.
0
 
LVL 4

Expert Comment

by:pbarry1
ID: 33547386
And do the same for your LOG backups...  (either in a subplan or in another maintenance plan).
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Introduction This article will provide a solution for an error that might occur installing a new SQL 2005 64-bit cluster. This article will assume that you are fully prepared to complete the installation and describes the error as it occurred durin…
This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
SQL Database Recovery Software repairs the MDF & NDF Files, corrupted due to hardware related issues or software related errors. Provides preview of recovered database objects and allows saving in either MSSQL, CSV, HTML or XLS format. Ensures recov…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

608 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question