I'm in the process of designing a migration of the diskpools to a better
organisation of disks. Some of the pools only have one volume, so they
will be no problem to move - there's only one other disk the data can go
to - but the other pools with more than one disk could cause problems.

Is there a standard approach for this activity? I considered:

a) updating the other volumes in the group to acc=unavail to ensure the
data doesn't to go those volumes, just the 'new' volume

b) instead of 'move data's, restore storage pool from our copy pool, which
is a little painful since they are offsite.

If there are any better suggestions than my a) out there I'd be happy to
hear them!

Cheers,
Matthew



Aviva plc
Registered Office: St. Helen's, 1 Undershaft, London EC3P 3DQ
Registered in England Number 02468686
www.aviva.com

This message and any attachments are confidential.
If you are not the intended recipient, please telephone
or e-mail the sender and delete this message and any
attachment from your system. Also, if you are not the
intended recipient you must not copy this message or
attachment or disclose the contents to any other person.