Re: TDP SQL Scheduling with multiple instances

2007-04-11 Thread Bell, Charles (Chip)
Yep, I was just doing that... I can also specify a different dsm.opt in the cmd file (backup script), which is what I would want if I have two nodes... Am I on the right track now? :) Thanks so much! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of

Re: TDP SQL Scheduling with multiple instances

2007-04-11 Thread Del Hoobler
Chip, Data Protection for SQL schedules are typically "COMMAND" type schedules... which means they call a batch file to perform their Data Protection for SQL backups. The batch file is where you will specify the the exact TDPSQLC command. In that specification, you would use the /SQLSERVER=instanc

Re: TDP SQL Scheduling with multiple instances

2007-04-11 Thread Bell, Charles (Chip)
If I configure 2 separate TDP schedulers, can I use the '/SQLSERVER=instance_name' in the 'dsmcutil inst /name:"TDP for SQL Scheduler"' command? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Wednesday, April 11, 2007 8:18 AM To: A

Re: TDP SQL Scheduling with multiple instances

2007-04-11 Thread Del Hoobler
Chip, I usually recommend that customers have a separate TSM NODENAME for each SQL Server instance that they back up. This allows for each SQL Server instance to have their data managed separately. I also recommend a separate scheduler instance for similar reasons. Use the '/SQLSERVER=instance-nam