Configuring Backup Realm Servers for Fault Tolerance

The primary server and each satellite server can each designate at most one backup server.

Task A Starting the Backup Server

1. Supply the --backupfor parameter, to start as a backup server.
2. If authentication is required, supply the --server.user and --server.password parameters, with credentials that the backup server can use to authenticate itself to the regular server.

   Ensure that this user name is in the authorization group ftl-backup.

Task B Starting the Regular Server

The regular server can be either the primary server or a satellite server.

3. Supply the --backupto parameter, indicating the location of the backup server (see Connect Port).
4. If authentication is required, supply the --server.user and --server.password parameters, with credentials that the regular server can use to authenticate itself to the affiliated servers.

   Ensure that this user name is in the appropriate authorization group (either ftl-primary or ftl-satellite).

   If satellites and backups require different authentication credentials, then also supply the --server.authtobackup.user and --server.authtobackup.password parameters. The regular server uses these credentials to authenticate itself to its backup server.

Task C Configuring Clients

5. In the realm connect call, programmers supply the locations of two realm servers:
   • Supply the location of the regular server as the realm server URL argument (see Connect Port).
   • Supply the location of the backup server as the value of the secondary server property (see Connect Port).

Copyright © Cloud Software Group, Inc. All rights reserved.