ADSM-L

Re: [ADSM-L] Select Statement

2009-02-27 13:30:30
Subject: Re: [ADSM-L] Select Statement
From: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 27 Feb 2009 13:27:15 -0500
-----Timothy Conway wrote: -----

>Ok, here.  Do a stgpool backup, disable sessions and do another
>stgpool backup to eliminate and prevent new data.  While sessions
>are still disabled, mark the volume in question destroyed, and do
>a stgpool backup preview.  That should tell you every primary
>volume that has data on the volume in question.  Mark the volume
>readonly again, enable sessions, obtain and checkin the volumes it
>said it needed, (search the appropriate actl slice for 1228s), and
>do your reclamation.  Since you're talking about a single volume,
>probably just a "move data"? Then again, if what's happenning is
>that your reclamation is ending on a particular offsite volume,
>you should first find out what all offsite volumes are below your
>threshold, and do the ba stg preview with them all marked
>destroyed.

The online help for 'update volume' states that 'access=destroyed'
is valid only primary storage pool volumes.

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