I've done this a couple of times now with slightly mixed results; on balance
I'd much rather have this capability than not.
In one instance the space remaining on the in-use drives was rather tight
(90+%) which caused the backup to blow out by an hour or so - at least we
couldn't see any other reason for the additional time - so we possibly
didn't buy ourselves all that much time by moving the data beforhand.
In another case the request returned a message stating that it couldn't find
the unit requested although it was clearly there. It turned out the error
was an incorrect error message; there was insufficient space to move the
data from this disks requested (in-house sandbox machine we were fooling
around with the commands on).
Other than those hiccups it worked fine for us on V5R4; if there's a
reasonable amount of space available it a useful tool.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Monday, 31 March 2008 9:23 a.m.
To: 'Midrange Systems Technical Discussion'
Subject: Swapping 35GB drives for 72GB drives
We are going to be removing a raid set of 36GB drives and putting in 72GB
drives in their place. We have sufficient disk space to migrate data off the
drives coming out before we do this swap. I found this redbook (chapter 10)
on the process for doing this but it was for V5R2, we are on V5R4.
The STRASPBAL command
that does this does not appear to have changed for V5R4. Is the procedure
still the same on V5R4? Are there any issues anyone has encountered when
doing this operation that we should look out for?