TSM Scheduler Missed

S

sus

ADSM.ORG Member
Joined
Sep 20, 2006
Messages
86
Reaction score
0
Points
0
Website
Visit site
I have a problem with scheduling the backup. I had scheduled the backup and associated the node, but when i given q event * * begind=+4(where the schedule should run) its not finding the schedule.

I had started the scheduler service from the client also.

My observation is the node is a TDP node, but in the TSM if i give q node it is showing as the platform is WinNT inseat of TDP node, any idea what is the prob ?
 
TSM Scheduler

Hi, have you seen the TSM Scheduler service in the node? Is it running? Is there any messagge in the TSM Scheduler log? (maybe Not scheduled task detected or something like that) Please verify your configuration of TSM Scheduler Service in the node, if you restart it you should get a message in the log.
 
It this a regular backup client node or a tdp client node or both? If it is both, you should have 2 schedule services one for each.
 
Yes it is having two different scheduler and it backups both filesystem and TDP backup.
 
sus said:
I have a problem with scheduling the backup. I had scheduled the backup and associated the node, but when i given q event * * begind=+4(where the schedule should run) its not finding the schedule.

I had started the scheduler service from the client also.

My observation is the node is a TDP node, but in the TSM if i give q node it is showing as the platform is WinNT inseat of TDP node, any idea what is the prob ?
Click to expand...

Quick check:

1. Are the node names different for each instance: the BA node has a different node name than the TDP node?
2. There should be two dsm.opt file.
3. Have you registered both nodes to the TSM Server?
4. Are two schedule services running and each have its own schedule and error logs?
 
Last edited:
TDP SQL Schedule Failed with Return Code 1.

Dear All, I have an error regarding TDP SQL Schedule Return code 1. There is nothing in dsmerror logs and schedlog files except schedule command failed with return code 1.I have BA Client installed and registered with different node name and TDP registered with different node name in TSM server. Both have separate schedule service. Can someone guide me how to resolve this issue.

Also where and how to define sqlfull.cmd file in TSM Admin Center.
If i enter only the name in macro field i-e sqlfull.cmd it gives error "could not open macro file". If i give full path i-e "C:\Program.....\sqlfull.cmd" in command field it gives return code 1.

Please take it on priority.

Thanks
 
RC 1 seems to mean that the script is failing. Could you post the contents of your sqlfull.cmd and tdpo.opt?
 
Dear maxdb82,

Here is the SQLFULL.CMD

@ECHO OFF
rem ==================================================================
rem sqlfull.smp sample command file
rem
rem Sample command file containing commands to do a scheduled full
rem backup of all SQL databases to an IBM Tivoli Storage Manager
rem server.
rem
rem This file is meant to be executed by the IBM Tivoli Storage
rem Manager central scheduler in response to a defined schedule on
rem the IBM Tivoli Storage Manager server.
rem
rem ==================================================================
rem ==================================================================
rem Replace "C:" with the drive where Data Protection for SQL
rem is installed. Update the directory to match the installation
rem directory that you chose when you installed the product.
rem ==================================================================
set sql_dir=C:\"Program Files"\Tivoli\TSM\TDPSql
C:
cd %sql_dir%
rem ==================================================================
rem The two lines below put a date/time stamp in a log file for you.
rem Note: You can change "sqlsched.log" to whatever you prefer in
rem lines below.
rem ==================================================================
date < NUL >> %sql_dir%\sqlsched.log
time < NUL >> %sql_dir%\sqlsched.log
rem ==================================================================
rem Now call the command-line interface to do the backup:
rem
rem Replace "srvrname" with the name of the options file name you
rem plan to use.
rem
rem If SQL authentication is being used and the SQL login settings have
rem not been stored via the GUI, you must also specify the /sqluser and
rem /sqlpassword options on the command below.
rem
rem In this example, we use the '*' to back up all of the databases
rem on the SQL server. Note that database 'tempdb' will not
rem be backed up.
rem
rem Note: You can change "sqlsched.log" and "sqlfull.log" to
rem whatever you prefer.
rem ==================================================================
%sql_dir%\tdpsqlc backup * full /tsmoptfile=%sql_dir%\dsm.opt /logfile=%sql_dir%\sqlfull.log >> %sql_dir%\sqlsched.log

=> And tdpo.opt infact dsm.opt in TSPSQL folder

*======================================================================*
* *
* IBM Tivoli Storage Manager for Databases *
* *
* Data Protection for Microsoft SQL Server *
* *
* Sample Options File *
* *
*======================================================================*
NODename backupsql
CLUSTERnode NO
PASSWORDAccess Generate
*======================================================================*
* TCP/IP Communication Options *
*======================================================================*
COMMMethod TCPip
TCPServeraddress xx.xx.xx.xx (TSM Server IP Address)
TCPPort 1531
TCPWindowsize 63
TCPBuffSize 32
*======================================================================*
* Named Pipes Communication Options *
*======================================================================*
*COMMMethod NAMEdpipe
*NAMedpipename \\.\pipe\tsmpipe
*======================================================================*
* - Compression Options *
* *
* Use the "COMPRESSION" option to compress the data before sending *
* it to the IBM Tivoli Storage Manager server. Use the *
* "COMPRESSALWAYS" option to specify whether to continue compressing *
* the data if it grows during compression. *
* *
*======================================================================*
COMPRESSIon NO
*COMPRESSAlways NO
*======================================================================*
* *
* - 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
*SCHEDLOGRetention 14
*SCHEDMODE Prompted
*TCPCLIENTADDRESS yy.yy.yy.yy
*TCPCLIENTPORT 1502
*======================================================================*
* Include/Exclude Processing *
* *
* For a more complete description of include/exclude processing refer *
* to the Data Protection for Microsoft SQL Server Installation and *
* User's Guide. *
*======================================================================*
*======================================================================*
* The following include statements assign all meta objects to *
* management class SqlDbMetaMgmtClass and all data objects to *
* SqlDbDataMgmtClass *
*======================================================================*
*INCLUDE "\...\meta\...\*" SqlDbMetaMgmtClass
*INCLUDE "\...\data\...\*" SqlDbDataMgmtClass
*======================================================================*
* The following include statements assign all log meta objects to *
* management class SqlLogMetaMgmtClass and all log data objects to *
* SqlLogDataMgmtClass *
*======================================================================*
*INCLUDE "\...\meta\...\log*" SqlLogMetaMgmtClass
*INCLUDE "\...\data\...\log*" SqlLogDataMgmtClass
*======================================================================*
* The following exclude statements exclude all log backups for *
* databases master and msdb *
*======================================================================*
*EXCLUDE "\...\master\...\log*"
*EXCLUDE "\...\msdb\...\log*"
*======================================================================*
* The following exclude statement excludes the "db1" database *
* from being compressed (if compression is enabled for backups.) *
*======================================================================*
*EXCLUDE.COMPRESSION "\...\db1\...\*"


=> Also dsm.opt located in baclient folder


NODENAME BACKUPSQLBA
TCPSERVERADDRESS xx.xx.xx.xx (TSM Server IP Address)
TCPPORT 1531
PasswordAccess Generate
 
Hi
Try to run TDP for SQL GUI. Does it works without errors?
Efim
 
Yes, TDP for SQL GUI works without error.
 
Attach files C:\"Program Files"\Tivoli\TSM\TDPSql\sqlsched.log and C:\"Program Files"\Tivoli\TSM\TDPSql\sqlfull.log
Efim
 
Here is sqlsched.log

03/30/2013 16:30:48 --- SCHEDULEREC QUERY BEGIN
03/30/2013 16:30:48 --- SCHEDULEREC QUERY END
03/30/2013 16:30:48 Next operation scheduled:
03/30/2013 16:30:48 ------------------------------------------------------------
03/30/2013 16:30:48 Schedule Name: SQL_DAILY
03/30/2013 16:30:48 Action: Command
03/30/2013 16:30:48 Objects: c:\"Program files"\tivoli\tsm\tdpsql\sqlfull.cmd
03/30/2013 16:30:48 Options:
03/30/2013 16:30:48 Server Window Start: 19:04:00 on 04/05/2013
03/30/2013 16:30:48 ------------------------------------------------------------
03/30/2013 16:30:48 Schedule will be refreshed in 12 hours.
03/31/2013 04:30:48 TSM Backup-Archive Client Version 6, Release 2, Level 4.0
03/31/2013 04:30:48 Querying server for next scheduled event.
03/31/2013 04:30:48 Node Name: BACKUPSQL
03/31/2013 04:30:48 Session established with server SECONDTSM: AIX-RS/6000
03/31/2013 04:30:48 Server Version 5, Release 5, Level 5.0
03/31/2013 04:30:48 Server date/time: 03/31/2013 04:22:19 Last access: 03/30/2013 19:04:08
03/31/2013 04:30:48 --- SCHEDULEREC QUERY BEGIN
03/31/2013 04:30:48 --- SCHEDULEREC QUERY END
03/31/2013 04:30:48 Next operation scheduled:
03/31/2013 04:30:48 ------------------------------------------------------------
03/31/2013 04:30:48 Schedule Name: SQL_DAILY
03/31/2013 04:30:48 Action: Command
03/31/2013 04:30:48 Objects: c:\"Program files"\tivoli\tsm\tdpsql\sqlfull.cmd
03/31/2013 04:30:48 Options:
03/31/2013 04:30:48 Server Window Start: 19:04:00 on 04/05/2013
03/31/2013 04:30:48 ------------------------------------------------------------
03/31/2013 04:30:48 Schedule will be refreshed in 12 hours.
03/31/2013 16:30:48 TSM Backup-Archive Client Version 6, Release 2, Level 4.0
03/31/2013 16:30:48 Querying server for next scheduled event.
03/31/2013 16:30:48 Node Name: BACKUPSQL
03/31/2013 16:30:48 Session established with server SECONDTSM: AIX-RS/6000
03/31/2013 16:30:48 Server Version 5, Release 5, Level 5.0
03/31/2013 16:30:48 Server date/time: 03/31/2013 16:22:19 Last access: 03/31/2013 12:02:32
03/31/2013 16:30:48 --- SCHEDULEREC QUERY BEGIN
03/31/2013 16:30:48 --- SCHEDULEREC QUERY END
03/31/2013 16:30:48 Next operation scheduled:
03/31/2013 16:30:48 ------------------------------------------------------------
03/31/2013 16:30:48 Schedule Name: SQL_DAILY
03/31/2013 16:30:48 Action: Command
03/31/2013 16:30:48 Objects: c:\"Program files"\tivoli\tsm\tdpsql\sqlfull.cmd
03/31/2013 16:30:48 Options:
03/31/2013 16:30:48 Server Window Start: 19:04:00 on 04/05/2013
03/31/2013 16:30:48 ------------------------------------------------------------
03/31/2013 16:30:48 Schedule will be refreshed in 12 hours.
04/01/2013 04:30:48 TSM Backup-Archive Client Version 6, Release 2, Level 4.0
04/01/2013 04:30:48 Querying server for next scheduled event.
04/01/2013 04:30:48 Node Name: BACKUPSQL
04/01/2013 04:30:48 Session established with server SECONDTSM: AIX-RS/6000
04/01/2013 04:30:48 Server Version 5, Release 5, Level 5.0
04/01/2013 04:30:48 Server date/time: 04/01/2013 04:22:19 Last access: 03/31/2013 19:04:08
04/01/2013 04:30:48 --- SCHEDULEREC QUERY BEGIN
04/01/2013 04:30:48 --- SCHEDULEREC QUERY END
04/01/2013 04:30:48 Next operation scheduled:
04/01/2013 04:30:48 ------------------------------------------------------------
04/01/2013 04:30:48 Schedule Name: SQL_DAILY
04/01/2013 04:30:48 Action: Command
04/01/2013 04:30:48 Objects: c:\"Program files"\tivoli\tsm\tdpsql\sqlfull.cmd
04/01/2013 04:30:48 Options:
04/01/2013 04:30:48 Server Window Start: 19:04:00 on 04/05/2013
04/01/2013 04:30:48 ------------------------------------------------------------
04/01/2013 04:30:48 Schedule will be refreshed in 12 hours.

And sqlfull.log: there is nothing.
 
Try to run TSM scheduler service from user who successfully can backup using TDP GUI.
Efim
 
Using the same user as GUI for Scheduler service.
 
Hi domino,

Same result, return code 1........
 
Try to run manually this script:

@ECHO Off
set sql_dir="C:\Program Files\Tivoli\TSM\TDPSql"
cd /d %sql_dir%
tdpsqlc backup * full /tsmoptfile=%sql_dir%\dsm.opt /logfile=%sql_dir%\sqlfull.log >> %sql_dir%\sqlsched_full.log
set RC=%ERRORLEVEL%
echo Return code was %RC% >> %sql_dir%\sqlsched_full.log
exit %RC%

Please show sqlsched_full.log and sqlfull.log

Efim
 
Contents of sqlsched_full.log:

Return code was 9009

sqlfull.log is empty.
 
:) run command:
C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc query sql
C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc query tsm
expected output in the file.
 

Attachments

  • out.txt
    1.7 KB · Views: 5
Efim,

Here is the output:

C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc query sql
IBM Tivoli Storage Manager for Databases:
Data Protection for Microsoft SQL Server
Version 5, Release 5, Level 0.0
(C) Copyright IBM Corporation 1997, 2007. All rights reserved.
Connecting to SQL Server, please wait...
SQL Server Information
----------------------
SQL Server Name ........................ BACKUP
SQL Server Version ....................... 9.0.2047 (SQL Server 2005)

===============================================================================

C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc query tsm
IBM Tivoli Storage Manager for Databases:
Data Protection for Microsoft SQL Server
Version 5, Release 5, Level 0.0
(C) Copyright IBM Corporation 1997, 2007. All rights reserved.
Tivoli Storage Manager Server Connection Information

----------------------------------------------------
Nodename ............................... BACKUPSQL
NetWork Host Name of Server ............ TSM Server IP
TSM API Version ........................ Version 6, Release 2, Level 4.0
TSM Server Name ........................ SECONDTSM
TSM Server Type ........................ AIX-RS/6000
TSM Server Version ..................... Version 5, Release 5, Level 5.0
Compression Mode ....................... Client Determined
Domain Name ............................ SQL_POLICY
Active Policy Set ...................... STANDARD
Default Management Class ............... STANDARD

The following line is not in output as in your case:
The operation completed successfully. (rc = 0)
 
Last edited:
You must log in or register to reply here.

Data Privacy Impact Assessment

Compliance Assurance in Every Byte: Discover the Impact of Our DPIA Services.

Sponsor ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

Navigation Menu

Forums
   IBM TSM
   EMC Backup and Recovery
   Symantec NetBackup  
   SAN  
   NAS
   Platforms / OS
Mailing List Archives
   ADSM-L
User Groups

NordVPN 3 Months FREE

Help Support ADSM.ORG and Get NordVPN with 64% Off and 3 Months FREE.

NordVPN with 64% off + 3 months FREE

Forum statistics

Threads
31,982
Messages
135,471
Members
21,953
Latest member
smeegama
Back
Top