ADSM-L

RE: Réf. : Re: Auditdb timing - FYI

2003-05-28 01:42:20
Subject: RE: Réf. : Re: Auditdb timing - FYI
From: Oscar Kolsteren <Oscar.Kolsteren AT POSTBANKMAIL DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 28 May 2003 07:41:56 +0200
Hi Etienne,

I can't find anything on the "cleanup backupgroup" command. Can you tell me 
more about it, please ?

Thanx,

Oscar

-----Original Message-----
From: GUILLAUMONT Etienne [mailto:eguillau AT RGB-TECHNOLOGIE DOT FR]
Sent: dinsdag 27 mei 2003 16:20
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Réf. : Re: Auditdb timing - FYI


Hi,

I don't know if it can help but I had a similar problem and a "cleanup
backupgroup" command helped a lot. My Db size decreased by 30 % And the
audit db went from days to minutes (my db was greatly smaller but so was my
server)

If my memory is good, Cleanup Backupgroup is used to clean bad entries in
the db wich were created by older versions of TSM, a bug in version 4.2 or
something like that. You just have to issue it once.

You will get no documentation but it works

Regards

Etienne GUILLAUMONT
e-mail : etienne AT rgb-technologie DOT fr

RGB Technologie
Parc d'Innovation, Bâtiment PYTHAGORE
11 Rue Jean SAPIDUS
67400 ILLKIRCH
Tél :  03 90 40 60 60
Fax : 03 90 40 60 61


                                                                                
                                                              
                    Henk ten Have                                               
                                                              
                    <[email protected]        Pour :  ADSM-L AT VM.MARIST DOT EDU    
                                                                     
                    L>                   cc :                                   
                                                              
                    Envoyé par :         Objet :      Re: Auditdb timing - FYI  
                                                              
                    "ADSM: Dist                                                 
                                                              
                    Stor Manager"                                               
                                                              
                    <ADSM-L AT VM DOT MA                                        
                                                                     
                    RIST.EDU>                                                   
                                                              
                                                                                
                                                              
                                                                                
                                                              
                    27/05/2003                                                  
                                                              
                    16:01                                                       
                                                              
                    Veuillez                                                    
                                                              
                    répondre à                                                  
                                                              
                    "ADSM: Dist                                                 
                                                              
                    Stor Manager"                                               
                                                              
                                                                                
                                                              
                                                                                
                                                              




Hi Gretchen,

> "Expiring.Objects".
> 05/27/2003 09:00:57  ANR9999D imfsdel.c(1872): ThreadId<25> Error 19
> deleting
> group leader 0 176658713.
[ cut ]
> The audit was successful and did allow me to delete the problem node.
> However,
> there really should be a way to go after the offending entry and blast
> it (under
> adult supervision, of course!). I'm not really going to be able to
> justify a down
> time of 7 days just to clean up an account. It's now happened again on
> another
> server, so I will have to do this test again to get a good estimate of
> the down time required to clean that server up.

First of all I bet that someone from development Level 3 already contact
you, if not, that will happen very soon and I know probably who...can't
give
you his name, I know he likes beer and he owns me a couple....;-)
Second of all your problem looks quite familiar to the problem we had
3 mounth ago (Expiration failed completely from a certain point).
They will give you some (hidden) tools to fix your problem, the same
they did with me. And if you'r lucky, you learn a lot more about the
inside of the TSM server....
And btw, our DB is "only" 75 Gbyte, we have "only" +550 million objects
and an auditdb fix=yes "only" took +5 days.....which is a no go
offcourse
for a production machine.
But we manage to fix the problems, with many effort and great help from
Tivoli Support L3.

Cheers,
Henk.

-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>