> 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
I have never done this kind of disk move, but have occasionally run into similar problems with tapes. I have always updated the old volumes to 'acc=readonly'. Using 'acc=unavailable' is likely to cause problems if any files are spread across multiple volumes.
