EnterpriseDB Release Announcement for EFM 3.1

This article was originally published on June 05, 2018

• More granular control of switchover - Failover Manager now has additional syntax for the efm promote command.
• Control over agent lock file - The Failover Manager property file now includes the lock.dir property; the property specifies the location of a lock file that is used to prevent starting multiple agents for the same cluster.
• Multiple virtual IP addresses - are now supported by Failover Manager.
• Non-sudo host supported by upgrade-conf - The efm upgrade-conf utility now provides syntax that supports those users whose clusters reside on non-sudo hosts.
• Stop unreachable failed master database - The Failover Manager property file now includes the stop.failed.master property; the property instructs Failover Manager to attempt to stop a failed master database that can no longer be reached.
• Control nodes file updates for clusters - The Failover Manager property file now includes the stable.nodes.file property. The property controls Failover Manager behavior related to the .nodes file (when new nodes join or leave the cluster).
• Manage minimum severity level for user notification - The Failover Manager property file now includes the notification.level property; the property allows you to limit the type of notifications sent.
• Virtual IPs included in cluster status report - The content of the cluster-status report and cluster-status-json report has been updated to include information about VIP addresses.