Zoltan,

The way we do this (with Exchange), is to define a schedule for each
hour (we run our logs 8am-8pm).  We then associate all our Exchange
servers with each schedule.  It would be nice to have one schedule that
could be defined for a certain time period, but the TSM Scheduler is
pretty basic.  Of course, once the schedules are setup, you don't
generally have to mess with them much...

Steve Schaub
Systems Engineer, WNI
BlueCross BlueShield of Tennessee
423-752-6574 (desk)
423-785-7347 (cell)
 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Monday, January 09, 2006 9:15 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] SQL Logs and Backup conflict

We are looking for a creative solution (or answer) to a long outstanding
"issue" when it comes to SQL TDP backups.

We have a major M$-SQL shared server.

There is an HOURLY schedule to dump the transaction logs.

When the daily backups kick off, the hourly transaction log backups then
proceed to fail, causing constant annoying "schedule has failed"
messages, until the DB backups finish.

How do other folks handle this kind of conflict ?  Are we missing some
TDP backup option ?

My prefered solution would be to have TSM scheduling be more flexible,
e.g. only run this schedule between 10am and 10pm.

Your thoughts ?
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm