ADSM-L

Re: [ADSM-L] Tape Reclamation Problem / Auditdb

2008-10-02 05:08:24
Subject: Re: [ADSM-L] Tape Reclamation Problem / Auditdb
From: Jeff White <jeff.white1 AT BARCLAYS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 2 Oct 2008 10:03:40 +0100
I remember doing an auditdb on a 120gb db and after 60 hours, based on the
number of 4k pages processed, it was about 40% complete. That was on a TSM
server running on z/os.

So yes, I am hoping that the audit vol has cured. But our design team are
asking for an estimate on how long the

dsmserv auditdb archstorage logmode=rollforward fix=yes

would take.

Thanks for the responses


Jeff White


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kelly Lipp
Sent: 02 October 2008 10:01
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Tape Reclamation Problem / Auditdb

Jeff,

Yes, the audit db is an off-line command so your TSM server will be down.
For a 180GB db, that could be a while.  I don't know for sure on a targeted
audit like this, however.  Might be shorter than I am accustomed to and I'm
sure others will weigh in.

Keep your fingers crossed.  Maybe you fixed it!

Thanks,

Kelly Lipp
STORServer, Inc.
________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Jeff 
White
[jeff.white1 AT BARCLAYS DOT COM]
Sent: Thursday, October 02, 2008 2:36 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Tape Reclamation Problem / Auditdb

Hi

TSM Server v5.3.3.1
Running on AIX

I have a problem where an offsite volume continues to be reclaimed many
times, even though it's utilization is 0% and pct_reclaimable space is 0%.
The reclaim process starts then ends, the starts again etc. Been doing that
for the last 3 days.

On the IBM support site, there is a hit, which was last updated in May 2008


Space reclamation is always processing the same volumes, even after
successfull completion. Problem possibly caused by inconsistency in the DB
archival storage information.

An offline database AUDIT on the archstorage subset will help to recover
from this situation:

dsmserv auditdb archstorage logmode=rollforward fix=yes

Having researched the forum, I found a similar hit, where it was recommended
to
Upd vol xxxxx acc=readw
Audit vol xxxxx fix=yes
Upd vol xxxxx acc=offsite

I've done this, and the reclaim has stopped, hopefully it will not
re-appear.

But if it does and I have to run the 'dsmserv auditdb archstorage
logmode=rollforward fix=yes', how long is that likely to take, as I will
need the TSM server offline? Database size is 180gb, if that is relevant.

Thanks


Jeff White



This e-mail and any attachments are confidential and intended solely for the
addressee and may also be privileged or exempt from disclosure under
applicable law. If you are not the addressee, or have received this e-mail
in error, please notify the sender immediately, delete it from your system
and do not copy, disclose or otherwise act upon any part of this e-mail or
its attachments.

Internet communications are not guaranteed to be secure or virus-free.
The Barclays Group does not accept responsibility for any loss arising from
unauthorised access to, or interference with, any Internet communications by
any third party, or from the transmission of any viruses. Replies to this
e-mail may be monitored by the Barclays Group for operational or business
reasons.

Any opinion or other information in this e-mail or its attachments that does
not relate to the business of the Barclays Group is personal to the sender
and is not given or endorsed by the Barclays Group.

Barclays Bank PLC.Registered in England and Wales (registered no. 1026167).
Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom.

Barclays Bank PLC is authorised and regulated by the Financial Services
Authority.

This e-mail and any attachments are confidential and intended solely for the 
addressee and may also be privileged or exempt from disclosure under applicable 
law. If you are not the addressee, or have received this e-mail in error, 
please notify the sender immediately, delete it from your system and do not 
copy, disclose or otherwise act upon any part of this e-mail or its attachments.

Internet communications are not guaranteed to be secure or virus-free.
The Barclays Group does not accept responsibility for any loss arising from 
unauthorised access to, or interference with, any Internet communications by 
any third party, or from the transmission of any viruses. Replies to this 
e-mail may be monitored by the Barclays Group for operational or business 
reasons.

Any opinion or other information in this e-mail or its attachments that does 
not relate to the business of the Barclays Group is personal to the sender and 
is not given or endorsed by the Barclays Group.

Barclays Bank PLC.Registered in England and Wales (registered no. 1026167).
Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom.

Barclays Bank PLC is authorised and regulated by the Financial Services 
Authority.