I think it might be one of the following:
1. Some objects has been deleted or changed but because the Replica is not
in-sync in all replicas(could be caused by slow server) it has not confirmed
the changed object on all replicas.
2. Not enough NDS rights for backup-user
Im not the expert but I think this could be why and why it works the next night
If you want to make sure check synchronization on master partition using
dsrepair and run "set dstrace=*u" and "set dstrace =*h" on the lagging server
console to force a hartbeat process
Regards
Louw Pretorius
_______________________________
Informasie Tegnologie
Stellenbosch Universiteit
There are only 10 kinds of people in the world: Those who understand binary and
those who don't
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Troy Frank
Sent: Wednesday, December 07, 2005 22:23
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] NDS problem
I've gotten messages like that occassionally, and there's usually 2 things that
are consistent.
1. The failed objects are all in the same partition.
2. The errors usually go away on their own the next night.
So what I'm thinking is that this maybe happens when backups are going on
during a replica udpate/syc?
Either way, I've never had to worry about it much, since it always sorts itself
out the next night.
>>> Timothy.Hughes AT OIT.STATE.NJ DOT US 12/7/2005 1:28:14 PM >>>
I am not 100% sure but I think we are receiving these messages at least some of
them is because the objects/file is not there anymore.
I checked the following and they are user ID's and it seems as though when a
user id is change to a different ID its trying still do a backup?
I guess when a object was backed up originally in the NDS tree it stays there
until it's deleted/taken out by someone (Novell admin)
I am not a novell person so...
ANS1228E Sending of object '.[Root].O=TREASURY.OU=OTIS.OU=OTISNET4.CN=OHRMCCL'
failed
11/23/2005 04:19:46 ANS1304W Active object not found
11/23/2005 04:20:04 ANS1228E Sending of object
'.[Root].O=TREASURY.OU=OTIX.OU=OTISNEX4.CN=CS3BROW' failed
11/23/2005 04:20:04 ANS1304W Active object not found
11/23/2005 04:25:50 ANS1228E Sending of object
'.[Root].O=TREASURY.OU=OTIX.OU=OTISNEXC.CN=OOHBRUN' failed
11/23/2005 04:25:50 ANS1304W Active object not found
11/23/2005 04:25:52 ANS1228E Sending of object
'.[Root].O=TREASURI.OU=OTIX.OU=OTISNEXC.CN=OOHCHAM' failed
11/23/2005 04:25:52 ANS1304W Active object not found
11/23/2005 04:27:43 ANS1228E Sending of object
'.[Root].O=TREASURY.OU=OTIX.OU=RV600.CN=OSXSIRA' failed
11/23/2005 04:27:43 ANS1304W Active object not found
11/23/2005 04:58:49 ANS1802E Incremental backup of '.[Root]' finished with 22
failure
Zoltan Forray/AC/VCU wrote:
> When we experienced similar issues, it was usually due to the ID being
> used for the backups not having sufficient rights.
>
> Either that or the TSA stuff being downlevel !
>
> Troy Frank < Troy.Frank AT UWMF.WISC DOT EDU > Sent by: "ADSM: Dist Stor
> Manager" < ADSM-L AT VM.MARIST DOT EDU >
> 12/07/2005 09:39 AM
> Please respond to
> "ADSM: Dist Stor Manager" < ADSM-L AT VM.MARIST DOT EDU >
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> Re: [ADSM-L] NDS problem
>
> This sounds like an eDir corruption problem, not a tsm problem per se.
> When you look through iManager/ConsoleOne, do you see that weird yyyy
> yyyy user, or haifa-cc object listed in the tree? Does the server
> doing nds backups have a master replica of the [root] partition? When
> you did the dsrepair, which kind of repair did you do?
>
>
> >>> rouzen AT UNIV.HAIFA.AC DOT IL 12/7/2005 3:54:39 AM >>>
> Hi to all
>
> I got this following error when trying to backup on a Novell client
> the directory (NDS) in my dsmerror.log:
>
> 12/06/2005 08:12:48 The directory database has been corrupted.
> 12/06/2005 08:12:48 The directory database has been corrupted.
> 12/06/2005 08:12:49 ANS1228E Sending of object
> '.[Root].O=HAIFA.OU=CC.Bindery Type=1959+CN=Haifa-cc' failed
> 12/06/2005 08:12:49 ANS1301E Server detected system error
>
> 12/06/2005 08:14:40 ANS1228E Sending of object
> '.[Root].O=HAIFA.OU=GLOBAL.OU=Apps.CN=ýýýýý ýýýý' failed
> 12/06/2005 08:14:40 ANS4005E Error processing
> '.[Root].O=HAIFA.OU=GLOBAL.OU=Apps.CN=ýýýýý ýýýý': file not found
> 12/06/2005 08:20:36 ANS1802E Incremental backup of '.[Root]' finished
> with
> 2 failure
>
> Do an exclude in my dsm.opt as:
> EXCLUDE "NDS:.[Root].O=HAIFA.OU=GLOBAL.OU=Apps.CN=ýýýýý ýýýý"
> EXCLUDE "NDS:.[Root].O=HAIFA.OU=CC.Bindery Type=1959+CN=Haifa-cc"
>
> And do a dsrepair on my novell client ....
>
> But still got the same errors !!!!!!!!!!!!
>
> My TSA NDS configuration :
>
> TSA Name: HAIFA
> TSA Module Nmae: tsands
> TSA Version: 6.54.1
> SMDR Version: 6.54.1
> User password location: XXX\sys:/tivoli/tsm/client/ba/tsm.pwd
> User/Password valid: YES
>
> My Novell server version is 6.05
> My Novell Tsm Client is 5.2.3.0
>
> Any ideas how to resolve this problem !!!!!!
> Regards
> Robert Ouzen
> E-mail: rouzen AT univ.haifa.ac DOT il
>
> Confidentiality Notice follows:
>
> The information in this message (and the documents attached to it, if
> any) is confidential and may be legally privileged. It is intended
> solely for the addressee. Access to this message by anyone else is
> unauthorized. If you are not the intended recipient, any disclosure,
> copying, distribution or any action taken, or omitted to be taken in
> reliance on it is prohibited and may be unlawful. If you have received
> this message in error, please delete all electronic copies of this
> message (and the documents attached to it, if any), destroy any hard
> copies you may have created and notify me immediately by replying to this
> email. Thank you.
Confidentiality Notice follows:
The information in this message (and the documents attached to it, if any) is
confidential and may be legally privileged. It is intended solely for the
addressee. Access to this message by anyone else is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any action
taken, or omitted to be taken in reliance on it is prohibited and may be
unlawful. If you have received this message in error, please delete all
electronic copies of this message (and the documents attached to it, if any),
destroy any hard copies you may have created and notify me immediately by
replying to this email. Thank you.
|
