Pinnacle Systems Interplay Engine - 2.2 User Manual

Avid® Interplay®Engine

Failover Guide

Legal Notices

Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.

This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be used in accordance with the license agreement.

Avid products or portions thereof are protected by one or more of the following United States Patents: 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,584,006; 5,640,601; 5,644,364; 5,654,737; 5,724,605; 5,726,717; 5,745,637; 5,752,029; 5,754,851; 5,799,150; 5,812,216; 5,828,678; 5,842,014; 5,852,435; 5,986,584; 5,999,406; 6,038,573; 6,069,668; 6,141,007; 6,211,869; 6,532,043; 6,546,190; 6,596,031; 6,747,705; 6,763,523; 6,766,357; 6,847,373; 7,081,900; 7,403,561; 7,433,519; 7,671,871; 7,684,096; D352,278; D372,478; D373,778; D392,267; D392,268; D392,269; D395,291; D396,853; D398,912. Other patents are pending.

Avid products or portions thereof are protected by one or more of the following European Patents: 0506870; 0635188; 0674414; 0752174; 1111910; 1629675. Other patents are pending.

This document is protected under copyright law. An authorized licensee of [product name] may reproduce this publication for the licensee’s own use in learning how to use the software. This document may not be reproduced or distributed, in whole or in part, for commercial purposes, such as selling copies of this document or providing support or educational services to others. This document is supplied as a guide for [product name]. Reasonable care has been taken in preparing the information it contains. However, this document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. does not accept responsibility of any kind for customers’ losses due to the use of this document. Product specifications are subject to change without notice.

The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:

Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.

THE SOFTWARE IS PROVIDED “AS-IS” AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

The following disclaimer is required by the Independent JPEG Group:

This software is based in part on the work of the Independent JPEG Group.

This Software may contain components licensed under the following conditions:

Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.

Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Daniel Dardailler makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.

This product includes software developed by the University of California, Berkeley and its contributors.

The following disclaimer is required by Nexidia Inc.:

Manufactured under license from the Georgia Tech Research Corporation, U.S.A. Patent Pending.

The following disclaimer is required by Paradigm Matrix:

Portions of this software licensed from Paradigm Matrix.

The following disclaimer is required by Ray Sauers Associates, Inc.:

“Install-It” is licensed from Ray Sauers Associates, Inc. End-User is prohibited from taking any action to derive a source code equivalent of “Install-It,” including by reverse assembly or reverse compilation, Ray Sauers Associates, Inc. shall in no event be liable for any damages resulting from reseller’s failure to perform reseller’s obligation; or any damages arising from use or operation of reseller’s products or the software; or any other damages, including but not limited to, incidental, direct, indirect, special or consequential Damages including lost profits, or damages resulting from loss of use or inability to use reseller’s products or the software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates has been advised, knew or should have known of the possibility of such damages.

The following disclaimer is required by Videomedia, Inc.:

“Videomedia, Inc. makes no warranties whatsoever, either express or implied, regarding this product, including warranties with respect to its merchantability or its fitness for any particular purpose.”

“This software contains V-LAN ver. 3.0 Command Protocols which communicate with V-LAN ver. 3.0 products developed by Videomedia, Inc. and V-LAN ver. 3.0 compatible products developed by third parties under license from Videomedia, Inc. Use of this software will allow “frame accurate” editing control of applicable videotape recorder decks, videodisc recorders/players and the like.”

The following disclaimer is required by Altura Software, Inc. for the use of its Mac2Win software and Sample Source Code:

The following disclaimer is required by 3Prong.com Inc.:

Certain waveform and vector monitoring capabilities are provided under a license from 3Prong.com Inc.

The following disclaimer is required by Interplay Entertainment Corp.:

The “Interplay” name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid products.

This product includes portions of the Alloy Look & Feel software from Incors GmbH.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product may include the JCifs library, for which the following notice applies:

Avid Interplay contains components licensed from LavanTech. These components may only be used as part of and in connection with Avid Interplay.

Attn. Government User(s). Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or “commercial computer software documentation.” In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.

Trademarks

003, 192 Digital I/O, 192 I/O, 96 I/O, 96i I/O, Adrenaline, AirSpeed, ALEX, Alienbrain, AME, AniMatte, Archive, Archive II, Assistant Station, AudioPages, AudioStation, AutoLoop, AutoSync, Avid, Avid Active, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid DNxHD, Avid DS Assist Station, Avid Liquid, Avid Media Engine, Avid Media Processor, Avid MEDIArray, Avid Mojo, Avid Remote Response, Avid Unity, Avid Unity ISIS, Avid VideoRAID, AvidRAID, AvidShare, AVIDstripe, AVX, Axiom, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Boom, Bruno, C|24, CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command|24, Command|8, Conectiv, Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, Dazzle, Dazzle Digital Video Creator, D-Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 003, DigiBase, DigiDelivery, Digidesign, Digidesign Audio Engine, Digidesign Development Partners, Digidesign Intelligent Noise Reduction, Digidesign TDM Bus, DigiLink, DigiMeter, DigiPanner, DigiProNet, DigiRack, DigiSerial, DigiSnake, DigiSystem, Digital Choreography, Digital Nonlinear Accelerator, DigiTest, DigiTranslator, DigiWear, DINR, DNxchange, DPP-1, D-Show, DSP Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, EveryPhase, Expander, ExpertRender, Fader Pack, Fairchild, FastBreak, Fast Track, Film Cutter, FilmScribe, Flexevent, FluidMotion, Frame Chase, FXDeko, HD Core, HD Process, HDPack, Home-to-Hollywood, HYBRID, HyperControl, HyperSPACE, HyperSPACE HDCAM, iKnowledge, Image Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, Instantwrite, Instinct, Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, inTONE, Intraframe, iS Expander, ISIS, IsoSync, iS9, iS18, iS23, iS36, ISIS, IsoSync, KeyRig, KeyStudio, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi, Luna, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, MassivePack, Massive Pack Pro, M-Audio, M-Audio Micro, Maxim, Mbox, Media Composer, MediaDock, MediaDock Shuttle, MediaFlow, MediaLog, MediaMatch, MediaMix, Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MicroTrack, MIDI I/O, Midiman, Mix Rack, MixLab, Moviebox, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, Nitris, NL3D, NLP, Nova, NRV-10 interFX, NSDOS, NSWIN, Octane, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Ozone, Ozonic, Painterly Effects, Palladium, Personal Q, PET, Pinnacle, Pinnacle DistanTV, Pinnacle GenieBox, Pinnacle HomeMusic, Pinnacle MediaSuite, Pinnacle Mobile Media, Pinnacle Scorefitter, Pinnacle Studio, Pinnacle Studio MovieBoard, Pinnacle Systems, Pinnacle VideoSpin, Podcast Factory, PowerSwap, PRE, ProControl, ProEncode, Profiler, Pro Tools|HD, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, Pro Tools, QuickPunch, QuietDrive, Realtime Motion Synthesis, Recti-Fi, Reel Tape Delay, Reel Tape Flanger, Reel Tape Saturation, Reprise, Res Rocket Surfer, Reso, RetroLoop, Reverb One, ReVibe, Revolution, rS9, rS18, RTAS, Salesview, Sci-Fi, Scorch, Scorefitter, ScriptSync, SecureProductionEnvironment, Serv|LT, Serv|GT, Session, Shape-to-Shape, ShuttleCase, Sibelius, SIDON, SimulPlay, SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, Solaris, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, Strike, Structure, Studiophile, SubCap, Sundance Digital, Sundance, SurroundScope, Symphony, SYNC HD, Synchronic, SynchroScope, SYNC I/O, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, Titansync, Titan, TL Aggro, TL AutoPan, TL Drum Rehab, TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities, tools for storytellers, Torq, Torq Xponent, Transfuser, Transit, TransJammer, Trigger Finger, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Velvet, Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, VTEM, Work-N-Play, Xdeck, X-Form, Xmon, XPAND!, Xponent, X-Session, and X-Session Pro are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

Adobe and Photoshop are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Apple and Macintosh are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. Windows is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. All other trademarks contained herein are the property of their respective owners.

Avid Interplay Engine Failover Guide • 0130-07643-02 Rev H • November 2010 • Created 11/10/10 • This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Viewing Help and Documentation on the Interplay Portal. . . . . . . . . . . . . . . . . . . . . 11

Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 1 Automatic Server Failover Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 13

Server Failover Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

How Server Failover Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Server Failover Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Server Failover Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installing the Failover Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

SR2400 Slot Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

SR2500 Slot Locations (for Infortrend A16F-R221) . . . . . . . . . . . . . . . . . . . . . . 22

SR2500 Slot Locations (for Infortrend A16F-R2431) . . . . . . . . . . . . . . . . . . . . . 23

Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration,

Infortrend A16F-221 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration,

Infortrend A16F-R2431 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Failover Cluster Connections: Avid Unity ISIS, Dual-Connected Configuration, 

Infortrend A16F-R221 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Failover Cluster Connections: Avid Unity ISIS, Dual-Connected Configuration, 

Infortrend A16F-R2431 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Failover Cluster Connections: Avid Unity MediaNetwork, 

Infortrend A16F-R221 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Failover Cluster Connections: Avid Unity MediaNetwork, 

Infortrend A16F-R2431 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Clustering Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 2 Creating a Microsoft Failover Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Server Failover Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Before You Begin the Server Failover Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 42

List of IP Addresses and Network Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Preparing the Server for the Cluster Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Setting the QLogic HBA Link Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Increasing the Boot Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Setting the ATTO Link Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Removing Unnecessary Windows Components . . . . . . . . . . . . . . . . . . . . . . . . 51

Renaming the Local Area Network Interface on Each Node. . . . . . . . . . . . . . . 52

Configuring the Private Network Adapter on Each Node . . . . . . . . . . . . . . . . . 55

Configuring the Binding Order Networks on Each Node . . . . . . . . . . . . . . . . . . 58

Configuring the Public Network Adapter on Each Node . . . . . . . . . . . . . . . . . . 60

Joining Both Servers to the Active Directory Domain . . . . . . . . . . . . . . . . . . . . 60

Configuring the Cluster Shared-Storage RAID Disks on Each Node . . . . . . . . 60

Configuring the Cluster Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Configuring the Cluster Service on the First Node . . . . . . . . . . . . . . . . . . . . . . 62

Validating the Cluster Service on the First Node. . . . . . . . . . . . . . . . . . . . . . . . 67

Configuring the Cluster Service on the Second Node. . . . . . . . . . . . . . . . . . . . 67

Configuring Rules for the Cluster Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Prioritizing the Heartbeat Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

After Setting Up the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Verifying the Quorum Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Setting the Startup Times on Each Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Testing the Cluster Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Installing the Distributed Transaction Coordinator . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Creating a Resource Group for the Distributed Transaction Coordinator . . . . . 77

Assigning an IP Address to the MSDTC Group. . . . . . . . . . . . . . . . . . . . . . . . . 78

Assigning a Network Name to the MSDTC Group . . . . . . . . . . . . . . . . . . . . . . 79

Creating a Physical Resource for the MSDTC Group . . . . . . . . . . . . . . . . . . . . 80

Assigning Distributed Transaction Coordinator Resource to the MSDTC Group 81

Bringing the MSDTC Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 3 Installing the Interplay Engine for a Failover Cluster . . . . . . . . . . . . . . . 83

Disabling Any Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Installing the Interplay Engine on the First Node . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Preparation for Installing on the First Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Starting the Installation and Accepting the License Agreement . . . . . . . . . . . . . 85

Installing the Interplay Engine Using Custom Mode. . . . . . . . . . . . . . . . . . . . . . 85

Specifying Cluster Mode During a Custom Installation . . . . . . . . . . . . . . . . 86

Specifying the Interplay Engine Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Specifying the Interplay Engine Service Name . . . . . . . . . . . . . . . . . . . . . . 89

Specifying the Destination Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Specifying the Default Database Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Specifying the Share Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Specifying the Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Specifying the Server User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Specifying the Server Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Enabling Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Installing the Interplay Engine for a Custom Installation on the First Node . 98

Bringing the Disk Resource Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Installing the Interplay Engine on the Second Node . . . . . . . . . . . . . . . . . . . . . . . . 102

Bringing the Interplay Engine Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Installing a Permanent License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Testing the Complete Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Updating a Clustered Installation (Rolling Upgrade) . . . . . . . . . . . . . . . . . . . . . . . . 106

Uninstalling the Interplay Engine on a Clustered System . . . . . . . . . . . . . . . . . . . . 107

Chapter 4 Automatic Server Failover Tips and Rules . . . . . . . . . . . . . . . . . . . . . . 109

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Using This Guide

Congratulations on the purchase of your Avid® Interplay™, a powerful system for managing media in a shared storage environment.

This guide is intended for all Avid Interplay administrators who are responsible for installing, configuring, and maintaining an Avid Interplay Engine with the Automatic Server Failover module integrated.

The documentation describes the features and hardware of all models. Therefore, your

system might not contain certain features and hardware that are covered in the documentation.

Symbols and Conventions

Avid documentation uses the following symbols and conventions:

Symbol or Convention Meaning or Action

> This symbol indicates menu commands (and subcommands) in the

(Windows), (Windows only), (Macintosh), or (Macintosh only)

A note provides important related information, reminders, recommendations, and strong suggestions.

A caution means that a specific action you take could cause harm to your computer or cause you to lose data.

A warning describes an action that could cause you physical harm. Follow the guidelines in this document or on the unit itself when handling electrical equipment.

order you select them. For example, File > Import means to open the File menu and then select the Import command.

This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.

This text indicates that the information applies only to the specified operating system, either Windows or Macintosh OS X.

Symbol or Convention Meaning or Action

Bold font Bold font is primarily used in task instructions to identify user interface

items and keyboard sequences.

Italic font Italic font is used to emphasize certain words and to indicate variables.

Courier Bold font

Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the

If You Need Help

If you are having trouble using your Avid product:

1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow.

2. Check the latest information that might have become available after the documentation was published:

- If the latest information for your Avid product is provided as printed release notes,

they ship with your application and are also available online.

If the latest information for your Avid product is provided as a ReadMe file, it is supplied on your Avid installation CD or DVD as a PDF document (README_product.pdf) and is also available online.

You should always check online for the most up-to-date release notes or ReadMe because the online version is updated whenever new information becomes available. To view these online versions, select ReadMe from the Help menu, or visit

the Knowledge Base at

Courier Bold font identifies text that you type.

mouse action. For example, Command+Option+C or Ctrl+drag.

www.avid.com/readme.

3. Check the documentation that came with your Avid application or your hardware for maintenance or hardware-related issues.

4. Visit the online Knowledge Base at www.avid.com/onlinesupport. Online services are available 24 hours per day, 7 days per week. Search this online Knowledge Base to find answers, to view error messages, to access troubleshooting tips, to download updates, and to read or join online message-board discussions.

Viewing Help and Documentation on the Interplay Portal

You can quickly access the Interplay Help, PDF versions of the Interplay guides, and useful external links by viewing the Interplay User Information Center on the Interplay Portal. The Interplay Portal is a web site that runs on the Interplay Engine.

You can access the Interplay User Information Center through a browser from any system in the Interplay environment. You can also access it through the Help menu in Interplay Access and the Interplay Administrator.

The Interplay Help combines information from all Interplay guides in one Help system. It includes a combined index and a full-featured search. From the Interplay Portal, you can run the Help in a browser or download a compiled (.chm) version for use on other systems, such as a laptop.

To open the Interplay User Information Center through a browser:

1. Type the following line in a web browser:

http://Interplay_Engine_name

For Interplay_Engine_name substitute the name of the computer running the Interplay Engine software. For example, the following line opens the portal web page on a system named docwg:

http://docwg

2. Click the “Avid Interplay Documentation” link to access the User Information Center web page.

To open the Interplay User Information Center from Interplay Access or the Interplay Administrator:

t Select Help > Documentation Website on Server.

Avid Training Services

Avid makes lifelong learning, career advancement, and personal development easy and convenient. Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment.

For information on courses/schedules, training centers, certifications, courseware, and books, please visit www.avid.com/support and follow the Training links, or call Avid Sales at 800-949-AVID (800-949-2843).

1 Automatic Server Failover Introduction

This chapter covers the following topics:

• Server Failover Overview

• How Server Failover Works

• Installing the Failover Hardware Components

• Clustering Terminology

Server Failover Overview

The automatic server failover mechanism in Avid Interplay allows client access to the Interplay Engine in the event of failures or during maintenance, with minimal impact on the availability. A failover server is activated in the event of application, operating system, or hardware failures. The server can be configured to notify the administrator about such failures using email.

The Interplay implementation of server failover uses Microsoft background information on clustering technology and links to Microsoft clustering information, see “Clustering Terminology” on page 39.

clustering technology. For

Additional monitoring of the hardware and software components of a high-availability solution is always required. Avid delivers Interplay preconfigured, but additional attention on the customer side is required to prevent outage (for example, when a private network fails, RAID disk fails, or a power supply loses power). In a mission critical environment, monitoring tools and tasks are needed to be sure there are no silent outages. If another (unmonitored) component fails, only an event is generated, and while this does not interrupt availability, it might go unnoticed and lead to problems. Additional software reporting such issues to the IT administration lowers downtime risk.

The failover cluster is a system made up of two server nodes and a shared-storage device connected over Fibre Channel. These are to be deployed in the same location given the shared access to the storage device. The cluster uses the concept of virtual servers to specify groups of resources that failover together.

1 Automatic Server Failover Introduction

FibreChannel

Intranet

Private Network

Disk #1 Quorum 4GB

Interplay Server (virtual)

11.22.33.201

MSDTC

11.22.33.202

Failover Cluster

11.22.33.200

Node #1 Intranet: 11.22.33.44 Private: 10.10.10.10

Node #2 Intranet: 11.22.33.45 Private: 10.10.10.11

Disk #2 MSDTC 5GB

Disk #3 Database 925GB +

Cluster Group

Resource groups

Clustered services

Disk resources (shared disks)

The following diagram illustrates the components of a cluster group, including sample IP addresses. For a list of required IP addresses and node names, see “List of IP Addresses and

Network Names” on page 43.

How Server Failover Works

If you are already using clusters, the Avid Interplay Engine will not interfere with your

current

setup.

Server failover works on two different levels:

• Failover in case of hardware failure

• Failover in case of network failure

Hardware Failover Process

When the Microsoft cluster service is running on both systems and the server is deployed in cluster mode, the Interplay Engine and its accompanying services are exposed to users as a virtual server. To clients, connecting to the clustered virtual Interplay Engine appears to be the same process as connecting to a single, physical machine. The user or client application does not know which node is actually hosting the virtual server.

Server Failover Configurations

When the server is online, the resource monitor regularly checks its availability and automatically restarts the server or initiates a failover to the other node if a failure is detected. The exact behavior can be configured using the Windows Cluster Administrator console. Because clients connect to the virtual network name and IP address, which are also taken over by the failover node, the impact on the availability of the server is minimal.

Network Failover Process

The cluster resource monitors one primary network that connects the virtual server to the intranet. If the primary network fails, the virtual server (and thus both cluster nodes) will go offline. Avid supports a configuration that uses connections to two public networks (VLAN 10 and VLAN 20) on a single switch. However, in this configuration Windows clustering technology binds multiple virtual IP addresses to VLAN 10 as the primary network, and if VLAN 10 fails the virtual server will go offline.

For a high degree of protection against network outages, Avid supports a configuration that uses two network switches, each connected to a shared primary network (VLAN 30) and protected by a failover protocol. If one network switch fails, the virtual server remains online through the other VLAN 30 network and switch.

These configurations are described in the next section.

Server Failover Configurations

There are three supported configurations for integrating a failover cluster into an existing network:

• A cluster in an Avid Unity ISIS environment that is integrated into the intranet through two layer-3 switches (VLAN 30 in Zone 3). This “redundant-switch” configuration protects against both hardware and network outages and thus provides a higher level of protection than the dual-connected configuration.

• A cluster in an Avid Unity ISIS environment that is integrated into the intranet through two public networks (VLAN 10 and VLAN 20 in Zone 1). This “dual connected” configuration protects against hardware outages and network outage on VLAN 20 but, because only VLAN 10 is monitored, does not protect against a outage on the other network.

• A cluster in an Avid Unity MediaNetwork environment that is integrated into the intranet through a single public network. This configuration protects against hardware outages.It relies on a single public network, and so does not protect against a network outage.

1 Automatic Server Failover Introduction

Two-node cluster in an Avid Unity ISIS environment (redundant switch)

Infortrend cluster shared-storage RAID array

Interplay clients

Intranet

LEGEND

Fibre connection

1 GB Ethernet connection

Interplay Engine - Cluster Node

Private network for heartbeat

Avid Network Switch 1 running VRRP/HSRP

Avid Network Switch 2 running VRRP/HSRP

VLAN 30

Redundant-Switch Configuration

The following diagram illustrates the failover cluster architecture for an Avid Unity ISIS environment that uses two layer-3 switches. These switches are configured for failover protection through either HSRP (Hot Standby Router Protocol) or VRRP (Virtual Router Redundancy Protocol). The cluster nodes are connected to two subnets (VLAN 30), each on a different switch. If one of the VLAN 30 networks fails, the virtual server remains online through the other VLAN 30 network and switch.

This guide does not describe how to configure redundant switches for an Avid Unity ISIS

media network. Configuration information is included in the Avid Unity ISIS Switch Reference Guide, which is available for download from the Avid Customer Support

Knowledge Base at

www.avid.com\onlinesupport.

The following table describes what happens in the redundant-switch configuration as a result

Two-node cluster in an Avid Unity ISIS environment (dual-connected)

Interplay Engine - Cluster Node

Infortrend cluster shared-storage RAID array

Interplay Engine - Cluster Node

Interplay clients

Intranet

Avid Network Switch

Private network for heartbeat

LEGEND

Fibre connection

1 GB Ethernet connection

VLAN 20

VLAN 10

of an outage:

Type of Outage Result

Server Failover Configurations

Hardware (CPU, network adapter, memory, cable, power supply) fails

The cluster detects the outage and triggers failover to the remaining node.

The Interplay Engine is still accessible.

Network switch 1 (VLAN 30) fails External switches running VRRP/HSRP detect the outage and make the

gateway available as needed.

The Interplay Engine is still accessible.

Network switch 2 (VLAN 30) fails External switches running VRRP/HSRP detect the outage and make the

gateway available as needed.

The Interplay Engine is still accessible.

Dual-Connected Configuration

The following diagram illustrates the failover cluster architecture for an Avid Unity ISIS environment. In this environment, each cluster node is “dual-connected” to the network switch: one network interface is connected to the VLAN 10 subnet and the other is connected to the VLAN 20 subnet. In this configuration Windows clustering technology binds multiple virtual IP addresses to VLAN 10 as the primary network, and if VLAN 10 fails the virtual server goes offline.

1 Automatic Server Failover Introduction

Two-node cluster in an Avid Unity MediaNetwork environment

Interplay Engine - Cluster Node

Infortrend cluster shared-storage RAID array

Interplay Engine - Cluster Node

Interplay clients

Intranet

Network Switch

Private network for heartbeat

Fibre Switch

LEGEND

Fibre connection

1 GB Ethernet connection

The following table describes what happens in the dual-connected configuration as a result of an outage:

Type of Outage Result

Hardware (CPU, network adapter, memory, cable, power supply) fails

Left ISIS VLAN (VLAN10, primary network) fails

The cluster detects the outage and triggers failover to the remaining node.

The Interplay Engine is still accessible.

The cluster detects the outage and triggers failover but detects that the second node is also disconnected from the left network, and both clusters fail.

The Interplay Engine is not accessible.

Right ISIS VLAN (VLAN 20) fails The Interplay Engine is still accessible through the left network.

Avid Unity MediaNetwork Configuration

The following diagram illustrates the failover cluster architecture for an Avid Unity MediaNetwork environment. In this environment, each cluster node is connected to a network switch through a single public network.

The following table describes what happens in the MediaNetwork configuration as a result of an outage:

Type of Outage Result

Server Failover Requirements

Hardware (CPU, network adapter, memory, cable, power supply) fails

Network switch fails The cluster detects the outage and triggers failover but detects that the

The cluster detects the outage and triggers failover to the remaining node.

The Interplay Engine is still accessible.

second node is also disconnected from the network, and both clusters fail.

The Interplay Engine is not accessible.

Server Failover Requirements

You should make sure the server failover system meets the following requirements.

Hardware

A dual-server failover cluster-capable system with an Infortrend® cluster shared-storage RAID disk set is needed. The automatic server failover system was developed on and tested with the following:

• Intel Server Chassis SR2500 Packaged Cluster, which is the recommended hardware:

http://www.intel.com/design/servers/chassis/sr2500/

• Intel Server Chassis SR2400 Packaged Cluster:

http://www.intel.com/design/servers/chassis/sr2400/

The servers in a cluster are connected using one or more cluster shared-storage buses and one or more physically independent networks acting as a heartbeat.

Server Software

Two licenses of Windows Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Edition are needed.

Space Requirements

The default disk configuration for the cluster shared RAID array is as follows:

• Quorum disk - 4GB

•MSDTC disk - 5GB

• Database disk - 925GB or larger

1 Automatic Server Failover Introduction

Antivirus Software

You can run antivirus software on a cluster, if the antivirus software is cluster-aware. For information about cluster-aware versions of your antivirus software, contact the antivirus vendor. If you are running antivirus software on a cluster, make sure you exclude these locations from the virus scanning: Q:\ (Quorum disk), C:\Windows\Cluster, and S:\Workgroup_Databases (database).

Functions You Need To Know

Before you set up a cluster in an Avid Interplay environment, you should be familiar with the following functions:

• Microsoft Windows Active Directory domains and domain users

• Microsoft Windows clustering (current version, as there are changes from prior version)

• Disk configuration (format, partition, naming)

• Network configuration

Installing the Failover Hardware Components

A failover cluster system includes the following components:

• Two Interplay Engine nodes or two Interplay Archive nodes (two SR2400 servers or two SR2500 servers)

• One Infortrend cluster shared-storage RAID array (one Infortrend A16F-R221 or one Infortrend A16F-R2431)

The following topics provide information about installing the failover hardware components for the supported configurations:

• “SR2400 Slot Locations” on page 21

• “SR2500 Slot Locations (for Infortrend A16F-R221)” on page 22

• “SR2500 Slot Locations (for Infortrend A16F-R2431)” on page 23

• “Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration,

Infortrend A16F-221” on page 24

• “Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration,

Infortrend A16F-R2431” on page 27

• “Failover Cluster Connections: Avid Unity ISIS, Dual-Connected Configuration,

Infortrend A16F-R221” on page 29

• “Failover Cluster Connections: Avid Unity ISIS, Dual-Connected Configuration,

Infortrend A16F-R2431” on page 32

• “Failover Cluster Connections: Avid Unity MediaNetwork, Infortrend A16F-R221” on

PCI slots

Serial A to F/C switch if needed

SCSI B

Video

USB

SR2400 Back Panel

Mouse

Keyboard

RJ 45 to serial B

Power supply

Slot 2

Slot 1

Slot 3

Small form factor slots not used

1 GB Ethernet

page 34

• “Failover Cluster Connections: Avid Unity MediaNetwork, Infortrend A16F-R2431” on

page 37

SR2400 Slot Locations

The SR2400 is supported as a server for the Interplay applications. This section describes the slot locations that are specific to the Interplay components in a cluster configuration.

Use the following figure and table as guides to configuring an SR2400 system.

Installing the Failover Hardware Components

On the SR2400, all boards must be installed starting in the top slot, and the second board must be in the middle slot. The second board cannot be in the bottom slot with the middle slot left open.

SR2400 Back Panel Configuration for Avid Unity Environment

Slot Avid Unity ISIS Avid Unity MediaNetwork

3 Intel Pro 1000MT ATTO

2 QLogic

1 Empty Intel Pro 1000MT

a. Unity MediaNetwork environment: the Pro 1000MT card is shipped in slot 3 (top). You must move the

card to slot 1 (bottom) and install the ATTO card in slot 3 (top). The Pro 1000MT is not used in an Unity MediaNetwork environment.

Card QLogic Card

1 Automatic Server Failover Introduction

PCI-X slots

Power supplies

Serial A to F/C switch if needed

Video

USB

SR2500 Back Panel

RJ 45 to serial B

Primary power supply on bottom

Slot 2

Slot 1

Slot 3

PCIe slots (small form factor)

1 GB Ethernet

Slot 2

Slot 1

SR2500 Slot Locations (for Infortrend A16F-R221)

The SR2500 is supported as a server for the Interplay applications. This section describes the slot locations that are specific to the Interplay components in a cluster configuration that uses the Infortrend model A16F-R221shared-storage RAID array.

Use the following figure and table as guides to configuring an SR2500 system.

It is important to match the slot locations in the following tables because they match the

order that the drivers are loaded on the SR2500 Recovery DVDs.

SR2500 Back Panel Configuration for Avid Unity Environment

Slot Type Slot Avid Unity ISIS Avid Unity MediaNetwork

PCI-X 3 Empty ATTO

PCIe NA NA NA

a. The SR2500 server might ship with the QLogic card in PCI-X slot 2 (middle). You must move the QLogic card to

PCI-X slot 1 (bottom), because this configuration matches the order that the drivers are loaded on the SR2500 Recovery DVDs.

2 Empty Empty

1QLogic Card

to Infortrend A16F-R221

QLogic Carda to Infortrend A16F-R221

2 Intel Pro 1000PT Intel Pro 1000PT

1 Empty Empty

Installing the Failover Hardware Components

PCI-X slots

Power supplies

Serial A to F/C switch if needed

Video

USB

SR2500 Back Panel

Mouse

Keyboard

RJ 45 to serial B

Primary power supply on bottom

Slot 2

Slot 1

Slot 3

PCIe slots (small form factor)

1 GB Ethernet

Slot 2

Slot 1

SR2500 Slot Locations (for Infortrend A16F-R2431)

Use the following figure and table as guides to configuring an SR2500 system.

SR2500 Back Panel Configuration for Avid Unity Environment

Slot Type Slot Avid Unity ISIS Avid Unity MediaNetwork

PCI-X 3 Empty Empty

PCIe NA NA NA

It is important to match the slot locations in the following tables because they match the

order that the drivers are loaded on the SR2500 Recovery DVDs.

2 Empty Empty

1 ATTO FC-41XS to

Infortrend A16F-R2431

ATTO FC-41XS to Infortrend A16F-R2431

2 Intel Pro 1000PT Intel Pro 1000PT

1 Empty ATTO FC-41EL to MediaNetwork

1 Automatic Server Failover Introduction

Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration, Infortrend A16F-221

Make the following cable connections to add a failover cluster to an Avid Unity ISIS environment, using the redundant-switch configuration with an Infortrend A16F-R221 RAID array:

• First cluster node:

- Left on-board network interface connector to layer-3 switch 1 (VLAN 30)

- QLogic card connector to RAID array, Fibre Channel 1 left connector

• Second cluster node:

- Left on-board network interface connector to layer-3 switch 2 (VLAN 30)

- QLogic card connector to RAID array, Fibre Channel 0 left connector

• Right connector on PCI adapter network interface in the first cluster node to right connector on PCI adapter network interface in second cluster node (private network for heartbeat)

• All switches on the cluster shared-storage RAID array are in the default “enable” position (left).

You can implement this configuration using either SR2400 servers or SR2500 servers. The following illustrations show the connections for each type of server.

Private network for heartbeat

PCI adapter network interface right connector

QLogic card

Right on-board network interface

Left on-board network interface

PCI adapter network interface right connector

LEGEND

Fibre connection

1GB Ethernet connection

QLogic card

Interplay Engine Cluster Node 1

Interplay Engine Cluster Node 2

Right on-board network interface

Left on-board network interface

Cluster Shared-Storage RAID Array

Fibre Channel 1

left connector Fibre Channel 0 left connector

FC CH0

FC CH1

All switches set to default “enabled” left

SR2400 Back Panel

To Avid Network Switch 1

To Avid Network Switch 2

Installing the Failover Hardware Components

Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration, SR2400, Infortrend A16F-R221

1 Automatic Server Failover Introduction

Private network for heartbeat

PCI adapter network interface right connector

To Avid Network Switch 1

QLogic card

Right on-board network interface

Left on-board network interface

PCI adapter network interface right connector

LEGEND

Fibre connection

1GB Ethernet connection

QLogic card

Interplay Engine Cluster Node 1

Interplay Engine Cluster Node 2

Right on-board network interface

Left on-board network interface

Cluster Shared-Storage RAID Array

Fibre Channel 1

left connector Fibre Channel 0 left connector

FC CH0

FC CH1

All switches set to default “enabled” left

SR2500 Back Panel

Slot 3 Slot 2 Slot 1

To Avid Network Switch 2

Failover Cluster Connections: Avid Unity ISIS Environment, Redundant-Switch Configuration, SR2500, Infortrend A16F-R221

Installing the Failover Hardware Components

Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration, Infortrend A16F-R2431

Make the following cable connections to add a failover cluster to an Avid Unity ISIS environment, using the redundant-switch configuration with an Infortrend A16F-R2431 RAID array:

• First cluster node:

- Left on-board network interface connector to layer-3 switch 1 (VLAN 30)

- ATTO 41XS card connector to RAID array, Fibre Channel 0 top-left connector

• Second cluster node:

- Left on-board network interface connector to layer-3 switch 2 (VLAN 30)

- ATTO 41XS card connector to RAID array, Fibre Channel 1 bottom-right connector

• Right connector on PCI adapter network interface in the first cluster node to right connector on PCI adapter network interface in second cluster node (private network for heartbeat)

• All switches on the cluster shared-storage RAID array are in the default “enable” position (left)

You can implement this configuration using SR2500 servers. The following illustration shows the connections for these servers.

1 Automatic Server Failover Introduction

Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration, SR2500, Infortrend A16F-R2431

PCI adapter network interface right connector

Interplay Engine Cluster Node 1

To Av i d Network Switch 1

All switches set to default “enabled” left

Interplay Engine Cluster Node 2

Fibre Channel 0 top left connector

FC CH0

Be sure both PSUs have same mark

Fibre Channel 1 bottom right connector

Slot 3 Slot 2 Slot 1

Right on-board network interface

Left on-board network interface

Cluster Shared-Storage RAID Array

BBU Status

Ctrl Status

C Dirty

Temp

CH0 CH1

123

COM1CO M2

456

BBU Status

Ctrl Status

C Dirty

Temp

123

COM1CO M2

ATTO 41XS card

ES A16F-R2431-1

BBU Link

Hist Bay Drv Bay

Service Only

ES A16F-R2431-1

BBU Link

Hist Bay Drv Bay

Service Only

Be sure both PSUs have same mark

PCI adapter network interface right connector

SR2500 Back Panel

Private network for heartbeat

SR2500 Back Panel

To Av i d Network Switch 2

Right on-board network interface

Left on-board network interface

ATTO 41XS card

LEGEND

1GB Ethernet connection Fibre connection

Installing the Failover Hardware Components

Failover Cluster Connections: Avid Unity ISIS, Dual-Connected Configuration, Infortrend A16F-R221

Make the following cable connections to add a failover cluster to an Avid Unity ISIS environment, using the dual-connected configuration with an Infortrend A16F-R221RAID array:

• First cluster node:

- Left on-board network interface connector to ISIS left subnet (VLAN 10)

- Right on-board network interface connector to ISIS right subnet (VLAN 20)

- QLogic card connector to RAID array, Fibre Channel 1 left connector

• Second cluster node:

- Left on-board network interface connector to ISIS left subnet (VLAN 10)

- Right on-board network interface connector to ISIS right subnet (VLAN 20)

- QLogic card connector to RAID array, Fibre Channel 0 left connector

• Right connector on PCI adapter network interface in the first cluster node to right connector on PCI adapter network interface in second cluster node (private network for heartbeat)

• All switches on the cluster shared-storage RAID array are in the default “enable” position (left)

You can implement this configuration using either SR2400 servers or SR2500 servers. The following illustrations show the connections for each type of server.

1 Automatic Server Failover Introduction

Private network for heartbeat

PCI adapter network interface right connector

To ISIS right subnet

To ISIS left subnet

To ISIS right subnet

To ISIS left subnet

QLogic card

Right on-board network interface

Left on-board network interface

PCI adapter network interface right connector

LEGEND

Fibre connection

1GB Ethernet connection

QLogic card

Interplay Engine Cluster Node 1

Interplay Engine Cluster Node 2

Right on-board network interface

Left on-board network interface

Cluster Shared-Storage RAID Array

Fibre Channel 1

left connector Fibre Channel 0 left connector

FC CH0

FC CH1

All switches set to default “enabled” left

SR2400 Back Panel

Failover Cluster Connections: Avid Unity ISIS, Dual-Connected Configuration, SR2400, Infortrend A16F-R221

+ 88 hidden pages

Pinnacle Systems Interplay Engine - 2.2 User Manual

Contents

Using This Guide

Symbols and Conventions

If You Need Help

Viewing Help and Documentation on the Interplay Portal

Avid Training Services

1 Automatic Server Failover Introduction

Server Failover Overview

How Server Failover Works

Server Failover Configurations

Server Failover Requirements

Installing the Failover Hardware Components

SR2400 Slot Locations

SR2500 Slot Locations (for Infortrend A16F-R221)

SR2500 Slot Locations (for Infortrend A16F-R2431)

Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration, Infortrend A16F-221

Failover Cluster Connections: Avid Unity ISIS, Redundant-Switch Configuration, Infortrend A16F-R2431

Failover Cluster Connections: Avid Unity ISIS, Dual-Connected Configuration, Infortrend A16F-R221