Hello guys,
sorry for a little bit longer post, but I think I should explain my
problem clearly.
My environment:
TSM server 5.2.3.0 on AIX 5.2
Two TDP for Domino 5.1.5 on W2K with TSM API client 5.2.0 on two Domino
servers 6.0, which are in Domino cluster.
Domino servers are not configured for transaction logging
These two Domino servers are primarily for mail processing. Both of them
contains the same databases (replicated through cluster replication
mechanism). Number of databases is approximately 5000 (most of them users
mail databases).
Both servers (lets call them mail1 and mail2) contains identical
configuration of TDP for Domino
with identical TSM node name.
Incremental backup of all databases is done daily from one of the servers
(in case of server failure, scheduler for backup is started manualy on
another server). Backup is done LAN-free.
Everything worked fine for some time. About week ago, arised my problem.
On one of the servers, lets say mail2, I am not able to perform
incremental backup using following
command:
domdsmc incremental *
I get following error message:
ANS1245E (RC122) Format unknown
When I start TDP for Domino GUI, in restore window I can see in left pane
entries for both Domino servers, but when I want to expand databases under
mail2 server, I get the same error message.
Strange thing is, that I can backup and restore databases using command
line, but I have to specify which databases I want to process in more
specific way, for example:
domdsmc incr mail\*
or
domdsmc restore mail\xyz.nsf /into=abc.nsf
Both of previous commands work fine.
On another server (mail1) everything works fine. My problem is, that for
some time, backups were done from mail2 server, so most recent backups are
stored in TSM under this server name (mail2.DOMDBS filesystem).
I decided to try tracing TDP for Domino and TSM API on mail2 server to
find out what is going on using following commands:
domdsmc query dbbackup * /tracefile=trace1.out /traceflag=service,api
domdsmc incr * /tracefile=trace2.out /traceflag=service,api
Examining trace logs I found out following problem:
in both of previous commands, TDP for Domino performs search in TSM DB for
backed up databases.
This search is done by sequencialy calling of DDsmApi::ddsmGetNextQObj()
function until there is another entry in TSM DB for mail2.DOMDBS
filespace.
This search stops in both cases after processing exactly the same database
(entry in TSM DB) with following error:
(this is part of trace.log file)
01/06/2005 12:43:35.077 [5548] : dsmapi.cpp (2097): Enter
DDsmApi::ddsmGetNextQObj()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 177): Enter
DBaseApi::StartApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 182): Exit
DBaseApi::StartApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 195): Enter
DBaseApi::EndApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 290): Enter
DBaseApi::GetApiName()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 294): Exit
DBaseApi::GetApiName(), returning api name TSM
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 221): Exit
DBaseApi::EndApiCall(), elapsed milliseconds 0, total time 472 for TSM
Apis
01/06/2005 12:43:35.077 [5548] : dsmapi.cpp (2104): Exit
DDsmApi::ddsmGetNextQObj(), rc = 122
01/06/2005 12:43:35.077 [5548] : dsmapi.cpp ( 588): Enter
DDsmApi::AgtDsmRCMsg()
01/06/2005 12:43:35.077 [5548] : dsmapi.cpp (2300): Enter
DDsmApi::ddsmRCMsg()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 177): Enter
DBaseApi::StartApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 182): Exit
DBaseApi::StartApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 195): Enter
DBaseApi::EndApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 290): Enter
DBaseApi::GetApiName()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 294): Exit
DBaseApi::GetApiName(), returning api name TSM
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 221): Exit
DBaseApi::EndApiCall(), elapsed milliseconds 0, total time 472 for TSM
Apis
01/06/2005 12:43:35.077 [5548] : dsmapi.cpp (2308): Exit
DDsmApi::ddsmRCMsg(), rc = 0
01/06/2005 12:43:35.077 [5548] : dsmapi.cpp ( 609): Exit
DDsmApi::AgtDsmRCMsg() rc = 0
01/06/2005 12:43:35.077 [5548] : dsmqberi.cpp ( 512):
dsmGetNextQObj returned with 418 on a q backup for filespace
SKMail2.DOMDBS object \*\*
01/06/2005 12:43:35.077 [5548] : dsmapi.cpp (2013): Enter
DDsmApi::ddsmEndQuery()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 177): Enter
DBaseApi::StartApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 182): Exit
DBaseApi::StartApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 195): Enter
DBaseApi::EndApiCall()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 290): Enter
DBaseApi::GetApiName()
01/06/2005 12:43:35.077 [5548] : baseapi.cpp ( 294): Exit
DBaseApi::GetApiName(), returning api name TSM
01/06/2005 12:43:35.093 [5548] : baseapi.cpp ( 221): Exit
DBaseApi::EndApiCall(), elapsed milliseconds 0, total time 472 for TSM
Apis
01/06/2005 12:43:35.093 [5548] : dsmapi.cpp (2020): Exit
DDsmApi::ddsmEndQuery(), rc = 0
01/06/2005 12:43:35.093 [5548] : dsmqberi.cpp ( 603): Exit
DDsmQueryBackupEri::ProcessReqestDetails(), rc = 418
01/06/2005 12:43:35.093 [5548] : dsmqferi.cpp ( 210): Enter & Exit
DDsmQueryFilespaceEri::~DDsmQueryFilespaceEri()
01/06/2005 12:43:35.093 [5548] : dsmqeri.cpp ( 293): Enter
DDsmQueryEri::~DDsmQueryEri()
01/06/2005 12:43:35.093 [5548] : dsmqeri.cpp ( 301): Exit
DDsmQueryEri::~DDsmQueryEri()
01/06/2005 12:43:35.093 [5548] : baseeri.cpp ( 149): Enter & Exit
DBaseEri::~DBaseEri()
01/06/2005 12:43:35.093 [5548] : domqberi.cpp (1599): ADSM specific
object information:
According to manuals, RC 122 unknown format of file, and for RC 418, there
is no description in manual, and in return codes source file is following
description:
#define DSM_RC_OPT_CLIENT_DOES_NOT_WANT 418/* Client doesn’t want this
value*/
/* from the server
What does this mean?
I suspect that there is some problem with one or more entries in TSM DB.
Will audit DB help to resolve this problem?
Is it possible to remove specific entry from TSM database?
Any help is appreciated.
Best regards
Ing. Jozef Zatko
Login a.s.
Dlha 2, Stupava
tel.: (421) (2) 60252618
|
