Hello
We have a customer's TSM who backups everything but misses a server.
Any idea WHY?
I have no experience on working with TSM, all i know is that its a beast.
Cheers
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hello, thanks for your post, I'm checking it atm, i'll just give you some extra-lights!
Its running in WS2003 Enterprise
I saw the daily report and noticed that INDMSCS04 was marked as missed, (cluster), all others including indmscs01,02,03 are ok.
i'll go step-by-step slowly so i can understand what im doing
thanks for your comment!
Hi
Why does a server report nodes as missed?
I think the common errors are:
- TSM Service on server is "hanging" .
- TSM Client is not installed.
- Wrong configuration towards the TSM Server.
- TSM Scheduler missed the assigned window becouse the TSM Server was/is too busy.
Check options file:
"c:\program files\tivoli\tsm\baclient\
This is the "brain" of the client. Here you define what, where, and how you want your backup too be.
Look for the path to scheduler log and error log. Check if the name/ip address of the TSM server is correct,
Check Scheduler log (sched.log):
Whats the last entry into the scheduler log. check if its has regulare connection to the server, if it seems like its has just stopped at a job or havent been talking to the TSM Server for a couble of days, restart the TSM Service.
If restarting the TSM Service dosnt work, please provide more info from the dsmerror.log, the sched.log and the dsm.opt fil.
Regards
Michael
Is the client that is missing the local node or the resource group(MSCS)? If it is the group, only the active nodes should be trying to backup. You might need to check out the TSM client cluster configuration.
http://publib.boulder.ibm.
Business Accounts
Answer for Membership
by: woolmilkporcPosted on 2009-09-10 at 04:08:44ID: 25299024
Hi,
It's a gentle beast if you know how to take it!
From your Q I assume that the customer's backups are taken using the Central Scheduler of TSM.
I assume further that you noticed that the node's backup is missing by checking the scheduler events.
So there are several things to check -
1) Which TSM schedule is the missed server node (which I will call "client_node" in the following) part of?
Check at the TSM server using the "dsmadmc" command line interface -
QUERY SCHEDULE * * NODE=client_node F=D
Check the output for correct settings, particularly verify "Expiration"
2) Is the client scheduler process running at the client?
What is the client's OS?
If Unix, check for a running "dsmc sched ..." process using "ps -ef | grep dsmc". Start or restart it using the appropriate command (mostly contained in an init script).
If Windows, check for the TSM scheduler service. Start or restart it! Take care to have "automatic" start configured.
3) Examine the client's logfiles for possible errors.
Under Unix they are by default /opt/tivoli/tsm/client/ba/
Under Windows it's by default in the "baclient" subdirectory of the installation tree.
4) Check server logs
Again using "dsmadmc" display the server messages around the projected start time of the missed backup -
QUERY ACTLOG NODE=client_node BEGINDATE=-x BEGINTIME=-y
with "-x" meaning "current date minus x days" and "-y" meaning "current time minus y hours"
That's enough to begin the investigation.
Please tell me what you found!
wmp