tdp domino schedule backup fails

[tejodeep]

HI all,

I am facing problem with tdp domino 5.4 windows as manual backup is running fine but schedule backup fails

error.log

07/30/2009 19:28:04 ANS1512E Scheduled event 'DAILY_INCR_MAILDB01' failed. Return code = 1.
07/30/2009 19:38:35 ANS1909E The scheduled command failed.
07/30/2009 19:38:35 ANS1512E Scheduled event 'DAILY_INCR_MAILDB01' failed. Return code = 1


and schedule.log


07/30/2009 19:38:35 --- SCHEDULEREC QUERY BEGIN
07/30/2009 19:38:35 --- SCHEDULEREC QUERY END
07/30/2009 19:38:35 Next operation scheduled:
07/30/2009 19:38:35 ------------------------------------------------------------
07/30/2009 19:38:35 Schedule Name: DAILY_INCR_MAILDB01
07/30/2009 19:38:35 Action: Command
07/30/2009 19:38:35 Objects: c:\tsmc\dominc.cmd
07/30/2009 19:38:35 Options:
07/30/2009 19:38:35 Server Window Start: 19:37:00 on 07/30/2009
07/30/2009 19:38:35 ------------------------------------------------------------
07/30/2009 19:38:35
Executing scheduled command now.
07/30/2009 19:38:35
Executing Operating System command or script:
c:\tsmc\dominc.cmd
07/30/2009 19:38:35 Finished command. Return code is: 1
07/30/2009 19:38:35 ANS1909E The scheduled command failed.
07/30/2009 19:38:35 ANS1512E Scheduled event 'DAILY_INCR_MAILDB01' failed. Return code = 1.
07/30/2009 19:38:35 Sending results for scheduled event 'DAILY_INCR_MAILDB01'.
07/30/2009 19:38:35 Results sent to server for scheduled event 'DAILY_INCR_MAILDB01'.
07/30/2009 19:38:35 ANS1483I Schedule log pruning started.
07/30/2009 19:38:35 ANS1484I Schedule log pruning finished successfully.
07/30/2009 19:38:35 Querying server for next scheduled event.
07/30/2009 19:38:35 Node Name: XFR-MAILDB01-LOTUS
07/30/2009 19:38:35 Session established with server XFR-AP-ORAC01_SERVER1: Windows
07/30/2009 19:38:35 Server Version 5, Release 4, Level 3.0
07/30/2009 19:38:35 Data compression forced on by the server
07/30/2009 19:38:35 Server date/time: 07/30/2009 19:38:34 Last access: 07/30/2009 19:38:34


any clue

thanks in advance

tejo

 

[cjhood]

Can you post the contents of the 'c:\tsmc\dominc.cmd' file?

-Chris

 

[tejodeep]

start /B domdsmc incremental * /subdir=yes /adsmoptfile=dsm.opt /logfile=domischnew1.log >> dominc.log

 

[eRogue]

there's definetely something wrong in your cmd file.

07/30/2009 19:38:35 Executing scheduled command now.
07/30/2009 19:38:35 Executing Operating System command or script:
c:\tsmc\dominc.cmd
07/30/2009 19:38:35 Finished command. Return code is: 1

As you can see the script starts and finish at the same second. Post the content if the command c:\tsmc\dominc.cmd. Also, do you have a file on that computer called dominc.cmd in c:\tsmc ? do you have it in c:\tsmc or c:\tsm ? maybe it's just a type in the schedule

Sebastian

 

[eRogue]

what's the content of c:\tsmc\dsm.opt ? Can you see anything in c:\tsmc\dsierror.log ?
also, if you're running this string from the c:\tsmc folder what happens ?

so open a cmd window and type
c:
cd c:\tsmc
start /B domdsmc incremental * /subdir=yes /adsmoptfile=dsm.opt /logfile=domischnew1.log

post the result here.

 

[tejodeep]

when i run dominc.cmd

out put is

The process cannot access the file because it is being used by another process.
The process cannot access the file because it is being used by another process.
The process cannot access the file because it is being used by another process.
The process cannot access the file because it is being used by another process.
The process cannot access the file because it is being used by another process.

 

[eRogue]

try running from c:\tsmc the following line

start /B domdsmc incremental * /subdir=yes /adsmoptfile=dsm.opt /logfile=templog.log and post the results. Also please look for a file called dsierror.log in the same folder and post the last 10 lines in here. Also look into the process tab and see how many domdsmc processes are running. It might be the log file that windows is complaining about. Also, you've specifed that runnign a domino backup from the tivoli data protection gui works right ?

 

[tejodeep]

dsieror.log are

07/30/2009 18:50:46 Management class 'DATA\...\*' named on include/exclude line 199 does not exist.
07/30/2009 20:39:21 Management class 'DATA\...\*' named on include/exclude line 195 does not exist.
07/30/2009 20:39:21 Management class 'DATA\...\*' named on include/exclude line 195 does not exist.
07/30/2009 20:39:22 Management class 'DATA\...\*' named on include/exclude line 195 does not exist.
07/30/2009 21:26:41 Management class 'DATA\...\*' named on include/exclude line 195 does not exist.
07/30/2009 21:27:04 cuConfirm: Received rc: -50 trying to receive ConfirmResp verb
07/30/2009 21:27:04 ANS1017E Session rejected: TCP/IP connection failure
07/30/2009 21:27:04 sessSendVerb: Error sending Verb, rc: -50
07/30/2009 21:27:04 cuConfirm: Received rc: -50 trying to send Confirm verb
07/30/2009 21:27:04 ANS1017E Session rejected: TCP/IP connection failure
07/30/2009 21:27:04 sessSendVerb: Error sending Verb, rc: -50
07/30/2009 21:27:04 ANS1017E Session rejected: TCP/IP connection failure


and two domdsmc process are running,

this is my current dominc.cmd script can you please check if there's any error in this script

-------------------------------------------------------------------------



rem ==================================================================
rem Replace "X:" with the drive where the Domino Application Client
rem is installed.
rem ==================================================================

set dom_dir="c:\Program Files\Tivoli\TSM\domino"

cd /d %dom_dir%

rem ==================================================================
rem The 2 lines below put a date and time stamp in a log file for
rem you.
rem
rem Note: You can change "dominc.log" to whatever you prefer.
rem ==================================================================
echo Current date is: >> dominc.log
date /t < NUL >> dominc.log
echo Current time is: >> dominc.log
time /t < NUL >> dominc.log

rem ==================================================================
rem Now call the command line to do the incremental:
rem
rem Note: You can change "domisch.log" to whatever you prefer.
rem ==================================================================
start /B domdsmc incremental * /subdir=yes /adsmoptfile=dsm.opt /logfile=domischnew1.log >> domincnew1.log


thanks

 

[eRogue]

first of all, kill both domdsmc if you don't run anything, then try again just the start /b command and post the result. if you have multiple processes you may have this issue. also do a q sess at the tsm server prompt and cancel all the session for that particular node. after that you can rerun the start /b command and everything should be ok.

 

[tejodeep]

thanks a lot i think this works