The master node in iCluster is a special concept – it is the first node created in iCluster when it is first configured and contains the master copy of the metadata. Remember it has NO bearing whatsoever on replication direction.
Did you know that you can now activate single member at a time? In previous releases the DMACTOBJ command would only refresh the entire file.
The iCluster synchronization check routines (sync check) are very useful for ensuring that files on the primary node are identical to the backup node.
Experienced iCluster users know how to find or create the sync check report, but newer users may wonder where it is.
Here are some assorted tips on how to make the apply process really fly: End journaling on the backup for busy files (or all files if you are never going to use the backup for a switchover but only for offloading backups). If your applications update records all over the file (i.e. random) vs. sequentially […]
The iCluster continuous sync check is great! It provides quick notification in the monitor when something is out of sync. No need to run nightly sync check reports, just look at the monitor.
Once iCluster nodes are configured using a specific IP address, they will continue to use this IP address, however what if your network changes? How do you change the IP address used by iCluster?
Did you know that option 13 Activate OOS on the WRKHATMON (Work with target monitor) command will automatically refresh all iCluster Out of Sync (OOS) objects for a group in one fell swoop? No need to issue option 8 and option 1 for each of individual entry.
Is it a pain to issue CHGCURLIB ICLUSTER and then GO DMCLUSTER to get into iCluster?
If you are having communications issues, you can see some of the internal comms messages that are generated by iCluster behind the scenes to assist in problem resolution.