ADSM-L

Re: [ADSM-L] TSM 6.1.2 DB Archivelog handling

2009-09-29 05:32:10
Subject: Re: [ADSM-L] TSM 6.1.2 DB Archivelog handling
From: Erwann Simon <erwann.simon AT FREE DOT FR>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 29 Sep 2009 11:29:36 +0200
Hi,

See also this technote : http://www-01.ibm.com/support/docview.wss?uid=swg21399352 It's been said that TSM also needs to sucessefully write its volhist?out (volhist.dat now !) file in order to allow deletion of archived logs, even if the DB backup was sucessfull.
The volhist.dat file is now required for restoring the TSM DB.

--
Best regards / Cordialement / مع تحياتي
Erwann SIMON


Grigori Solonovitch a écrit :
You need to run at least 2 full backups to clean the both log and arc

Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com

Please consider the environment before printing this Email


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Stefan Holzwarth
Sent: Tuesday, September 29, 2009 11:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM 6.1.2 DB Archivelog handling

We just started our new TSM 6 environment and are having problems
controlling amount of archived log files.
I could not find any parameter for setting retention or number of
logfiles in first and/or second archlog directory.
Also full dbbackups do not remove any of that files.

What do I miss?

Kind regards
Stefan Holzwarth

Please consider the environment before printing this Email.

"This email message and any attachments transmitted with it may contain confidential 
and proprietary information, intended only for the named recipient(s). If you have 
received this message in error, or if you are not the named recipient(s), please delete 
this email after notifying the sender immediately. BKME cannot guarantee the integrity of 
this communication and accepts no liability for any damage caused by this email or its 
attachments due to viruses, any other defects, interception or unauthorized modification. 
The information, views, opinions and comments of this message are those of the individual 
and not necessarily endorsed by BKME."