Pinnacle Systems Interplay Engine - 1.1.2 User Manual

Avid® Interplay™ Engine

Failover Guide

make manage move | media

™

Avid

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,746,994; 4,970,663; 5,045,940; 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,452,378; 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,715,018; 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,987,501; 6,061,758; 6,223,211; 6,301,105; 6,532,043; 6,546,190; 6,636,869; 6,747,705, 6,763,523; 6,813,622. 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 Avid Interplay. 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.

APPLE COMPUTER, 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. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE.

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:

Portions of this software are based 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 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, AniMatte, AudioSuite, AudioVision, AutoSync, Avid, 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, ChromaCurve, ChromaWheel, 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, FieldPak, Film Composer, FilmScribe, FluidMotion, HIIP, HyperSPACE, HyperSPACE HDCAM, IllusionFX, Image Independence, iNEWS, iNEWS ControlAir, Instinct, Interplay, Intraframe, iS9, iS18, iS23, iS36, 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, MetaSync, MissionControl, 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, Sci-Fi, ScriptSync, SecureProductionEnvironment, Show Center, Softimage, Sound Designer II, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Symphony, TARGA, Thunder, Trilligent, UnityRAID, Vari-Fi, Video RAID, Video Slave Driver, VideoSPACE, and Xdeck 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.

Footage

Arizona Images — KNTV Production — Courtesy of Granite Broadcasting, Inc., Editor/Producer Bryan Foote. Eco Challenge Morocco — Courtesy of Discovery Communications, Inc. News material provided by WFTV Television Inc. Tornados + Belle Isle footage — Courtesy of KWTV News 9. WCAU Fire Story — Courtesy of NBC-10, Philadelphia, PA. Women in Sports – Paragliding — Courtesy of Legendary Entertainment, Inc.

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 A • June 2007 • 06/21/07 15:54

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

Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

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

How to Order Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

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

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

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Summary of the Way it Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing the Failover Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SR2400 Slot Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installing a Failover Cluster in an Avid Unity ISIS Environment. . . . . . . . . . . . . 17

Failover Cluster Connections in an Unity ISIS Environment . . . . . . . . . . . . 18

Installing a Failover Cluster in an Avid Unity MediaNetwork Environment. . . . . 19

Failover Cluster Connections in an Unity MediaNetwork Environment . . . . 20

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 2 Automatic Server Failover Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Antivirus Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Need To Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Before You Start: Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

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

Renaming Local Area Network Interface on Each Node . . . . . . . . . . . . . . . . . . 28

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

Configuring Private Network Adapter on Each Node . . . . . . . . . . . . . . . . . . . . . 32

Configuring Public Network Adapter on Each Node. . . . . . . . . . . . . . . . . . . . . . 34

Join Both Servers to the Active Directory Domain. . . . . . . . . . . . . . . . . . . . . . . 35

Setting Up a Cluster User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configuring the Cluster Shared RAID Disks on Each Node . . . . . . . . . . . . . . . 35

Configuring the Cluster Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

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

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

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

Configuring Rules For The Cluster Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Prioritizing the Heartbeat Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

After Setting Up the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Verifying the Quorum Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

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

Testing the Cluster Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Installing the Distributed Transaction Coordinator . . . . . . . . . . . . . . . . . . . . . . . . . . 52

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

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

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

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

Assigning Distributed Transaction Coordinator Resource to the MSDTC Group 56

Bring the MSDTC Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Disabling Any Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

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

Preparation and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

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

Preparing the Server for the Interplay Engine Installation Using Custom Mode 60

Specify Cluster Mode During a Custom Installation . . . . . . . . . . . . . . . . . . 61

Specifying the Interplay Engine Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Specifying the Interplay Engine Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Specifying the Destination Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Specifying the Default Database Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Specifying the Share Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Specifying the Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Specifying the Server User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Specifying the Server Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Enabling Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Preparing the Server for the Interplay Engine Installation Using Typical Mode . 72

Specify Cluster Mode During a Typical Installation . . . . . . . . . . . . . . . . . . . 72

Specifying the Cluster Information During a Typical Installation . . . . . . . . . 73

Specifying the Server User During a Typical Installation. . . . . . . . . . . . . . . 75

Beginning the Installation of Interplay Engine on the First Node . . . . . . . . . . . . 76

Bringing the Disk Resource Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

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

Bring the Interplay Engine Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

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

Updating a Clustered Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Uninstalling the Interplay Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

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

Don't Access the Machines Directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Make Sure to Connect to the Interplay Engine Resource Group . . . . . . . . . . . . . . . 87

Do Not Rename Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Do Not Install the Server on a Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Do Not Change the Interplay Engine Execution User. . . . . . . . . . . . . . . . . . . . . . . . 88

Do Not Edit the Registry While the Server is Offline . . . . . . . . . . . . . . . . . . . . . . . . . 88

Do Not Remove the Dependencies of the Affiliated Services . . . . . . . . . . . . . . . . . . 88

Consider Disabling Failover When Experimenting . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Using This Guide

Congratulations on your purchase of 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.

Using This Guide

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

Margin tips

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

Courier Bold font

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 symbol represents the Apple or Command key. Press and hold the Command key and another key to perform a keyboard shortcut.

In the margin, you will find tips that help you perform tasks more easily and efficiently.

variables.

Courier Bold font identifies text that you type.

Ctrl+key or mouse action k+key or mouse action

Press and hold the first key while you press the last key or perform the mouse action. For example, k+Option+C or Ctrl+drag.

If You Need Help

If you are having trouble using Avid Interplay:

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 for 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 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 the online ReadMe, visit the Knowledge Base at

www.avid.com/readme.

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

If You Need Help

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.

Accessing the Online Library

The Avid Interplay Online Library DVD contains all the Avid Interplay product documentation in PDF format.

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.

The Online Library includes a Master Glossary of all specialized terminology used in the documentation for Avid products.

Using This Guide

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.

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 http://learn.avid.com.

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

Chapter 1

Automatic Server Failover Introduction

This chapter covers the following topics:

• Introduction

• Summary of the Way it Works

• Installing the Failover Hardware Components

• Terminology

Introduction

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.

Chapter 1 Automatic Server Failover Introduction

The following diagram illustrates the failover cluster architecture.

Two-Node Cluster in Unity MediaNetwork environment

Interplay clients

Intranet

Cluster shared RAID array

Network Switch

Private network for heartbeat

Interplay Engine - Cluster Node

Fibre Switch

If you are already using clusters, the Avid Interplay Engine won't interfere with your current setup.

Summary of the Way it Works

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 cluster group.

Summary of the Way it Works

Avid Unity MediaNetwork environment

Failover Cluster

11.22.33.200

Node #1 Intranet: 11.22.33.44 Private: 10.10.10.10

Disk #1 Quorum 4GB

Cluster Group

Intranet

Interplay Server (virtual)

11.22.33.201

Private Network

FibreChannel

Disk #2 MSDTC 5GB

MSDTC

11.22.33.202

Intranet

Node #2 Intranet: 11.22.33.45 Private: 10.10.10.11

Disk #3 Database 925GB +

Chapter 1 Automatic Server Failover Introduction

Installing the Failover Hardware Components

A failover cluster system includes the following components:

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

• Cluster shared storage - RAID array

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

SR2400 Back Panel

All boards must be installed starting in the top slot, and the second board must be in the middle slots, it cannot be in the bottom slot with the middle slot left open.

SR2400 Back Panel Configuration for Avid Unity Environment

Slot

3 Intel Pro 1000MT ATTO

2 QLogic Card QLogic Card

1 Empty Intel Pro 1000MT

PCI slots not used

Unity ISIS Interplay Engine Node and Archive Engine Node

PCI SlotsSmall form factor

Slot 3 Slot 2 Slot 1

Unity MediaNetwork Interplay Engine Node and Archive Engine Node

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.

Installing the Failover Hardware Components

Installing a Failover Cluster in an Avid Unity ISIS Environment

The following illustration shows the required cable connections when adding a failover cluster in an Unity ISIS environment. For a description of the connections, see “Failover

Cluster Connections in an Unity ISIS Environment” on page 18.

PCI adapter network interface right connector

Interplay Engine Cluster Node

To Unity ISIS left subnet

To Unity ISIS right subnet

Fibre Channel 0 left connector

Right - on board network interface

Left - on board network interface

Cluster Shared Storage RAID array

QLogic card

Fibre Channel 1 left connector

Private network for heartbeat

all switches set to default “enabled” left

Interplay Engine Cluster Node

To Unity ISIS left subnet

To Unity ISIS right subnet

FC CH0

LEGEND

Fibre connection

1GB Ethernet connection

Right - on board network interface

Left - on board network interface

FC CH1

PCI adapter network interface right connector

QLogic card

Chapter 1 Automatic Server Failover Introduction

Failover Cluster Connections in an Unity ISIS Environment

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

• First cluster node:

- Left - on board network interface connector to Unity ISIS Left subnet

- Right - on board network interface connector to Unity ISIS Right subnet

- QLogic card connector to cluster shared storage RAID array - left Fibre Channel 1 connector

• Second cluster node:

- Left - on board network interface connector to Unity ISIS Left subnet

- Right - on board network interface connector to Unity ISIS Right subnet

- QLogic card connector to cluster shared storage RAID array - left Fibre Channel 0 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 Infortrend cluster shared storage RAID array are in the default “enable” position (left)

For more details, see the illustration in “Installing a Failover Cluster in an Avid Unity ISIS

Environment” on page 17.

Installing the Failover Hardware Components

Installing a Failover Cluster in an Avid Unity MediaNetwork Environment

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

“Failover Cluster Connections in an Unity MediaNetwork Environment” on page 20.

Interplay Engine Cluster Node

To Ethernet Public Network

all switches set to default “enabled” left

Interplay Engine Cluster Node

Private network for heartbeat

ATTO ca r d

Right - on board network interface

Left - on board network interface

Fibre Channel 0 left connector

FC CH0

ATTO ca r d

Slot 3 Slot 2 Slot 1

QLogic card

PCI adapter network interface - not used

Cluster Shared Storage RAID array

Slot 3 Slot 2 Slot 1

To Unity MediaNetwork FC switch

Fibre Channel 1 left connector

FC CH1

To Unity MediaNetwork FC switch

To Ethernet Public Network

LEGEND

Right - on board network interface

Left - on board network interface

Fibre connection

1GB Ethernet connection

QLogic card

PCI adapter network interface - not used

Chapter 1 Automatic Server Failover Introduction

Failover Cluster Connections in an Unity MediaNetwork Environment

The Interplay Engine Cluster nodes 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

public network

- QLogic card connector to cluster shared storage RAID array - left Fibre Channel

connector

- ATTO card connector to Unity MediaNetwork FC switch

• Second cluster node:

- Left - on board network interface connector to Ethernet

public network

- QLogic card connector to cluster shared storage RAID array - left Fibre Channel

connector

- ATTO card connector to Unity MediaNetwork FC switch

• 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 Infortrend cluster shared storage RAID array are in the default “enable” position (left)

For more details, see the illustration in “Installing a Failover Cluster in an Avid Unity

MediaNetwork Environment” on page 19.

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 - refers to individual computers.

• Cluster service - refers to the group of components on each node that perform a cluster-specific activity.

• Resource - refers to cluster components (hardware and software) that are managed by the cluster service. Physical hardware devices such as disk drives, and logical items such as IP addresses and applications are referred to as resources.

• Online - refers to a resource that is available and is providing its service.

• Quorum resource - is a special common cluster resource. This resource plays a critical role in cluster operations.

Terminology

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

Chapter 1 Automatic Server Failover Introduction

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

You can install the cluster service during any step of the overall Avid Interplay installation process. For the Cluster Group, create a partition on the cluster shared RAID array. This partition is used as the quorum disk (4GB). You also need to create two more partitions: a partition for the MSDTC (see “Installing the Distributed Transaction

Coordinator” on page 52) and a large partition for the server databases. The latter is to store

both the database and the non Avid files. Activate the volumes on both nodes and assign identical drive letters as described in “Configuring the Cluster Shared RAID Disks on Each

Node” on page 35.

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

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

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

Chapter 2 Automatic Server Failover Installation

This chapter covers the following topics:

• Requirements

• Before You Start: Preparation

• Configuring the Cluster Service

• Configuring Rules For The Cluster Networks

• After Setting Up the Cluster

• Installing the Distributed Transaction Coordinator

• Disabling Any Web Servers

• Installing the Interplay Engine on the First Node

• Installing Interplay Engine on the Second Node

• Bring the Interplay Engine Online

• Testing the Complete Installation

• Updating a Clustered Installation

• Uninstalling the Interplay Engine

Requirements

Hardware

A dual server failover cluster capable system with a cluster shared RAID disk set is needed. The automatic server failover system was developed on and tested with Intel Server Chassis SR2400 Packaged Cluster, which is the recommended hardware:

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

Need To Know

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

• Microsoft Windows Active Directory Domains & Domain Users

Requirements

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

• Disk configuration (format, partition, naming)

• Network configuration

Chapter 2 Automatic Server Failover Installation

Before You Start: Preparation

Before you begin the installation process you need to obtain some IP addresses, IP host names, domain user accounts, and establish server addresses on your network.

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

• Install and setup an Avid Unity client on the Interplay Engine servers. See the Avid

Unity MediaNetwork File Manager Setup Guide or the Avid Unity ISIS System Setup Guide.

• 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 Engine.

• You need two domain user accounts when configuring a cluster:

You can use one account for the Cluster Service Account and the Cluster Installation Account. However, this allows the Cluster Service Account more privileges than are needed.

- Cluster Service Account (Server Execution)—Decide on the cluster user name. The

procedures in this document use sqauser as an example for the Cluster Service Account. This user account must have a unique name and be a domain user. This user is assigned administrative rights on both servers. The Interplay Engine service also runs under this account; you should be aware of this during the set up. The server needs to access the media files and this might be a consideration when these are to be located on a non-default location, that is, when the Avid Unity mounting feature is going to be used.

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—Identify the user account to use during the

installation process. This user account is a domain user account with privileges to add servers to the domain. This user account is only required during the installation of the cluster.

• An existing Active Directory Domain is required before installing or configuring the cluster.

• You need several static IP addresses for all network interfaces and host names. See “List

of IP Addresses and Network Names” on page 27.

List of IP Addresses and Network Names

You need to reserve IP host names and static IP addresses before you begin the installation process. A Unity ISIS environment needs 8 IP addresses and a Unity MediaNetwork needs 5 IP addresses. The following table provides a list of example names that you can use when configuring the cluster. The procedures in this chapter use these example names.

Before You Start: Preparation

Make sure that these IP addresses are outside of the range that is available to DHCP so they cannot automatically be assigned to other machines.

Required IP Addresses and Node Names

Node or Service Item Required Example Name Where Used

First Cluster Node • 1 Host Name

• 2 ISIS IP addresses - public (one for left and one for right)

• 1 IP address - private (Heartbeat)

SECLUSTER1 See “Configuring the

Cluster Service on the

First Node” on page 37

and “Creating a Resource

Group for the Distributed Transaction Coordinator” on page 53.

Second Cluster Node • 1 Host Name

• 2 ISIS IP addresses - public (one for left and one for right)

• 1 IP address - private (Heartbeat)

SECLUSTER2 See “Configuring the

Cluster Service on the

Second Node” on page 42

and “Creating a Resource

Group for the Distributed Transaction Coordinator” on page 53.

Cluster service • 1 Network Name

(virtual host name)

• 1 ISIS IP address

MSDTC service — Distributed Transaction Coordinator

Interplay Engine service

• 1 Network Name (virtual host name)

• 1 IP address

• 1 Network Name (virtual host name)

• 2 ISIS IP addresses - public (one for left and one for right)

SECLUSTER See “Configuring the

Cluster Service on the First Node” on page 37.

CLUSTERMSDTC See “Assigning a Network

Name to the MSDTC Group” on page 55.

SEENGINE See “Specifying the

Interplay Engine Details” on page 62 and

“Specifying the Interplay Engine Name” on page 63.

a. All names must be a valid and unique network host name. b. In an Avid Unity MediaNetwork environment you only need one public IP address.

Chapter 2 Automatic Server Failover Installation

Renaming Local Area Network Interface on Each Node

When you rename the LAN interface on each node, make sure you use the same names. The names and network connections must match on both nodes.

To rename the local area network connections:

1. Open the Network Connections window. a. Click Start and select Control Panel. b. Right-click Network Connections, and select Open.

The Network Connections window opens.

2. Right-click one of the listed network connections and select Rename.

+ 64 hidden pages

Pinnacle Systems Interplay Engine - 1.1.2 User Manual

Contents

Using This Guide

Symbols and Conventions

If You Need Help

Accessing the Online Library

How to Order Documentation

Avid Training Services

Automatic Server Failover Introduction

Introduction

Summary of the Way it Works

Installing the Failover Hardware Components

SR2400 Slot Locations

Installing a Failover Cluster in an Avid Unity ISIS Environment

Failover Cluster Connections in an Unity ISIS Environment

Installing a Failover Cluster in an Avid Unity MediaNetwork Environment

Failover Cluster Connections in an Unity MediaNetwork Environment

Terminology

Automatic Server Failover Installation

Requirements

Hardware

Server Software

Space Requirements

Antivirus Software

Need To Know

Before You Start: Preparation

List of IP Addresses and Network Names

Renaming Local Area Network Interface on Each Node