Summary

To plan for the event that the Master becomes unavailable for a substantial period of time, Fox Technologies strongly recommends that you designate at least one of your Replicas as a failover Replica to back up the Master. In the event that the Master needs to be replaced, it would be this Replica that you would convert to become the new Master, perhaps only until the old Master can be brought back online.

This article details how to configure such a failover Replica.

Reference Information

Failover Replicas require a number of preparatory steps to ensure they can be quickly brought into production as the Master if needed.


The failover Replica should:

  • Have an identical $BOKS_etc/ENV file as the Master, with the exception that the BOKSINIT variable should be set to server rather than master. In addition, the variable ISMASTER must NOT be set on the failover Replica. For a full list of the variables that must be identical on the Master and Failover Replica, see "ENV variables" below.
  • Have the same hotfixes installed as are installed on the Master to ensure a smooth transition and equal operation after converting the Replica to the Master.
  • If you have installed the presentation server for FoxT Control Center on the Master, it should also be installed on the failover Replica. In the file /etc/opt/bccps.properties, use the hostname for the Replica rather than the (current) Master for the AdminServerURL attribute.

Note: If you have installed the FCC presentation server on a host other than the Master, you need to update the file /etc/opt/bccps.properties with the name of the failover Replica in the AdminServerURL attribute if it is converted to become the Master.

  • Have the following BoKS ENV variable settings: BCCASD=on and BCCASD_ABAC=on (this one is only needed if you are using ABAC). This will ensure that the BoKS admin server is automatically started if the Replica is converted to become the new Master.
  • The shared memory size SHM_SIZE should be the same and large enough to provide a sufficient amount of free space. Preferably 50% or more recommended. You can check the available space using the command dumpbase -m.
  • Have a copy of the directory $BOKS_var/sso_creds, or on BoKS 7.2 $BOKS_var/ca, that is identical to the directory on the Master on the failover Replica. This directory contains the PKI infrastructure for BoKS. You can configure the program push_files to copy this directory (and other files) to the failover Replica by adding the following lines to the file $BOKS_etc/distrib.cfg:
    SERVERS name_of_failover_replica
    $BOKS_var/ca/*

    or for pre-7.2 versions:

    SERVERS name_of_failover_replica 
    $BOKS_data/sso_creds/ca_creds/keypkgs/*

    For more information see the BoKS man page push_files and the comments in the distrib.cfg file.

  • The Replica must have a host certificate (BoKS 7.2 and later) or host virtual card (BoKS pre-7.2 versions).
  • The root account on the Replica must be properly protected
  • If you are using BoKS password checkout, the Replica must have a copy of the password encryption key $BOKS_etc/pwm/keys/pwmd.key identical to the key on the BoKS Master.

In addition, Fox Technologies recommends following these best practices for your failover Replica:

  • This Replica should match the configuration of the Master.
  • This Replica should be as far removed from the Master as possible, so as not to be affected by the same disaster.
  • Define disaster recovery procedures.
  • Plan for multiple types of disaster, for example the Master being out of commission, the Master and Replicas being separated for an extended period.
  • Practice disaster recovery regularly.
  • Use backup to create an archive copy of the database, making sure you follow your organization’s record retention policy with the backup.

Root Account on Failover Replica

Plan to protect the root account on this Replica just as you do for the root account on the Master. This might include:

  • Restrict knowledge of the root password on this Replica to a limited number of administrators.
  • Consider creating a Host Group for administration that includes only the Master and the Replica that is designated as backup to the Master, so that Access Routes for administration can be easily set up and will already be in place if the Replica needs to be quickly converted to Master.

You need to have a BoKS account for the root account on this backup Replica. A BoKS account is needed for administration on any host, but is particularly important to have in place for the backup Replica, since access as root is required during and after conversion, and at a time when you cannot use the Master to add the account to the database. With no local root account in the database, you would need to either work locally on the console or deactivate BoKS Protection.

ENV Variables

List of ENV variables that should be the same on the Master and Failover Replica where applicable (some are normally left at the default setting or not set at all):

  • ADSYNC (if AD Bridge is being used)
  • AUTO_DEREGISTRATION_HOURS
  • AUTOREGISTER_POSTPROGRAM
  • BCCASD
  • BCCASD_ABAC (if ABAC is being used)
  • BCCASD_CIPHER_LIST
  • BCCASD_LOGIN_EXPAND_HGROUP
  • BCCASD_PORT
  • BCCASD_SESS_EXPIRE
  • BLOGSD_CIPHER_LIST
  • BLOGSD_LOGTO_AUDITLOG
  • BLOGSD_RELAYTO_SYSLOG
  • BLOGSD_SYSLOG_ADDR
  • BLOGSD_SYSLOG_PORT
  • BLOGSD_SYSLOG_TLS
  • BOKS_SSH_USERKEY_PROVISIONING
  • BRIDGE_MASTER_R_STAT_INTERVAL_MINUTES
  • BRIDGE_MASTER_R_STAT_INTERVAL_SECONDS
  • BRIDGE_MASTER_R_STAT_TIMESLOTS
  • BRIDGE_MASTER_R_STAT_MAXFILESIZE_KB
  • BRIDGE_SERVM_S_STAT_INTERVAL_MINUTES
  • BRIDGE_SERVM_S_STAT_INTERVAL_SECONDS
  • BRIDGE_SERVM_S_STAT_TIMESLOTS
  • BRIDGE_SERVM_S_STAT_MAXFILESIZE_KB
  • BRIDGE_TIME_BETWEEN_CONNECT_ATTEMPTS
  • CRLDOWNLOAD_CACERT_FILE
  • DISABLE_EXTENDED_LOG_INFO
  • DRAINMAST_ASYNC_BATCH_DATA_MAX
  • DRAINMAST_ASYNC_BATCH_MAX
  • DRAINMAST_FEED_DBUPDATES
  • DRAINMAST_FEED_LOGUPDATES
  • DRAINMAST_FQUE_NSYNC
  • DRAINMAST_LOG_SLOW_SECONDS, DRAINMAST_PSWUPDATE_LOG_SLOW_SECONDS
  • DRAINMAST_STAT_INTERVAL_MINUTES, DRAINMAST_PSWUPDATE_STAT_INTERVAL_MINUTES
  • DRAINMAST_STAT_INTERVAL_SECONDS, DRAINMAST_PSWUPDATE_STAT_INTERVAL_SECONDS
  • DRAINMAST_STAT_SLOW_LIST_SECONDS, DRAINMAST_PSWUPDATE_STAT_SLOW_LIST_SECONDS
  • DRAINMAST_STATLOG_MAXFILESIZE_KB, DRAINMAST_PSWUPDATE_STATLOG_MAXFILESIZE_KB
  • DRAINMAST_TRL_BATCH_DATA_MAX
  • DRAINMAST_TRL_BATCH_MAX
  • FORCED_PSWVALIDTIME
  • KSL_LOGFILE_FDLOCATION
  • KSLFD_LOGLEVEL
  • KSLFD_MAXAGE
  • KSLOG_FINALIZE_STALELOG
  • LOGFILEMODE
  • LOGIN_SPECIAL_CHARS
  • MKHOME_OVERWRITE
  • MASTER_EMS_NSYNC
  • MASTER_FQUE_NSYNC
  • MASTER_LOG_SLOW_SECONDS
  • MASTER_QUEUE_TIMEOUT
  • MASTER_STAT_INTERVAL_MINUTES
  • MASTER_STAT_INTERVAL_SECONDS
  • MASTER_STAT_SLOW_LIST_SECONDS
  • MASTER_STATLOG_MAXFILESIZE_KB
  • MASTER_VCSYNCD_NSYNC
  • OVERLAPPING_ACCOUNT_CHECK
  • PSWFLUSHTIME
  • SAVEDB
  • SKIP_LOGINOUT_UPDATE
  • SKIP_LOGINOUT_UPDATE_ARRAY_SIZE
  • SKIP_LOGINOUT_UPDATE_EXPIRE_TIME
  • SHM_SIZE
  • SYNC_DOWNLOAD_ONLY
  • TRANSACTIONLOG_SIZE_KB
  • UID_ALLOC_SCHEME
  • UIDRANGE

Note: The variable BCCASD_LISTENADDR should be the same on the Master and the Failover Replica only if the 2 hosts have the same IP address.

See Also

For information on recovery procedures in the event of an outage of the BoKS Master, see the BoKS Manager Administration Guide for your BoKS Manager version.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: March 21, 2019