I think that each DISK storage pool volume has a 4kB header created when
it is defined.  I get this from the fact that a small volume has a
non-zero %util even when it is first defined and empty.

You'll note that the DR module's plan file includes macros to mark the
original disk pool volumes as destroyed and defines replacement ones.
When the pool is completely empty (from the point of view of the DB
backup which is being restored), you are accomplishing the same thing by
doing what John indicates.

Cheers...
Bruce

John Schuch wrote:
>
>    I don't know why it's happening, but when I did my
>    Disaster Recovery test I ran into the same problem and I
>    had to delete and redefine my storage volumes in ADSM...
>
>    delete volume /adsmstg/stgvol01...
>    define volume poolname /adsmstg/stgvol01...
>
> ______________________________ Reply Separator 
> _________________________________
> Subject: Vary on disk volume fails
> Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at 
> PO_EXTERNET
> Date:    7/23/98 1:01 PM
>
> I am testing the migration of a AIX v2 server to an AIX v3 server running
> on a different box. I am getting the following error message when trying
> to vary on all the disk storage pools onto the v3 server:
>
> ANR1315E Vary-on failed for disk volume ...... invalid label block
>
> The disk storage pools were empty on the v2 system so I formatted new ones
> on the v3 system using "dsmfmt -data" command. The dsmfmt ran without any
> errors.
>
> Does anyone know why the disk storage pools are getting the invalid label
> block error?
>
> Thanks in advance for your help,
> Robert Jarry
>
> ------------------------------------------------------------------------------
> Robert Jarry                             email:  r.jarry AT cc.utexas DOT edu
> Unix Services                            phone:  (512) 475-9330
> Academic Computing & IT Services
> The University of Texas at Austin