Avid® Interplay™Engine Failover Guide m a k e m a n a g e m ove | m e d i a ™ Avid ®
Legal Notices Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting Avid's Web site at www.avid.com. The terms of that license are also available in the product in the same directory as the software.
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 1996 Daniel Dardailler.
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.
Contents Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Viewing User Documentation on the Interplay Portal . . . . . . . . . . . . . . . . . . . . . . . . 11 Accessing the Online Library . . . . . . . . . . . .
Renaming the Local Area Network Interface on Each Node . . . . . . . . . . . . . . . 33 Configuring the Private Network Adapter on Each Node . . . . . . . . . . . . . . . . . 35 Configuring the Binding Order Networks on Each Node . . . . . . . . . . . . . . . . . . 38 Configuring the Public Network Adapter on Each Node . . . . . . . . . . . . . . . . . . 40 Joining Both Servers to the Active Directory Domain . . . . . . . . . . . . . . . . . . . .
Specifying the Default Database Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Specifying the Share Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Specifying the Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Specifying the Server User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Specifying the Server Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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. n The documentation describes the features and hardware of all models.
Symbol or Convention Meaning or Action Bold font Bold font is primarily used in task instructions to identify user interface items and keyboard sequences. Italic font Italic font is used to emphasize certain words and to indicate variables. Courier Bold font Courier Bold font identifies text that you type. Ctrl+key or mouse action 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.
Viewing User Documentation on the Interplay Portal Viewing User Documentation on the Interplay Portal You can quickly access the Interplay user documentation from any system in the Interplay environment. Type the following line in your Web browser: http://Interplay_Engine_name where Interplay_Engine_name is the name of the computer running the Interplay Engine software.
Avid Training Services Avid makes lifelong learning, career advancement, and personal development easy and convenient. Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment. To learn about Avid's new online learning environment, Avid Learning Excellerator™ (ALEX), visit http://learn.avid.com.
1 Automatic Server Failover Introduction This chapter covers the following topics: • Server Failover Overview • How Server Failover Works • Installing the Failover Hardware Components • Clustering Terminology Server Failover Overview The automatic server failover mechanism in Avid Interplay allows client access to the Interplay Engine in the event of failures or during maintenance, with minimal impact on the availability.
1 Automatic Server Failover Introduction Network Switch Two-node cluster in an Avid Unity MediaNetwork environment Private network for heartbeat Interplay clients Interplay Engine - Cluster Node Intranet LEGEND Infortrend cluster shared-storage RAID array Interplay Engine - Cluster Node 1 GB Ethernet connection Fibre connection Fibre Switch The following diagram illustrates the failover cluster architecture for an Avid Unity ISIS environment.
How Server Failover Works How Server Failover Works When the Microsoft® Windows® cluster service is running on the machines and the server is deployed in cluster mode, the Interplay Engine and its accompanying services are exposed to users as a virtual server. To clients, however, connecting to the clustered virtual Interplay Engine appears to be the same process as connecting to a single, physical machine. The user or client application does not know which node is actually hosting the virtual server.
1 Automatic Server Failover Introduction Server Failover Requirements You should make sure the server failover system meets the following requirements. Hardware A dual-server failover cluster-capable system with an Infortrend® cluster shared-storage RAID disk set is needed. The automatic server failover system was developed on and tested with the following: • Intel Server Chassis SR2500 Packaged Cluster, which is the recommended hardware: http://www.intel.
Installing the Failover Hardware Components Functions You Need To Know Before you set up a cluster in an Avid Interplay environment, you should be familiar with the following functions: • Microsoft Windows Active Directory domains and domain users • Microsoft Windows clustering (current version, as there are changes from prior version) • Disk configuration (format, partition, naming) • Network configuration Installing the Failover Hardware Components A failover cluster system includes the followin
1 Automatic Server Failover Introduction SR2400 Slot Locations The SR2400 is supported as a server for the Interplay applications. This section describes the slot locations that are specific to the Interplay components in a cluster configuration. Use the following figure and table as guides to configuring your SR2400 systems in an Interplay cluster environment.
Installing the Failover Hardware Components SR2500 Slot Locations The SR2500 is supported as a server for the Interplay applications. This section describes the slot locations that are specific to the Interplay components in a cluster configuration. Use the following figure and table as guides to configuring your SR2500 systems in an Interplay cluster environment.
1 Automatic Server Failover Introduction Making Failover Cluster Connections in an Avid Unity ISIS Environment Make the following cable connections to add a failover cluster to an Avid Unity ISIS environment: • • First cluster node: - Left on-board network interface connector to ISIS left subnet (VLAN 10) - Right on-board network interface connector to ISIS right subnet (VLAN 20) - QLogic card connector to RAID array, Fibre Channel 1 left connector Second cluster node: - Left on-board network inte
Installing the Failover Hardware Components Failover Cluster Connections in an Avid Unity ISIS Environment (SR2400) The following illustration shows the required cable connections when adding a failover cluster in an Avid Unity ISIS environment (SR2400 servers). For a description of the connections, see “Making Failover Cluster Connections in an Avid Unity ISIS Environment” on page 19.
1 Automatic Server Failover Introduction Failover Cluster Connections in an Avid Unity ISIS Environment (SR2500) The following illustration shows the required cable connections when adding a failover cluster in an Avid Unity ISIS environment (SR2500 servers). For a description of the connections, see “Making Failover Cluster Connections in an Avid Unity ISIS Environment” on page 19.
Installing the Failover Hardware Components Making Failover Cluster Connections in an Avid Unity MediaNetwork Environment The Interplay Engine Cluster nodes (SR2400 servers) ship with an Intel Pro 1000 MT card in slot 3 (top). You need to move this card to slot 1 (bottom). Then add an ATTO host bus adapter in slot 3 (top).
1 Automatic Server Failover Introduction Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2400) The following illustration shows the required cable connections when adding a failover cluster in an Avid Unity MediaNetwork environment (SR2400 servers). For a description of the connections, see “Making Failover Cluster Connections in an Avid Unity MediaNetwork Environment” on page 22.
Installing the Failover Hardware Components Failover Cluster Connections in an Avid Unity MediaNetwork Environment (SR2500) The following illustration shows the required cable connections when adding a failover cluster in an Avid Unity MediaNetwork environment (SR2500 servers). For a description of the connections, see “Making Failover Cluster Connections in an Avid Unity MediaNetwork Environment” on page 22.
1 Automatic Server Failover Introduction Clustering Terminology Clustering is not always straightforward, so it is important that you get familiar with the terminology of server clusters before you start. A good source of information is the Microsoft Technology Center for Clustering Services under: http://www.microsoft.com/windowsserver2003/technologies/clustering/default.mspx Detailed architecture documentation can be found here: http://www.microsoft.com/windowsserver2003/techinfo/overview/servercluster.
2 Automatic Server Failover Installation This chapter describes the processes for configuring the automatic server failover. It is crucial that you follow the instructions given in this chapter completely, otherwise the automatic server failover will not work.
2 Automatic Server Failover Installation Server Failover Installation Overview Installation and configuration of the automatic server failover consists of the following major tasks: n • Make sure that the network is correctly set up and that you have reserved IP host names and static IP addresses (see “Before You Begin the Server Failover Installation” on page 28). • Prepare the servers for the cluster service (see “Preparing the Server for the Cluster Service” on page 31).
Before You Begin the Server Failover Installation • Create or select two domain user accounts: - Cluster Service Account (Server Execution User): Create or select an account (sometimes called the cluster user account) that is used to start the cluster service and is also used by the Interplay Engine service. This account must be a domain user and it must be a unique name that will not be used for any other purpose. The procedures in this document use sqauser as an example of a Cluster Service Account.
2 Automatic Server Failover Installation 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. An Avid Unity ISIS environment needs 8 IP addresses and an Avid Unity MediaNetwork needs 5 IP addresses. The following table provides a list of example names that you can use when configuring the cluster. The procedures in this chapter use these example names.
Preparing the Server for the Cluster Service Required IP Addresses and Node Names (Continued) Node or Service Item Required Example Name Where Used Cluster service • 1 Network Name (virtual host name) SECLUSTER • 1 ISIS IP address or 1 MediaNetwork IP address See “Configuring the Cluster Service on the First Node” on page 42. CLUSTERMSDTC See “Assigning a Network Name to the MSDTC Group” on page 59.
2 Automatic Server Failover Installation Setting the QLogic HBA Link Speed To avoid possible problems with the Infortrend RAID array, Avid recommends that you change the QLogic HBA link speed (data rate) from the default setting to 2 Gbps. You need to specify this setting on both the SR2400 server and the SR2500 server. Change the setting by using the SAN Surfer utility on both nodes. To set the QLogic HBA link speed: 1.
Preparing the Server for the Cluster Service 5. Click Save. 6. When prompted for a password, enter config and click OK. 7. On the other node, repeat steps 1 through 6. 8. Verify that the SAN Surfer data rate is set to 2 Gbps on both nodes. Renaming the Local Area Network Interface on Each Node You need to rename the LAN interface on each node to appropriately identify each network.
2 Automatic Server Failover Installation c Both nodes must 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 following table. 3. Depending on your Avid Unity network and the device you selected, type a new name for the network connection and press Enter. Use the following illustration and table for reference. The illustration uses an SR2400 in an Avid Unity ISIS environment as an example.
Preparing the Server for the Cluster Service Naming Network Connections (Continued) Network Interface Right PCI adapter network interface. Avid Unity ISIS New Names Avid Unity MediaNetwork New Names Private Not used Comment ISIS - Private network used for heartbeat between the two servers in the cluster. MediaNetwork - Disabled 4. Repeat steps 2 and 3 for each network connection. The following Network Connections window shows the new names used in an Avid Unity ISIS environment. 5.
2 Automatic Server Failover Installation Select this check box. All others are unchecked. 4. Select Internet Protocol (TCP/IP) and click Properties. The Internet Protocol (TCP/IP) Properties dialog box opens.
Preparing the Server for the Cluster Service Type the private IP address for the node you are configuring. 5. On the General tab of the Internet Protocol (TCP/IP) Properties dialog box: n 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 30.
2 Automatic Server Failover Installation 7. 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. 8. On the WINS tab, do the following: t Make sure no values are defined in the WINS addresses area. t Uncheck “Enable LMHOSTS Lookup”. t Select “Disable NetBIOS over TCP/IP.” 9. Click OK. A message might by displayed stating “This connection has an empty primary WINS address.
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 one node, open the Network Connections window. 2. Select Advanced > Advanced Settings. 3.
2 Automatic Server Failover Installation - For an Avid Unity MediaNetwork environment use the following order: - Public - Private 4. Click OK. 5. Repeat this procedure on the other node 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 Adapter as you normally would. For examples of public network settings, see “List of IP Addresses and Network Names” on page 30.
Configuring the Cluster Service The following illustration shows the required names and drive letters. Configure disks as shown 5. Verify you can access the disk and that it is working by creating a file and deleting it. 6. Shut down the first node and start the second node. 7. On the second node, assign drive letters and names. You do not need to format the disks. a. Open the Disk Management tool. Right-click the partition, select Change Drive Letter, and enter the appropriate letter.
2 Automatic Server Failover Installation 3. Validate the cluster service installation on the first node. See “Validating the Cluster Service on the First Node” on page 47. 4. Turn on the second node. Leave first node turned on. 5. Configure the second node using Add Cluster Computers Wizard. See “Configuring the Cluster Service on the Second Node” on page 47. Configuring the Cluster Service on the First Node To configure the cluster service on the first node: 1.
Configuring the Cluster Service Type the Cluster service name. 8. Click Next. The Select Computer dialog box opens. n You might be prompted for an account. If so, use a domain user account, such as the Cluster Installation Account referred to in “Before You Begin the Server Failover Installation” on page 28. Do not use the Cluster Service Account (Service Execution User).
2 Automatic Server Failover Installation 9. In the Select Computer dialog box, in the Computer name text box, type the Cluster node host name of the first node. For example, use SECLUSTER1. See “List of IP Addresses and Network Names” on page 30. 10. Click Advanced. The Advanced Configuration Options dialog box opens. 11. Select Advanced (minimum) configuration, and click OK. 12. Click Next.
Configuring the Cluster Service The setup process analyzes the node for hardware or software problems that might cause problems during installation. A warning icon displays next to “Checking Cluster feasibility.” In this case, the warnings do not indicate a problem. 13. Click Next after the analyze is complete and the Task Complete bar is green. 14. In the IP Address dialog box, type the Cluster Service ISIS IP address for the left side in the IP Address text box.
2 Automatic Server Failover Installation 18. Click Quorum. The Cluster Configuration Quorum dialog box opens. 19. Select Disk Q: from the menu, and click OK. 20. Review the summary on the Proposed Cluster Configuration dialog box to verify all the information for creating the cluster is correct. 21. Click Next. The Creating the Cluster dialog box opens. 22. Review any errors during the cluster creation. n If red errors display, check the Cluster Service ISIS IP address you entered in step 14. 23.
Configuring the Cluster Service 24. Click Finish. Validating the Cluster Service on the First Node To validate the first node cluster installation: 1. Click Start and select Programs > Administrative Tools > Cluster Administrator. 2. In the left pane, click Resources to make sure all resources are online. Verify Resources Configuring the Cluster Service on the Second Node To configure the cluster service on the second node: 1. Make sure the first node is on and all storage devices are turned on. 2.
2 Automatic Server Failover Installation 7. Click Advanced. The Advanced Configuration Options dialog box opens. 8. Select Advanced (minimum) configuration, and click OK. 9. Click Next. The setup process analyzes the node for hardware or software problems that might cause problems during installation. A warning icon displays next to “Checking Cluster feasibility.” In this case, the warnings do not indicate a problem. 10. Click Next after the analyze is complete and the Task Complete bar is green.
Configuring the Cluster Service 11. Type the password for the cluster service account. This account is used to start the cluster service. 12. Click Next. 13. In the Proposed Cluster Configuration dialog box, review the summary to verify all the information for creating the cluster is correct. 14. Click Next. The Adding Nodes to the Cluster dialog box opens. 15. Review any errors during the cluster creation. A warning icon displays next to “Reanalyzing cluster.
2 Automatic Server Failover Installation Configuring Rules for the Cluster Networks After the networks are configured on each node and the cluster service is configured, you need to configure the network roles to determine the function within the cluster. n The procedures in this section use Left-74 and Right-75 as examples of the public networks. You should replace the numbers with your subnet numbers. To configure the rules for the cluster networks: 1.
Configuring Rules for the Cluster Networks - Name: Left-74 - Enable this network for cluster use - All communications (mixed network) 7. Click OK. 8. In the left pane, click Cluster Configuration > Networks, and right-click Right-75 and select Properties. 9. In the Right-75 Properties dialog box, verify these options: - Name: Right-75 - Enable this network for cluster use - All communications (mixed network) 10. Click OK.
2 Automatic Server Failover Installation 4. Verify the Private network is at the top of the list. You can use the Move Up and Move Down buttons to change the priority order. 5. Click OK. After Setting Up the Cluster After you finish setting up the cluster you need to verify that the quorum disk is using disk Q, set the startup times for each node, and test the cluster installation.
After Setting Up the Cluster Verifying the Quorum Disk The Cluster Configuration Wizard automatically selects the disk used as the quorum device. Check to make sure the quorum device is using disk Q. To verify the quorum disk: 1. On either node, click Start and select Programs > Administrative Tools > Cluster Administrator. 2. In the left pane, right-click the cluster name at the top of the list and select Properties. 3. Click the Quorum tab and make sure Quorum resource displays Disk Q. 4. Click OK.
2 Automatic Server Failover Installation To set the time for displaying the list of operating systems: 1. On the first node, click Start and right-click My Computer and select Properties. 2. Click the Advanced tab. 3. In the Startup And Recovery area, click Settings. The Setup and Recovery dialog box opens. 4. Select “Time to display list of operating systems.” 5.
After Setting Up the Cluster Testing the Cluster Installation You must test the cluster installation to make sure the failover process is working. To verify that resources will failover: 1. Click Start, and select Programs > Administrative Tools > Cluster Administrator. The Cluster Administrator window opens. Click Groups 2. In the left pane, open the Groups folder, right-click Cluster Group, and select Move Group. The group and all its resources are moved to the other node.
2 Automatic Server Failover Installation All resources are online Second node is now owner of the resources 3. Move the group back to node 1 after you finish testing the cluster installation. 4. Close the Cluster Administrator. Configuration of the cluster service on all nodes is complete and the cluster is fully operational. You can now install cluster resources, such as file shares, cluster aware services such as Distributed Transaction Coordinator.
Installing the Distributed Transaction Coordinator • “Creating a Physical Resource for the MSDTC Group” on page 60 • “Assigning Distributed Transaction Coordinator Resource to the MSDTC Group” on page 60 When performing these procedures Avid suggests you use the same entries shown in the procedure. These entries are from the list in section “List of IP Addresses and Network Names” on page 30.
2 Automatic Server Failover Installation You can use any name for the group name, however Avid suggests you use MSDTC. 4. Click Next. The Preferred Owners dialog box opens. 5. Select both owners in the Available nodes list and add them to the Preferred owners list. 6. Click Finish. The group is created. Assigning an IP Address to the MSDTC Group To assign an IP address to MSDTC group: 1. In the Cluster Administrator, right-click MSDTC group and select New > Resource. 2.
Installing the Distributed Transaction Coordinator 4. Complete the Dependencies dialog box as follows: - Leave the Resource dependencies list empty. 5. Complete TCP/IP Address Parameters dialog box as follows: - Address: type the IP address of the MSDTC service. See “List of IP Addresses and Network Names” on page 30. - Subnet mask: displays subnet for the network - Network: select the default network connection: Right-subnet or Left-subnet (for ISIS), or Public (for MediaNetwork).
2 Automatic Server Failover Installation Creating a Physical Resource for the MSDTC Group To create a physical disk resource for MSDTC group: 1. In the Cluster Administrator, right-click MSDTC group and select New > Resource. 2. Complete the New Resource dialog box as follows: - Name: MSDTC DISK R - Resource Type: Physical disk - Group: MSDTC 3. Click Next. 4. Complete the Possible Owners dialog box as follows: - Add the cluster server host names to the Possible owners lists.
Installing the Distributed Transaction Coordinator 4. Complete the Possible Owners dialog box as follows: - Add the cluster server host names to the Possible owners lists. For example, SECLUSTER1 and SECLUSTER2. See “List of IP Addresses and Network Names” on page 30. 5. Click Next. 6. Complete the Dependencies dialog box as follows: - Add MSDTC DISK R and MSDTC NAME to the Resource dependencies list. 7. Click Finish.
2 Automatic Server Failover Installation Installing the Interplay Engine After you set up and configure the cluster, you need to install the Interplay Engine software on both nodes.
Installing the Interplay Engine on the First Node 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 Engine service IP address of the resource group. For a list of example names, see “List of IP Addresses and Network Names” on page 30. • Subnet Mask: the subnet mask on the local network.
2 Automatic Server Failover Installation 4. 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. 5. Read the license agreement information and then accept the license agreement by selecting “I accept the agreement.” Click Next. The Specify Installation Type dialog box opens. 6. Continue the installation as described in the next topic.
Installing the Interplay Engine on the First Node Specifying Cluster Mode During a Custom Installation To specify cluster mode: 1. In the Specify Installation Type dialog box, select Custom. 2. Click Next. The Specify Cluster Mode dialog box opens.
2 Automatic Server Failover Installation 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. To specify the Interplay Engine details: 1. Type the following values: - Virtual IP address: This is the Interplay Engine service IP Address, not the Cluster service IP address.
Installing the Interplay Engine on the First Node c 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. Specifying the Interplay Engine Name In this dialog box, type the name of the Interplay Engine. To specify the Interplay Engine name: 1.
2 Automatic Server Failover Installation 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. Specifying the Destination Location In this dialog box specify the folder in which you want to install the Interplay Engine program files. To specify the destination location: 1.
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. To specify the default database folder: 1. Type S:\Workgroup_Databases. Make sure the path specifies the shared drive (S:). This folder should reside on the shared drive that is owned by the resource group of the server. Avid strongly recommends using the shared drive resource so that it can be monitored and managed by the cluster service.
2 Automatic Server Failover Installation Specifying the Share Name In this dialog box specify a share name to be used for the database folder. 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 98, Windows ME, 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.
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. Set for both nodes. Use this option for Interplay Archive Engine 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.
2 Automatic Server Failover Installation If you specify the wrong CCS, you can change the setting later on the server machine in the Windows Registry. See “Automatic Server Failover Tips and Rules” on page 89. 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.
Installing the Interplay Engine on the First Node c 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. 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.
2 Automatic Server Failover Installation The Enable Email Notification dialog box opens if you are installing the Avid Interplay Engine for the first time. 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.
Installing the Interplay Engine on the First Node 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.
2 Automatic Server Failover Installation Installing the Interplay Engine for a Custom Installation on the First Node In this dialog box, begin the installation of the engine software. 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.
Installing the Interplay Engine on the First Node 3. Do one of the following: t Click Finish. t 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 Avid Workgroup resource group. This applies to the installation on the first node only.
2 Automatic Server Failover Installation 2. Open the Avid Workgroup Server resource group. The list of resources should look similar to those in the following illustration. Avid Workgroup Disk is online The Avid Workgroup Disk resource should be online and all other resources offline. 3. Bring the disk resource online manually before continuing if necessary. n Avid does not recommend starting the server at this stage yet, since it is not installed on the other node and a failover would be impossible. 4.
Installing the Interplay Engine on the First Node - Add the cluster server host names to the Possible owners lists. For example, SECLUSTER1 and SECLUSTER2. See “List of IP Addresses and Network Names” on page 30. d. Complete the Dependencies dialog box as follows: e. f. Leave the Resource dependencies list empty. Complete TCP/IP Address Parameters dialog box as follows: - Address: type the second Interplay Engine service Avid Unity ISIS IP address.
2 Automatic Server Failover Installation Affect the group option j. Click OK. 5. When the installation is complete, 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 81. 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.
Bringing the Interplay Engine Online 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. c 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.
2 Automatic Server Failover Installation To test the complete installation: 1. To start the server, bring the resource group online; this starts the Interplay Engine and its affiliated services. After starting the Avid Interplay Engine on the first node, the Cluster Administrator should look similar to the following figure. 2. Start an Interplay Administrator, install the licenses if needed, create a test database and add some files to it.
Updating a Clustered Installation (Rolling Upgrade) 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. n For information about updating specific versions of the Interplay Engine and a cluster, see the Avid Interplay ReadMe.
2 Automatic Server Failover Installation 5. During the installation, the installer displays a dialog box that asks you to move the Avid Workgroup Server group to the second node. Move the group, 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. 6. For a split database, update the workgroup.xml file (see “Updating the Workgroup.xml File for a Split Database” on page 85). 7.
Uninstalling the Interplay Engine on a Clustered System On a cluster system, (after both nodes have been upgraded), do the following on the active node: Copy S:\WorkgroupData\Apache\conf\workgroup.080807-101852.xml over the file S:\WorkgroupData\Apache\conf\workgroup.xml n On a cluster system, the following file is installed on both nodes: C:\Program Files\Avid\Avid Interplay Engine\Data\Apache\conf\workgroup.xml. These files are not currently used and do not need to be edited or overwritten.
2 Automatic Server Failover Installation 4. When you are asked if you want to delete the cluster resources, click No. 5. When you are asked if you want to restart the system, click Yes. 6. At the end of the uninstallation process, if you are asked to restart the system, click Yes. 7. After the uninstallation on the inactive node is complete, wait until the last restart is done. Then open the Cluster Administrator on the active node and make sure the inactive node is shown as online.
3 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 Machines Directly Don’t access the machines (nodes) directly. 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 30). Never use the actual physical names or IP addresses of the machines that are part of the cluster.
3 Automatic Server Failover Tips and Rules 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 28) 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.
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: HKEY_LOCAL_MACHINE/Software/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 online, otherwise your changes to the registry won't be effective.
3 Automatic Server Failover Tips and Rules 92
Index A C Antivirus software running on a failover cluster 16 Apache web server on failover cluster 62 Avid Unity environment ISIS failover cluster connections SR2400 (illustration) 20 ISIS failover cluster connections SR2500 (illustration) 21 MediaNetwork failover cluster connections SR2400 (illustration) 23 MediaNetwork failover cluster connections SR2500 ( illustration) 24 SR2400 server slot locations (failover cluster) 17 SR2500 server slot locations (failover cluster) 18 Avid Unity ISIS connections
Index installing 56 resource group for 56 public network adapter 40 required 30 E L Email notification setting for failover cluster 75 License agreement (failover server) 63 License requirements failover cluster system 16 F Failover cluster connections in Avid Unity ISIS 19 connections in Avid Unity MediaNetwork 22 hardware and software requirements 16 system components 15 system overview 13 H Hardware requirements for failover cluster system 16 Heartbeat adapter prioritizing 51 Heatbeat connection
Index Public network adapter configuring 40 Q Quorum disk 28 configuring 42 verifying 53 Quorum resource defined 26 R RAID array configuring for failover cluster 40 Registry editing while offline 89 Resource group connecting to 89 defined 26 services 89 Resources defined 26 renaming 89 Rolling upgrade (failover cluster) 84 SR2500 server (failover cluster) 18 Software requirements for failover cluster system 16 SR2400 server slot locations (failover cluster) 17 SR2500 server slot locations (failover clus
Index 96
