Tivoli Client Scheduler Troubleshooting: Difference between revisions

From UNIX Systems Administration
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
== Client Scheduler Troubleshooting ==
== Client Scheduler Troubleshooting ==
# The <tt>'''dsm.opt'''</tt> file if using <tt>'''MANAGEDSERVICES'''</tt> option must be commented out and the scheduler that is being reviewed must be running.
# Always check your firewall ports.
# Check CAD from the TSM Server by telnetting to the client node on port 1581.
# Check the connection from the client node by running dsmc from the command line on the client node.


== AIX and Linux==
== AIX and Linux==
# The <tt>'''dsm.opt'''</tt> file if using <tt>'''MANAGEDSERVICES'''</tt> option must be commented out and the scheduler that is being reviewed must be running.
# The following commands must be run as a user with rights to Tivoli.
# The following commands must be run as a user with rights to Tivoli.
# Path to the <tt>'''/usr/tivoli/tsm/client/ba/bin64 folder'''</tt>.
# Path to the <tt>'''/usr/tivoli/tsm/client/ba/bin64 folder'''</tt>.
Line 11: Line 14:


== Windows ==
== Windows ==
# The <tt>'''dsm.opt'''</tt> file if using <tt>'''MANAGEDSERVICES'''</tt> option must be commented out and the scheduler that is being reviewed must be running.
# Run <tt>'''CMD.EXE'''</tt> as Administrator.
# Run <tt>'''CMD.EXE'''</tt> as Administrator.
# Path to the baclient folder.
# Path to the baclient folder.

Revision as of 13:36, 15 August 2014

Client Scheduler Troubleshooting

  1. Always check your firewall ports.
  2. Check CAD from the TSM Server by telnetting to the client node on port 1581.
  3. Check the connection from the client node by running dsmc from the command line on the client node.

AIX and Linux

  1. The dsm.opt file if using MANAGEDSERVICES option must be commented out and the scheduler that is being reviewed must be running.
  2. The following commands must be run as a user with rights to Tivoli.
  3. Path to the /usr/tivoli/tsm/client/ba/bin64 folder.
  4. Run the dsm client program to start the scheduler in the foreground.
    1. dsmc sched -optfile="<path to the options file from the previous step>"
  5. On the TSM Server, modify the schedule or create a new scheduler with the option STARTTIME=now
  6. Review and correct errors on the client side.

Windows

  1. The dsm.opt file if using MANAGEDSERVICES option must be commented out and the scheduler that is being reviewed must be running.
  2. Run CMD.EXE as Administrator.
  3. Path to the baclient folder.
  4. Gather the list of installed TSM Client Schedulers.
    1. dsmutil list
  5. Gather the dsm.opt path from the options field for the failing scheduler service, use the output exactly from the previous step.
    1. dsmcutil query /name:"<name of TSM scheduler>"
  6. Run the dsm client program to start the scheduler in the foreground.
    1. dsmc sched -optfile="<path to the options file from the previous step>"
  7. On the TSM Server, modify the schedule or create a new scheduler with the option STARTTIME=now
  8. Review and correct errors on the client side.

Further Reading

  1. IBM Knowledge Center
  2. Scheduled backup fails with ANS1909E, ANS1512E, or ANR2579E
  3. Dsmcutil commands: Required options and examples
  4. Dsmcutil valid options