Philip,
Attention for the parameter "OPTIONS" The configuration file " progra~1\tivoli\tsm\tdpsql\sqlfull.cmd " it must be placed in OBJECTS ... OK! ------------------------------------------------------------ 02/18/2003 02:37:35 Schedule Name: ENTERPRISE_SQL_BACKUP 02/18/2003 02:37:35 Action: Command 02/18/2003 02:37:35 Objects: 02/18/2003 02:37:35 Options: c:\progra~1\tivoli\tsm\tdpsql\sqlfull.cmd <--- 02/18/2003 02:37:35 Server Window Start: 02:30:00 on 02/19/2003 02/18/2003 02:37:35 ------------------------------------------------------------ <<<<< CORRECT FORM>>>>> Policy Domain Name: ---- Schedule Name: ENTERPRISE_SQL_BACKUP Description: Action: Command Options: Objects: c:\progra~1\tivoli\tsm\tdpsql\sqlfull.cmd <- Priority: ------ Start Date/Time: ------ Duration: ------ Period: ------ Day of Week: ------ Expiration: Last Update by (administrator): ADMIN Last Update Date/Time: ------ Managing profile: King regards, Elenara ® Elenara Geraldo TSM Administrator Phone : 55 41 381 7849 Cellular: 55 44 91077262 -----Mensagem original----- De: Hamlin, Philip [mailto:[EMAIL PROTECTED]] Enviada em: terça-feira, 18 de fevereiro de 2003 14:03 Para: [EMAIL PROTECTED] Assunto: SQL TDP fails to run with scheduler I am having trouble getting the SQL TDP v2.2.1 to run with the scheduler. Here is the system description: Both the TSM server and the SQL server are running Windows 2000 with SP3. The SQL server is running SQL 2000 patched to SP3. TSM server version 4.2.1.12 TSM BAClient version 4.2.2.8 TSM Tivoli Data Protection of Microsoft SQL Server v2.2.1.0 I installed the TDP following the install instructions and the Redbook. The directories are default. I installed a separate scheduler service using default names. The scheduler kicks off and (as you can see) quits with three error lines in the excerpt from the tdpsched.log. I can run the "sqlfull.cmd" manually and it runs fine each and every time. I have included the tdpsched.log, sqlfull.cmd, and dsm.opt files below. I set this TSM install as close as I could to an another, existing server where the TDP works great. I have tried to remark out items in the dsm.opt file (which I think is where the complains are coming from). I have recreated the dsm.opt and sqlfull.cmd files in case they were somehow corrupted. When I redid the dsm.opt file, I used a copy of the sample file to start with and modified to what you see. I looked at ADSM.org for help as well as the IBM Tivoli sites. I cannot find anything that is relevant. I first installed the v2.2.0 with the 4.2.28 baclient. Then I "upgraded" to version 2.2.1.0. Same outcome with both versions. Any ideas would be most appreciated. Here are the log and file excerpts: TDPSCHED.LOG 02/18/2003 02:37:35 Executing scheduled command now. 02/18/2003 02:37:35 ANS1038S Invalid option specified 02/18/2003 02:37:35 ANS1820E Command line options must be preceded by a '-' 02/18/2003 02:37:35 ANS1512E Scheduled event 'ENTERPRISE_SQL_BACKUP' failed. Return code = 4. 02/18/2003 02:37:35 Sending results for scheduled event 'ENTERPRISE_SQL_BACKUP'. 02/18/2003 02:37:35 Node Name: CIONISQL001_SQL 02/18/2003 02:37:35 Session established with server CIONITSM001: Windows NT 02/18/2003 02:37:35 Server Version 4, Release 2, Level 1.12 02/18/2003 02:37:35 Server date/time: 02/18/2003 02:37:35 Last access: 02/17/2003 20:42:35 02/18/2003 02:37:35 Results sent to server for scheduled event 'ENTERPRISE_SQL_BACKUP'. 02/18/2003 02:37:35 ANS1483I Schedule log pruning started. 02/18/2003 02:37:35 Schedule Log Prune: 684 lines processed. 104 lines pruned. 02/18/2003 02:37:35 ANS1484I Schedule log pruning finished successfully. 02/18/2003 02:37:35 Querying server for next scheduled event. 02/18/2003 02:37:35 Node Name: CIONISQL001_SQL 02/18/2003 02:37:35 Session established with server CIONITSM001: Windows NT 02/18/2003 02:37:35 Server Version 4, Release 2, Level 1.12 02/18/2003 02:37:35 Server date/time: 02/18/2003 02:37:35 Last access: 02/18/2003 02:37:35 02/18/2003 02:37:35 --- SCHEDULEREC QUERY BEGIN 02/18/2003 02:37:35 --- SCHEDULEREC QUERY END 02/18/2003 02:37:35 Next operation scheduled: 02/18/2003 02:37:35 ------------------------------------------------------------ 02/18/2003 02:37:35 Schedule Name: ENTERPRISE_SQL_BACKUP 02/18/2003 02:37:35 Action: Command 02/18/2003 02:37:35 Objects: 02/18/2003 02:37:35 Options: c:\progra~1\tivoli\tsm\tdpsql\sqlfull.cmd 02/18/2003 02:37:35 Server Window Start: 02:30:00 on 02/19/2003 02/18/2003 02:37:35 ------------------------------------------------------------ 02/18/2003 02:37:35 Schedule will be refreshed in 6 hours. SQLFULL.CMD @ECHO OFF set sql_dir=C:\Progra~1\Tivoli\TSM\TDPSql C: cd %sql_dir% date < NUL >> %sql_dir%\sqlsched.log time < NUL >> %sql_dir%\sqlsched.log %sql_dir%\tdpsqlc backup * full /tsmoptfile=%sql_dir%\dsm.opt /logfile=%sql_dir%\sqlfull.log >> %sql_dir%\sqlsched.log DSM.OPT *======================================================================* * * * Tivoli Data Protection for Microsoft SQL Server * * * * 2/17/03 by PH * * * *======================================================================* NODename CIONISQL001_SQL CLUSTERnode no COMPRESSIon Off PASSWORDAccess Generate *======================================================================* * TCP/IP * *======================================================================* COMMMethod TCPip TCPPort 1500 TCPServeraddress cionitsm001 TCPWindowsize 63 TCPBuffSize 32 * following items remed out or changed 2/17/02 by PH for testing *TCPBuffSize 256 *txnbytelimit 25600 *largecommbuffers yes *tcpnodelay yes *resourceutilization 3 *commrestartduration 120 *commrestartinterval 60 *======================================================================* * * * - Scheduling Options * * * * The default scheduling mode is the client polling method. * * To use server prompted scheduling, you must be sure to use a tcp * * client port different than the one used by the regular backup * * client. * * * *======================================================================* SCHEDMODE Polling maxcmdretries 4 changingretries 0 schedlogname c:\tsmlogfiles\tdpsched.log schedlogretention 7 D errorlogname c:\tsmlogfiles\tdperror.log errorlogretention 7 D *======================================================================* * Include/Exclude Processing * * * * For a more complete description of include/exclude processing see * * the Tivoli Data Protection for Microsoft SQL Server Installation and * * User's Guide (Chapter 3 and Appendix B) * *======================================================================* INCLUDE "\...\meta\...\*" TDP_METADATA **************************************************************************** ***************************************************************** Again thanks for the time to consider this problem. Philip Hamlin Network Analyst, Information Systems Independent Bank Corporation 616.527.5820 ex1383 mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Privacy Statement: This message may contain confidential information that is protected under state and/or federal law. If you received this message in error, please notify the sender by fax or email and delete this message. If you properly received this message, you may use its contents only in strict accordance with our instructions and privacy policy. If any person makes a false or misleading representation to obtain customer information, that person may have committed a federal crime, and we may report that person to the proper authorities.