ETC Eos v1.3 - Manual (Page 311)

B
Multi-console and Synchronized Backup 297
Appendix B
Multi-console and Synchronized
Backup
Overview
This appendix outlines the procedures required to use multiple Eos control devices (such as an Eos
console, Remote Processor Unit (RPU), Remote Video Interface (RVI), or PC with client dongle)
simultaneously on a network. It outlines the setup, configuration, and behavior that is entailed in an
Eos multi-console scenario.
Eos multi-console functionality is also used to provide synchronized backup of your show while
running multiple Eos devices on the network.
Definition of terms
Familiarize yourself with these terms prior to setting up a multi-console system.
• Primary - When an Eos is configured as a primary, other Eos devices can connect and
synchronize with it. If using a backup processor, the primary is the Eos that will be backed up.
Only Eos consoles and RPUs can be set to primary. By default, all Eos consoles will start up
as a primary.
• Backup - The Eos capable of taking control of the system if the primary fails. You may input
data and run your show from a backup. There can only be one backup in an Eos network and
you must specify which primary it is backing up. Only Eos consoles and RPUs can be set to
backup.
• Client - Any online Eos that is not the master or backup is a client. Client data is sent and
received over the network, and clients will synchronize with a designated primary.
• Offline - Any Eos controller that is disconnected from the Eos network. Changes to show data
performed on an offline Eos will not affect the rest of the Eos network or the lighting system.
• Master - The Eos that is currently sending control data to the lighting system is the master. In
most circumstances this is also the primary. Should a primary fail and a backup takes control,
then the backup will be acting as the master.
• Tracking - Any console that is synchronized with a master is tracking. Once a backup takes
control it becomes a master and is no longer tracking.
• User - A user is an Eos defined by a user ID. If it has a unique user ID, the Eos will operate
separate from other Eos devices on the network, but still track show data. If it shares a user
ID, Eos will synchronize with like IDs. See
User ID and multi-console features, page 300 .
• System - One primary Eos, one backup Eos, and (if available) multiple clients synchronized
together.
N o t e : Eos consoles, RPUs or a PC running Eos with a client dongle may all be
considered active units on an Eos network. For the sake of brevity, the term Eos
is used to represent any/all of these options in the following descriptions.