Grass Valley iTX System v.2.6 - Manual (Page 302)

System resilience
Configuring resilience modes
Services that are designed to run in load-balanced mode do so automatically; no configuration
is needed.
For a primary-backup arrangement, the primary service requires no configuration. For the back-
up service, you need to enter the command-line parameter "-backup" in the Server Controller
Configuration window. More details , page 223.
Checking the resilience mode
You can check the resilience mode of a service in the service window. The illustrations show a
load-balanced System Service and a primary Routing Data Service:
Redundancy options
System Database
For the Database Server, you may run a back-up machine in parallel with the main one. Both
machines run Microsoft SQL Server and the iTX services.
You use SQL Server functionality (either clustering or mirroring) to keep the main and back-up
System Databases synchronised. If you use SQL Server mirroring functionality, the witness SQL
Server runs on another machine in your iTX system (for example, the Time Server machine).
For more information about SQL Server clustering or mirroring functionality, see the Help
information for SQL Server or contact iTX Support.
Output Server
An Output Server has some built-in redundancy: it has a local cache in which it keeps copies of
media files that are in its current schedule. So long as the required files are in the cache, the
Output Server can play out a schedule even if the Media Store or the System Database goes
offline.
To cover for the potential failure of an Output Server, you may use either of two methods:
• For each channel, run a back-up Output Server in parallel with the main Output Server.
The back-up machine plays the same schedule as the main one, which delivers the
content for transmission.
Such a set-up is often called an N + N system; for any number of main Output Servers
there is an equal number of back-up Output Servers.
March 2015 System Administrator Guide Page 302 of 404