ADSM-L

Re: [ADSM-L] TSM v6 - virtual volume deletion leaves archive objects on target server

2010-07-14 13:59:22
Subject: Re: [ADSM-L] TSM v6 - virtual volume deletion leaves archive objects on target server
From: Dave Canan <ddcanan AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 14 Jul 2010 10:30:19 -0700
Joerg, I checked with development on this. Are you doing this with a dedup
storage pool? They did have one APAR for that 2 months ago. I would first
suggest getting a PMR opened; if you do that, I can pursue it.



Dave Canan
IBM Advanced Technical Support
TSM Performance
ddcananATUSDOTIBMDOTCOM

On Mon, Jul 12, 2010 at 6:16 PM, J. Pohlmann <jpohlmann AT shaw DOT ca> wrote:

> I am just wondering if other folks have encountered this problem where the
> deletion of a virtual volume (for example as result of reclamation) on the
> source server leaves the archive object "dangling" on the target server.
> Delgraceperiod is the default of 5 days. Reconcile volumes fix=yes cleans
> it
> all up again. I have seen this on TSM v6.1 and v6.2. TSM v5 works fine with
> this default. Does anyone have a fix for this? I have been doing ad-hoc
> periodic reconcile volumes for months on a v6 virtual volume environment
> because I first suspected server-to-server communications problems, but
> then
> saw the same thing happen in other installations.
>
>
>
> Joerg Pohlmann
>
> 250-585-3711
>

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