DARE - Snapshot
HACMP provides a facility that allows changes to cluster topology and resources to be made while the cluster is active. This facility is known as DARE or to give it it's full name Dynamic Automatic Reconfiguration Event. This requires three copies of the HACMP ODM.
Keep in mind:all SMIT actions only affect the DCD. Invoking a synchronize at this point causes the DCD copied to all cluster nodes and a dynamic reconfiguration event is invoked. (ACD is never changed directly by the user)
When you configure an HACMP cluster, configuration data is stored in HACMP specific object classes in the Configuration Database (ODM). The AIX ODM object classes are stored in the default system configuration directory (DCD), /etc/es/objrepos. At cluster startup, HACMP copies HACMP-specific ODM classes into a separate directory called the Active Configuration Directory (ACD). If you synchronize the cluster (topology or resources) while the cluster manager is running on the local node, this action triggers a dynamic reconfiguration event. During Dynamic Reconfiguration the Default Configuration Directories (DCDs) on all cluster nodes are updated, and the data in the ACD is overwritten with the new configuration data, then the HACMP daemons are refreshed.
HOW DARE WORKS:
1. change topology or resources in smitty hacmp (this will change the DCD)
If you want to discard this changes what you make (in DCD) (only if you did not synch. yet):
Problem Determ. Tools --> Restore HACMP Conf. Database from Active Conf.
(during this a snapshot will be taken of the DCD if needed in future)
2. synchronize topology or resources in smitty:
-Verifying and Synchronizing (Standard): (this is under Initialisation and Standard Conf.)
(If you choose this there is no opportunity to modify the process in any way)
-Verifying and Synchronizing (Extended): (this is under Extended Conf.) here you can choose:
emulate or actual: emulate the change before actually doing it
force: this is dangerous, should be on "no"
verify changes only: it will be not synch. only verify, so it can be tested if a change is valid
logging: verbose can be used if standard does not show the reason why verification fails.
During the synchronization:
DCD is copied to SCD on the nodes -> snapshot of the ACD* -> content of SCD copied to ACD -> clstrmgr refresh -> SCD deleted
1. If DARE change successful after synch., but it does not give the desired result, then use the snapshot taken prior*
snapshot path: /usr/es/sbin/cluster/snapshots (i.e: active.0.odm, 0 is the most recent)
Extended Configuration --> Snapshot Conf. --> Apply Snapshot
2. If a DARE change fails and SCD does not cleared, then SCD acts as a lock and it prevents further config. changes.
If an SCD exists on any cluster node, then no further synch. permitted until it is deleted in smitty hacmp:
Problem Determ. Tools --> Release Locks Set by Dyn. Reconf.
Except cluster name, the add and delete functions can be used while the cluster is running.
It records the cluster configuration.
Adding a snapshot: Ext. Conf. -> Snapsh. Conf. ...
SNAPSHOTPATH variable shows the path to snapshots.
Default path: /usr/es/sbin/cluster/snapshots
Applying a snapshot:
When a cluster snapshot is applied, it overwrites the existing HACMP ODM classes on all cluster nodes with the HACMP ODM classes contained in the snapshot.
A snapshot may be applied from any cluster node.
if a snapshot is applied to a running cluster it will trigger a cluster wide DARE operation. In addition to modifying the default configuration directory (DCD), it also replaces the configuration data stored in the active configuration directory (ACD), and makes those changes the active configuration of the system.
"Un/Configure Cluster Resources?": If this option set to yes, HACMP changes the definition of the resource in the ODM and it performs any configuration necessary as well. (e.g: if removing a filesystem, it will be removed from the ODM, and it will be unmounted as well.)
- FS - LVM
- STORAGE - BACKUP
- UPD. - INSTALL