I'll be speaking with someone later this week who is doing this "regularly".

The new name is something like PowerHA SystemMirror (version 6.1 and beyond for now). I am not as active with HACMP/PowerHA as I once was.

Basically, it should be fairly simple with XD, i.e. all in smit screens - as XD knows how to talk with storage systems. If I recall correctly XD negotiates the visibility of the disks. On the side/site that is active - the disks are visible, on the inactive side they are invisible, or otherwise inaccessable. On a node failure, or directed move of a resource group XD/SystemMirror cause the visibility status to change.

Maybe visibility is the wrong term - but the "smarts" of CD is that it negotiates with the storage system where the LUNs are visible/active.

And today I just heard that there are two or three new courses from IBM training for HACMP/PowerHA/SystemMirror. The course codes are AN41-AN46 (some of these course are already a year old, others are less than a few weeks.)

When I have time I'll look a bit deeper - so maybe someone who has more recent experience will give an answer before that.

NFS has been fairly integrated into HACMP for many years. I have forgotten how long ago HANFS product was discontinued as a separate product - being fully integrated into mainstream HACMP/PowerHA.

HaGeo was the old name for what became HACMP/XD. HAGEO was a collection of scripts and additional monitors to assist with using the GeoRM product. GeoRM was an AIX LVM-like system for remote mirroring.

These days setting up a remote node, or dual-site/cross-site cluster depends on whether you are doing the mirroring using a product like GeoRM, or whether the mirroring is being done in the background by the storage system.

In short, before anyone can really help you will need to tell us more about your plans and/or capabilities for maintaining remote mirrors.