The backup server for a remote application is a PC that is designated to take over the role and responsibilities of the primary configuration server in the event that the primary should fail.
A backup server acts as a client unless it is called upon to take over the role of the primary configuration server.
Note: Although a backup server enables the application to continue to run, users will be able to complete operational changes only. Configuration changes can be made only when the primary configuration server is online (for more details see Operational Changes vs. Configuration Changes).
Any given remote application can have one or more backup servers specified. Backup servers are identified in your application's Sync.WIF file.
Within the Sync.WIF file is a section similar to the following example::
[Configuration-Servers]
Name = Chief
Name = EngineRoom
Name = WatchKeeperStation
The first workstation name to appear in the list ("Chief" in the example above) is the designated primary configuration server for the application (see Primary Configuration Server). All subsequent workstations referenced in the list are the designated backup servers. In this example, two backup servers are specified: The workstation named, "EngineRoom" will enable your application to continue to run in the event that the workstation named, "Chief" fails. In the event that both the "Chief" and the "EngineRoom" workstations fail, the workstation named, "WatchKeeperStation" will enable your application to continue running.
The list of configuration servers can also be configured using the application’s Properties dialog from the VAM. See: Designation of Primary and Backup Servers.
Note: A detailed example of how your application manages data when one or more servers fail can be found in Server Redundancy.