Home

Avid Interplay Engine Failover Guide for AS3000

image

Contents

1. ABEEEEEESSSSEESEEEEEeeeeEeeee OODDOCSOo0g90090090 1 2 QOOOOOO000000 Ej Ea a OOOO0000000000 1 QE GE PARRER QOODOUOOUOOOOOODO00000 I B m LLL LLL i 4 I 1 1 I 1 Ethernet to Avid network switch 1 Fibre Channel to Infortrend 1 1 Ethernet to node 2 1 i 1 Private network Infortrend RAID Array i Back Panel i peewee eee ooooao ooooo0G oooggo ERA EREET oooo0oo onoono Fibre Channel to Infortrend Interplay Engine Cluster Node 2 AS3000 Back Panel ooon omn peaeoocoonor0igponia CEDSOSOceoe0go 12 20000000000 EEEESHSCeeEEEe omna 6 0 moe SPM Ethernet to Avid network switch 2 LEGEND 1 GB Ethernet connection Fibre Channel connection 22 Installing the Failover Hardware Components Failover Cluster Connections Dual Connected Configuration Make the following cable connections to add a failover cluster to an Avid ISIS environment as a dual connected configuration e First cluster node AS3000 Top right network interface connector 2 to the ISIS left subnet VLAN 10 public network Bottom right network interface connector 4 to the ISIS right subnet VLAN 20 public network Bottom left network interface connector
2. Add Edit Remove NetBIOS Status OK DNS Status OK Kerberos Status OK coc n 7 Click Apply A confirmation box asks you to confirm that all cluster nodes need to be restarted You will restart the nodes later in this procedure so select Yes Please confirm action These changes may cause currently connected administrative clients to temporarily lose their connection to this cluster You will also need to manually restart all cluster nodes Are you sure you wish to proceed gt Yes 8 Click the Dependencies tab and check if the new IP address was added with an OR conjunction 66 Configuring the Cluster Service Name muc vticlu04 Properties x General Dependencies Policies Advanced Policies Specify the resources that must be brought online before this resource can be brought online AND OR Resource gt IP Address 10 129 101 40 DR IP Address 10 129 102 40 Click here to add a dependency Insert Delete IP Address 10 129 101 40 OR IP Address 10 129 102 40 How resource dependencies work If the second IP address is not there click Click here to add a dependency Select OR from the list in the AND OR column and select the new IP address from the list in the Resource column 9 Click OK and restart both nodes Start with node one and after it is back online restart the other node Testing th
3. E mail Notification Details Avir Please specify the details for the e mail notification Make sure that you enter the corect SMTP server IP m E mail Details Recipient e mail address administrator mydomain con Sender e mail address Workgroups erver mydomain com SMTP server IP fi23 123 123 123 IV Send critical notifications also to Avid Support Avid Interplay lt Back Cancel 2 Type the administrator s email address and the email address of the server which is the sender If an event such as Resource Failure or Disk Full occurs on the server machine the administrator receives an email from the sender s email account explaining the problem so that the administrator can react to the problem You also need to type the static IP address of your SMTP server The notification feature needs the SMTP server in order to send emails If you do not know this IP ask your administrator 3 If you also want to inform Avid Support automatically using email if problems arise select Send critical notifications also to Avid Support 4 Click Next The installer modifies the file Config xml in the Workgroup_Data Server Config Config directory with your settings If you need to change these settings edit Config xml The Ready to Install dialog box opens 86 Installing the Interplay Engine on the First Node Installing the Interplay Engine for a Custom Installation on the First Node
4. The Disk Management window opens The following illustration shows the shared storage drives labeled Disk 1 Disk 2 and Disk 3 In this example they are offline not initialized and unformatted 45 Preparing the Server for the Cluster Service Disk Management volume _ Layout Type Fie system status ______ capacty _ Free space e Free Fault Toleranc Simple Basic Healthy Active Recovery Partition 10 00 G6 10 00 GB 100 C DATA D Simple Basic NTFS Healthy Primary Partition 841 51 GB 397 91GB 47 90s C Simple Basic NTFS Healthy Boot Page File Crash Dump Primary Partition 80 00 GB 54 00GB 67 sDisk 0 Basic os C DATA D 931 51 GB 10 00 GB 80 00 GB NTFS 841 51 GB NTFS Online Healthy Active Recovery Partiti Healthy Boot Page File Crash Dump Pri Healthy Primary Partition Disk 1 Le Unknown 10 00 GB 10 00 GB Offline i Unallocated Help Disk 2 ae Unknown 10 00 GB 10 00 GB Offline i Unallocated Help Disk 3 Unknown 814 16 GB 814 16 GB Offline i Unallocated Help 3 If the disks are offline right click Disk 1 in the left column and select Online Repeat this action for Disk 3 Do not bring Disk 2 online 4 If the disks are not already initialized right click Disk 1 in the left column and select Initialize Disk The Initialize Disk dialog box opens 46 Preparing th
5. on page 45 The tasks in this section do not require the administrative privileges needed for Microsoft cluster creation see Requirements for Domain User Accounts on page 27 Changing Default Settings for the ATTO Card on Each Node You need to use the ATTO Configuration Tool to change some default settings on each node in the cluster To change the default settings for the ATTO card 1 On the first node click Start and select Programs gt ATTO ConfigTool gt ATTO ConfigTool The ATTO Configuration Tool dialog box opens 2 In the Device Listing tree left pane click the expand box for localhost A login screen is displayed 33 Preparing the Server for the Cluster Service El Network fl localhost Login to localhost 3 Type the user name and password for a local administrator account and click Login 4 In the Device Listing tree navigate to the appropriate channel on your host adapter 5 Click the NVRAM tab 34 Preparing the Server for the Cluster Service EB atto ConfigTool Piel x File Network Help Device Listing Basic Info N RAM Network m localhost NYRAM Configuration ia pcis086 2822 a Celerity FC 81EN Node Name 20 00 00 10 86 03 21 6e Port Name 21 00 00 10 86 03 21 6e DS_S12F R1440 z eae Boot Driver fenabled sd D5_512F R1440 Hard Address Enable Disabled Hard Address pp Execution Throttle be F
6. Interplay Engine service Item Required 1 Host Name 1 ISIS IP address public 1 IP address private Heartbeat 1 Host Name 1 ISIS IP address public 1 IP address private Heartbeat 1 Network Name virtual host name 1 ISIS IP address public virtual IP address 1 Network Name virtual host name 1 ISIS IP address public virtual IP address Example Name SECLUSTERI1 SECLUSTER2 SECLUSTER SEENGINE Where Used See Creating the Cluster Service on page 52 See Creating the Cluster Service on page 52 See Creating the Cluster Service on page 52 See Specifying the Interplay Engine Details on page 76 and Specifying the Interplay Engine Service Name on page 78 30 Before You Begin the Server Failover Installation The following table provides a list of example names that you can use when configuring the cluster for an ISIS dual connected configuration Fill in the blanks to use as a reference IP Addresses and Node Names ISIS Dual Connected Configuration Node or Service Cluster node 1 Cluster node 2 Microsoft cluster service Interplay Engine service Item Required 1 Host Name 2 ISIS IP addresses public left right 1 IP address private Heartbeat 1 Host Name 2 ISIS IP addresses public left right 1 IP address private Heartbeat 1 Network N
7. In this dialog box begin the installation of the engine software Ready to install Avir You are now ready to install Avid Interplay Engine Press the Next button to begin the installation or the Back button to reenter the installation information Avid Interplay Cancel To install the Interplay Engine software 1 Click Next Use the Back button to review or change the data you have entered You can also terminate the installer using the Cancel button because no changes have been done to the system yet The first time you install the software a dialog box opens and asks if you want to install the Sentinel driver This driver is used by the licensing system 2 Click Continue The Installation Completed dialog box opens after the installation is completed 87 Installing the Interplay Engine on the First Node Installation Completed AVIP Avid Interplay 2 4 0 26990 Engine has been successfully installed OK The service Avid Workgroup Engine Monitor has been installed successfully OK The service Avid Workgroup Server Browser has been installed successfully OK The service Avid Workgroup TCP COM Bridge has been installed successfully OK The service Avid_Workgroup_Preview_Server has been installed successfully OK The service Avid Workgroup YSS Service has been installed successfully OK This server itself acts as Central Configuration Server CCS OK The Avid Workgr
8. Sharing Connect using Intel R 82574L Gigabit Network Connection This connection uses the following items o Client for Microsoft Networks L Sos Packet Scheduler amp File and Printer Sharing for Microsoft Networks Internet Protocol Version 6 TCP IP v6 Pe Internet Protocol Version 4 TCP IP v4 Link Layer Topology Discovery Mapper 1 0 Driver Link Layer Topology Discovery Responder Install Uninstall Properties Description Transmission Control Protocol Internet Protocol The default wide area network protocol that provides communication across diverse interconnected networks lt Select this check box All others are unchecked OK Cancel 5 Select Internet Protocol Version 4 TCP IPv4 and click Properties The Internet Protocol Version 4 TCP IPv4 Properties dialog box opens 40 Preparing the Server for the Cluster Service Internet Protocol ersion 4 TCP IP 4 Properties General You can get IP settings assigned automatically if your network supports this capability Otherwise you need to ask your network administrator for the appropriate IP settings Obtain an IP address automatically Use the Following IP address IP address 192 168 100 1 Subnet mask 255 255 255 0 Default gateway Obtain DNS server address automatically Use the following DNS server address
9. Streamgenie StreamRAID SubCap Sundance Sundance Digital SurroundScope Symphony SYNC HD SYNC I O Synchronic SynchroScope Syntax TDM FlexCable TechFlix Tel Ray Thunder TimeLiner Titansync Titan TL Aggro TL AutoPan TL Drum Rehab TL Everyphase TL Fauxlder TL In Tune TL MasterMeter TL Metro TL Space TL Utilities tools for storytellers Transit TransJammer Trillium Lane Labs TruTouch UnityRAID Vari Fi Video the Web Way VideoRAID VideoSPACE VTEM Work N Play Xdeck X Form Xmon and XPAND are either registered trademarks or trademarks of Avid Technology Inc in the United States and or other countries Adobe and Photoshop are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and or other countries Apple and Macintosh are trademarks of Apple Computer Inc registered in the U S and other countries Windows is either a registered trademark or trademark of Microsoft Corporation in the United States and or other countries All other trademarks contained herein are the property of their respective owners Avid Interplay Engine Failover Guide for AS3000 Servers 0130 07643 03 Rev C February 2013 Created 5 9 13 e This document is distributed by Avid in online electronic form only and is not available for purchase in printed form Chapter 1 Chapter 2 Contents Using This Guide 0 00000 9 Revision USUI Saas pte dean eerie eb eau Rede Reh Be BOP Rie dead
10. gi Configuration 3 Storage Server Name O amp Name muc srvcluvtl2 Online a IP Address 10 129 101 49 Online aM IP Address 10 129 102 49 Online File Server FileServer muc srvcluvtl2 Avid Online Disk Drives Ca Avid Workgroup Disk Online Other Resources E Avid Workgroup Engine Monitor Online OF Avid Workgroup Preview Server Online P Avid Workgroup Server Browser Online LF Avid Workgroup TCP COM Bridge Online b Avid Workgroup VSS Service Online After Installing the Interplay Engine After you install the Interplay Engine install the following applications on both nodes e Interplay Access From the Interplay Server Installer Main Menu select Servers gt Avid Interplay Engine gt Avid Interplay Access e Avid ISIS client See the Avid ISIS System Setup Guide If you cannot log in or connect to the Interplay Engine make sure the database share WG_Database exists You might get the following error message when you try to log in The network name cannot be found 0x80070043 For more information see Creating the Database Share Manually on page 91 Then create an Interplay database as described in Creating an Interplay Database on page 103 102 Creating an Interplay Database Creating an Interplay Database Before testing the failover cluster you need to create a database The following procedure des
11. the container in which new computer objects get created such as the computer s Organizational Unit OU 28 Before You Begin the Server Failover Installation Create computer objects for the cluster service virtual host name and the Interplay Engine service virtual host name in the Active Directory AD and grant the user Full Control on them For examples see List of IP Addresses and Network Names on page 29 The account for these objects must be disabled so that when the Create Cluster wizard and the Interplay Engine installer are run they can confirm that the account to be used for the cluster is not currently in use by an existing computer or cluster in the domain The cluster creation process then enables the entry in the AD For more information on the cluster creation account and setting permissions see the Microsoft article Failover Cluster Step by Step Guide Configuring Accounts in Active Directory at http technet microsoft com en us library cc73 1002 28WS 10 29 aspx e Cluster administration account Create or select a user account for logging in to and administering the failover cluster server Depending on the account policies of your site this account could be the same as the cluster installation account or it can be a different domain user account with administrative permissions on the servers that will become cluster nodes Do not use the same username and password for the Server Execution User and t
12. 2 In the Server Manager list open Features gt Failover Cluster Manager gt cluster_name 3 Click Storage 60 Configuring the Cluster Service 4 In the Storage window right click Cluster Disk 1 and select Properties Storage re Summary of Storage w Storage Total Capacity 2 Total Disks 2 online Totat 1 82 T8 1 Avalabke Disks 1 online Free Space 677 36 GB 1 In Use Disks 1 ontine Percent Free 36 4 Bring ths resource onfine Take this resource offline Change dive letter Show the critical events for this resource Show Dependency Report More Actions gt Properties Help Available SI E Ce D aba Volume The Properties dialog box opens Cluster Disk 1 Properties General Dependencies Policies Advanced Paicies Shadow Copies ye Resource Name Cluster Dick 1 I Resource type Physical Disk Status Onine Recent Cluster Events Available Capacity Tota 1 81 TB Free Space 667 45GB Percent Free 35 10 GB 99 1 free muc stvast vil 1 81 TB 36 0 free 5 In the Resource Name dialog box type a name for the cluster disk In this case Cluster Disk 1 is the Quorum disk so type Quorum as the name 61 Configuring the Cluster Service To remove all disks other than Cluster Disk 1 Quorum 1 In the Storage window right click Cluster Disk 2 and select Delete 2 In the Storage window right click Cluster Disk 3 if available or Databases if
13. Active Directory and DNS Requirements nananana aaan 32 Preparing the Server for the Cluster Service 0 0c cee eee eee eee eee 33 Changing Default Settings for the ATTO Card on Each Node 5 33 Changing Windows Server Settings on Each Node naaasar srann 36 Renaming the Local Area Network Interface on Each Node 36 Configuring the Private Network Adapter on Each Node 00065 39 Configuring the Binding Order Networks on Each Node hh Baa I Configuring the Public Network Adapter on Each Node 44 Configuring the Cluster Shared Storage RAID Disks on Each Node 45 Configuring the Cluster Service 0c 0c cc ne kee ceed eee eee eee eee eed eee 49 Joining Both Servers to the Active Directory Domain 49 Installing the Failover Clustering Feature 20 022002e eee eee 49 Creating the Cluster Service ae ate wi ea oe earn aren eae Bae 52 Renaming the Cluster Networks in the Failover Cluster Manager Sea OO Renaming Cluster Disk 1 and Deleting the Remaining Cluster Disks 60 Adding a Second IP Address to the Cluster 20020000 00 0ee 62 Tasting the Cluster Installation esi c204 5004 0c0 ee eek suede cenaeewenew ses 67 Chapter 3 Installing the Interplay Engine for a Failover Cluster 70 Disabling Any Web Servers 4 lt c s20ce00eueseeeuseae
14. Avid Workgroup resource group This applies to the installation on the first node only Subsequent installations should be run as described in Updating a Clustered Installation Rolling Upgrade on page 105 or in the Avid Interplay ReadMe Checking the Status of the Resource Group After installing the Interplay Engine check the status of the resources in the Avid Workgroup Server resource group To check the status of the resource group 1 After the installation is complete right click My Computer and select Manage The Server Manager window opens 2 In the Server Manager list open Features and click Failover Cluster Manager 3 Open the Avid Workgroup Server resource group The list of resources should look similar to those in the following illustration 89 Installing the Interplay Engine on the First Node Fe Roles all Features Avid Workgroup Server AT gt Failover Cluster Manager R muc vtlasclut VTL local ik Services and applications kgroup Server Status Offline Alerts lt none gt Storage Networks Preferred Owners lt none gt Current Owner muc srvas2vtl Cluster Events 7 a Diagnostics F EN Configuration S Storage Server Name Sieg Name muc srvcluvtl2 a IP Address 10 129 101 49 File Server FileServer muc srvcluvtl2 Avid Disk Drives Ca Avid Workg
15. 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 amp Feel software from Incors GmbH This product includes software developed by the Apache Software Foundation http www apache org DevelopMentor This product may include the JCifs library for which the following notice applies JCifs Copyright 2004 The JCIFS Project is licensed under LGPL http jcifs samba org See the LGPL txt file in the Third Party Software directory on the installation CD Avid Interplay contains components licensed from LavanTech These components may only be used as part of and in connection with Avid Interplay Attn Government User s Restricted Rights Legend U S GOVERNMENT RESTRICTED RIGHTS This Software and its documentation are commercial computer software or commercial computer software documentation In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the U S Government all rights with respect to this Software and documentation are subject to the terms of the License Agreement pursuant to FAR 12 212 a and or DFARS 227 7202 1 a as applicable Trademarks 003 192 Digital I O 192 I O 96 I O 96i I O Adrenaline AirSpeed ALEX Alienbrain AME AniMatte Archive Archive II Assistant Station AudioPages AudioStation AutoLoop Auto
16. Create failover clusters validate hardware for potential faloves clusters and perfcem configuration changes to pour fafover A failover cluster is 4 set of independent computers that work together to increase the avaiabilly of senices and applications The clustered servers called nodes are connected by physical cables and by software If one of the nodes fails another node begins to provide services a process known as falover To begin to use failover clustering first validate your hardware configuration then create a cluster Alter these steps ae complete you can manage the cluster Managing a cluster can include migrating services and applications to it from a cluster sunning Windows Server 2003 Windows Server 2008 or Windows Server 2008 R2 nderstai ater v tests Crealing a failover cluster or adding a cluster node Managing a fafover cluster Miorati r icali Failover cluster topics on the Web Brae ses cob Wit BB Microsoft sunpoet page on the Web The Create Cluster Wizard opens with the Before You Begin window 6 Review the information and click Next you will validate the cluster in a later step 7 In the Select Servers window type the simple computer name of node 1 and click Add Then type the computer name of node 2 and click Add The Cluster Wizard checks the entries and if the entries are valid lists the fully qualified domain names in the list of servers as shown in the following illustration 53 Configuri
17. Engine for the first time on a machine with cluster services you are asked to choose between clustered and regular installation The installation on the second node or later updates reuses the configuration from the first installation without allowing you to change the cluster specific settings In other words it is not possible to change the configuration settings without uninstalling the Interplay Engine Bringing the Shared Database Drive Online You need to make sure that the shared database drive S is online To bring the shared database drive online 1 Shut down the second node 2 Open the Disk Management tool in one of the following ways gt Right click My Computer and select Manage In the Server Manager list select Storage gt Disk Management gt Click Start type Disk and select Create and format hard drive The Disk Management window opens The following illustration shows the shared storage drives labeled Disk 1 Disk 2 and Disk 3 Disk 1 is online Disk 2 is not formatted and is offline not used and Disk 3 is formatted but offline 72 Installing the Interplay Engine on the First Node L Server Manager File Action View Help gt m Gle Ta Server Manager MUC SRVAS2VTL E ES Roles all Features E amp Failover Cluster Manager E amp 3 muc vtlasclut VTL local ic iE Services and applications Nodes Storage A Networks 83 Cluster Events E Diagno
18. Server 118 Service name examples for failover cluster 29 Services dependencies 110 112 Shared drive bringing online 72 configuring for failover cluster 45 specifying for Interplay Engine 76 Slot locations AS3000 server failover cluster 21 Software requirements for failover cluster system 19 Subnet Mask 76 T Training services 12 Troubleshooting 10 server failover 110 112 U Uninstalling Interplay Engine failover cluster 107 Updating cluster installation 105 V Virtual IP address for Interplay Engine failover cluster 76 W Web Server IIS role removing 115 Web servers disabling 70 Windows Firewall disabling 120 Windows server settings changing before installation 36 112 125 Index ABCDEFGHIJKLMNOPQRSTUVWXYZ 126
19. Service Right Properties xi Networking Sharing Connect using a gt Intel R PRO 1000 PT Dual Port Server Adapter This connection uses the following items of Client for Microsoft Networks v 2 QoS Packet Scheduler v A File and Printer Sharing for Microsoft Networks E Internet Protocol Version 6 TCP Pv6 Internet Protocol Version 4 TCP IPv4 Link Layer Topology Discovery Mapper 1 0 Driver Link Layer Topology Discovery Responder Install Uninstall Properties Description TCP IP version 6 The latest version of the internet protocol that provides communication across diverse interconnected networks 4 4 4 OK Cancel Configuring the Cluster Shared Storage RAID Disks on Each Node Both nodes must have the same configuration for the cluster shared storage RAID disk When you configure the disks on the second node make sure the disks match the disk configuration you set up on the first node Make sure the disks are Basic and not Dynamic To configure the shared storage RAID disks on each node 1 Shut down the server node you are not configuring at this time 2 Open the Disk Management tool in one of the following ways gt Right click My Computer and select Manage In the Server Manager list select Storage gt Disk Management gt Click Start type Disk and select Create and format hard drive
20. You can also access it through the Help menu in Interplay Access and the Interplay Administrator The Interplay Help combines information from all Interplay guides in one Help system It includes a combined index and a full featured search From the Interplay Portal you can run the Help in a browser or download a compiled chm version for use on other systems such as a laptop To open the Interplay User Information Center through a browser 1 Type the following line in a web browser http Interplay_Engine_name For Interplay_Engine_name substitute the name of the computer running the Interplay Engine software For example the following line opens the portal web page on a system named docwg http docwg 11 Avid Training Services 2 Click the Avid Interplay Documentation link to access the User Information Center web page To open the Interplay User Information Center from Interplay Access or the Interplay Administrator gt Select Help gt Documentation Website on Server Avid Training Services Avid makes lifelong learning career advancement and personal development easy and convenient Avid understands that the knowledge you need to differentiate yourself is always changing and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment For information on courses schedules training centers certifications courseware and
21. dialog box is displayed with two networks and two IP addresses Name muc srycluyti2 Properties xi General Dependencies Policies Advanced Policies ra Resource Name Avid Workgroup Name Resource type Network Name Status Online J Publish PTR records DNS Name muc srveluvti2 Full Name muc srycluvti2 YTL local IP Addresses Network IP Address a 10 129 101 0 24 10 129 101 49 a 10 129 102 0 24 10 129 102 49 Add Edit Remove NetBIOS Status OK DNS Status OK Kerberos Status OK 94 Installing the Interplay Engine on the First Node 6 Check that you entered the IP address correctly then click Apply 7 Click the Dependencies tab and check that the second IP address was added with an OR in the AND OR column Name muc srycluvtl2 Properties xi General Dependencies Policies Advanced Policies Specify the resources that must be brought online before this resource can be brought online AND OR Resource IP Address 10 129 101 49 OR IP Address 10 129 102 49 Click here to add a dependency Insert Delete IP Address 10 129 101 49 OR IP Address 10 129 102 49 How resource dependencies work Cancel Apply 8 Click OK The resources screen should look similar to the following illustration 95 Installing the Interplay Engine on the First Node Avid Workgroup Server Avid Workgroup Server Fa Summary of Avid Wor
22. domain user account to use during the installation and configuration process There are special requirements for the account that you use for the Microsoft cluster installation and creation process described below If your site allows you to use an account with the required privileges you can use this account throughout the entire installation and configuration process If your site does not allow you to use an account with the required privileges you can work with the site s IT department to use a domain administrator s account only for the Microsoft cluster creation steps For other tasks you can use a domain user account without the required privileges In addition the account must have administrative permissions on the servers that will become cluster nodes You can do this by adding the account to the local Administrators group on each of the servers that will become cluster nodes Requirements for Microsoft cluster creation To create a user with the necessary rights for Microsoft cluster creation you need to work with the site s IT department to access Active Directory AD Depending on the account policies of the site you can grant the necessary rights for this user in one of the following ways Make the user a member of the Domain Administrators group There are fewer manual steps required when using this type of account Grant the user the permissions Create Computer objects and Read All Properties in
23. failover See Testing the Cluster Installation on page 67 Creating the cluster service requires an account with particular administrative privileges For more information see Requirements for Domain User Accounts on page 27 Joining Both Servers to the Active Directory Domain After configuring the network information join the two servers to the Active Directory domain Each server requires a reboot to complete this process At the login window use the domain administrator account see Requirements for Domain User Accounts on page 27 Installing the Failover Clustering Feature The Failover Clustering feature is a Windows Server 2008 feature that contains the complete Failover functionality The Failover Cluster Manager which is a snap in to the Server Manager is installed as part of the Failover Clustering installation 49 Configuring the Cluster Service To install the Failover Clustering featurer 1 On the first node right click My Computer and select Manage The Server Manager window opens 2 In the Server Manager list click Features 3 On the right side of the Features window click Add Features A View the status of features installed on this server and add or remove features Features Summary Features Summary Help Features 7 of 42 installed ee Add Features 5 Remove Features Background Intelligent Transfer Service BITS Compact Server Windows PowerShell Integrated Scripting Envi
24. for use with the FC 81EN host adapter 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 The automatic failover system was qualified on the following operating system e Windows Server 2008 R2 Enterprise A license for the Interplay Engine failover cluster is required A license for a failover cluster includes two hardware IDs For installation information see Installing a Permanent License on page 104 Space Requirements The default disk configuration for the Infortrend shared RAID arrays are as follows Infortrend Disk 12F R1440 Disk 1 Quorum disk 10 GB Disk 2 not used 10 GB Disk 3 Database disk 814 GB or larger 19 Installing the Failover Hardware Components Antivirus Software You can run antivirus software on a cluster if the antivirus software is cluster aware For information about cluster aware versions of your antivirus software contact the antivirus vendor If you are running antivirus software on a cluster make sure you exclude these locations from the virus scanning Q Quorum disk C Windows Cluster and S Workgroup_Databases database Functions You Need To Know Before you set up a cluster in an Avid Interplay environment you should be familiar with the following functions e Microsoft Windows Active Directory domains and domain users e Microsoft Windows clusterin
25. host names and IP addresses see Before You Begin the Server Failover Installation on page 27 e Prepare the servers for the cluster service see Preparing the Server for the Cluster Service on page 33 This includes configuring the nodes for the network and formatting the drives e Configure the cluster service see Configuring the Cluster Service on page 49 e Install the Interplay Engine on both nodes see Installing the Interplay Engine for a Failover Cluster on page 70 e Test the complete installation see Testing the Complete Installation on page 103 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 Before You Begin the Server Failover Installation For more details about Microsoft clustering technology see the Windows Server 2008 R2 Failover Clustering resource site www microsoft com windowsserver2008 en us failover clustering technical aspx Before You Begin the Server Failover Installation Before you begin the installation process you need to do the following Make sure all cluster hardware connections are correct See Installing the Failover Hardware Components on page 20 Make sure that the site has a network that is qualified to run Active Directory an
26. on the server machine in the Windows Registry See Automatic Server Failover Tips and Rules on page 110 82 Installing the Interplay Engine on the First Node 2 Click Next The Specify Server User dialog box opens Specifying the Server User In this dialog box define the Cluster Service account Server Execution User used to run the Avid Interplay Engine The Server Execution User is the Windows domain user that runs the Interplay Engine and the cluster service This account is automatically added to the Local Administrators group on the server This account must be the one that was used to set up the cluster service See Before You Begin the Server Failover Installation on page 27 Specify Server User AVI gt Please specify the user account you want to use to run the Avid Interplay 1 0 0 4439 Engine and the password If the user is not available locally this program will try to create it If you want to use a user account from a domain please enter the user like MYDOMAIN MYUSER ATTENTION you are installing in cluster mode The user specified here must be the domain user that was entered to set up the cluster service Server Execution User User Name mydomain sqauser Password Confirm Password Avid Interplay Eem To specify the Server Execution User 1 Type the Cluster Service Account user login information A The installer cannot check the username or password you type i
27. ooosg0oooo0oo0O Doooog0o00o00000 Dooosg0o00o00000 200000000000 opopoop0000000000000 0000000 LLL LLELLE 3 4 Adapter card in top PCle slot Failover Cluster Connections Avid ISIS Redundant Switch Configuration Make the following cable connections to add a failover cluster to an Avid ISIS environment using the redundant switch configuration First cluster node Top right network interface connector 2 to layer 3 switch 1 VLAN 30 Bottom left network interface connector 3 to the bottom left network interface connector on the second cluster node private network for heartbeat Fibre Channel connector on the ATTO Celerity FC 81EN card to the Fibre Channel top connector on the Infortrend RAID array e Second cluster node Top right network interface connector 2 to layer 3 switch 2 VLAN 30 Bottom left network interface connector 3 to the bottom left network interface connector on the second cluster node private network for heartbeat Fibre Channel connector on the ATTO Celerity FC 81EN card to the Fibre Channel bottom connector on the Infortrend RAID array 21 Installing the Failover Hardware Components The following illustration shows these connections Failover Cluster Connections Avid ISIS Redundant Switch Configuration Interplay Engine Cluster Node 1 AS3000 Back Panel
28. outages Avid supports a configuration that uses two network switches each connected to a shared primary network VLAN 30 and protected by a failover protocol If one network switch fails the virtual server remains online through the other VLAN 30 network and switch These configurations are described in the next section Changes for Windows Server 2008 This document describes a cluster configuration that uses the cluster application supplied with Windows Server 2008 R2 Enterprise The cluster creation process is simpler than that used for Windows Server 2003 and eliminates the need to rely on a primary network Requirements for the Microsoft cluster installation account have changed see Requirements for Domain User Accounts on page 27 Requirements for DNS entries have also changed see Active Directory and DNS Requirements on page 32 Installation of the Interplay Engine and Interplay Archive Engine now supports Windows Server 2008 but otherwise has not changed 15 Server Failover Configurations Server Failover Configurations There are two supported configurations for integrating a failover cluster into an existing network e Accluster in an Avid ISIS environment that is integrated into the intranet through two layer 3 switches VLAN 30 in Zone 3 This redundant switch configuration protects against both hardware and network outages and thus provides a higher level of protection than the dual connected configu
29. test the failover use the hostname of the non active node The following illustration shows the command and result if the non active node node 2 is named warrm ipe4 The status Partially Online is normal les Administrator C Windows system32 cmd exe Cz gt cluster group Cluster Group move warrmn ipe4 Moving resource group Cluster Group Group Node Status Cluster Group warrn ipe4 Partially Online 4 Open the Server Manager and select Features gt Failover Cluster Manager gt cluster_name gt Storage Make sure that the Quorum disk is online and that current owner is node 2 as shown in the following illustration 68 Configuring the Cluster Service r eF Ba sas Haack WARRIHPES H F gt Roles 5 a Features Storage Recent Cluster Events 4 E B Failover Cluster Manager ia E4 warrm cluster2 avid we Summary of Storage ad amp Services and applic iE Avid Workgroup amp Nodes Storage Total Capacity Available Capacity 3 warrm ipe3 3 Total Disks 3 online Total 824 15 GB Total 0 Bytes E warrm ipe4 1 Available Disks 1 online Free Space 823 29 GB Free Space 0 Bytes E Storage 2 In Use Disks 2 online Percent Free 99 9 Percent Free 0 E Networks FA Cluster Networl F ISIS_Left F 1515_Right es es Ce Le Cluster Events Disk Witness in Quorum mz Diagnostics F E Configuration cw Quor
30. 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 1993 1998 Altura Software Inc 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
31. two nodes in the cluster Public This is a public network connected to a network switch Preparing the Server for the Cluster Service New Names Dual connected configuration Not used Right This is a public network connected to network switch You can include the subnet number of the interface For example Right 10 Private This is a private network used for the heartbeat between the two nodes in the cluster Left This is a public network connected to network switch You can include the subnet number of the interface For example Left 20 4 Right click a network connections and select Rename Device Name Intel R 82567LM 4 Gigabit Network Connection Intel R PRO 1000 PT Dual Port Server Adapter Intel R 82574L Gigabit Network Connection Intel R PRO 1000 PT Dual Port Server Adapter Avid recommends that both nodes use identical network interface names Although you can use any name for the network connections Avid suggests that you use the naming conventions provided in the previous table 5 Depending on your Avid network and the device you selected type a new name for the network connection and press Enter 6 Repeat steps 4 and 5 for each network connection 38 Preparing the Server for the Cluster Service The following Network Connections window shows the new names used in a dual connected Avid ISIS environment un Control Panel Network and Interne
32. which they are accessed by network services Connections ath Right ah Private 3 at Local Area Connection x Bindings for Left File and Printer Sharing for Microsoft Networks t Internet Protocol Version 4 TCP IPv4 2 Internet Protocol Version 6 TCP IPv6 v o Client for Microsoft Networks vV Internet Protocol Version 4 TCP IP v4 Internet Protocol Version 6 TCP IP v6 43 Preparing the Server for the Cluster Service 4 In the Connections area use the arrow controls to position the network connections in the following order Fora redundant switch configuration in an Avid ISIS environment use the following order Public Private Fora dual connected configuration in an Avid ISIS environment use the following order as shown in the illustration Left Right Private 5 Click OK 6 Repeat this procedure on node 2 and make sure the configuration matches on both nodes Configuring the Public Network Adapter on Each Node Make sure you configure the IP address network interfaces for the public network adapters as you normally would For examples of public network settings see List of IP Addresses and Network Names on page 29 Avid recommends that you disable IPv6 for the public network adapters as shown in the following illustration 44 Preparing the Server for the Cluster
33. you renamed it and select Delete Storage Recent Cluster Events ied Summary of Storage w Storage Total Capacity Available Capacity 2 Total Disks 2 online Totat 1 82 T8 Tota 1 81 TB 1 Avalable Disks 1 online Free Space 677 36 GB Free Space 667 45 GB 1 In Use Disks 1 ontine Percent Free 364 Percent Free 36 Disk Witness in Quorum E c Quorum Onine muc srvast vti Volume Q File System NTFS 10 GB 99 1 free Available Storage 5 cs EEES Bang this resource online Take this resource offline Change drive letter Show the critical events for this resource Show Dependemy Report More Actions Delete N Properties Hel Adding a Second IP Address to the Cluster If you are configuring a dual connected cluster you need to add a second IP address for the cluster application virtual server To add a second IP address to the cluster 1 Right click My Computer and select Manage The Server Manager window opens 2 In the Server Manager list open Features gt Failover Cluster Manager gt cluster_name 3 Click Networks Make sure that Cluster Use is enabled for both ISIS networks as shown in the following illustration 62 a Server Manager MUC SRVASIYTL E Roles Configuring the Cluster Service a Features Networks Recent Cluster Events None in the last 24 EA Failover Cluster Ma
34. 12 0 GB System type 64 bit Operating System Pen and Touch No Pen or Touch Input is available for this Display 2 Click Advanced system settings on the left of the window The System Properties dialog box opens System Properties x Computer Name Hardware Advanced Remote You must be logged on as an Administrator to make most of these changes m Performance Visual effects processor scheduling memory usage and virtual memory Settings r User Profiles Desktop settings related to your logon Settings r Startup and Recovery System startup system failure and debugging information Settings Environment Variables OK Cancel Apply 3 Click the Advanced tab and click Settings in the Performance area The Performance Options dialog box opens 119 Disabling the Windows Firewall 4 Click the Advanced tab 5 In the Processor scheduling area under Adjust for best performance of select Programs as shown in the following illustration Performance Options xi Visual Effects Advanced Data Execution Prevention M Processor scheduling Choose how to allocate processor resources Adjust for best performance of Programs Background services M Virtual memory A paging File is an area on the hard disk that Windows uses as if it were RAM Total paging file size for all drives 18432 MB Change Cance
35. 3 to the bottom left network interface connector on the second cluster node private network for heartbeat Fibre Channel connector on the ATTO Celerity FC 81EN card to the Fibre Channel top connector on the Infortrend RAID array e Second cluster node AS3000 Top right network interface connector 2 to the ISIS left subnet VLAN 10 public network Bottom right network interface connector 4 to the ISIS right subnet VLAN 20 public network Bottom left network interface connector 3 to the bottom left network interface connector on the first cluster node private network for heartbeat Fibre Channel connector on the ATTO Celerity FC 81EN card to the Fibre Channel bottom connector on the Infortrend RAID array 23 Installing the Failover Hardware Components The following illustration shows these connections Failover Cluster Connections Avid ISIS Dual Connected Configuration Interplay Engine Cluster Node 1 AS3000 Back Panel O DO OOO0O000000000000000u000000u00 O0000000000000000000 OOOODOOOOOOOOOOOOOOOOoOoOoOOOoO0000 P s9 a2 EEE f b 4 if al REC amaaan i TE LLLLL LLL i L 1 Ethernet to ISIS left subnet i 1 Ethernet to ISIS right subnet I 9 Fibre Channel to Infortrend u 1 Ethernet to node 2 F Private network Infortrend RAID Array Back Panel 1 ooogGD ooooo00 oooooo o
36. ATTENTION you are installing in cluster mode It is strongly recommended that you NOT use another CCS server If you decide to choose another server it should be at least as high availability as this typically another clustered installation Set for both nodes Central Configuration Server Use this option for This Avid Interplay Engine Interplay Archive Engine Another Avid Interplay Engine Avid Interplay Cancel A Central Configuration Server CCS is an Avid Interplay Engine with a special module that is used to store server and database spanning information For more information see the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide To specify the server to act as the CCS server 1 Select either the server you are installing or a previously installed server to act as the Central Configuration Server Typically you are working with only one server so the appropriate choice is This Avid Interplay Engine which is the default If you need to specify a different server as the CCS for example if an Interplay Archive Engine is being used as the CCS select Another Avid Interplay Engine You need to type the name of the other server to be used as the CCS in the next dialog box Only use a CCS that is at least as high availability as this cluster installation typically another clustered installation If you specify the wrong CCS you can change the setting later
37. AV i gt Avid Interplay Engine Failover Guide for AS38000 Servers Revision 4 Image Legal Notices Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology Inc This product is subject to the terms and conditions of a software license agreement provided with the software The product may only be used in accordance with the license agreement This product may be protected by one or more U S and non U S patents Details are available at www avid com patents This document is protected under copyright law An authorized licensee of 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 product name Reasonable care has been taken in preparing the information it contains However this document may contain omissions technical inaccuracies or typographical errors Avid Technology Inc does not accept responsibility of any kind for customers losses due to the use of this document Product specifications are subject to change without notice Copyright 2013 Avid Technology Inc and its licensors All rights reserved The following disclaimer is required by Sam Leffler and Silicon Gra
38. Cluster service configuring 52 defined 25 specifying name 52 Cluster Service account Interplay Engine installation 83 specify name 52 Create Database view 103 D Database creating 103 Database folder default location failover cluster 80 Dual connected cluster configuration 16 E Email notification setting for failover cluster 85 F Failover cluster adding second IP address in Failover Cluster Manager 62 Index ABCDEFGHIJKLMNOPQRSTUVWXYZ Avid ISIS dual connected configuration 23 Avid ISIS redundant switch configuration 21 before installation 27 configurations 16 hardware and software requirements 19 installation overview 26 system components 14 system overview 13 Failover Clustering feature adding 49 removing 115 Firewall disabling 120 G GUIDs creating new 112 H Hardware requirements for failover cluster system 19 Heartbeat connection configuring 39 IIS role removing 115 Importing license 104 Infortrend shared storage RAID array supported models 20 Installation failover cluster testing 67 Installing Interplay Engine failover cluster 74 Interplay Access default folders in 103 Interplay Engine Central Configuration Server specifying for failover cluster 82 cluster information for installation 76 default database location for failover cluster 80 enabling email notifications 85 installing on first node 71 preparation for installing on first node 71 Server Execution User specifying fo
39. DHCP server does not provide NetBIOS setting enable NetBIOS over TCP IP Enable NetBIOS over TCP IP Disable NetBIOS over TCP IP 8 On the DNS tab make sure no values are defined and that the Register this connection s addresses in DNS and Use this connection s DNS suffix in DNS registration are not selected 9 On the WINS tab do the following gt Make sure no values are defined in the WINS addresses area gt Make sure Enable LMHOSTS lookup is selected gt Select Disable NetBIOS over TCP IP 10 Click OK A message might by displayed stating This connection has an empty primary WINS address Do you want to continue Click Yes 11 Repeat this procedure on node 2 using the static private IP address for that node 42 Preparing the Server for the Cluster Service Configuring the Binding Order Networks on Each Node Repeat this procedure on each node and make sure the configuration matches on both nodes To configure the binding order networks 1 On node 1 click Start gt Control Panel gt Network and Sharing Center The Network and Sharing Center window opens 2 Click Change adapter settings on the left side of the window The Network Connections window opens 3 From the Advanced menu select Advanced Settings The Advanced Settings dialog box opens Advanced Settings xi Adapters and Bindings Provider Order Connections are listed in the order in
40. ILESERVER network_share PreviewServer The preview server cache folder is normally located inside the default database folder m Preview Server Cache Folder S Workgroup_Databases PreviewServer Browse Avid Interplay Cancel To specify the server cache folder 1 Type or browse to the path of the server cache folder Typically the default path is used 2 Click Next The Enable Email Notification dialog box opens if you are installing the Avid Interplay Engine for the first time 84 Installing the Interplay Engine on the First Node Enabling Email Notifications The first time you install the Avid Interplay Engine the Enable Email Notification dialog box opens The email notification feature sends emails to your administrator when special events such as Cluster Failure Disk Full and Out Of Memory occur Activate email notification if you want to receive emails on special events server or cluster failures Enable E mail Notification AvI gt The Avid Interplay Engine is able to send e mail notifications to your administrator when special events such as Disk Full etc occur Would you like to activate this feature Avid Interplay lt Back Cancel To enable email notification 1 Option Select Enable email notification on server events The Email Notification Details dialog box opens 85 Installing the Interplay Engine on the First Node
41. Network 3 Up Inema E tmuc srves2vtl a Storage E GP Networks JA Cluster Network 1 FP Cluster Network 2 FP Cluster Network 3 fE Custer Events It is possible that Cluster Network 2 usually Right or VLAN 20 is not configured to be external by the Create Cluster Wizard In this case right click Cluster Network 2 select Properties and check Allow clients to connect through this network Cluster Network 2 Properties xi General Cluster Network 2 Name Cluster Network 2 Allow cluster network communication on this network IV Allow clients to connect through this network Donot allow cluster network communication on this network Status Up Subnets 10 129 102 0 24 The following illustration shows components of a cluster in a redundant switch ISIS environment Cluster Network 1 is an external network connecting to one of the redundant switches and Cluster Network 2 is a private internal network for the heartbeat 57 Configuring the Cluster Service B Server Manager Fie Action View Hep gt Alm Ble ip Server Manager MUC SRYASIVTL Networks F Roks ooo gy Features Networks Recent Cluster Events E I Failover Cluster Manager F muc vtlasdu2 YTL local F Services and applications E SR Nodes F muc srves2vtl Storage B Networks J Cluster Network 1 FP Cluster Network 2 fE Custer Events Renaming the Cluster Networks in the Failover Cluster Manag
42. Node on page 71 In contrast to the installation on the first node the installer automatically detects all settings previously entered on the first node The Attention dialog box opens Attention x The installer will set up Avid Interplay Engine in Db cluster mode The following configuration data was retrieved from the cluster service Network Name SEENGINE Share Name wG_Database Shared Drive S Abort the installer now if this information is not correct 3 Click OK 4 The same installation dialog boxes will open that you saw before except for the cluster related settings that only need to be entered once Enter the requested information and allow the installation to proceed 100 Bringing the Interplay Engine Online A Make sure you use the installation mode that you used for the first node and enter the same information throughout the installer Using different values results in a corrupted installation 5 The installation procedure requires the machine to restart up to twice Allow the restart as requested A If you receive a message that the Avid Workgroup Name resource was not found you need to check the registry See Changing the Resource Name of the Avid Workgroup Server on page 98 Bringing the Interplay Engine Online To bring the Interplay Engine online 1 Right click My Computer and select Manage The Server Manager window opens 2 In the Server Manager list open Featu
43. Sync Avid Avid Active Avid Advanced Response Avid DNA Avid DNxcel Avid DNxHD Avid DS Assist Station Avid Ignite Avid Liquid Avid Media Engine Avid Media Processor Avid MEDIArray Avid Mojo Avid Remote Response Avid Unity Avid Unity ISIS Avid VideoRAID AvidRAID AvidShare AVIDstripe AVX Beat Detective Beauty Without The Bandwidth Beyond Reality BF Essentials Bomb Factory Bruno C 24 CaptureManager ChromaCurve ChromaWheel Cineractive Engine Cineractive Player Cineractive Viewer Color Conductor Command 24 Command 8 Control 24 Cosmonaut Voice CountDown d2 d3 DAE D Command D Control Deko DekoCast D Fi D fx Digi 002 Digi 003 DigiBase Digidesign Digidesign Audio Engine Digidesign Development Partners Digidesign Intelligent Noise Reduction Digidesign TDM Bus DigiLink DigiMeter DigiPanner DigiProNet DigiRack DigiSerial DigiSnake DigiSystem Digital Choreography Digital Nonlinear Accelerator DigiTest DigiTranslator DigiWear DINR DNxchange Do More DPP 1 D Show DSP Manager DS StorageCalc DV Toolkit DVD Complete D Verb Eleven EM Euphonix EUCON EveryPhase Expander ExpertRender Fader Pack Fairchild FastBreak Fast Track Film Cutter FilmScribe Flexevent FluidMotion Frame Chase FXDeko HD Core HD Process HDpack Home to Hollywood HYBRID HyperSPACE HyperSPACE HDCAM iKnowledge Image Independence Impact Improv iNEWS iNEWS Assign iNEWS ControlAir InGame Instantwrite Instinct Int
44. TL local af Summary of Cluster muc vtlasclul F3 Services and applications Fy T orv o PP mucwytlasclul has 1 applications services and 2 nodes ie Avid Workgroup Server i Nodes Name muc vtlasclut VTL local Networks Left Private Right Mmuc srvas1vtl j muc srvas2vtl Current Host Server muc srvas vtl Subnets 3 Pv4 and 0 Pv6 B Storage Quorum Configuration Node and Disk Majority Quorum ae Networks Recent Cluster Events H Critical 1 Error 54 8 Cluster Events 3 If the current host of the cluster is not the active node you need to stop the cluster service of the non active node which moves it to the active node a Inthe Server Manager tree right click the node that you want to go offline and select More Actions gt Stop Cluster Service b After the Cluster Service has stopped right click the node for which you just stopped the cluster service and select More Actions gt Start Cluster Service 106 Uninstalling the Interplay Engine on a Clustered System Run the Interplay Engine installer to update the installation on the non active node second node Select Typical mode to reuse values set during the previous installation on that node Restart as requested and continue with Part 2 of the installation The installer will ask you to restart again after Part 2 A Do not move the Avid Workgroup Server to the second node yet 5 Make sure that first node is active Run the Interplay Engine installer to u
45. Workgroup Server application 6 You might also want to experiment by terminating the Interplay Engine manually using the Windows Task Manager NxNServer exe This is also a good way to get familiar with the failover settings which can be found in the Properties dialog box of the Avid Workgroup Server and on the Policies tab in the Properties dialog box of the individual resources 7 Look at the related settings of the Avid Workgroup Server If you need to change any configuration files make sure that the Avid Workgroup Disk resource is online the configuration files can be found on the resource drive in the Workgroup_Data folder Installing a Permanent License During Interplay Engine installation a temporary license for one user is activated automatically so that you can administer and install the system There is no time limit for this license A permanent license is provided by Avid in the form of a file nxn usually on a USB flash drive A license for an Interplay Engine failover cluster includes two hardware IDs You install this license through the Interplay Administrator For more information on managing licenses see the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide 104 Updating a Clustered Installation Rolling Upgrade To install a permanent license l 2 3 Start and log in to the Interplay Administrator Make a folder for the license file on the root directory C of
46. ame virtual host name 2 ISIS IP addresses public virtual IP addresses left right 1 Network Name virtual host name 2 ISIS IP addresses public virtual IP addresses left right Example Name SECLUSTER1 SECLUSTER2 SECLUSTER SEENGINE Where Used See Creating the Cluster Service on page 52 See Creating the Cluster Service on page 52 See Creating the Cluster Service on page 52 See Specifying the Interplay Engine Details on page 76 and Specifying the Interplay Engine Service Name on page 78 31 Before You Begin the Server Failover Installation Active Directory and DNS Requirements Use the following table to help you add Active Directory accounts for the cluster components to your site s DNS If you are familiar with installing a Windows Server 2003 cluster use the second table as a reference Windows Server 2008 DNS Entries Computer Account DNS Dynamic DNS Static Component in Active Directory Entry Entry Cluster node 1 node_1_name Yes No Cluster node 2 node_2_name Yes No MSDTC Not used Not used Not used Microsoft cluster service cluster_name Yes Yes Interplay Engine service virtual ie_name Yes Yes a Entries are dynamically added to the DNS when the node logs on to Active Directory b If you manually created Active Directory entries for the Microsoft cluster service and Interplay Engine service make sure
47. ame the other network Private This network is used for the heartbeat 59 Configuring the Cluster Service Private Properties x General Fri Private Name Privatel Allow cluster network communication on this network J Allow clients to connect through this network Do not allow cluster network communication on this network Status Up Subnets 192 168 100 0 24 Cancel Apply For this private network leave the option Allow clients to connect through this network unchecked Renaming Cluster Disk 1 and Deleting the Remaining Cluster Disks gt amp You can more easily manage the cluster by renaming Cluster Disk 1 which is listed under the Failover Cluster Manager You must delete any disks other than Cluster Disk 1 that are listed In this operation deleting the disks means removing them from cluster control After the operation the disks are labeled offline in the Disk Management tool This operation does not delete any data on the disks Cluster Disk 2 is not used You bring the Databases S drive back online in a later step Bringing the Shared Database Drive Online on page 72 Before renaming or deleting disks make sure you select the correct disk by checking the drive letter either in the Properties dialog box or by expanding Cluster Disks in the Summary of Storage screen To rename Cluster Disk 1 1 Right click My Computer and select Manage The Server Manager window opens
48. amp Computer a Disk drives Display adapters E Monitors Network adapters Intel R 82567 aN anurans Ren at ees Intel R 825741 Update Driver Software Intel R PROs1 Enable Intel R PRO 1 Uninstall 1D Ports COM amp LPT Processors lt gt Storage controllers JE System devices Universal Serial Bus controllers OE bbe bes te Scan For hardware changes Properties 113 Creating New GUIDs for the AS3000 Network Adapters 6 In the pop up dialog box make sure that Delete the driver software for this device is not selected then click OK Confirm Device Uninstall Ea A Intel R 82567LM 4 Gigabit Network Connection 8 Warning You are about to uninstall this device from your system J Delete the driver software for this device Cancel After the last adapter is removed the Network Adapters category disappears 7 Select Action gt Scan for hardware changes ont Device Manager File Action View Help KE fa Scan For hardware changes Add legacy hardware Help Ca E Display adapters ta Human Interface Devices Keyboards A Mice and other pointing devices A Monitors a Ports COM amp LPT Processors lt gt Storage controllers gE System devices g Universal Serial Bus controllers Fe Wait until all four network adapters are repopulated 8 Reconnect the
49. ano tie Be slo 9 Symbols aiid Conventions 2cei4 25442444405 44 66 644540e4eeens eee Rew eeeeeee 10 F You Need HeD i cceiadetacadededeiadedeiaiadatgeatecdeeedt sed daunden 10 Viewing Help and Documentation on the Interplay Portal 2000 11 Avid Tamno SOIC aha pan ak ate liebein Lele kshakeiuws She denen hada hak oie 12 Automatic Server Failover Introduction 200 13 Server Failover OVEMiOW is 046 5 cas honekene dean ekeke keh ake kiisk Esk ESRR 13 How Server Failover WOKS os aac SEE AEM he EAEE EAEE hole 3 os 14 Server Failover Configurations 0 00200 e cece eee eee eee 16 Server Failover Requirements 20020 cece eee eee eee eee 19 Installing the Failover Hardware Components 22 200 eeeeeeeee 20 ASOD SOU LOCMONS sc aces caes TAba SAGA Saeateashrda seas hrdasada dade 21 Failover Cluster Connections Avid ISIS Redundant Switch Configuration 21 Failover Cluster Connections Dual Connected Configuration 23 Clustering Technology and Terminology s an aaaea nanea 25 Creating a Microsoft Failover Cluster 0 000 c cece 26 Server Failover Installation Overview 20000002 eee eee eee eens 26 Before You Begin the Server Failover Installation 0 0 0 0 e eee eee oT Requirements for Domain User Accounts 0000 cece eee eee eee 27 List of IP Addresses and Network Names 200000 e eee eeeeee 29
50. at you entered for the resource group in the previous dialog box Macintosh systems are not always able to map server names to IP addresses If you type a static IP address make sure this IP address is not provided by a DHCP server 2 Click Next The Specify Destination Location dialog box opens 78 Installing the Interplay Engine on the First Node Specifying the Destination Location In this dialog box specify the folder in which you want to install the Interplay Engine program files Specify Destination Location AVI gt Setup will install Avid Interplay 2 4 0 26990 Engine in the following folder To install into a different folder click Browse and select another folder ATTENTION you are installing in cluster mode It is important that the installation takes place on a local disk of the host and not on a cluster disk It is also essential that the same location is used on the other machine Destination Folder l C Program Files x86 Avids vid Interplay Engine Browse Avid Interplay Cancel To specify the destination location 1 Avid recommends that you keep the default path C Program Files Avid Avid Interplay Engine Under no circumstances attempt to install to a shared disk independent installations are required on both nodes This is because local changes are also necessary on both machines Also with independent installations you can use a rolling upgrade approach later upgrading
51. ation for your Avid product is provided as printed release notes they are shipped 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 media 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 www avid com support 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 support Online services are available 24 hours per day 7 days per week Search this online Knowledge Base to find answers to view error messages to access troubleshooting tips to download updates and to read or join online message board discussions Viewing Help and Documentation on the Interplay Portal You can quickly access the Interplay Help PDF versions of the Interplay guides and useful external links by viewing the Interplay User Information Center on the Interplay Portal The Interplay Portal is a web site that runs on the Interplay Engine You can access the Interplay User Information Center through a browser from any system in the Interplay environment
52. aution 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 This symbol indicates menu commands and subcommands in the order you select them For example File gt 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 Bold font is primarily used in task instructions to identify user interface items and keyboard sequences Italic font is used to emphasize certain words and to indicate variables Courier Bold font identifies text that you type Press and hold the first key while you press the last key or perform the mouse action For example Command Option C or Ctrl drag 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 10 Viewing Help and Documentation on the Interplay Portal Ifthe latest inform
53. books please visit www avid com support and follow the Training links or call Avid Sales at 800 949 AVID 800 949 2843 12 a Automatic Server Failover Introduction This chapter covers the following topics e Server Failover Overview e How Server Failover Works e Installing the Failover Hardware Components e Clustering Technology and Terminology Server Failover Overview The automatic server failover mechanism in Avid Interplay allows client access to the Interplay Engine in the event of failures or during maintenance with minimal impact on the availability A failover server is activated in the event of application operating system or hardware failures The server can be configured to notify the administrator about such failures using email The Interplay implementation of server failover uses Microsoft clustering technology For background information on clustering technology and links to Microsoft clustering information see Clustering Technology and Terminology on page 25 A 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 unmo
54. ce appear in supporting documentation This software is provided as is without express or implied warranty Copyright 1996 Daniel Dardailler 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 Modifications Copyright 1999 Matt Koss under the same license as above Copyright c 1991 by AT amp T 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 amp 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 develope
55. cluster mode so that you can take advantage of the failover support r Installation Type Cluster Installs in cluster mode The server will be available under the name of the resource group and will provide automatic failover The installation has to be performed on both machines of the cluster Standalone Installs in standalone mode The server will be available under the physical name of the host and will not be integrated with the cluster Avid Interplay Cancel 3 Select Cluster and click Next to continue the installation in cluster mode The Specify Interplay Engine Details dialog box opens Specifying the Interplay Engine Details In this dialog box provide details about the Interplay Engine Specify Interplay Engine Details Ayip Setup will create the resource group with the parameters specified here The virtual IP address is going to be used for the resource group of the server The drive must be a shared resource that is mounted using the same drive letter on the other machine Interplay Engine Information Virtual IP Address 172 20 74 180 not the C luster IP address Subnet Mask 255 255 255 192 Public Network fet Shared Drive f Avid Interplay lt Back Cancel 76 Installing the Interplay Engine on the First Node To specify the Interplay Engine details 1 Type the following values Virtual IP address This is the Interplay Engine service IP Address no
56. cribes basic information about creating a database For complete information see the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide To create an Interplay database l 2 Start the Interplay Administrator and log in In the Database section of the Interplay Administrator window click the Create Database icon The Create Database view opens In the New Database Information area leave the default AvidWG in the Database Name text box For an archive database leave the default AvidAM These are the only two supported database names Type a description for the database in the Description text box such as Main Production Server Select Create default Avid Interplay structure After the database is created a set of default folders within the database are visible in Interplay Access and other Interplay clients For more information about these folders see the Avid Interplay Access User s Guide Keep the root folder for the New Database Location Meta Data The metadata database must reside on the Interplay Engine server Keep the root folder for the New Data Location Assets If you are creating a split database this entry should show the Avid shared storage workspace that you set in the Server Settings view For more information see the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide Click Create to create directories a
57. d DNS services Make sure the network includes an Active Directory domain before you install or configure the cluster Determine the subnet mask the gateway DNS and WINS server addresses on the network Reserve static IP addresses for all network interfaces and host names See List of IP Addresses and Network Names on page 29 Make sure the time settings for both nodes are in sync If not you must synchronize the times or you will not be able to add both nodes to the cluster Make sure the Remote Registry service is started and is enabled for Automatic startup Open Server Management and select Configuration gt Services gt Remote Registry Create or select domain user accounts for creating and administering the cluster See Requirements for Domain User Accounts on page 27 Create an Avid shared storage user account with read and write privileges This account is not needed for the installation of the Interplay Engine but is required for the operation of the Interplay Engine for example media deletion from shared storage The user name and password must exactly match the user name and password of the Server Execution User Be prepared to install and set up an Avid shared storage client on both servers after the failover cluster configuration and Interplay Engine installation is complete See the Avid ISIS System Setup Guide Requirements for Domain User Accounts Before beginning the cluster installation process
58. d by the University of California Berkeley and its contributors The following disclaimer is required by Nexidia Inc 2010 Nexidia Inc All rights reserved worldwide Nexidia and the Nexidia logo are trademarks of Nexidia Inc All other trademarks are the property of their respective owners All Nexidia materials regardless of form including without limitation software applications documentation and any other information relating to Nexidia Inc and its products and services are the exclusive property of Nexidia Inc or its licensors The Nexidia products and services described in these materials may be covered by Nexidia s United States patents 7 231 351 7 263 484 7 313 521 7 324 939 7 406 415 7 475 065 7 487 086 and or other patents pending and may be manufactured under license from the Georgia Tech Research Corporation USA 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 lIt 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
59. d can be disabled To disable it select the corresponding Local Area Connection entry and select File gt Disable 3 Determine which numbered connection physical port refers to which device name You can determine this by connecting one interface at a time For example you can start by determining which connection refers to the lower left network connection the heartbeat comnection numbered 3 on AS3000 back panel Use the following illustration and table for reference The illustration uses connections in a dual connected Avid ISIS environment as an example Interplay Engine Cluster Node 1 AS3000 Back Panel DOCS CS SC SRoRoo0o0oR0ER0o00u00u000o0uuo BSCSSSSCERSR0e000C080ERgngE0g0Hg Psoocsqaneeqeqesqocca rae DBOSSSneqsoo0ao 2 DODSSSneosoceo pe bH Oa ey LLLLL LLL Ethernet to ISIS left subnet Eth t to ISIS right subnet ernet to ISIS right subne Fibre Channel to Infortrend Ethernet to node 2 Private network 37 Naming Network Connections Label Network on AS3000 Interface Top left network 1 connector Top right network 2 connector Bottom left 3 network connector Bottom right 4 network connector New Names Redundant switch configuration Not used Not used Private This is a private network used for the heartbeat between the
60. de trki kami kabian iaa 70 Installing the Interplay Engine on the First Node 020000e ee eeee fi Preparation for Installing on the First Node 2000002e ee eee 71 Bringing the Shared Database Drive Online 20 02200055 72 Starting the Installation and Accepting the License Agreement 74 Installing the Interplay Engine Using Custom Mode 74 Checking the Status of the Resource Group ee eee oe ee oer ee 89 Creating the Database Share Manually TEETE ET 91 Adding a Second IP Address Dual Connected Configuration 92 Changing the Resource Name of the Avid Workgroup Server 98 Installing the Interplay Engine on the Second Node 2 20 05 100 Bringing the Interplay Engine Online 2000 eee eeeee eaaee 104 After Installing the Interplay Engine 020 002 c ee eee eee va Bare 102 Creating an Interplay Database 22 ccs0cececn enue sacwaeceaneu sue ean 103 Testing the Complete Installation acs cack cack cach bedi saed van den ad wa dmn een 103 Installing a Permanent License 0000 eee eee 104 Updating a Clustered Installation Rolling Upgrade 2 2000 105 Uninstalling the Interplay Engine on a Clustered System 107 Chapter 4 Appendix A Automatic Server Failover Tips and Rules 110 Win
61. dows Server Settings Included in Latest Image 112 Creating New GUIDs for the AS3000 Network Adapters 5 112 Removing the Web Server IIS Role 0 200 02 eee eee eee e eee 115 Removing the Failover Clustering Feature 2 0020 cece eee eeeees 115 Beee a PRG ak A E TAEI LE AL E E wei ne heme SES ALL eam kia ede aR a 118 Switching the Server Role to Application Server 0000002e ee eee 118 Disabling the Windows Firewall citcintoiimcinediiwciad died dak bee eek ae 120 INGEN jade eae E TE EO bk Ripe Si Ring Shea 123 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 This guide is for Interplay Engine clusters that use Avid AS3000 servers 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 Revision History Date Revised May 2013 February 2013 November 2012 January 10 2012 January 6 2012 December 12 2011 November 7 2011 Changes Made Revisions to remove support for Infortrend A16F R2431with the new ATTO FC 81EN card and to d
62. e bring the disks online and assign drive letters You do not need to initialize or format the disks a Open the Disk Management tool as described in step 2 b Bring Disk 1 and Disk 3 online as described in step 3 c Right click a partition select Change Drive Letter and enter the appropriate letter d Repeat these actions for the other partitions 9 Boot the first node 48 Configuring the Cluster Service 10 Open the Disk Management tool to make sure that the disks are still online and have the correct drive letters assigned At this point both nodes should be running Configuring the Cluster Service Take the following steps to configure the cluster service 1 Add the servers to the domain See Joining Both Servers to the Active Directory Domain on page 49 2 Install the Failover Clustering feature See Installing the Failover Clustering Feature on page 49 3 Start the Create Cluster Wizard on the first node See Creating the Cluster Service on page 52 This procedure creates the cluster service for both nodes 4 Rename the cluster networks See Renaming the Cluster Networks in the Failover Cluster Manager on page 58 5 Rename and delete the cluster disks See Renaming Cluster Disk 1 and Deleting the Remaining Cluster Disks on page 60 6 For a dual connected configuration add a second IP address See Adding a Second IP Address to the Cluster on page 62 7 Test the
63. e Cluster Installation At this point test the cluster installation to make sure the failover process is working To test the failover 1 Make sure both nodes are running 2 Determine which node is the active node the node that owns the quorum disk Open the Server Manager and select Features gt Failover Cluster Manager gt cluster_name gt Storage The server that owns the Quorum disk is the active node In the following figure warrm ipe3 node 1 is the current owner of the Quorum disk and is the active node 67 Configuring the Cluster Service E 5 gt Roles a Features Recent Cluster Events amp Failover Cluster Manager g warrm cluster2 avid we Summary of Storage a F Services and applic yer lee Avid Workgroup 2 E7 Nodes Storage Total Capacity Available Capacity warrm ipe3 3 Total Disks 3 online Total 824 15 GB Total 0 Bytes F warrm ipe4 1 Available Disks 1 online Free Space 823 29 GB Free Space 0 Bytes Cc Storage 2 In Use Disks 2 online Percent Free 99 9 Percent Free 0 A a Networks F Cluster Networl H ISIS_Left F 1SI5_Right u Cluster Events Disk Witness in Quorum ga Diagnostics m F att Configuration E ca Quorum Online warm ipe3 3 Open a Command Prompt and enter the following command cluster group Cluster Group move node_hostname This command moves the cluster group including the Quorum disk to the node you specify To
64. e Server for the Cluster Service Initialize Disk xi You must initialize a disk before Logical Disk Manager can access it Select disks Use the following partition style for the selected disks MBR Master Boot Record GPT GUID Partition Table Note The GPT partition style is not recognized by all previous versions of Windows It is recommended for disks larger than 2TB or disks used on Itanium based computers Cancel _ Select Disk 1 and Disk 3 and make sure that MBR is selected Click OK 5 Use the New Simple Volume wizard to configure the disks as partitions Right click each disk select New Simple Volume and follow the instructions in the wizard Disk 1 Basic 10 00 GB 10 00 GB Online Unallocated New Simple Volume New Spanned Volume Ce M 5t Ped Vole ER New Mirrored Volume 10 00 GB 10 00 GB New RAID 5 Volume Not Initialized Unallocated Properties LaDisk 3 ee Basic 814 16 GB 814 16 GB Online Unallocated Use the following names and drive letters Infortrend Disk Name and Drive Letter S12F R1440 Disk 1 Quorum Q 10 GB Disk 3 Databases S 814 GB or larger Do not assign a name or drive letter to Disk 2 47 Preparing the Server for the Cluster Service If you need to change the drive letter after running the wizard right click the drive letter in the right column and select Change Drive Letter or Path If yo
65. each node individually without affecting the operation of the cluster 2 Click Next The Specify Default Database Folder dialog box opens 79 Installing the Interplay Engine on the First Node Specifying the Default Database Folder In this dialog box specify the folder where the database data is stored Specify Default Database Folder ywip Please select the default Avid Interplay database folder The default database folder will be shared throughout the network If you want to set the default folder on another computer enter the path to the share manually fie WFILESERVER network_share ATTENTION you are installing in cluster mode If the directory is specified using a drive letter it must be on a shared drive that is mounted under the same drive letter on the other machine m Default Database Folder S Workgraup_Databases Browse Avid Interplay lt Back Cancel To specify the default database folder 1 Type S Workgroup_Databases Make sure the path specifies the shared drive S This folder must reside on the shared drive that is owned by the resource group of the server You must use this shared drive resource so that it can be monitored and managed by the cluster service The drive must be assigned to the physical drive resource that is mounted under the same drive letter on the other machine 2 Click Next The Specify Share Name dialog box opens 80 Install
66. ealthy Primary Partition 73 Installing the Interplay Engine on the First Node If you attempt to change the drive letter you receive a warning tells you that some programs that rely on drive letters might not run correctly and asks if you want to continue Click Yes Starting the Installation and Accepting the License Agreement To start the installation 1 2 Ws Make sure the second node is shut down Insert the Avid Interplay Servers installation flash drive A start screen opens Select the following from the Interplay Server Installer Main Menu Servers gt Avid Interplay Engine gt Avid Interplay Engine The Welcome dialog box opens Close all Windows programs before proceeding with the installation Information about the installation of Apache is provided in the Welcome dialog box Read the text and then click Next The License Agreement dialog box opens Read the license agreement information and then accept the license agreement by selecting T accept the agreement Click Next The Specify Installation Type dialog box opens Continue the installation as described in the next topic If you receive a message that the Avid Workgroup Name resource was not found you need to check the registry See Changing the Resource Name of the Avid Workgroup Server on page 98 Installing the Interplay Engine Using Custom Mode The first time you install the Interplay Engine on a cluster syste
67. eates the cluster At the end of the process a Summary window opens and displays information about the cluster WP create Cluster Wizard x Summary You have successfully completed the Create Cluster Wizard Create Cluster Confirmation Creating New Chistes Cluster muc ytlasclu2 Node muc srvasLyt ytl local C Node muc srvas2vtl vtllocal Quorum Node and Disk Majority Cluster Disk 1 X To view the report created by the wizard cick View Report To close thie wizard cick Finish View Report You can click View Report to see a log of the entire cluster creation 13 Click Finish Now when you open the Failover Cluster Manager in the Server Manager the cluster you created and information about its components are displayed including the networks available to the cluster cluster networks The following illustration shows components of a dual connected cluster Cluster Network 1 and Cluster Network 2 are external networks connected to VLAN 10 and VLAN 20 on Avid ISIS and Cluster Network 3 is a private internal network for the heartbeat 56 Configuring the Cluster Service Fie Action View Help gt Alm Ble ia Server Manager MUC SRYASIYTL amp JP Roks a Features es Failover Cluster Manager 3 EK muc vtlasdu2 VTL local E FS Services and applications Networks Recent Cluster Events luste Network 1 F Custe Network 2 E i Nodes Enabled J mue srvastvtl F Chister
68. eature Remove Features Wizard aa Select Features Features NET Framework 3 5 1 Features a Background Intelligent Transfer Service BITS BitLocker Drive Encryption Not Installed BranchCache Not Installed Connection Manager Administration Kit Not Installed Desktop Experience Not Installed irectAccess Management Console Not Installed ering Group Policy Management Not Installed Ink and Handwriting Services Not Installed Internet Printing Client Not Installed Internet Storage Name Server Not Installed LPR Port Monitor Not Installed Message Queuing Not Installed Multipath 1 0 Not Installed Network Load Balancing Not Installed Peer Name Resolution Protocol Not Installed Quality Windows Audio Video Experience Not Installed Remote Assistance Not Installed a o E Oo Oo o E aO E Oo a o Oo oO E o o Previous Wext gt Remove 4 Clear the check box for Failover Clustering A message asks if you have removed this server from a cluster Select Yes 5 In the Select Features screen click Next The Confirm Removal Selections screen opens 116 Removing the Failover Clustering Feature Remove Features Wizard an Confirm Removal Selections Confirmation This server might need to be restarted after the removal completes Failover Clustering 6 Click Remove 7 Follow the system prompts to restart the server The following illustration s
69. eed to have a globally unique identifier GUID you must first delete the installed network adapters and then add them to create new GUIDs A This procedure removes all settings for the network adapters such as the IP address name and bindings Creating New GUIDs for the AS3000 Network Adapters To create a new GUIDs 1 Disconnect the ISIS client from the System Director and disconnect the network cables from all network ports at the back of the AS3000 2 Use the registry editor to delete registry keys as follows f Click Start type regedit exe and press Enter Navigate to the key HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Network Select the REG_BINARY value config and press Delete Navigate to the key HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet services Tcpip Parameters In the subkey Adapters search for the following subkeys select them and delete them 00514BC2 D21A 4F92 A04A AC629A4E021A 21E0E360 9BF6 4840 9ED5 1648E15CA8DC 2EEFFD4F 57E4 47D8 AA1 A E96888272635 5E8B8896 03FA 4E95 9CA4 05A995EF5S59A In the subkey Interfaces search for the same subkeys select them and delete them 3 Click Start type Device Manager and press Enter 4 Expand the Network Adapters category 5 Right click on each network adapter and select Uninstall a Device Manager Fie Action View Help e9 mHOlH TEH IS iS g Muc srvasivtl
70. el on the right side select More Actions gt Shutdown Cluster muc vtlasclu1 TL local E7 Configure a Service or Application Validate This Cluster a View Validation Report CS Enable Cluster Shared Volumes J Add Node Close Connection More Actions Configure Cluster Quorum Settings View Migrate services and applications iQ Refresh Shut down Cluster E Properties Destroy Cluster B Help 99 Installing the Interplay Engine on the Second Node 5 Do the following to bring the cluster on line a Inthe Server Manager tree left panel select the cluster b In the context menu or the Actions panel on the right side select Start Cluster Service Installing the Interplay Engine on the Second Node To install the Interplay Engine on the second node 1 Leave the first machine running so that it maintains ownership of the resource group and start the second node A Do not attempt to move the resource group over to the second node or similarly do not shut down the first node while the second is up before the installation is completed on the second node A Do not attempt to initiate a failover before installation is completed on the second node and you create an Interplay database See Testing the Complete Installation on page 103 2 Perform the installation procedure for the second node as described in Installing the Interplay Engine on the First
71. elligent Content Management Intelligent Digital Actor Technology IntelliRender Intelli Sat Intelli sat Broadcasting Recording Manager InterFX Interplay inTONE Intraframe iS Expander iS9 iS18 iS23 iS36 ISIS lsoSync LaunchPad LeaderPlus LFX Lightning Link amp Sync ListSync LKT 200 Lo Fi MachineControl Magic Mask Make Anything Hollywood make manage move media Marquee MassivePack Massive Pack Pro Maxim Mbox Media Composer MediaFlow MediaLog MediaMix Media Reader Media Recorder MEDIArray MediaServer MediaShare MetaFuze MetaSync MIDI I O Mix Rack Moviestar MultiShell NaturalMatch NewsCutter NewsView NewsVision Nitris NL3D NLP NSDOS NSWIN OMF OMF Interchange OMM OnDVD Open Media Framework Open Media Management Painterly Effects Palladium Personal Q PET Podcast Factory PowerSwap PRE ProControl ProEncode Profiler Pro Tools Pro Tools HD Pro Tools LE Pro Tools M Powered Pro Transfer QuickPunch QuietDrive Realtime Motion Synthesis Recti Fi Reel Tape Delay Reel Tape Flanger Reel Tape Saturation Reprise Res Rocket Surfer Reso RetroLoop Reverb One ReVibe Revolution rS9 rS18 RTAS Salesview Sci Fi Scorch ScriptSync SecureProductionEnvironment Serv GT Serv LT Shape to Shape ShuttleCase Sibelius SimulPlay SimulRecord Slightly Rude Compressor Smack Soft SampleCell Soft Clip Limiter SoundReplacer SPACE SPACEShift SpectraGraph SpectraMatte SteadyGlide Streamfactory
72. entire Avid Workgroup Server resource group You should click Yes only when uninstalling from the second node When you are asked if you want to restart the system click Yes At the end of the uninstallation process if you are asked to restart the system click Yes After the uninstallation on the inactive node is complete wait until the last restart is done Then open the Failover Cluster Manager on the active node and make sure the inactive node is shown as online Start the uninstallation on the active node the node that owns the Avid Workgroup Resource Group When you are asked if you want to delete the cluster resources click Yes A confirmation dialog box opens 108 Uninstalling the Interplay Engine on a Clustered System Please Confirm x You are about to move offline and delete all d cluster resources of the Avid Workgroup Server resource group Users will no longer be able to connect to the virtual server 11 Click Yes 12 When you are asked if you want to restart the system click Yes 13 At the end of the uninstallation process if you are asked to restart the system click Yes 14 After the uninstallation is complete but before you reinstall the Interplay Engine rename the folder S Workgroup_Data for example S Workgroup_Data_Old so that it will be preserved during the reinstallation process In case of a problem with the new installation you can check the old configuration informat
73. er You can more easily manage the cluster by renaming the networks that are listed under the Failover Cluster Manager To rename the networks 1 Right click My Computer and select Manage The Server Manager window opens 2 In the Server Manager list open Features gt Failover Cluster Manager gt cluster_name 3 Click Networks 4 In the Networks window right click Cluster Network 1 and select Properties Networks Intema Inteinal F Chiste Netw F Custe Netw The Properties dialog box opens 5 Click in the Name text box and type a meaningful name for example a name that matches the name you used in the TCP IP properties For a redundant switch configuration use Public For a dual connected configuration use Left as shown in the following example For this network keep the option Allow clients to connect through this network 58 Networks Rd Cluster Network 1 Properties Fa General P Cluster Network 1 Name C Alow cluster network communication on this network Allow clents to connect though this network C De not alow cluster network communication on this network Status Up Subnet 10123101 0 24 Lig J Concel Arr 6 Click OK Configuring the Cluster Service 7 If you are configuring a dual connected cluster configuration rename Cluster Network 2 using Right For this network keep the option Allow clients to connect through this network 8 Ren
74. er window type a name for the cluster then click in the Address text box and enter an IP address 54 Configuring the Cluster Service PP create Cluster wizard x 3a Access Point for Administering the Cluster Before You Begin Type the name you want to use when administering the cluster Select Servers ER mcmes M One or more IPv4 addresses could not be configured automatically For each network to be used make sure the network is selected and then hype an address Confirmatio Networks Addes 0 O R Networks ane Vv 10 129 101 0 24 10 29 Summaty If you are configuring a dual connected cluster you need to add a second IP address after renaming and deleting cluster disks This procedure is described in Adding a Second IP Address to the Cluster on page 62 Click Next A message informs you that the system is validating settings At the end of the process the Confirmation window opens am Confirmation Before You Begin You are ready to create a cluster EN CEECEE The wizard wil create your cluster with the following settings Waldation Warming Ken Ponti Cluster mucrvtlasclu2 Admnisesng Hick Node mucesrvasivtl vtllocal Cluster Node muc srvas2vtl villocal IP Address 10 129 101 47 Confirmation Creating New Cluster Summary 55 Configuring the Cluster Service 12 Review the information and if it is correct click Next The Create Cluster Wizard cr
75. ersity of California All rights reserved 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 Copyright C 1989 1991 by Jef Poskanzer 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 Copyright 1995 Trinity College Computing Center Written by David Chappell 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 noti
76. es Preferred DNS server i J validate settings upon exit Aen Type the private IP address for the node you are configuring Alternate DNS server 6 On the General tab of the Internet Protocol TCP IP Properties dialog box a Select Use the following IP address b IP address type the IP address for the Private network connection for the node you are configuring See List of IP Addresses and Network Names on page 29 When performing this procedure on the second node in the cluster make sure you assign a static private IP address unique to that node In this example node I uses 192 168 100 1 and node 2 uses 192 168 100 2 c Subnet mask type the subnet mask address Make sure you use a completely different IP address scheme from the one used for the public network d Make sure the Default gateway and Use the Following DNS server addresses text boxes are empty 7 Click Advanced The Advanced TCP IP Settings dialog box opens 41 Preparing the Server for the Cluster Service Advanced TCP IP Settings 21x IP Settings DNS WINS WINS addresses in order of use Add Edit Remove If LMHOSTS lookup is enabled it applies to all connections for which TCP IP is enabled IV Enable LMHOSTS lookup Import LMHOSTS NetBIOS setting C Default Use NetBIOS setting from the DHCP server IF static IP address is used or the
77. escribe login to the ATTO Configuration Tool Changing Default Settings for the ATTO Card on Each Node on page 33 Revisions to describe Rev 4 image including new appendix Windows Server Settings Included in Latest Image on page 112 Moved information on preparing server from Preparing the Server for the Cluster Service on page 33 to Windows Server Settings Included in Latest Image on page 112 Corrected step 1 in Starting the Installation and Accepting the License Agreement on page 74 and added cross reference in Testing the Complete Installation on page 103 Revised Testing the Cluster Installation on page 67 for additional enhancements Revised Testing the Cluster Installation on page 67 to describe command line method Revisions include the following e Requirements for Domain User Accounts on page 27 Expanded description and use of cluster installation account e Testing the Cluster Installation on page 67 Corrected to show both networks online Symbols and Conventions Symbols and Conventions Avid documentation uses the following symbols and conventions Symbol or Convention Meaning or Action A A Windows Windows only Macintosh or Macintosh only Bold font Italic font Courier Bold font Ctrl key or mouse action If You Need Help A note provides important related information reminders recommendations and strong suggestions A c
78. et up the cluster resources cannot be changed Additionally all other values must be reused so Avid strongly recommends choosing the Typical installation mode Changes to the fundamental attributes can only be achieved by uninstalling both nodes first and installing again with the new settings Make sure you follow the procedure in this order otherwise you might end up with a corrupted installation 105 Updating a Clustered Installation Rolling Upgrade To update a cluster 1 On either node determine which node is active a Right click My Computer and select Manage The Server Manager window opens b Inthe Server Manager list open Features and click Failover Cluster Manager c Inthe Summary panel check the name of the Current Owner Avid Workgroup Server Avid Workgroup Server A Summary of Avid Workgroup Server A Status Online Alerts lt none gt Preferred Owners lt none gt Current Owner muc sryas vtl Consider this the active node or the first node 2 Make sure this node is also the current host of the cluster You can check the owner of cluster by selecting the cluster in the Server Management tree and checking the Current Host Server in the Summary panel EN Server Manager MUC SRVASIVTL muc vtlasclu1 TL local J gt Roles i Features Cluster muc vtlasclu1 VTL local FEN Failover Cluster Manager See muc vtlasclut
79. f hardware failure e Failover in case of network failure Hardware Failover Process When the Microsoft cluster service is running on both systems and the server is deployed in cluster mode the Interplay Engine and its accompanying services are exposed to users as a virtual server or cluster application To clients connecting to the clustered virtual Interplay Engine appears to be the same process as connecting to a single physical machine The user or client application does not know which node is actually hosting the virtual server 14 How Server Failover Works 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 Failover Cluster Manager Because clients connect to the virtual network name and IP address which are also taken over by the failover node the impact on the availability of the server is minimal Network Failover Process Avid supports a configuration that uses connections to two public networks VLAN 10 and VLAN 20 on a single switch The cluster monitors both networks If one fails the cluster application stays on line and can still be reached over the other network If the switch fails both networks monitored by the cluster will fail simultaneously and the cluster application will go offline For a high degree of protection against network
80. g for Windows Server 2008 see Clustering Technology and Terminology on page 25 e Disk configuration format partition naming e Network configuration For information about Avid Networks and Interplay Production search for document 244197 Network Requirements for ISIS and Interplay Production on the Customer Support Knowledge Base at www avid com onlinesupport Installing the Failover Hardware Components A failover cluster system includes the following components e Two Interplay Engine nodes or two Interplay Archive nodes two AS3000 servers e One Infortrendcluster shared storage RAID array Infortrend S12F R1440 The following topics provide information about installing the failover hardware components for the supported configurations e AS3000 Slot Locations on page 21 e Failover Cluster Connections Avid ISIS Redundant Switch Configuration on page 21 e Failover Cluster Connections Dual Connected Configuration on page 23 20 AS3000 Slot Locations Installing the Failover Hardware Components Each AS3000 server requires a ATTO Celerity FC 81EN Fibre Channel host adapter to connect to the Infortrend RAID array The card should be installed in the top expansion slot as shown in the following illustration Avid AS3000 Rear View Able DOO OOOoO000000000000000000000R DOO oOoSOAooeooonRooooooo0o0o000
81. gE W ponooa oooooo oooooo 1 I 1 Fibre Channel 1 to Infortrend I I 1 I Interplay Engine Cluster Node 2 AS3000 Back Panel DOOOOO0000000000000000000000002 DOOOAAAAASooooRRS88oooo00oo0008 20000000000 poort as OO0099899oo000 lataa a am a a a a ataa 0000000000000 a 00000000 2 0 2 ea O O O 0 0 0 0 0 Ethernet to ISIS left subnet Ethernet to ISIS right subnet LEGEND 1 GB Ethernet connection Fibre Channel connection 24 Clustering Technology and Terminology Clustering Technology and Terminology Clustering is not always straightforward so it is important that you get familiar with the technology and terminology of failover clusters before you start A good source of information is the Windows Server 2008 R2 Failover Clustering resource site www microsoft com windowsserver2008 en us failover clustering technical aspx The following link describes the role of the quorum in a cluster http technet microsoft com en us library cc770620 WS 10 aspx Here is a brief summary of the major concepts and terms Nodes Individual computers in a cluster configuration Cluster service A Windows service that provides the cluster functionality When this service is stopped the node a
82. he cluster installation and cluster administration accounts These accounts have different functions and require different privileges List of IP Addresses and Network Names You need to reserve IP host names and static IP addresses on the in network DNS server before you begin the installation process The number of IP addresses you need depends on your configuration e An Avid ISIS environment with a redundant switch configuration requires 4 public IP addresses and 2 private IP addresses e An Avid ISIS environment with a dual connected configuration requires 8 public IP addresses and 2 private IP addresses 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 If your Active Directory domain or DNS includes more than one cluster to avoid conflicts you need to make sure the cluster names MSDTC names and IP addresses are different for each cluster All names must be valid and unique network host names 29 Before You Begin the Server Failover Installation The following table provides a list of example names that you can use when configuring the cluster for an ISIS redundant switch configuration You can fill in the blanks with your choices to use as a reference during the configuration process IP Addresses and Node Names ISIS Redundant Switch Configuration Node or Service Cluster node 1 Cluster node 2 Microsoft cluster service
83. hows the Removal Results screen that is displayed after you restart 117 Disabling IPv6 Resume Configuration Wizard xi ic Removal Results ca Resuming Configuration E g The following roles role services or features were removed successfully Progress Results Failover Clustering Removal succeeded Print e mail or save the removal report Previous Next gt close Gancel Disabling IPv6 Disabling IPv6 completely is no longer recommended IPv6 is enabled in the latest Rev 4 image Binding network interface cards NICs to IPv6 is not recommended Switching the Server Role to Application Server A This procedure is not needed with the latest Rev 4 server image To switch the Server Role to Application Server 1 Click Control Panel gt System and Security gt System The System control panel opens 118 Switching the Server Role to Application Server Control Panel System and Security System go Control Panel System and Security System amp Search Control Panel D Fie Edit View Tools Help a Control Panel Home iew basic information about your computer a Device Manager Windows edition Windows Server 2008 R2 Standard Copyright 2009 Microsoft Corporation All rights reserved Remote settings Advanced system settings System Manufacturer Avid Processor Intel R Xeon R CPU 15518 2 13GHz 2 13 GHz 2 processors Installed memory RAM
84. ine 10 Right click the Name resource and select Properties 97 Installing the Interplay Engine on the First Node Name muc srvcluvtl2 Properties Ea General Dependencies Policies Advanced Policies ra Resource Name Avid Workgroup Name Resource type Network Name Status Online I Publish PTR records DNS Name muc srvcluvtl2 Full Name muc srvcluvtl2 VTL local IP Addresses Network IP Address a 10 129 101 0 24 10 129 101 49 am 10 129 102 0 24 10 129 102 49 Add Edit Remove NetBIOS Status OK DNS Status OK Kerberos Status OK Cancel Apply The Resource Name must be listed as Avid Workgroup Name If it is not see Changing the Resource Name of the Avid Workgroup Server on page 98 11 Leave this node running so that it maintains ownership of the resource group and proceed to Installing the Interplay Engine on the Second Node on page 100 Changing the Resource Name of the Avid Workgroup Server If you find that the resource name of the Avid Workgroup Server application is not Avid Workgroup Name as displayed in the properties for the Server Name you need to change the name in the Windows registry To change the resource name of the Avid Workgroup Server 1 On the node hosting the Avid Workgroup Server the active node open the registry editor and navigate to the key HKEY_LOCAL_MACHINE Cluster Resources If you are installing a dual connec
85. ing the Interplay Engine on the First Node Specifying the Share Name In this dialog box specify a share name to be used for the database folder Specify Share Name avir Keep the default or designate another name to the new shared directory Please do not use any wildcards or special characters Please use a at the end to hide the share in the file system wG_D atabase Share Name Avid Interplay To specify the share name 1 Accept the default share name Avid recommends you use the default share name WG_Database This name is visible on all client platforms such as Windows NT Windows 2000 and Windows XP The at the end makes the share invisible if you browse through the network with the Windows Explorer For security reasons Avid recommends using a at the end of the share name If you use the default settings the directory S Workgroup_Databases is accessible as InterplayEngine WG_Database 2 Click Next This step takes a few minutes When finished the Specify Configuration Server dialog box opens 81 Installing the Interplay Engine on the First Node Specifying the Configuration Server In this dialog box indicate whether this server is to act as a Central Configuration Server Specify Configuration Server AVi Please specify the Avid Interplay Central Configuration Server CCS The CCS is a central Avid Interplay Engine that provides cross database information
86. ion in that folder If you do not rename the Workgroup_Data the reinstallation might fail because of old configuration files within the folder Make sure to rename the folder before you reinstall the Interplay Engine 109 4 Automatic Server Failover Tips and Rules This chapter provides some important tips and rules to use when configuring the automatic server failover Don t Access the Interplay Engine Through Individual Nodes Don t access the Interplay Engine directly through the individual machines nodes of the cluster Use the virtual network name or IP address that has been assigned to the Interplay Engine resource group see List of IP Addresses and Network Names on page 29 Make Sure to Connect to the Interplay Engine Resource Group The network names and the virtual IP addresses resolve to the physical machine they are being hosted on For example it is possible to mistakenly connect to the Interplay Engine using the network name or IP address of the cluster group see List of IP Addresses and Network Names on page 29 The server is found using the alternative address also but only while it is online on the same node Therefore under no circumstances connect the clients to a network name other than what was used to set up the Interplay Engine resource group Do Not Rename Resources Do not rename resources The resource plugin the installer and the uninstaller all depend on the names of the cluster resource
87. iting clients Interplay Engine cluster node 1 er as ne aa Private network for heartbeat Infortrend RAID array Interplay Engine cluster node 2 LEGEND 1 GB Ethernet connection EUS S R Fibre Channel Connection The following table describes what happens in the dual connected configuration as a result of an outage Type of Outage Result Hardware CPU network adapter memory cable power supply fails Left ISIS VLAN VLAN10 fails Right ISIS VLAN VLAN 20 fails The cluster detects the outage and triggers failover to the remaining node The Interplay Engine is still accessible The Interplay Engine is still accessible through the right network The Interplay Engine is still accessible through the left network 18 Server Failover Requirements Server Failover Requirements You should make sure the server failover system meets the following requirements Hardware The automatic server failover system was qualified with the following hardware e Two Avid AS3000 servers functioning as nodes in a failover cluster For installation information see the Avid AS3000 Setup Guide e Two ATTO Celerity FC 81EN Fibre Channel host adapters one for each server in the cluster installed in the top PCIe slot One Infortrend S12F R1440 For more information see the Infortrend EonStor DS S12F R1440 Installation and Hardware Reference Manual A The Infortrend A16F R2431 Gen 2 is not supported
88. kgroup Server Status Offline Alerts lt none gt Preferred Owners lt none gt Current Owner muc srvas1 vtl Server Name m Name muc srvcluvtl2 Offline a IP Address 10 129 101 49 Offline a IP Address 10 129 102 49 Offline File Server m FileServer muc srvcluvtl2 Avid Offline 9 Bring the Name both IP addresses and the File Server resource online by doing one of the following Right click the resource and select Bring this resource online Select the resources and select Bring this resource online in the Actions panel The following illustration shows the resources online 96 Installing the Interplay Engine on the First Node Avid Workgroup Server Avid Workgroup Server m Summary of Avid Workgroup Server ty Status Partial Online Alerts lt none gt Preferred Owners lt none gt Current Owner muc sryas1 vtl Server Name E o Name muc srvcluvtl2 Online a IP Address 10 129 101 49 Online Peg IP Address 10 129 102 49 Onine File Server FileS erver muc srvcluvtl2 4vid Workgroup Disk Online Disk Drives a Avid Workgroup Disk Online Volume File System NTFS Other Resources s Avid Workgroup Engine Monitor Offline ts Avid Workgroup Preview Server Offline ts Avid Workgroup Server Browser Offline ts Avid Workgroup TCP COM Bridge Offline P Avid Workgroup SS Service Offl
89. l Apply 6 Click Apply then click OK to close the window 7 Click OK to close the System properties window then close the System window Disabling the Windows Firewall A This procedure is not needed with the latest Rev 4 server image Disabling the Windows Firewall is not required for a cluster configuration Disabling the Windows Firewall is optional depending on the policies of your site To disable the Windows Firewall 1 Open All Programs gt Administrative Tools gt Windows Firewall with Advanced Security 2 In the Actions section on the right select Properties as shown in the following illustration 120 Disabling the Windows Firewall S Windows Firewall with Advanced Security olx File Action View Help Ble Windows Firewall with Advanced 5 BUT neiane hae tienes katt sae ete my tes E Inbound Rules E5 Outbound Rules Bay Connection Security Rules Monitoring Windows Firewall with Advanced 5 a Pg Windows Firewall with Advanced Security provides network security for Windows computers e Import Policy Export Policy Overview Restore Default Policy For your security some settings are controlled by Group Policy Diagnose Repair k ae i P view gt Domain Profile is Active Windows Firewall is on Q Refresh Inbound connections that do not match a rule are blocked i Help Ou
90. l is off as shown in the following illustration Windows Firewall with Advanced Security on Local Computer af Windows Firewall with Advanced Security provides network security for Windows computers Overview Domain Profile is Active Windows Firewall is off Private Profile x Windows Firewall is off Public Profile is Active x Windows Firewall is off gt Windows Firewall Properties For your security some settings are controlled by Group Policy 122 ABCDEFGHIJKLMNOPQRSTUVWXYZ Index A Active Directory domain adding cluster servers 49 Antivirus software running on a failover cluster 19 Apache web server on failover cluster 70 AS3000 server slot locations failover cluster 21 ATTO card setting link speed 33 Avid online support 10 training services 12 Avid ISIS failover cluster configurations 16 failover cluster connections for dual connected configuration 23 failover cluster connections for redundant switch configuration 21 Avid Unity MediaNetwork failover cluster configuration 16 Binding order networks configuring 43 C Central Configuration Server CCS changing for failover cluster 110 112 specifying for failover cluster 82 Cluster overview 13 See also Failover cluster Cluster disks renaming 60 Cluster group partition 45 Cluster installation updating 105 Cluster installation and administration account described 27 Cluster networks renaming in Failover Cluster Manager 58
91. l2 Avid Offline 3 Right click the Name resource and select Properties The Properties dialog box opens 92 Installing the Interplay Engine on the First Node Name muc sry cluvtl2 Properties xi General Dependencies Policies Advanced Policies 7d Resource Name Avid Workgroup Name Resource type Network Name Status Online J Publish PTR records DNS Name Imuc srvoluvtl2 Full Name muc srvcluvtl2 VTL local IP Addresses Network IP Address a 10 129 101 0 24 10 129 101 49 Add Edit Remove NetBIOS Status OK DNS Status OK Kerberos Status OK Cancel Apply Note that the Resource Name is listed as Avid Workgroup Name Make sure to check the Resource Name after adding the second IP address and bringing the resources on line in step 9 If the Kerberos Status is offline you can continue with the procedure After bringing the server online the Kerberos Status should be OK 4 Click the Add button below the IP Addresses list The IP Address dialog box opens 93 Installing the Interplay Engine on the First Node Network 10 129 102 0 24 si IP Address Use DHGP Use Static Address 10 129 102 49 The second ISIS sub network and a static IP Address are already displayed 5 Type the second Interplay Engine service Avid ISIS IP address See List of IP Addresses and Network Names on page 29 Click OK The Properties
92. m you should use the Custom installation mode This lets you specify all the available options for the installation This is the recommended option to use The following procedures are used to perform a Custom installation of the Interplay Engine Specifying Cluster Mode During a Custom Installation on page 75 Specifying the Interplay Engine Details on page 76 Specifying the Interplay Engine Service Name on page 78 Specifying the Destination Location on page 79 Specifying the Default Database Folder on page 80 74 Installing the Interplay Engine on the First Node e Specifying the Share Name on page 81 e Specifying the Configuration Server on page 82 e Specifying the Server User on page 83 e Specifying the Server Cache on page 84 e Enabling Email Notifications on page 85 e Installing the Interplay Engine for a Custom Installation on the First Node on page 87 For information about updating the installation see Updating a Clustered Installation Rolling Upgrade on page 105 Specifying Cluster Mode During a Custom Installation To specify cluster mode 1 In the Specify Installation Type dialog box select Custom Specify Installation Type s OF 2 Click Next The Specify Cluster Mode dialog box opens 75 Installing the Interplay Engine on the First Node Specify Cluster Mode AVIP Please specify whether you want to install the server in
93. n this dialog Make sure that the password is set correctly or else you will need to uninstall the server and repeat the entire installation procedure Avid does not recommend changing the Server Execution User in cluster mode afterwards so choose carefully A When typing the domain name do not use the full DNS name such as mydomain company com because the DCOM part of the server will be unable to start You should use the NetBIOS name for example mydomain 83 Installing the Interplay Engine on the First Node 2 Click Next The Specify Preview Server Cache dialog box opens 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 Specifying the Server Cache In this dialog box specify the path for the cache folder For more information on the Preview Server cache and Preview Server configuration see Avid Workgroup Preview Server Service in the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide Specify Preview Server Cache AvI gt Please specify the Avid Interplay Engine preview server cache folder To set up the preview server cache folder on another computer select the Browse button and enter the path manually i e F
94. nager Ag muc vtlasclul TL local F 2 Services and applications i Nodes Right Up Enabled Storage F Private Up Internal a Diagnostics i Configuration E3 Storage If a network is not enabled right click the network select Properties and select Allow clients to connect through this network Right Properties x General if Name Right Allow cluster network communication on this network VV Allow clients to connect through this network Do not allow cluster network communication on this network Status Up Subnets 10 129 102 0 24 Cancel Apply 4 In the Failover Cluster Manager select the cluster application by clicking on the Cluster name in the left column of the Failover Cluster Manager 63 Configuring the Cluster Service Server Manager MUC SRYASIYTL B Roles al Features Services and applications A Nodes Storage Networks Cluster Events Diagnostics oi Configuration amp S Storage 5 In the Actions panel right column select Properties in the Name section muc vticlu04 TL local Ey Configure a Service or Application F Validate This Cluster 28 View Validation Report Q Enable Cluster Shared Volumes J Add Node Close Connection More Actions View IG Refresh El Properties Help Name muc vtlclu04 fa Bring this urce online Fa Take this
95. nce it is very easy to forget the implications of the registry replication Remember that the registry is restored by the resource monitor before the process is put online thereby wiping out any changes that you made while the resource the server was offline Only changes that take place while the resource is online are accepted Do Not Remove the Dependencies of the Affiliated Services The TCP COM Bridge the Preview Server and the Server Browser services must be in the same resource group and assigned to depend on the server Removing these dependencies might speed up some operations but prohibit automatic failure recovery in some scenarios Consider Disabling Failover When Experimenting If you are performing changes that could make the Avid Interplay Engine fail consider disabling failover The default behavior is to restart the server twice threshold 3 and then initiate the failover with the entire procedure repeating several times before final failure This can take quite a while Changing the CCS If you specify the wrong Central Configuration Server CCS you can change the setting later on the server machine in the Windows Registry under 32 bit OS HKEY_LOCAL_MACHINE Software Avid Technology Workgroup DatabaseServer 64 bit HKEY_LOCAL_MACHINE Software Wow6432Node Avid Technology Workgroup DatabaseServer The string value CMS specifies the server Make sure to set the CMS to a valid entry while the Interplay Engine is
96. nd files for the database The Interplay database is created Testing the Complete Installation After you complete all the previously described steps you are now ready to test the installation Make yourself familiar with the Failover Cluster Manager and review the different failover related settings If you want to test the Microsoft cluster failover process again see Testing the Cluster Installation on page 67 103 Installing a Permanent License To test the complete installation 1 Bring the Interplay Engine online as described in Bringing the Interplay Engine Online on page 101 2 Make sure you created a database see Creating an Interplay Database on page 103 You can use the default license for testing Then install the permanent licenses as described in Installing a Permanent License on page 104 3 Start Interplay Access and add some files to the database 4 Start the second node if it is not already running 5 Initiate a failover by right clicking Avid Workgroup Server and moving it to another node by selecting Move this server or application to another node After the move is complete all resources should remain online and the target node should be the current owner You can also simulate a failure by right clicking a resource and selecting More Actions gt Simulate failure of this resource A failure of a resource does not necessarily initiate failover of the complete Avid
97. ne service IP address of the resource group For a list of example names see List of IP Addresses and Network Names on page 29 Subnet Mask the subnet mask on the local network Public Network the name of the public network connection For a redundant switch ISIS configuration type Public or whatever name you assigned in Renaming the Local Area Network Interface on Each Node on page 36 Fora dual connection ISIS configuration type Left subnet or whatever name you assigned in Renaming the Cluster Networks in the Failover Cluster Manager on page 58 For a dual connection configuration you set the other public network connection after the installation See Checking the Status of the Resource Group on page 89 To check the public network connection on the first node open the Networks view in the Failover Cluster Manager and look up the name there Shared Drive the letter for the shared drive that holds the database Use S for the shared drive letter You need to make sure this drive is online See Bringing the Shared Database Drive Online on page 72 Cluster Service Account User and Password Server Execution User the domain account that is used to run the cluster See Before You Begin the Server Failover Installation on page 27 71 Installing the Interplay Engine on the First Node Shut down the second node when installing Interplay Engine for the first time When installing the Interplay
98. network cables and reboot the host 114 Removing the Web Server IIS Role Removing the Web Server IIS Role A This procedure is not needed with the latest Rev 4 server image To remove the Web Server IIS role 1 2 3 Click Start gt All Programs gt Administrative Tools gt Server Manager Click Roles on the left side of the window Click Remove Roles and click Server Roles The Remove Server Roles dialog box opens Uncheck Web Server IIS A dialog box opens and asks if you want to remove the dependent features Click Remove Dependent Features Click Next then click Remove Follow the system prompts to remove the role After you click the Close command the server restarts and displays a confirmation window that reports the successful removal Removing the Failover Clustering Feature A This procedure is not needed with the latest Rev 4 server image You need to remove this feature because it includes settings that do not apply to the Interplay Engine failover cluster You add this feature and configure it later in the cluster creation process To remove the Failover Clustering feature 1 2 3 Click Start gt All Programs gt Administrative Tools gt Server Manager Click Features on the left side of the window Click Remove Features from the right side of the window The Remove Features Wizard starts and displays the Select Features screen 115 Removing the Failover Clustering F
99. ng the Cluster Service Rt Create Custer Wizard Ea aw Select Servers Before You Begin Add the names of all the servers that pou want to have in the cluster You must add at least one server Selected severs mucesrvas vil vtliocal mucsrvas2vil vtllocal u Enter server name Browse Add Flemave Confirmation Creating New Cluster Summary If you cannot add the remote node to the cluster and receive an error message Failed to connect to the service manager on lt computer name gt check the following Make sure that the time settings for both nodes are in sync Make sure that the login account is a domain account with the required privileges Make sure the Remote Registry service is enabled For more information see Before You Begin the Server Failover Installation on page 34 8 Click Next 10 The Validation Warning window opens Select Yes and click Next several times When you can select a testing option select Run All Tests The automatic cluster validation tests begin The tests can take up to twenty minutes After running these validation tests and receiving notification that the cluster is valid you are eligible for technical support from Microsoft The following tests display warnings which you can ignore Validate SCSI device Vital Product Data VPD Validate All Drivers Signed Validate Memory Dump Settings In the Access Point for Administering the Clust
100. nitored 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 a virtual server to specify groups of resources that failover together This virtual server is referred to as a cluster application in the failover cluster user interface How Server Failover Works The following diagram illustrates the components of a cluster group including sample IP addresses For a list of required IP addresses and node names see List of IP Addresses and Network Names on page 29 Cluster Group Interplay Server cluster application Resource groups Failover Cluster 11 22 33 200 11 22 33 201 Node 1 Node 2 pening Intranet 11 22 33 44 Private Network Intranet 11 22 33 45 Private 10 10 10 11 Private 10 10 10 10 FibreChannel Disk resources Disk 1 Disk 3 shared disks Quorum Database If you are already using clusters the Avid Interplay Engine will not interfere with your current setup How Server Failover Works Server failover works on two different levels e Failover in case o
101. ode and a failover would be impossible Creating the Database Share Manually If the File Server resource or the database share WG_Database is not created see Checking the Status of the Resource Group on page 89 you can create it manually by using the following procedure If you copy the commands and paste them into a Command Prompt window you must replace any line breaks with a blank space To create the database share and File Server resource manually 1 In the Failover Cluster Manager make sure that the Avid Workgroup Disk resource the S drive is online Open a Command Prompt window 3 To create the database share enter the following command net share WG_DatabaseS S Workgroup_Databases UNLIMITED GRANT users FULL GRANT Everyone FULL REMARK Avid Interplay database directory Y If the command is successful the following message is displayed WG_DatabaseS was shared successfully Enter the following command Substitute the virtual host name of the Interplay Engine service for ENGINESERVER cluster res FileServer ENGINESERVER Avid Workgroup Disk priv MyShare WG_Database str No message is displayed for a successful command Enter the following command Again substitute the virtual host name of the Interplay Engine service for ENGINESERVER cluster res Avid Workgroup Engine Monitor adddep FileServe
102. onent Services expand Computers right click My Computer and select Properties 3 Click the Default Properties tab 4 In the Default Distributed COM Communication Properties section change the Default Authentication Level from None to Connect 51 Configuring the Cluster Service C Console Root E amp Component Services I Ei com applications E E Computers E Dcom Config ae My Computer E Rumning Processes More Actions COM Applications C9 Distributed Transaction Coordinator DCOM Config Running Processes Distributed Transac iu Event Viewer Local My Computer Properties C4 Services Local My Computer S ee eee J Provide additional se nity for reference tracking 1E Avid Workgroup Engine Mo be Avid Workgroup Preview Se Onir Es Avid Workgroup Server Bro Onir F Avid Workgroup TCP COM Onir FF Avid Workgroup VSS Service Onlit 5 Click OK Creating the Cluster Service To create the cluster service 1 Make sure all storage devices are turned on 2 Log in to the operating system using the cluster installation account see Requirements for Domain User Accounts on page 27 3 On the first node right click My Computer and select Manage The Server Manager window opens 4 In the Server Manager list open Features and click Failover Cluster Manager 52 Configuring the Cluster Service 5 Click Create a Cluster Failover Cluster Manager Ha
103. online otherwise your changes to the registry won t be effective After the registry is updated stop and restart the server using the Cluster Administrator in the Administration Tools folder in Windows Specifying an incorrect CCS can prevent login See Troubleshooting Login Problems in the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide For more information see Understanding the Central Configuration Server in the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide 111 Windows Server Settings Included in Latest Image The latest image for the AS3000 Windows Server 2008 R2 Standard x64 Rev 4 October 17 2012 includes system settings that required manual changes in previous versions of the image This appendix lists those settings for reference e Creating New GUIDs for the AS3000 Network Adapters on page 112 e Removing the Web Server IIS Role on page 115 e Removing the Failover Clustering Feature on page 115 e Disabling IPv6 on page 118 e Switching the Server Role to Application Server on page 118 e Disabling the Windows Firewall on page 120 You need to change these settings on each node of the cluster Changes must be made through an Administrator account Creating New GUIDs for the AS3000 Network Adapters A This procedure is not needed with the latest Rev 4 server image Because all network adapters in a cluster n
104. oup Server resource has been successfully set up al Press the Finish button to exit this installation Avid Interplay The Windows Firewall is turned off by the server image see Windows Server Settings Included in Latest Image on page 112 If the Firewall is turned on you get messages that the Windows Firewall has blocked nxnserver exe the Interplay Engine and the Apache server from public networks Windows Security Alert xi Name ke Publisher Avid Technology Path C program files x86 avid avid interplay engine server nxnserver exe Allow Avid Workgroup to communicate on these networks J Public networks such as those in airports and coffee shops not recommended because these networks often have little or no security What are the ri f allowyit rogram through a firewall Allow access Cancel If your customer wants to allow communication on public networks click Allow access and select the check box for Public networks such as those in airports and coffee shops 88 Installing the Interplay Engine on the First Node 3 Do one of the following gt Click Finish gt Analyze and resolve any issues or failures reported 4 Click OK if prompted for a restart the system The installation procedure requires the machine to restart up to twice For this reason it is very important that the other node is shut down otherwise the current node loses ownership of the
105. pdate the installation on the first node Select Typical mode so that all values are reused During the installation the installer displays a dialog box that tells you that the engine will be taken offline now in order to update cluster resources Click OK and the installer will take the Engine offline and will update the cluster resources The installer displays a dialog box that asks you to move the Avid Workgroup Server to the second node Move the application then click OK in the installation dialog box to continue Restart as requested and continue with Part 2 of the installation The installer will ask you to restart again after Part 2 After you move the application bring the Interplay Engine online by right clicking the Avid Workgroup Server and selecting Bring this server or application online You might want to test the final result of the update by moving the server back to the first node The Interplay Administrator can be used to display the version of the server After completing the above steps your entire clustered installation is updated to the new version Should you encounter any complications or face a specialized situation contact Avid Support as instructed in If You Need Help on page 10 Uninstalling the Interplay Engine on a Clustered System To uninstall the Avid Interplay Engine use the Avid Interplay Engine uninstaller first on the inactive node then on the active node A The unin
106. phics Inc for the use of their TIFF library Copyright 1988 1997 Sam Leffler Copyright 1991 1997 Silicon Graphics Inc 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 Copyright c 1989 The Regents of the Univ
107. ppears offline to other cluster nodes 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 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 and that are always brought online on the same node 25 Creating a Microsoft Failover Cluster This chapter describes the processes for creating a Microsoft failover cluster for 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 e Server Failover Installation Overview e Before You Begin the Server Failover Installation e Preparing the Server for the Cluster Service e Configuring the Cluster Service Instructions for installing the Interplay Engine are provided in Installing the Interplay Engine for a Failover Cluster on page 70 Server Failover Installation Overview Installation and configuration of the automatic server failover consists of the following major tasks e Make sure that the network is correctly set up and that you have reserved IP
108. r ENGINESERVER Avid Workgroup Disk If the command is successful the following message is displayed Making resource Avid Workgroup Engine Monitor depend on resource FileServer ENGINESERVER Avid Workgroup Disk Make sure the File Server resource and the database share WG_Database are listed in the Failover Cluster Manager see Checking the Status of the Resource Group on page 89 91 Installing the Interplay Engine on the First Node Adding a Second IP Address Dual Connected Configuration If you are setting up an Avid ISIS dual connected configuration you need use the Failover Cluster Manager to add a second IP address To add a second IP address 1 In the Failover Cluster Manager select Avid Workgroup Server 2 Bring the Name IP Address and File Server resources offline by doing one of the following Right click the resource and select Take this resource offline Select all resources and select Take this resource offline in the Actions panel of the Server Manager window The following illustration shows the resources offline Avid Workgroup Server Fa Summary of Avid Workgroup Server Status Offline Alerts lt none gt Preferred Owners lt none gt Current Owner muc srvas1 vtl Server Name Bey Name muc srvcluvtl2 Offline a IP Address 10 129 101 49 Offline File Server ms FileServer muc srvcluvt
109. r failover cluster 83 share name for failover cluster 81 specify engine name 78 specifying server cache 84 uninstalling 107 Interplay Portal viewing 1 IP addresses failover cluster private network adapter 39 public network adapter 44 required 29 IPv6 disabling 118 L License requirements failover cluster system 19 Licenses importing 104 permanent 104 N Network connections naming for failover cluster 36 Network interface renaming LAN for failover cluster 36 Network names examples for failover cluster 29 Node defined 25 name examples 29 O Online resource defined 25 Online support 10 P Permanent license 104 Port for Apache web server 70 124 ABCDEFGHIJKLMNOPQRSTUVWXYZ Index Private network adapter configuring 39 Public Network for failover cluster 76 Public network adapter configuring 44 Q Quorum disk configuring 52 Quorum resource defined 25 R RAID array configuring for failover cluster 45 Redundant switch cluster configuration 16 Registry editing while offline 110 112 Resource group connecting to 110 112 defined 25 services 110 112 Resources defined 25 renaming 110 112 Rolling upgrade failover cluster 105 S Server cache Interplay Engine cluster installation 84 Server Execution User changing 110 112 described 27 specifying for failover cluster 83 Server Failover overview 13 See also Failover cluster Server Role switching to Application
110. rame Size 2048 X Device Discovery noe ww Connection Mode PTP Preferred Data Rate facbisce o Interrupt Coalesce Low x Port Down Retry Count s Link Down Timeout 0 Spinup Delay 30 4 Load Save Commit Restore Defaults Status ATTO NYRAM settings loaded 6 Change the following settings if necessary Boot driver Enabled Execution Throttle 32 Device Discovery Node WWN Data Rate 4 Gb sec Interrupt Coalesce Low Spinup Delay 30 You can keep the default values for the other settings 7 Click Commit 8 Reboot the system 9 Open the Configuration tool again and verify the new settings 35 Preparing the Server for the Cluster Service 10 On the other node repeat steps through 6 Changing Windows Server Settings on Each Node The latest image for the AS3000 Windows Server 2008 R2 Standard x64 Rev 4 October 17 2012 includes system settings that previously required manual changes For information about these settings see Windows Server Settings Included in Latest Image on page 112 Disabling IPv6 completely is no longer recommended IP v6 is enabled in the Rev 4 image Binding network interface cards NICs to IPv6 is not recommended At the first boot after installing the Rev 4 image unique GUIDs are assigned to the network adapters used by the failover cluster The registry might show the same GUID on different ser
111. ration e A cluster in an Avid ISIS environment that is integrated into the intranet through two public networks VLAN 10 and VLAN 20 in Zone 1 This dual connected configuration protects against hardware outages and network outages If one network fails the cluster application stays on line and can be reached over the other network Redundant Switch Configuration The following diagram illustrates the failover cluster architecture for an Avid ISIS environment that uses two layer 3 switches These switches are configured for failover protection through either HSRP Hot Standby Router Protocol or VRRP Virtual Router Redundancy Protocol The cluster nodes are connected to two subnets VLAN 30 each on a different switch If one of the VLAN 30 networks fails the virtual server remains online through the other VLAN 30 network and switch This guide does not describe how to configure redundant switches for an Avid ISIS media network Configuration information is included in the ISIS Qualified Switch Reference Guide which is available for download from the Avid Customer Support Knowledge Base at www avid com onlinesupport 16 Server Failover Configurations Two Node Cluster in an Avid ISIS Environment Redundant Switch Configuration Avid network switch 1 running VRRP or HSRP Interplay editing clients Avid network switch 2 running VRRP or HSRP i VLAN 30 N VLAN 30 Interplay Engine cluster node 1 Bio ee Priva
112. red as a service if no other web server for example IIS is serving the port 80 or 443 Stop and disable or uninstall any other http services before you start the installation of the server You must perform this procedure on both nodes No action should be required because the only web server installed at this point is the ITS and it should already be disabled in the server image see Windows Server Settings Included in Latest Image on page 112 Installing the Interplay Engine on the First Node Installing the Interplay Engine on the First Node The following sections provide procedures for installing the Interplay Engine on the first node For a list of example entries see List of IP Addresses and Network Names on page 29 Preparation for Installing on the First Node on page 71 Starting the Installation and Accepting the License Agreement on page 74 Installing the Interplay Engine Using Custom Mode on page 74 Checking the Status of the Resource Group on page 89 Creating the Database Share Manually on page 91 Adding a Second IP Address Dual Connected Configuration on page 92 A Shut down the second node while installing Interplay Engine for the first time Preparation for Installing on the First Node You are ready to start installing the Interplay Engine on the first node During setup you must enter the following cluster related information Virtual IP Address the Interplay Engi
113. res and click Failover Cluster Manager 3 In the Server Manager tree right click Avid Workgroup Server and select Bring this service or application online E Server Manager Fie Action View Help esm Elen a Server Manager MUC SRVAS1VTL Avid Workgroup Server H gt Roles qi Features Avid Workgroup Server Failover Cluster Manager 7 SS muc vtlasclut VTL local les Summary of Avid Wo iE Services and applications iE 7 Nodes Bring this service or application online Ed Storage Take this service or application offline 7 33 Networks Move this service or application to another node gt Cluster Events Manage shares and storage F E Diagnostics All resources are now online as shown in the following illustration 101 After Installing the Interplay Engine a Server Manager MUC SRYASLYTL Avid Workgroup Server H gt Roles aj Features Avid Workgroup Server 5 EA Failover Cluster Manager z Y muc vtlasclut VTL local Irs Summary of Avid Workgroup Server iE Services and applications e Avid Workgroup Server 3 Nodes Status Online z muc srvas1vtl Alerts lt none gt a muc srvas2vtl Preferred Owners lt none gt scar Current Owner muc srvas vtl F Networks Cluster Events 7 a Diagnostics
114. resource offline Show the critical events for this resource sl Show Dependency Report More Actions Help The Properties dialog box opens 64 Configuring the Cluster Service Name muc vticlu04 Properties xi General Dependencies Policies Advanced Policies ra Resource Name Cluster Name Resource type Network Name Status Online I Publish PTR records DNS Name muc vticlu04 Full Name muc vtlelu04 VTL local IP Addresses IP Address 10 129 101 40 Network a 10 129 101 0 24 Add Edit Remove NetBIOS Status OK DNS Status OK Kerberos Status OK Cancel Apply In the network column if lt unknown network gt or lt No Network gt is displayed instead of the network identifier close the Server Manager window and after waiting a few seconds open it again 6 In the General tab do the following a Click Add b Type the IP address for the other ISIS network c Click OK The General tab shows the IP addresses for both ISIS networks 65 Configuring the Cluster Service Name muc vticlu04 Properties x General Dependencies Policies Advanced Policies ra Resource Name Cluster Name Resource type Network Name Status Online J Publish PTR records DNS Name muc vticlu04 Full Name muc vtlclu04 VTL local IP Addresses IP Address 10 129 101 40 10 129 102 40 Network a 10 129 101 0 24 a 10 129 102 0 24
115. ronment ISE SNMP Services SNMP Service SNMP WMI Provider Telnet Client Telnet Server Windows Process Activation Service Process Model NET Environment Configuration APIs NET Framework 3 5 1 Features NET Framework 3 5 1 WCF Activation Non HTTP Activation A list of features is displayed If a list of Features does not display and Error is displayed instead see Displaying the List of Server Features on page 51 4 Select Failover Clustering from the list of features and click Next 5 On the next screen click Install The Failover Cluster Manager installation program starts At the end of the installation a message states that the installation was successful 6 Click Close 50 Configuring the Cluster Service To check if the feature was installed open the Server Manager and open Features The Failover Cluster Manager should be displayed Ba Server Manager MUC SRYASZYTL i Roles T Failover Cluster Manager z ji Diagnostics S g Configuration E orage YE Windows Server Backup Eee Disk Management 7 Repeat this procedure on the second node Displaying the List of Server Features If a list of server features does not display and Error is displayed instead change the Default Authentication Level as described in the following procedure To display the list of server features 1 Click Start the select Administrative Tools gt Component Services 2 In the directory tree expand Comp
116. roup Disk Other Resources L Avid Workgroup Engine Monitor L5 Avid Workgroup Preview Server Ce Avid Workgroup Server Browser Online Online O Online Online Offline Offline Offline CS Avid Workgroup TCP COM Bridge Offline L5 Avid Workgroup VSS Service Shared Folders Offline a Server Manager MUC SRYAS1VTL Avid Workgroup Server Fa Summary of Avid Workgroup Server Folder Path P s SA P WG_Database S Workgroup_Databa Windows Windows The Server Name and IP Address File Server and Avid Workgroup Disk resources should be online and all other resources offline S and WG_Database should be listed in the Shared Folders section Take one of the following steps Ifthe File Server resource or the shared folder WG_Database is missing you must create it manually as described in Creating the Database Share Manually on page 91 Ifyou are setting up a redundant switch configuration leave this node running so that it maintains ownership of the resource group and proceed to Installing the Interplay Engine on the Second Node on page 100 90 Installing the Interplay Engine on the First Node Ifyou are setting up an Avid ISIS dual connected configuration proceed to Adding a Second IP Address Dual Connected Configuration on page 92 Avid does not recommend starting the server at this stage because it is not installed on the other n
117. s These are assigned by the installer and even though it is possible to modify them using the cluster administrator doing so corrupts the installation and is most likely to result in the server not functioning properly Do Not Install the Interplay Engine Server on a Shared Disk The Interplay Engine must be installed on the local disk of the cluster nodes and not on a shared resource This is because local changes are also necessary on both machines Also with independent installations you can later use a rolling upgrade approach upgrading each node individually without affecting the operation of the cluster The Microsoft documentation is also strongly against installing on shared disks Do Not Change the Interplay Engine Server Execution User The domain account that was entered when setting up the cluster the Cluster Service Account see Before You Begin the Server Failover Installation on page 27 also has to be the Server Execution User of the Interplay Engine Given that you cannot easily change the cluster user the Interplay Engine execution user has to stay fixed as well For more information see Troubleshooting the Server Execution User Account in the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide Do Not Edit the Registry While the Server is Offline If you edit the registry while the server is offline you will lose your changes This is something that most likely will happen to you si
118. stall mechanism of the cluster resources only functions properly if the names of the resources or the resource groups are not changed Never change these names 107 Uninstalling the Interplay Engine on a Clustered System To uninstall the Interplay Engine 1 If you plan to reinstall the Interplay Engine and reuse the existing database create a complete backup of the AvidWG database and the _InternalData database in S Workgroup_Databases For information about creating a backup see Creating and Restoring Database Backups in the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide Dual connected configuration only Remove the second network address within the Avid Workgroup Server group a Inthe Cluster Administrator right click Avid Workgroup Server b Right click Avid Workgroup Address 2 and select Remove 3 Make sure that both nodes are running before you start the uninstaller 10 On the inactive node the node that does not own the Avid Workgroup Server resource group start the uninstaller by selecting Programs gt Avid gt Avid Interplay Engine gt Uninstall Avid Interplay Engine When you are asked if you want to delete the cluster resources click No Cluster Resource Uninstall E x 9 The uninstaller has detected that there are tf cluster resources associated with the server Do you want to delete these Selecting Yes will move the resources offline and delete the
119. stics m g Configuration Disk Management hele Badle ar an D Simple Basic NTFS 905 C Simple Basic NTFS CaQuorum Q Simple Basic NTFS Healthy Active Recovery Partition Healthy Primary Partition Healthy Boot Page File Crash Dump Primary Partition 80 00 GB Healthy Primary Partition 10 00 GB No No No No 10 00 E 841 51 GB 835 54GB 99 53 84 GB 10 006B 9 91 GB 841 51 GB NTFS Healthy Primary Partition E S Storage Ww Windows Server Backup Disk Management yl Os C DATA D a 931 51 GB 10 00 GB 80 00 GB NTFS Online Healthy Active Recovery Part Healthy Boot Page File Crash Dump Basic Quorum Q 10 00 GB 10 00 GB NTFS Reserved Healthy Primary Partition Disk 2 Unknown 10 00 GB 10 00 GB Offline i Unallocated Help Disk 3 Basic 814 16 GB 814 16 GB Offline i Help If Disk 3 is online you can skip the following steps 3 Right click Disk 3 in the left column and select Online Disk 3 E Basic 814 16 GB Offline i Online Help Properties Help 4 Make sure the drive letter is correct S and the drive is named Databases If not you can change it here Right click the disk name and letter right column and select Change Drive Letter or Path LaDisk 3 SEES Basic Databases S 814 16 GB 814 16 GB NTFS Online H
120. t the Cluster service IP address For a list of examples see List of IP Addresses and Network Names on page 29 For a dual connected configuration you set the other public network connection after the installation See Adding a Second IP Address Dual Connected Configuration on page 92 Subnet Mask The subnet mask on the local network Public Network For a redundant switch ISIS configuration type Public or whatever name you assigned in Renaming the Local Area Network Interface on Each Node on page 36 For a dual connected ISIS configuration type the name of the public network on the first node for example Left or whatever name you assigned in Renaming the Cluster Networks in the Failover Cluster Manager on page 58 This must be the cluster resource name To check the name of the public network on the first node open the Networks view in the Failover Cluster Manager and look up the name there Shared Drive The letter of the shared drive that is used to store the database Use S for the shared drive letter Make sure you type the correct information here as this data cannot be changed afterwards Should you require any changes to the above values later you will need to uninstall the server on both nodes 2 Click Next The Specify Interplay Engine Name dialog box opens 77 Installing the Interplay Engine on the First Node Specifying the Interplay Engine Service Name In this dialog box type
121. tbound connections that do not match a rule are allowed Private Profile Windows Firewall is on 8 Inbound connections that do not match a rule are blocked Outbound connections that do not match a tule are allowed Public Profile is Active Windows Firewall is on 98 Inbound connections that do not match a rule are blocked v Outbound connections that do not match a rule are allowed 6 Windows Firewall Properties 3 Set the Firewall state to Off in at least the Domain and the Private Profile tabs If your site allows it also set the state to Off in the Public Profile tab The following illustration shows the Firewall state tuned off for the Domain Profile 121 Windows Firewall with Advanced Security on Local Computer Pro EG Domain Profile Private Profile Public Profile IPsec Settings For your security some settings are controlled by Group Policy Specify behavior for when a computer is connected to its corporate domain State Pd Firewall state M Inbound connections Block default z Outbound connections allow default z Protected network connections Customize Settings l apean semos mar control Windows Customize Logging lal Sprat eaa settings for Customize Learn more about these setti 4 Click OK Disabling the Windows Firewall The Overview section in the center column shows that the firewal
122. te network for heartbeat Infortrend Raid Array LEGEND 1 GB Ethernet connection SSeS RG Fibre Channel connection Interplay Engine cluster node 2 The following table describes what happens in the redundant switch configuration as a result of an outage Type of Outage Hardware CPU network adapter memory cable power supply fails Network switch 1 VLAN 30 fails Network switch 2 VLAN 30 fails Result The cluster detects the outage and triggers failover to the remaining node The Interplay Engine is still accessible External switches running VRRP HSRP detect the outage and make the gateway available as needed The Interplay Engine is still accessible External switches running VRRP HSRP detect the outage and make the gateway available as needed The Interplay Engine is still accessible 17 Server Failover Configurations Dual Connected Configuration The following diagram illustrates the failover cluster architecture for an Avid 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 one of the subnets fails the virtual server remains online through the other subnet Two Node Cluster in an Avid ISIS Environment Dual Connected Configuration Avid network switch 1 running VRRP or HSRP VLAN 10 VLAN 20 Interplay ed
123. ted cluster make sure to edit the Cluster key Do not edit other keys that include the word Cluster such as the 0 Cluster key 98 Installing the Interplay Engine on the First Node 2 Browse through the GUID named subkeys looking for the one subkey where the value Type is set to Network Name and the value Name is set to lt incorrect_name gt 3 Change the value Name to Avid Workgroup Name 4 Do the following to shut down the cluster A Make sure you have edited the registry entry before you shut down the cluster a Inthe Server Manager tree left panel select the cluster In the following example the cluster name is muc vtlasclul VTL local t Server Manager File Action View Help es Al n Gia Za Server Manager MUC SRVAS2VTL muc vtlasclu1 TL local F gt Roles a Features Cluster muc vtlasclu1 YTL local EA Failover Cluster Manager sclu1 YTL local FEY Summary of Cluster muc vtlasclu1 H Pe Fones muc vtlasclu1 has 1 applications services and 2 nodes dt a Nodes Tal Name muc vtlasclul VTL local Networks Left Private Right muc srvas1 vl 2 muc srvas2vtl Current Host Server muc srvas2vtl Subnets 3 Pv4 and 0 IPv6 Storage Quorum Configuration Node and Disk Majority Quorum eee Recent Cluster Events None in the last 24 hours b In the context menu or the Actions pan
124. the Interplay Engine server or another server For example C Interplay_Licenses Insert the USB flash drive into any USB port You can access the license file from the USB flash drive The advantage of copying the license file to a server is that you have easy access to installer files if you should ever need them in the future o N A Nn A If the USB flash drive does not automatically display a Double click the computer icon on the desktop b Double click the USB flash drive icon to open it Copy the license file nxn into the new folder you created In the Server section of the Interplay Administrator window click the Licenses icon Click the Import license button Browse for the nxn file Select the file and click Open You see information about the permanent license in the License Types area Updating a Clustered Installation Rolling Upgrade A major benefit of a clustered installation is that you can perform rolling upgrades You can keep a node in production while updating the installation on the other then move the resource over and update the second node as well For information about updating specific versions of the Interplay Engine and a cluster see the Avid Interplay ReadMe The ReadMe describes an alternative method of updating a cluster in which you lock and deactivate the database before you begin the update When updating a clustered installation the settings that were entered to s
125. the name of the Interplay Engine service Specify Interplay Engine Name AVI gt Please specify the names that are going to be associated with the Avid Interplay Engine The specified Network Name will be used to register the clustered installation in the DNS This should be a new unused name and not the name of any machine The Server Name field can be used to enter a static IP address if you use Avid Interplay Clients on MAC or Unix systems and these can not resolve the Network Name Interplay Engine Name Network Name seenaine not the MS Cluster name Server Name seenaine Avid Interplay lt Back Cancel To specify the Interplay Engine name 1 Specify the public names for the Avid Interplay Engine service by typing the following values The Network Name will be associated with the virtual IP Address that you entered in the previous Interplay Engine Details dialog box This is the Interplay Engine service name see List of IP Addresses and Network Names on page 29 It must be a new unused name and must be registered in the DNS so that clients can find the server without having to specify its address The Server Name is used by clients to identify the server If you only use Avid Interplay Clients on Windows computers you can use the Network Name as the server name If you use several platforms as client systems such as Macintosh and Linux you need to specify the static IP address th
126. ti Network Connections ou yy E Control Panel Network and Internet Network Connections s Fie Edit View Tools Advanced Help Organize Disable this network device Diagnose this connection Rename this connection view status of this connection Change settings of th Name Status Device Name 4 Local Area Connection Disabled Intel R 82567LM 4 Gigabit Network Connection g Enabled Intel R 74L Gigabit Network Connection 4 Right Unidentified network Intel R PRO 1000 PT Dual Port Server Adapter Y Left TL local Intel R PRO 1000 PT Dual Port Server Adapter 2 7 Close the Network Connections window 8 Repeat this procedure on node 2 using the same names that you used for node 1 Configuring the Private Network Adapter on Each Node Repeat this procedure on each node To configure the private network adapter for the heartbeat connection 1 On node 1 click Start gt Control Panel gt Network and Sharing Center The Network and Sharing Center window opens 2 Click Change adapter settings on the left side of the window The Network Connections window opens 3 Right click the Private network connection Heartbeat and select Properties The Private Properties dialog box opens 4 On the Networking tab click the following check box Internet Protocol Version 4 TCP IPv4 Uncheck all other components 39 Preparing the Server for the Cluster Service Private Properties Ea Networking
127. to disable the entries in Active Directory in order to build the Microsoft cluster see Requirements for Domain User Accounts on page 27 c Add reverse static entries only Forward entries are dynamically added by the failover cluster Static entries must be exempted from scavenging rules Windows Server 2003 DNS Entries Computer Account DNS Dynamic DNS Static Component in Active Directory Entry Entry Cluster node 1 node_1_name Yes No Cluster node 2 node_2_name Yes No MSDTC No No Yes Microsoft cluster service No No Yes Interplay Engine service virtual No No Yes a Entries are dynamically added to the DNS when the node logs on to Active Directory b Entries must be manually added to the DNS and must be exempted from scavenging rules 32 Preparing the Server for the Cluster Service Preparing the Server for the Cluster Service Before you configure the cluster service you need to complete the tasks in the following procedures e Changing Default Settings for the ATTO Card on Each Node on page 33 e Changing Windows Server Settings on Each Node on page 36 e Renaming the Local Area Network Interface on Each Node on page 36 e Configuring the Private Network Adapter on Each Node on page 39 e Configuring the Binding Order Networks on Each Node on page 43 e Configuring the Public Network Adapter on Each Node on page 44 e Configuring the Cluster Shared Storage RAID Disks on Each Node
128. u receive a warning tells you that some programs that rely on drive letters might not run correctly and asks if you want to continue Click Yes The following illustration shows Disk 1 and Disk 3 with the required names and drive letters for the Infortrend S12F R1440 Disk Management Graphic Fault Tol als Basic Healthy Active Recovery Partition 10 00 GB TE GB 100 No Data D Simple Basic NTFS Healthy Primary Partition 841 51 GB 639 96 GB 76 No CaDatabases 5 Simple Basic NTFS Healthy Primary Partition 814 49 GB 594 60 GB68 73 No 90s C Simple Basic NTFS Healthy Boot Page File Crash Dump Primary Partition 80 00 GB 53 46 GB 67 No CaQuorum Q Simple Basic NTFS Healthy Primary Partition 10 00GB 9 91 GB 99 No LDisk 0 Basic 931 51 GB Online Os C 80 00 GB NTFS Healthy Boot Page File Crash Dump Pr DATA D 841 51 GB NTFS Healthy Primary Partition 10 00 GB Healthy Active Recovery Partiti Quorum Q 10 00 GB NTFS Healthy Primary Partition siDisk 1 Basic 10 00 GB Reserved Disk 2 Unknown 10 00 GB 10 00 GB Offline i Unallocated Help Disk 3 Basic 814 49 GB Reserved Databases S 814 49 GB NTFS Healthy Primary Partition 6 Verify you can access the disk and that it is working by creating a file and deleting it 7 Shut down the first node and start the second node 8 On the second nod
129. um Online warm iped 5 In the Server Manager select Features gt Failover Cluster Manager gt cluster_name gt Networks The status of all networks should be Up The following illustration shows networks for a dual connected configuration Networks Recent Cluster Events qi Private Internal F Left Up Enabled a Right Up Enabled 6 Repeat the test by using the Command Prompt to move the cluster back to node 1 Configuration of the cluster service on all nodes is complete and the cluster is fully operational You can now install the Interplay Engine 69 Installing the Interplay Engine for a Failover Cluster After you set up and configure the cluster you need to install the Interplay Engine software on both nodes The following topics describe installing the Interplay Engine and other final tasks e Disabling Any Web Servers Installing the Interplay Engine on the First Node e Installing the Interplay Engine on the Second Node e Bringing the Interplay Engine Online e Testing the Complete Installation e Updating a Clustered Installation Rolling Upgrade e Uninstalling the Interplay Engine on a Clustered System The tasks in this chapter do not require the domain administrator privileges that are required when creating the Microsoft cluster see Requirements for Domain User Accounts on page 27 Disabling Any Web Servers The Interplay Engine uses an Apache web server that can only be registe
130. vers This GUID is not used and you can ignore it Renaming the Local Area Network Interface on Each Node You need to rename the LAN interface on each node to appropriately identify each network Although you can use any name for the network connections Avid suggests that you use the naming conventions provided in the table in the following procedure Avid recommends that you use the same name on both nodes Make sure the names and network connections on one node match the names and network connections on the other To rename the local area network connections 1 On node 1 click Start gt Control Panel gt Network and Sharing Center The Network and Sharing Center window opens 2 Click Change adapter settings on the left side of the window The Network Connections window opens 36 Preparing the Server for the Cluster Service ntrol Panel Network and Internet Network Connections og Jy E Control Panel Network and Internet Network Connections Fie Edit View Tools Advanced Help Organize v Name Status Device Name i Local Area Connection 4 Disabled Intel R 82567LM 4 Gigabit Network Connection 4 Local Area Connection Connected Intel R PRO 1000 PT Dual Port Server Adapter 2 U Local Area Connection Connected Intel R 82574L Gigabit Network Connection U Local Area Connection Connected Intel R PRO 1000 PT Dual Port Server Adapter The top left network connector on the AS3000 number 1 is not used an
131. you need to select or create the following user accounts in the domain that includes the cluster Server Execution User Create or select an account that is used by the Interplay Engine services listed as the Avid Workgroup Engine Monitor and the Avid Workgroup TCP COM Bridge in the list of Windows services 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 27 Before You Begin the Server Failover Installation use sqauser as an example of a Server Execution User 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 not used to start the cluster service for a Windows Server 2008 installation Windows Server 2008 uses the system account to start the cluster service The Server Execution User is used to start the Avid Workgroup Engine Monitor and the Avid Workgroup TCP COM Bridge 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 Help Cluster installation account Create or select a

Download Pdf Manuals

image

Related Search

Related Contents

Cobas Integra 400 Troubleshooting  Crestron electronic AAS-1 CD Player User Manual  FLUVO C2-rondo - Montageanleitung  GDxPRO - Amedeolucente.it  操作手順  Manual  

Copyright © All rights reserved.
Failed to retrieve file