Other Topic Library Versions

Recovering from a failover

DANGER
Do not attempt this procedure except under the supervision of qualified Grass Valley personnel.

In the following procedures, K2server1 and K2server2 represent your redundant K2 Media Servers. The procedure begins with K2server1 being the server on the failed side of the SAN. K2server2 is acting as the primary K2 Media Server.

  1. Verify primary/backup roles and make sure K2server2 is the primary.
  2. Start up K2server1. It is now out of service.
  3. Determine the cause of the failover and take corrective action as necessary. If you need to do service work on K2server1 or other devices on the failed side of the SAN, you can do it now. After your work is complete, proceed with the next step.
  4. If there are K2 Media Servers with role of iSCSI bridge, Ethernet switches, or Fibre Channel switches on the same redundant “side” as K2server1, start or restart them. Make sure they have been started up at least once before putting K2server1 into service.
  5. In Server Control Panel, for K2server1, click Start. This notifies K2server2 (via a heartbeat signal on the serial cable) that K2server1 is coming online as backup.
  6. Verify K2server1 as backup.
  7. All failover processes are complete. All media management mechanisms are now running and K2server1 is now qualified and acting as the backup.

Copyright © 2015 Grass Valley USA, LLC. All rights reserved. K2 Summit 9.5 gvtp_20151106_14:27:14