Grass Valley K2 Summit Storage Area Network v.7.1 - Manual (Page 402)

26 October 2009 K2 Storage Area Network Installation and Service Manual 402
Managing redundancy on a K2 SAN
Managing redundancy on a K2 SAN
If you have a redundant K2 SAN, use the procedures in this section to control the
primary/redundant roles of the K2 Media Servers. Procedures are as follows:
• “Identifying current primary/backup K2 Media Servers” on page 402
• “Triggering an intentional failover” on page 404
• “Recovering from a failover” on page 405
Identifying current primary/backup K2 Media Servers
Before attempting any configuration or service work on a redundant K2 Media
Server, you must know if the server is the current primary server or the current backup
server for the media file system and the metadata service. While most configuration
and service work can be accomplished on a backup server without affecting the
operation of the SAN, if you attempt configuration or service work on the operating
primary server, it will likely result in record/play failures and/or a loss of media.
To identify the current primary/backup K2 Media Server, use one or more of the
methods described in the following procedures:
Identifying primary/backup from NetCentral
While monitoring the K2 Media Server in NetCentral, do the following:
1. In the NetCentral tree view, select the K2 Media Server.
2. Click the Facility view control button
3. Open the Roles subsystem
4. Click the Media Database Server or Metadata Server link.
The Media Database Server dialog box opens and reports the Failover Mode as
either Primary or Backup.
Identifying primary/backup from the K2 System Configuration application
1. In the tree view, select the name of the K2 SAN, which is the top node of the
storage system tree.
2. Click the Server Control Panel button. The Server Control Panel opens.