Data types to be synced

Pertinent data that is used by Db2 Data Management Console servers such as server environment, monitoring configuration, bootstrap properties, jvm options must be synced between the two high availability nodes so that when failover occurs, the online server uses the same data and results with seamless experience from users.

Db2 Data Management Console logs are also synced from the online nodes to the offline node, in a different set of logs folder so that log data is not mixed. This will help analyze or troubleshoot issues after the failover occurs. These log syncs are done by using crontab and rsync services, which are also available in Linux® OS.

Sync is performed only from online to offline node and not from offline to online node to avoid any interruption to data in the online node. The only special cases are when non-log files are deleted from source, which will be automatically recovered from target.

Changes to the data occur in real time by using inotifywait and rsync services available in Linux OS.

The following directories and files must be set up to be synced between the two high availability nodes. Object path begins with <dmc-installed-location>/ibm-datamgmtconsole.

Type	Path	Frequency
Directory	/Config	Real time
Directory	/logs	Periodic (every 5 mins)
Directory	/wlp/usr/servers/dsweb/resources/security	Real time
File	/wlp/usr/servers/dsweb/bootstrap.properties	Real time
File	/wlp/usr/servers/dsweb/server.env	Real time
File	/wlp/usr/servers/dsweb/jvm.options	Real time
File	/addons/drs/drs-agent/.env	Real time
File	/addons/drs/drs-agent/config.yaml	Real time
Directory	/addons/drs/drs-agent/insightdb	Real time
Directory	/addons/drs/drs-agent/logs	Periodic (every 1 hour)
File	/addons/job-scheduler/config/config.json	Real time
Directory	/addons/job-scheduler/logs	Periodic (every 1 hour)

Note: You can set up data sync by using the syncup.sh script. For more information, see Creating a resource (Step 10 - Example of syncup.sh script).