topic Re: Changing SAN on MC/SG cluster questions in Operating System - HP-UX

Changing SAN on MC/SG cluster questions

Gino Castoldi_2 — Mon, 16 Nov 2009 17:08:50 GMT

Hi

Servers: rp5470, HPUX 11.11 MC/SG (2 nodes), SAN (EMC SYM)

We are moving our 2 servers to another SAN (EMC SYM). My understanding is that in order for the cluster and systems to see the new disks we need to make configuration changes - Create new volume groups, LVM changes, quorum disk, change the cluster configuration, etc.

Does anyone have a list of procedures on what needs to be done?

10 points to any answer.
Thank you
-Gino

Re: Changing SAN on MC/SG cluster questions

Calandrello — Mon, 16 Nov 2009 18:03:46 GMT

dear
this can be done in two ways
Firstly
you will use the disks that are now associated with the server in the new SAN
if this is necessary you should make the zonning that these disks are seen by the OS on the new SAN
run the command
vgexport-s -m -p vgname /tmp/vgname_map
after the new SAN you should recognize the disks with the command insf
and then importing the map created vgimport /tmp/vgname_map
If you plan to use new disks
just create new vgs
new lvols
change the scripts cluster /etc/cmcluster

Re: Changing SAN on MC/SG cluster questions

Wim Rombauts — Tue, 17 Nov 2009 13:31:55 GMT

Do you have MirrorDisk/UX available on your server ? If so, that could make the migration easier, since you could mirror the database on the old storage to the new storage, while you can keep one database instance operational.
Otherwise, you will probably have to make a cold copy, and shutdown your database completely during that time.

Re: Changing SAN on MC/SG cluster questions

Steven E. Protter — Tue, 17 Nov 2009 14:18:12 GMT

Shalom,

1) Take a cold backup of any data. Things can go wrong.
2) Connect new SAN, pvcreate the new disks.
3) Stop the cluster
4) use lvextend -m 1 lvol_name new_disk

Step 4 requires mirror/ux. It will permit you to back copy the data very quickly. There are SAN utilities that are even faster.

5) Make changes to cluster configuration. Change you lock disk.
6) cmquerycl/cmcheckconf/cmapplyconf

Step 6 will have you end up with a new, hopefully working cluster.

The lesson here is to cover you options ahd schedule downtime. This can not be done safely on a running system, especially a database server.

SEP