Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Tape Rotation Without Partitioning

Updated: 21 May 2010 | 6 comments
Pete Burgess's picture
0 0 Votes
Login to vote

Hey folks

My ideal setup is that one job would run every night and I could use overwrite protection of 7 days so that I could ensure tape rotation. Unfortunately I have more than one job... one job runs the vast majority of the backups and there's another job that truncates my SQL logs. The fact that I have to do 2 jobs to backup SQL and truncate is really annoying, but that's one for another day.

Now what I could do is partition my tape drive and set up 2 jobs for each day of the month, each pair (i.e. "Main Backup Job" and "SQL Truncate Job") using a different partition on my tape library. This is, obviously, insanely time consuming. Is there an easier way to do this ?

Thanks

Pete

Comments

Ken Putnam's picture
07
May
2009
0 Votes 0
Login to vote

RE: Tape Rotation Without Partitioning

Why would you need a job for each day of the month?

You would only need two jobs and two partitions, if I understand what you are trying to do correctly. 

If this response answers your concern, please mark it as a "solution"

Pete Burgess's picture
08
May
2009
0 Votes 0
Login to vote

I think I didn't explain

I think I didn't explain myself properly.

Let's say I have my 2 backup jobs running daily. The first backups my file data and does a full SQL backup, the second job just backs up the SQL logs then truncates. If I use any kind of overwrite protection then the tape in slot #1 will get marked as unappendable. If I was running just the one job that would be perfect : the next day's job would use the tape in slot #2 and therefore I can control my tape rotation. However, because I have to have the SQL log truncate job run too then that job will get forced to use a different tape.

What I want to happen is on (e.g.) Monday the main backup and the SQL log backup to go to the same tape. On Tuesday I want them to go to a different tape. On Wednesday I want them to go to a different tape... and so on. This way I can ensure that I always have at least 24 days of backups on hand and at the end of the month I can pull a single tape with all backups and drop it into a tape safe for archiving.

Hopefully that explains it a little better.

Thanks

Pete

Scott Meltzer's picture
08
May
2009
0 Votes 0
Login to vote

RE: I think I didn't explain

Unless you can't run both jobs at the same general time, you should combine both your main backup and SQL log backup jobs into one single job.     That way, you'll be able to direct both jobs to the same tape and still use overwrite protection.

Pete Burgess's picture
08
May
2009
0 Votes 0
Login to vote

Doesn't work

Doesn't work unfortunately.

When you create the backup job you go to your SQL options and are presented with the list of backups types (log, log no truncate, full, etc.). There is no option for full backup with log truncate. The only way to do a full SQL backup and also truncate logs is split it into 2 different jobs.

I could have sworn SQL full backup with log truncate was in an earlier version (maybe 10 ?) but maybe I'm confusing it with the Exchange backup options.

Ken Putnam's picture
08
May
2009
0 Votes 0
Login to vote

RE: Tape Volume Rotation

If I use any kind of overwrite protection then the tape in slot #1 will get marked as unappendable

huh?
Only if the media set has no OPP, or if you have two different media sets

From your description, I think you need two jobs and one media set, and no partitions at all.  Define the main job as Overwrite, and the Log/Trunc as Append only, both pointed to the same media set.

Set the media set  OPP (Overwrite Protection) to 28 days and APP (Append period) to 12 hours

That should stack both jobs on one tape, and use a different tape each day, and never overwrite before 28 days (for FEB  |8^)  )

I could have sworn SQL full backup with log truncate was in an earlier version (maybe 10 ?) but maybe I'm confusing it with the Exchange backup options.

It was definitly an option for v7, 8 & 9, and I think 10 also.  But for some reason, Veritas had problems making it work.  It would backup both database and logs  but would not truncate the log files.  Never understood how the MS SQL backup would do it with no probkems, but Veritas couldn't hook the API to make it work with BackupExec

If this response answers your concern, please mark it as a "solution"

Pete Burgess's picture
08
May
2009
0 Votes 0
Login to vote

Thanks Ken, that acheives

Thanks Ken, that acheives exactly what I want.

I think I'm going to describe this as a senior moment on my part ! I really should have figured that out myself. That makes perfect sense.