Appendix: PRA Administration Settings for Failover
Below is a list of all the administration settings available when setting up a backup B Series Appliance for failover. These are found in /login > Management > Failover. This information is also found in your Administrative Guide.
Setup a Failover Relationship
New Backup Site Connection Details
Host Name or IP Address
Enter the hostname or IP address of the B Series Appliance you wish to use as the backup in a failover relationship.
Enter the TLS port allowing this primary B Series Appliance to connect to the backup B Series Appliance.
Reverse Connection Details To This Primary Site
Host Name or IP Address
Enter the hostname or IP address of this B Series Appliance, which you wish to use as the primary in a failover relationship.
Enter the TLS port allowing the backup B Series Appliance to connect to this primary B Series Appliance.
This host's status
View the hostname of this site, along with its status of primary site instance or backup site instance.
Peer host's status
View the hostname of this site, along with its status of primary site instance or backup site instance. Also view the date and time of the last status check.
Expand or collapse a table of status events that have occurred.
Primary or Backup Site Instance Status
Text confirms that you are either on the primary or backup site instance for your host site.
Manually force a data sync from the primary B Series Appliance to the backup B Series Appliance.
Switch roles with the peer B Series Appliance, essentially forcing a failover for planned maintenance or a known failover event.
Check this box to pull a data-sync from the site instance at example.com while becoming the backup/primary
If you want to synchronize data from the peer B Series Appliance prior to swapping roles, select this checkbox. If this option is selected, all users on the existing primary B Series Appliance will be disconnected during the data sync, and no other operations will be available until the swap is complete.
Check this box to become a backup even if the peer site instance at example.com cannot be contacted
On the primary site instance, you have the option to become the backup even if the peer B Series Appliance cannot be contacted. If this option is unchecked, failover will be canceled if both B Series Appliances cannot be kept in sync in terms of their failover roles (one primary and one backup).
For example, if you know the current backup B Series Appliance is online but cannot be reached by the primary due to a network connection issue, you may wish to check this option to make the primary the backup before the network connection is restored. In this example, you would also need to access the current backup and make it the primary.
Break Failover Relationships
Break the failover relationship, removing each B Series Appliance from its role as primary or backup.
Primary or Backup Site Instance Configuration
Control the shared IP address the site instance uses in the event of a failover by selecting the checkbox for the failover IP address. If you change the relationship between the sites, the checked IP addresses will disable when a primary site becomes a backup, and will enable when a backup becomes a primary site. You should manually mirror the setting on the peer site, as the setting is not shared.
The settings you configure here will be enabled only when the site instance you are configuring is in a backup role.
When on the primary site instance, select Backup Settings to expand or collapse the page displaying the configuration fields.
Enable Backup Operations
Enable or disable site backups.
Primary Site Instance Timeout
Set how long the primary site must be unreachable before failing over.
Automatic Data-Sync Interval
You can control the timing details of the automatic data-sync interval.
Data-Sync Bandwidth Limit
Set bandwidth parameters for data-sync.
Enable Automatic Failover
Quickly enable or disable automatic failover.
Network Connectivity Test IPs
Enter IP addresses for the backup site to check to determine whether the backup's inability to reach the primary is because the primary is offline or the backup has lost its network connection.