'Log storage policy' (or 'SQL Server & saving a tape')

[NATD]

I'm in danger of flooding this forum, but here we go with a new question.

I've got a SQL server which is backing up in my usual way...fulls on Friday nights and inc/diffs mon-thursday.

I've been ignoring the fact that my SQL jobs consume two tapes each night and with lots of my other niggles pretty much out of the way I turned my attention to this tonight.

From what I can tell, it boild down to the job using both the inc/diff storage policy AND the full one. It puts the actual differential data on one and then a small amount of 'database backup' on the other as a full.

It means I'm using twice the tapes which is a waste as well as the knock on costs of transport and storage.

What are my options? Books Online doesn't seem to directly address the subject other than acknowledging that SQL backups have this extra tab to select a policy.

 

[birky]

Are you using an incremetal storage policy?...if so then this will go to 2 storage locations (ie. use 2 tapes).

The idea for incremental storage policies is usually that you can put your full backups directly to tape and incrementals to disk.



Birky
CommVault Certified Engineer

 

[birky]

btw. when configuring SQL I usually just create a Full schedule and incr or diffs..with transaction log backups every couple of hours.

All these go to the same SP (usually pointing to disk) with the primary having a short retention (ie 7 days)and then aux copy to tape with a longer retention.



Birky
CommVault Certified Engineer

 

[Frbutler]

I agree with Birky.
I do nightly fulls and hourly tlog backups to disk and then aux to tape daily. (about 500gb a day)
It does sound as if you are using 2 different SP's which would explain the 2 tape issue.

Changing your data storage policy to match your log SP should resolve the 2 tape issue