Recently, Oracle RAC on HPUX was implemented because serviceguard first read the documents three days in advance to build a car by closed doors.
Getting started at the site also removes some questions about reading documents, which may be the same for many people.
1. About whether service guard is required:
If you use ASM to manage disks, you do not need serviceguard (10 Gb later)
To use a shared vg lv bare device, you must not only use serviceguard, but also use serviceguard extension for RAC.
2. About lock VG
2 nodes are required, and 3 or more nodes are recommended.
# Consider the following when indexing a cluster.
# For a two-node cluster, you must use a cluster lock.
# A cluster of three or four nodes, a cluster lock is strongly
# Recommended. For a cluster of more than four nodes,
# Cluster lock is recommended. If you decide to configure
# A lock for a cluster of more than four nodes, it must be
# A quorum server.
Lock VG is not necessarily a specialized VG, but a data VG.
If the lock VG is an independent VG, you only need to describe it in ops_volume_group and do not need to activate it in the package. That is to say, the lock VG is always inactive.
3./etc/lvmrc File
Auto_vg_activate = 0, even if you do not add vg00 to custom_vg_activation () is okay, the HP-UX will not be silly to do not activate the root volume group.
4. About export VG
After that, we found that the size of some LV is small and lvextend is required. To check the internet, we also need export and import!
In fact, this is not necessary because vgexport is only used to export a list. This action is not required if no LV is added or deleted.
Don't worry, it's a big deal to reactivate VG.
5. Configuration
Similar
Cmquerycl-v-C/etc/cmcluster. ASCII
Cmmakepkg-P/etc/cmcluster/pkg1/pkg1.conf
In fact, these are not configuration files. They can only be called a "template"
Finally, apply these files to the configuration of serviceguard.
Cmapplyconf-v-C/etc/cmcluster. ascii-P/etc/cmcluster/pkg1/pkg1.conf
Others are careful ....