SyncHA process

Before the shared file system is up, some configuration files must be available. These are initially “mirrored” to the secondary server by the cnvt2ha.sh script, and then maintained across the two server computers by the syncHA process, which is run once per minute from cron.

On the Primary, the command stat's the mirrored files to see what has changed, and copies these out to the /usr/adic/HAM/shared/mirror folder. On the secondary server, the files that have changed are copied in. The list of mirrored files is defined in the /usr/cvfs/config/filelist and /usr/adic/gui/config/filelist tables as follows.

In the /usr/cvfs/config directory:

• license.dat
• fsmlist
• fsnameservers
• fsroutes
• fsports
• *.cfg
• *.cfgx
• *.opt
• nss_cctl.xml
• snpolicyd.conf
• blockpool_settings.txt
• blockpool_root
• blockpool_config.tmpl
• blockpool_config.txt
• bp_settings

In the usr/adic/gui directory:

• database/derby_backup.tar
• logs/jobs/*
• config/host_port.conf

Note: By default, the syncha process backs up the internal state of the StorNext GUI every minute, which may cause a performance impact to some GUI operations. The file /usr/adic/gui/config/syncha_interval.conf can be used to reduce the frequency of the GUI state backups. The contents of the file, if present, should contain an integer value that specifies the minimum number of seconds between GUI state backups. This file is host dependant and applies only to syncha when it is run in cron mode on the primary system.