-
-
Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
Please help
- Thread starter reddy
- Start date
For anyone to be able to assist, need some additional info:
What version of the TSM Client and OS are we running?
What version of the TSM Server and OS, that the TSM Client is backing up to?
Are we able to perform a manual backup?
In the dsmerror.log/dsmsched.log were there any message around the time frame when the schedule backup failed?
If we start the schedule daemon/service in the foreground, do we see schedule information or do we see an error message?
Is the schedule daemon/service running at the time?
What version of the TSM Client and OS are we running?
What version of the TSM Server and OS, that the TSM Client is backing up to?
Are we able to perform a manual backup?
In the dsmerror.log/dsmsched.log were there any message around the time frame when the schedule backup failed?
If we start the schedule daemon/service in the foreground, do we see schedule information or do we see an error message?
Is the schedule daemon/service running at the time?
Thanx for your response LED888!
TSM server has v534 on aix and client is linux RHAS with v525.
Scheduler is running at schedule time and no messages on dsmerror and sched.log files except the error I posted.
I ran manual incremental and completed with no failure.
Thanks.
TSM server has v534 on aix and client is linux RHAS with v525.
Scheduler is running at schedule time and no messages on dsmerror and sched.log files except the error I posted.
I ran manual incremental and completed with no failure.
Thanks.
Hmmmm........
If there are no error message in the dsmerror.log or in the dsmsched.log.
We are able to run a manual backup with out any problems.
1. Make sure that we start the schedule daemon as root.
2. In the dsm.sys file update the schedmode oppsite to its current setting.
schedmode polling <- This is the default.
update to or visa versa.
schedmode prompted
Need to add the following when using schedmode prompted.
tcpclientaddress ip.addres.of.client
tcpclientport 1501 <- I use the same port as for tcppport.
Any update made in the dsm.opt/sys need to stop/restart the schedule daemon.
Majority of the return codes are from the operating system.
Need to find out what 126 means for RHAS Linux to get a hint on why the schedule backup failing with an RC 126.
Good Luck,
Sias
If there are no error message in the dsmerror.log or in the dsmsched.log.
We are able to run a manual backup with out any problems.
1. Make sure that we start the schedule daemon as root.
2. In the dsm.sys file update the schedmode oppsite to its current setting.
schedmode polling <- This is the default.
update to or visa versa.
schedmode prompted
Need to add the following when using schedmode prompted.
tcpclientaddress ip.addres.of.client
tcpclientport 1501 <- I use the same port as for tcppport.
Any update made in the dsm.opt/sys need to stop/restart the schedule daemon.
Majority of the return codes are from the operating system.
Need to find out what 126 means for RHAS Linux to get a hint on why the schedule backup failing with an RC 126.
Good Luck,
Sias
