It is possible to use two Media Router service instances in a redundancy setup. In this case one of the Media Router service instances is configured to be the Primary in a Primary/ Secondary relationship. The following rules are applied:

• There shall be only one Media Router service configured as Primary. This is done using the PreferredMaster property.

• The Secondary Media Router service will automatically take control if the Primary is down or not responding. This behaviour may be overridden by setting the AutoFailover property to false. If so, activating the secondary Media Router service has to be done manually by issuing the SetActive command.

• The Primary Media Router service will always be the active Media Router service instance if it is running. This means that if the Primary is started then the Primary will take over the control of any active secondaries.

• Inactive or idle Media Router services will ignore any crosspoint changes sent from any clients.

• The Primary Media Router service will ensure that the Media Router state is synchronized with the secondary. This way, both Primary and Secondary shall always have the same configuration and crosspoints.

• Clients controlling the Media Router services have to apply one of the following strategies:

  • Send crosspoints to both Primary and Secondary Media Router services.

  • Send crosspoints only to the active Media Router service. In this case the clients need to monitor whether the Media Router services are active or not.

Related service properties

• Id: To set an unique identity of the Media Router service

• PreferredMaster: Set to true for the primary Media Router service

• Slave: Connection string to the other Media Router service in a redundancy setup.

• AutoFailover: Set to false to ignore automatic failover by the secondary when loosing connection to the primary.