Actually, I would need 20, assuming a 4-hour window for the backups, since the log dumping would need to resume after the backups are finished !
"Schaub, Steve" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> 01/09/2006 10:01 AM Please respond to "ADSM: Dist Stor Manager" <[email protected]> To [email protected] cc Subject Re: [ADSM-L] SQL Logs and Backup conflict Zoltan, Assuming you associate both servers to each sched, you will only end up with 10 log schedules, which isnt too bad, and it is a lot more straightforward than disabling schedules behind the scenes. A slightly more complicated scheme would be to build a command script that runs a log backup if the time is between 10am-10pm, a full backup if the time is between 10pm-11pm, and exits if the time is between 11pm-10am. 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:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, January 09, 2006 9:48 AM To: [email protected] Subject: Re: [ADSM-L] SQL Logs and Backup conflict Thanks for the suggestions. I thought about doing it this way, as well, but what a pain, especially since I actually have two SQL servers doing this ! Another thought I had was to setup an Administrative schedule that would do an UPDATE SCHEDULE to disable the logs schedule just before the backup (can this be done via pre/post commands from the client side ? Can you run DSMADMC commands via pre/post for a TDP command file ?) and another admin schedule to re-enable it after the backup finished. The problem with this is guessing how long the backup runs ? I am hoping there is some option in the TDP process, to handle this ! "Schaub, Steve" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> 01/09/2006 09:36 AM Please respond to "ADSM: Dist Stor Manager" <[email protected]> To [email protected] cc Subject Re: [ADSM-L] SQL Logs and Backup conflict 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:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, January 09, 2006 9:15 AM To: [email protected] 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 Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
