| One method of migrating from hsz40's, using manual procedures.
Be aware that stiriped mirror sets from versions 2.7 on up are different
that 2.5 striped mirror sets. Check for striped mirror sets.
There is another method if the user is using SWCC.
From SWCC - save to configuration file- record name - for restoring
configuration, you can use SWCC, havent' tried it all but if you need
help let me know.
Here is the manual method.
Be aware version 3.x and version 5.x save configuration information is
incompatable. So using HSZ save_configuration information will not
be seen when going to a new major version, such as v3 to v5
This procedure is only a suggestion and is in no way a supported or
documented procedure. No guarantees are made.
1. Backup user data, just in case
Shutdown databases/Dismount all volumes from host operating system
2. Obtain and record the following information from the hsz subsystems:
show this full
show other full - if dual configured
show device full
show storage full
show units full
Note physical placement of devices
3. Delete all units
4. Delete all storage sets(raid 5, raid 0 , raid 1, raid 0+1)
5. Delete all devices
6. Shutdown both controllers
7. Install hsz40's including installation of all devices in the appropriate
shelves, according to information obtained from step 2. Of course all
you would have to do is just install the hsz40's into the controller
shelves, you wouldn't have to physcially remove the devices, since you
will be using the same shelves.
Have license information ready
8. REmove program cards PCMCIA from controllers,
Power on hsz40's and all shelves
While holding in reset button, push in one controller PCMCIA card on
one of the controllers. Release reset button when card is full seated.
Do the same on the other controller if dual configured
9. set hsz controller parameters as recorded in step 2.
(SCSI ID's, cache_policy, etc.)
10. Install licenses as needed
11. Set FAilover mode if dual configured
12. Wait until battery condition shows good consistently, if dual
controller configuration, wait until battery shows good on both
controllers, consistently.
If battery condition changes or stays low, wait until battery condition
shows good consistently.
12. Do NOT Initialize any devices, or storage sets etc.
All disk devices should have been physically installed into their
appropriate shelves according to information obtained in step 2.
a. If disks have not been configured into the hsz's then use
"add disk" commands as needed or run the config utility on the
hsz. Device configuration should match that information obtained
in step 2. - DO NOT INITIALIZE
b. Add storage sets as needed according to information in step 2.
Do NOT INITIALIZE
C. Configure storage sets and single jbods(if any) into the appropriate
units according to information obtained in step 2.
DO NOT INITIALIZE -
IF THIS STEP GIVES ERRORS SUCH AS METADATA NOT CORRECT, THEN BE
SURE THAT STORAGE SET LIST OF DEVICES IS EXACTLY THE SAME AS
THAT RECORDED IN STEP 2. DO SHOW STORAGE FULL
D. Show units full - all units should either be available or on line
to one or both controllers. Set writeback on units according to
information obtained in step 2.
To test controllers before restarting/mounting the file systems:
1. Set nopreferred on one of the controllers.
2. If the host system is stopped; at the console prompt, issue a show
device command to insure that all target id's can be seen from the
hsz. You should at least see all lun 0 devices, depending upon the
console type.
If the host system is running and unix is being used
then use the file utility to access at least one unit on each target id
on the hsz. If using vms use the show dev/full to insure that the
devices are still on line.
3. Set nopreferred on the other controller, if dual configured,
4. Do step 2 again, to be sure that both controllers can be accessed from
the host system.
5. Restart sytem/mount file systems
|