Move SG cluster to new location

[Mike Smith_33]

I apologize if this has already been asked, I could not get the advanced search to work. I am in the process of planning a move of a 2 node Serviceguard cluster to a co-location site to run on new hardware. I have a couple ideas of how I think this can be done but I would like to know if anyone has run across a best practices document on how to do this or if anyone has already done this and can share any details, that would be appreciated as well.

[Steven E. Protter]

Shalom,

Plan on some downtime.

Tasks at hand:

1) Getting a clean copy of data on shared storage to the new site.
2) The majority of the serviceguard configuration can be copied across. A standard cmquerycl/cmcheckconf/cmapplyconf cluster rebuild will be required.
3) Construct the servers on the new site so the volume group names and logical volume names are similar to the old site, identical if possible. If not, you will need to edit configuration files before step 2.

SEP

[Mike Smith_33]

What I have done up to this point.
- Taken make_tape_recovery of vg00 for both nodes
- Loaded these on the new hardware at the colo site
- Worked extensively with volume groups using identical names and minor numbers to get these accessible to the systems
- Successfully recovered data to the volume groups

The ip addresses will need to be changed which I see a couple of documents on that. I believe I am headed in the right direction so far. Thanks for any direction.

[Stephen Doud]

Please provide more details.
co-location means what?
Will the nodes in the cluster get new hostnames or IP addresses?
What changes will take place, that may affect the cluster? (Use cmviewconf now and identify any parameters that will change).

[Mike Smith_33]

In this case co-location means we are moving the servers to a hosted data center. They will provide the space, power, etc... and we will manage remotely. My goal is to keep the same names but the ip addresses will be changing. I did find a document on how to do this but no joy so far. The hardware will be equivalent, with the exception of a firmware version here or there.

I will check cmviewconf and see what that reveals.

[Stephen Doud]

Okay - so you will be putting new hardware in place at the new data center, and intend on using the same hostnames as the nodes in the original cluster, albeit with different IP addressing. Since it is new hardware, configure a new cluster. It's okay to use the same hostnames, because the subnet's will be different from the original location.

However configuring this new cluster will require some shared storage.

Will you be moving the shared disk storage from the old cluster to the new cluster? This has a bearing on whether you will have to vgimport the volume groups from that array.

How about cluster arbitration? LVM Lock disk, or quorum server?