Radha,
I think this is a different problem.
(Vint solved his problem with my suggestion of
renaming the log file name.)
The "hang" problem you are experiencing will probably
require some tracing. If this continues for you, please call
IBM/Tivoli support.
Thanks,
Del
----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com
"It's a beautiful day. Don't let it get away." -- Bono
Radha
Parameswaran To: ADSM-L AT VM.MARIST DOT EDU
<csctivol@BART cc:
.GOV> Subject: Re: Domino TDP Woes
Sent by:
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MAR
IST.EDU>
06/18/2001
06:23 PM
Please respond
to "ADSM: Dist
Stor Manager"
I have a very similar problem. I have setup the logfiles to be archived at
certain set time throughout the day. For example this morning, the 5:00 am
schedule worked fine and it archived some log files. But at noon, though
the backup started, it hung up. If you look at the log file on the domino
server, this is what you see.
Tivoli Storage Manager
Tivoli Data Protection for Lotus Domino - Version 1, Release 1, Level 1.0
(C) Copyright IBM Corporation 1999, 2000. All rights reserved.
License file exists and contains valid license data.
ACD5221I The d:\PROGRA~1\IBM\ADSM\domino\domasch.log log file has been
pruned successfully.
Starting Domino transaction log archive...
Initializing Domino connection...
The only way to fix the problem is to reboot the server. I do not get any
Dr.Watson error.
"Vint A.
Maggs" To: ADSM-L AT VM.MARIST DOT EDU
<vint.maggs@S cc:
RS.GOV> Subject: Domino TDP Woes
Sent by:
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MA
RIST.EDU>
06/13/01
10:44 AM
Please
respond to
"ADSM: Dist
Stor Manager"
Hello All,
We have been troubleshooting problems with three of our Domino servers
without luck. At one point all was well but gradually the backups began
failing. Nothing has changed on the TSM server side so the thinking is it
must be a client problem. Various schedules are failing with no apparent
reason. We are running TSM 3.7.3.0 on Solaris 2.7. The clients are
running NT 4.0, Lotus Domino R5, and Domino TDP 1.0.
Prior to this morning, schedules were failing, though not the same
schedules. On one server the daily incremental schedule is failing while
on others the hourly archive is failing. As a work around we could run a
backup from the gui and it worked.
This morning, we broke down what occurs when the scheduled backup runs and
realized that it kicks off the domarc.cmd at the required interval. All
commands (domarc, dominc, domina) use the same .cfg and .opt file for the
specific node. I executed the domarc.cmd file for SERVER A from a DOS
window and the Dr. Watson appeared. I then tried just the statement that
runs the job (start /B domdsmc archivelog... excluding the log locations)
and it ran fine. So this backed me into the log files. I changed the log
file name and paths and when executing the domarc.cmd file it ran as
expected. I duplicated this scenario on SERVER B (which has also been a
problem child) and again it fixed the problem as well. I then went to
SERVER C and did the same for the dominc.cmd that has been failing. Before
making the changes the Dr. Watson appeared. After making the changes and
executing the command in a DOS window it ran without the error on all
three servers.
So with all of that discourse, what gives with the .log files? The Dr
Watson is usually an access violation error. Is the log file in an open
state from an earlier failure, thus since it can't write it just stops
goes no further? If this were the case, why does it right some of the
information (i.e. Valid License File....) before the Dr. Watson error
occurs?
Anyone else experience this?
Thanks,
Vint
|
