Pinnacle Systems Interplay Engine - 1.2.4 User Manual

Avid® Interplay™Engine

Failover Guide

make manage move | media

™

Avid

Legal Notices

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

The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting Avid's Web site at www.avid.com. The terms of that license are also available in the product in the same directory as the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement.

Avid products or portions thereof are protected by one or more of the following United States Patents: 4,970,663; 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,627,765; 5,640,601; 5,644,364; 5,654,737; 5,715,018; 5,719,570; 5,724,605; 5,726,717; 5,729,673; 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,999,406; 6,038,573; 6,061,758; 6,141,007; 6,211,869; 6,532,043; 6,546,190; 6,596,031; 6,636,869; 6,747,705; 6,763,523; 6,766,357; 6,813,622; 6,847,373; 7,081,900; RE40,107; D352,278; D372,478; D373,778; D392,267; D392,268; D392,269; D395,291; D396,853; D398,912. Other patents are pending.

This document is protected under copyright law. An authorized licensee of Avid Interplay 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 Interplay Framework. 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

888 I/O, Adrenaline, AirPlay, AirSPACE, AirSPACE HD, AirSpeed, ALEX, Alexis, AniMatte, AudioSuite, AudioVision, AutoSync, Avid, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid DNxHD, AVIDdrive, AVIDdrive Towers, Avid DS Assist Station, Avid ISIS, Avid Learning Excellerator, Avid Liquid, Avid Mojo, AvidNet, AvidNetwork, Avid Remote Response, AVIDstripe, Avid Unity, Avid Unity ISIS, Avid Xpress, AVoption, AVX, CamCutter, CaptureManager, ChromaCurve, ChromaWheel, Conectiv, CountDown, DAE, Dazzle, Deko, DekoCast, D-Fi, D-fx, DigiDelivery, Digidesign, Digidesign Audio Engine, Digidesign Intelligent Noise Reduction, DigiDrive, Digital Nonlinear Accelerator, DigiTranslator, DINR, DNxchange, do more, D-Verb, Equinox, ExpertRender, Face Robot, FACE ROBOT, FastBreak, Fast Track, FieldPak, Film Composer, FilmScribe, FluidMotion, FXDeko, HIIP, HyperSPACE, HyperSPACE HDCAM, IllusionFX, Image Independence, iNEWS, iNEWS ControlAir, Instinct, Interplay, Intraframe, iS9, iS18, iS23, iS36, ISIS, IsoSync, LaunchPad, Lightning, Lo-Fi, Magic Mask, make manage move | media, Marquee, Matador, Maxim, MCXpress, Media Browse, Media Composer, MediaDock, MediaDock Shuttle, Media Fusion, Media Illusion, MediaLog, Media Reader, Media Recorder, MEDIArray, MediaShare, MediaStream, Meridien, MetaFuze, MetaSync, MicroTrack, MissionControl, MovieBox, NaturalMatch, Nearchive, NetReview, NewsCutter, Nitris, OMF, OMF Interchange, OMM, Open Media Framework, Open Media Management, PCTV, Pinnacle MediaSuite, Pinnacle Studio, Pinnacle Systems, ProEncode, Pro Tools, QuietDrive, Recti-Fi, RetroLoop, rS9, rS18, SalesView, Sci-Fi, ScriptSync, SecureProductionEnvironment, Show Center, Softimage, Sound Designer II, SPACE, SPACEShift, SpectraGraph, SpectraMatte, Sputnik, SteadyGlide, SubCap, Symphony, SynchroScience, TARGA, Thunder, Thunder Station, TimeLiner, Torq, Trilligent, UnityRAID, Vari-Fi, Velvet, Video RAID, Video Slave Driver, VideoSPACE, Xdeck, and X-Session 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.

GOT FOOTAGE?

Editors — Filmmakers — Special Effects Artists — Game Developers — Animators — Educators — Broadcasters — Content creators of every genre — Just finished an incredible project and want to share it with the world?

Send us your reels and we may use your footage in our show reel or demo!*

For a copy of our release and Avid’s mailing address, go to www.avid.com/footage.

*Note: Avid cannot guarantee the use of materials submitted.

Avid Interplay Engine Failover Guide • 0130-07643-02 Rev C • June 2008 • 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 User Documentation on the Interplay Portal . . . . . . . . . . . . . . . . . . . . . . . . 11

Accessing the Online Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

How to Order Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

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

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

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

How Server Failover Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Server Failover Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installing the Failover Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SR2400 Slot Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SR2500 Slot Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Making Failover Cluster Connections in an Avid Unity ISIS Environment . . . . . 19

Failover Cluster Connections in an Avid Unity ISIS Environment (SR2400) . . . 20

Failover Cluster Connections in an Avid Unity ISIS Environment (SR2500) . . . 21

Making Failover Cluster Connections in an Avid Unity MediaNetwork

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Failover Cluster Connections in an Avid Unity MediaNetwork

Environment (SR2400) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Failover Cluster Connections in an Avid Unity MediaNetwork Environment

(SR2500). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Clustering Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 2 Automatic Server Failover Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Server Failover Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

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

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

Preparing the Server for the Cluster Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Setting the QLogic HBA Link Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

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

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

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

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

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

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

Configuring the Cluster Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

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

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

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

Configuring Rules for the Cluster Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Prioritizing the Heartbeat Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

After Setting Up the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Verifying the Quorum Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

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

Testing the Cluster Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Installing the Distributed Transaction Coordinator . . . . . . . . . . . . . . . . . . . . . . . . . . 56

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

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

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

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

Assigning Distributed Transaction Coordinator Resource to the MSDTC Group 60

Bringing the MSDTC Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Installing the Interplay Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Disabling Any Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

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

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

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

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

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

Specifying the Interplay Engine Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Specifying the Interplay Engine Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Specifying the Destination Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Specifying the Default Database Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Specifying the Share Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Specifying the Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Specifying the Server User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Specifying the Server Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Enabling Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

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

Bringing the Disk Resource Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

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

Bringing the Interplay Engine Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Testing the Complete Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

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

Updating the Workgroup.xml File for a Split Database . . . . . . . . . . . . . . . . . . . 85

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

Chapter 3 Automatic Server Failover Tips and Rules . . . . . . . . . . . . . . . . . . . . . . . 89

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

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 User Documentation on the Interplay Portal

You can quickly access the Interplay user documentation from any system in the Interplay environment. Type the following line in your Web browser:

http://

where Interplay_Engine_name is 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

• Click the “Avid Interplay User Documentation” link to access the User Information

Interplay_Engine_name

Center page. On this page, select the Avid Interplay Framework User’s Guide from the list of user’s

guides.

Accessing the Online Library

The Avid Interplay Online Library DVD contains all the Avid Interplay product documentation in PDF format.The Online Library includes a Master Glossary of all specialized terminology used in the documentation for Avid products.

Most Avid online libraries also include multimedia content such as feature presentations. This multimedia content is an excellent first resource for learning how to use your application or for helping you understand a particular feature or workflow.

You need Adobe® Reader® to view the documentation online. You can download the latest

version from the Adobe web site.

To access the online library from the Online Library DVD:

1. Insert the Online Library DVD into the drive.

2. Double-click the Mainmenu file.

How to Order Documentation

To order additional copies of this documentation from within the United States, call Avid Sales at 800-949-AVID (800-949-2843). If you are placing an order from outside the United States, contact your local Avid representative.

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.

To learn about Avid's new online learning environment, Avid Learning Excellerator™ (ALEX), visit

For information on courses/schedules, training centers, certifications, courseware, and books, please visit (800-949-2843).

http://learn.avid.com.

www.avid.com/training or call Avid Sales at 800-949-AVID

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.

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.

The following diagram illustrates the failover cluster architecture for an Avid Unity MediaNetwork environment. (This diagram and the next diagram do not show the complete Interplay environment. For more detailed illustrations, see Avid Interplay Best Practices.)

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

Two-node cluster in an Avid Unity ISIS environment

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

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.

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

current

setup.

How Server Failover Works

FibreChannel

Intranet

Private Network

Intranet

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

When the Microsoft® Windows® cluster service is running on the machines 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, however, 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.

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. Given that clients connect to the virtual network name and IP address, which are also taken over by the failover node, this minimizes the impact on the availability of the server.

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

Network Names” on page 30.

How Server Failover Works

“List of IP Addresses and

1 Automatic Server Failover Introduction

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

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).

Installing the Failover Hardware Components

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 SR 2400 or two SR 2500 servers)

• One Infortrend cluster shared-storage RAID array

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

• “SR2400 Slot Locations” on page 17

• “SR2500 Slot Locations” on page 18

• “Making Failover Cluster Connections in an Avid Unity ISIS Environment” on page 19

• “Failover Cluster Connections in an Avid Unity ISIS Environment (SR2400)” on page

• “Failover Cluster Connections in an Avid Unity ISIS Environment (SR2500)” on page

• “Making Failover Cluster Connections in an Avid Unity MediaNetwork Environment”

on page 22

• “Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2400)”

on page 23

• “Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2500)”

on page 24

1 Automatic Server Failover Introduction

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

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 your SR2400 systems in an Interplay cluster environment.

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

Card QLogic Card

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.

SR2500 Slot Locations

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

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.

Use the following figure and table as guides to configuring your SR2500 systems in an Interplay cluster environment.

Installing the Failover Hardware Components

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

Its 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 QLogic Card

QLogic Card

2 Intel Pro 1000PT Intel Pro 1000PT

1 Empty Empty

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.

1 Automatic Server Failover Introduction

Making Failover Cluster Connections in an Avid Unity ISIS Environment

Make the following cable connections to add a failover cluster to an Avid Unity ISIS environment:

• 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)

For more details, see the illustrations in:

• “Failover Cluster Connections in an Avid Unity ISIS Environment (SR2400)” on page

20.

• “Failover Cluster Connections in an Avid Unity ISIS Environment (SR2500)” on page

21.

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

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

Installing the Failover Hardware Components

Failover Cluster Connections in an Avid Unity ISIS Environment (SR2400)

The following illustration shows the required cable connections when adding a failover cluster in an Avid Unity ISIS environment (SR2400 servers). For a description of the connections, see

on page 19.

“Making Failover Cluster Connections in an Avid Unity ISIS Environment”

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

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

Failover Cluster Connections in an Avid Unity ISIS Environment (SR2500)

The following illustration shows the required cable connections when adding a failover cluster in an Avid Unity ISIS environment (SR2500 servers). For a description of the connections, see

on page 19.

“Making Failover Cluster Connections in an Avid Unity ISIS Environment”

Installing the Failover Hardware Components

Making Failover Cluster Connections in an Avid Unity MediaNetwork Environment

The Interplay Engine Cluster nodes (SR2400 servers) ship with an Intel Pro 1000 MT card in slot 3 (top). You need to move this card to slot 1 (bottom). Then add an ATTO host bus adapter in slot 3 (top).

Make the following cable connections to add a failover cluster to an Unity MediaNetwork environment:

• First cluster node:

- Left on-board network interface connector to Ethernet

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

- ATTO card connector to Unity MediaNetwork FC switch

• Second cluster node:

- Left on-board network interface connector to Ethernet

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

- ATTO card connector to Unity MediaNetwork FC switch

public network

• Right on-board network interface connector on the first cluster node to right on-board network interface connector on the second cluster node (private network for heartbeat)

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

For more details, see the illustration in:

• “Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2400)”

on page 23.

• “Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2500)”

on page 24.

1 Automatic Server Failover Introduction

Private network for heartbeat

ATTO card

To Ethernet Public Network

Right on-board network interface

Left on-board network interface

To MediaNetwork FC switch

LEGEND

Fibre connection

1GB Ethernet connection

To MediaNetwork FC switch

Interplay Engine Cluster Node

Right on-board network interface

Left on-board network interface

To Ethernet Public Network

QLogic card

PCI adapter network interface - not used

Fibre Channel 1 left connector

Fibre Channel 0 left connector

FC CH0

FC CH1

All switches set to default “enabled” left

Cluster Shared-Storage RAID Array

SR2400 Back Panel

Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2400)

The following illustration shows the required cable connections when adding a failover cluster in an Avid Unity MediaNetwork environment (SR2400 servers). For a description of the connections, see

“Making Failover Cluster Connections in an Avid Unity MediaNetwork

Environment” on page 22.

Installing the Failover Hardware Components

Slot 3

Slot 1

Private network for heartbeat

ATTO card

To Ethernet public network

Right on-board network interface

Left on-board network interface

To MediaNetwork FC switch

LEGEND

Fibre connection

1GB Ethernet connection

To MediaNetwork FC switch

Interplay Engine Cluster Node

Right on-board network interface

Left on-board network interface

To Ethernet public network

QLogic card

Fibre Channel 1 left connector

Fibre Channel 0 left connector

FC CH0

FC CH1

All switches set to default “enabled” left

Cluster Shared-Storage RAID Array

SR2500 Back Panel

PCI adapter network interface - not used

Slot 2

Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2500)

The following illustration shows the required cable connections when adding a failover cluster in an Avid Unity MediaNetwork environment (SR2500 servers). For a description of the connections, see

Environment” on page 22.

“Making Failover Cluster Connections in an Avid Unity MediaNetwork

1 Automatic Server Failover Introduction

Clustering Terminology

Clustering is not always straightforward, so it is important that you get familiar with the terminology of server clusters before you start. A good source of information is the Microsoft Technology Center for Clustering Services under:

http://www.microsoft.com/windowsserver2003/technologies/clustering/default.mspx

Detailed architecture documentation can be found here:

http://www.microsoft.com/windowsserver2003/techinfo/overview/servercluster.mspx

Here is a brief summary of the major concepts and terms:

• Nodes: Individual computers in a cluster configuration.

• Cluster service: The group of components on each node that perform a cluster-specific activity.

• Resource: Cluster components (hardware and software) that are managed by the cluster service. Resources are physical hardware devices such as disk drives, and logical items such as IP addresses and applications.

• Online resource: A resource that is available and is providing its service.

• Quorum resource: A special common cluster resource. This resource plays a critical role in cluster operations.

• Resource group: A collection of resources that are managed by the cluster service as a single, logical unit.

2 Automatic Server Failover Installation

This chapter describes the processes for configuring the automatic server failover. It is crucial that you follow the instructions given in this chapter completely, otherwise the automatic server failover will not work.

This chapter covers the following topics:

• Server Failover Installation Overview

• Before You Begin the Server Failover Installation

• Preparing the Server for the Cluster Service

• Configuring the Cluster Service

• Configuring Rules for the Cluster Networks

• After Setting Up the Cluster

• Installing the Distributed Transaction Coordinator

• Installing the Interplay Engine

• Disabling Any Web Servers

• Installing the Interplay Engine on the First Node

• Installing the Interplay Engine on the Second Node

• Bringing the Interplay Engine Online

• Testing the Complete Installation

• Updating a Clustered Installation (Rolling Upgrade)

• Uninstalling the Interplay Engine on a Clustered System

2 Automatic Server Failover Installation

Server Failover Installation Overview

Installation and configuration of the automatic server failover consists of the following major tasks:

• Make sure that the network is correctly set up and that you have reserved IP host names and static IP addresses (see “Before You Begin the Server Failover Installation” on page

28).

• Prepare the servers for the cluster service (see “Preparing the Server for the Cluster

Service” on page 31). This includes configuring the nodes for the network and

formatting the drives.

• Configure the cluster service (see “Configuring the Cluster Service” on page 41,

“Configuring Rules for the Cluster Networks” on page 49, and “After Setting Up the Cluster” on page 52).

• Install the Distributed Transaction Coordinator (MSDTC group) (see “Installing the

Distributed Transaction Coordinator” on page 56).

• Install the Interplay Engine on both nodes (see “Installing the Interplay Engine” on page

62).

• Test the complete installation (see “Testing the Complete Installation” on page 82).

Do not install any other software on the cluster machines except the Interplay engine. For

example, Media Indexer software needs to be installed on a different server. For complete installation instructions, see the Avid Interplay Software Installation and Configuration

Guide.

For more details about server clusters, see the Microsoft document “Guide to Creating and Configuring a Server Cluster under Windows Server 2003,” available at:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering /confclus.mspx

Before You Begin the Server Failover Installation

Before you begin the installation process, you need to do the following:

• Make sure that the facility has a network that is qualified to run Active Directory and DNS services.

• Determine the subnet mask, the gateway, DNS, and WINS server addresses on the network.

• Install and set up an Avid Unity client on both servers. See the Avid Unity MediaNetwork File Manager Setup Guide or the Avid Unity ISIS System Setup Guide.

Before You Begin the Server Failover Installation

• Create or select two domain user accounts:

- Cluster Service Account (Server Execution User): Create or select an account (sometimes called the cluster user account) that is used to start the cluster service and is also used by the Interplay Engine service. This account must be a domain user and it must be a unique name that will not be used for any other purpose. The procedures in this document use sqauser as an example of a Cluster Service Account. This account is automatically added to the Local Administrators group on each node by the Interplay Engine software during the installation process.

The Server Execution User is critical to the operation of the Interplay Engine. If necessary, you can change the name of the Server Execution User after the installation. For more information, see “Troubleshooting the Server Execution User Account” and “Re-creating the Server Execution User” in the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide and the Interplay ReadMe.

For information on creating a cluster user account, see the Microsoft document “Guide to Creating and Configuring a Server Cluster under Windows Server 2003.”

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/cl ustering/confclus.mspx.

- Cluster Installation Account: Create or select a user account to use during the installation process. This user account must be a domain user account with privileges to add servers to the domain. This user account is required only during the installation of the cluster.

Do not use the same username and password for the Cluster Service Account and the

Cluster Installation Account. These accounts have different functions and require different privileges.

• Create an Avid Unity user account with read and write privileges. This account is not needed for the installation of Interplay Engine, but is required for the operation of Interplay of the Cluster Service Account.

• Make sure the network includes an Active Directory domain before you install or configure the cluster.

• Reserve static IP addresses for all network interfaces and host names. See “List of IP

Addresses and Network Names” on page 30.

Engine. The user name and password must match the user name and password

+ 65 hidden pages

Pinnacle Systems Interplay Engine - 1.2.4 User Manual

Contents

Using This Guide

Symbols and Conventions

If You Need Help

Viewing User Documentation on the Interplay Portal

Accessing the Online Library

How to Order Documentation

Avid Training Services

1 Automatic Server Failover Introduction

Server Failover Overview

How Server Failover Works

Server Failover Requirements

Installing the Failover Hardware Components

SR2400 Slot Locations

SR2500 Slot Locations

Making Failover Cluster Connections in an Avid Unity ISIS Environment

Failover Cluster Connections in an Avid Unity ISIS Environment (SR2400)

Failover Cluster Connections in an Avid Unity ISIS Environment (SR2500)

Making Failover Cluster Connections in an Avid Unity MediaNetwork Environment

Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2400)

Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2500)

Clustering Terminology

2 Automatic Server Failover Installation

Server Failover Installation Overview

Before You Begin the Server Failover Installation