Avid Interplay Engine ® ™ Failover Guide m a k e m a n a g e m ove | m e d i a ™ Avid ®
Copyright and Disclaimer 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.
Copyright © 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.
The following disclaimer is required by Interplay Entertainment Corp.: The “Interplay” name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid products. This product includes portions of the Alloy Look & Feel software from Incors GmbH. This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
Contents Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Accessing the Online Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 How to Order Documentation . . . . . . .
Join Both Servers to the Active Directory Domain. . . . . . . . . . . . . . . . . . . . . . . 35 Setting Up a Cluster User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Configuring the Cluster Shared RAID Disks on Each Node . . . . . . . . . . . . . . . 35 Configuring the Cluster Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Configuring the Cluster Service on the First Node . . . . . . . . . . . . . . . . . . . . . .
Specifying the Server Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Enabling Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Preparing the Server for the Interplay Engine Installation Using Typical Mode . 72 Specify Cluster Mode During a Typical Installation . . . . . . . . . . . . . . . . . . . 72 Specifying the Cluster Information During a Typical Installation . . . . . . . . .
Using This Guide Congratulations on your purchase of Avid Interplay, a powerful system for managing media in a shared storage environment. This guide is intended for all Avid Interplay administrators who are responsible for installing, configuring and maintaining an Avid Interplay Engine with the Automatic Server Failover module integrated. n The documentation describes the features and hardware of all models.
Using This Guide Symbols and Conventions Avid documentation uses the following symbols and conventions: Symbol or Convention Meaning or Action n A note provides important related information, reminders, recommendations, and strong suggestions. c A caution means that a specific action you take could cause harm to your computer or cause you to lose data. w 10 A warning describes an action that could cause you physical harm.
If You Need Help If You Need Help If you are having trouble using Avid Interplay: 1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow. 2. Check for the latest information that might have become available after the documentation was published: - If the latest information for your Avid product is provided as printed release notes, they ship with your application and are also available online.
Using This Guide Most Avid online libraries also include multimedia content such as feature presentations. This multimedia content is an excellent first resource for learning how to use your application or for helping you understand a particular feature or workflow. How to Order Documentation To order additional copies of this documentation from within the United States, call Avid Sales at 800-949-AVID (800-949-2843).
Chapter 1 Automatic Server Failover Introduction This chapter covers the following topics: • Introduction • Summary of the Way it Works • Installing the Failover Hardware Components • Terminology Introduction The automatic server failover mechanism in Avid Interplay allows client access to the Interplay Engine in the event of failures or during maintenance, with minimal impact on the availability. A failover server is activated in the event of application, operating system, or hardware failures.
Chapter 1 Automatic Server Failover Introduction The following diagram illustrates the failover cluster architecture. Two-Node Cluster in Unity MediaNetwork environment Network Switch Interplay clients Private network for heartbeat Interplay Engine - Cluster Node Intranet Cluster shared RAID array Interplay Engine - Cluster Node Fibre Switch n 14 If you are already using clusters, the Avid Interplay Engine won't interfere with your current setup.
Summary of the Way it Works Summary of the Way it Works When the Microsoft® Windows® cluster service is running on the machines and the server is deployed in cluster mode, the Interplay Engine and its accompanying services are exposed to users as a virtual server. To clients, however, connecting to the clustered virtual Interplay Engine appears to be the same process as connecting to a single, physical machine. The user or client application does not know which node is actually hosting the virtual server.
Chapter 1 Automatic Server Failover Introduction Installing the Failover Hardware Components A failover cluster system includes the following components: • Two Interplay Engine nodes or two Interplay Archive nodes (SR2400 servers) • Cluster shared storage - RAID array SR2400 Slot Locations The SR2400 is supported as a server for the Interplay applications. This section describes the slot locations that are specific to the Interplay components in a cluster configuration.
Installing the Failover Hardware Components Installing a Failover Cluster in an Avid Unity ISIS Environment The following illustration shows the required cable connections when adding a failover cluster in an Unity ISIS environment. For a description of the connections, see “Failover Cluster Connections in an Unity ISIS Environment” on page 18.
Chapter 1 Automatic Server Failover Introduction Failover Cluster Connections in an Unity ISIS Environment Make the following cable connections to add a failover cluster to an Unity ISIS environment: • • First cluster node: - Left - on board network interface connector to Unity ISIS Left subnet - Right - on board network interface connector to Unity ISIS Right subnet - QLogic card connector to cluster shared storage RAID array - left Fibre Channel 1 connector Second cluster node: - Left - on board
Installing the Failover Hardware Components Installing a Failover Cluster in an Avid Unity MediaNetwork Environment The following illustration shows the required cable connections when adding a failover cluster in an Unity MediaNetwork environment. For a description of the connections, see “Failover Cluster Connections in an Unity MediaNetwork Environment” on page 20.
Chapter 1 Automatic Server Failover Introduction Failover Cluster Connections in an Unity MediaNetwork Environment The Interplay Engine Cluster nodes ship with an Intel Pro 1000 MT card in slot 3 (top). You need to move this card to slot 1 (bottom). Then add an ATTO host bus adapter in slot 3 (top).
Terminology 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.
Chapter 1 Automatic Server Failover Introduction 22
Chapter 2 Automatic Server Failover Installation This chapter describes the processes for configuring the automatic server failover. It is crucial that you follow the instructions given in this chapter completely, otherwise the automatic server failover will not work. You can install the cluster service during any step of the overall Avid Interplay installation process. For the Cluster Group, create a partition on the cluster shared RAID array. This partition is used as the quorum disk (4GB).
Chapter 2 Automatic Server Failover Installation This chapter covers the following topics: • Requirements • Before You Start: Preparation • Configuring the Cluster Service • Configuring Rules For The Cluster Networks • After Setting Up the Cluster • Installing the Distributed Transaction Coordinator • Disabling Any Web Servers • Installing the Interplay Engine on the First Node • Installing Interplay Engine on the Second Node • Bring the Interplay Engine Online • Testing the Complete I
Requirements Space Requirements The default disk configuration for the cluster shared RAID array is as follows: • Quorum disk - 4GB • MSDTC disk - 5GB • Database disk - 925GB or larger Antivirus Software You can run antivirus software on a cluster, if the antivirus software is cluster-aware. For information about cluster-aware versions of your antivirus software, contact the antivirus vendor.
Chapter 2 Automatic Server Failover Installation Before You Start: Preparation Before you begin the installation process you need to obtain some IP addresses, IP host names, domain user accounts, and establish server addresses on your network. n • Establish the subnet mask, the gateway, DNS and WINS server addresses on your network. • Install and setup an Avid Unity client on the Interplay Engine servers.
Before You Start: Preparation List of IP Addresses and Network Names You need to reserve IP host names and static IP addresses before you begin the installation process. A Unity ISIS environment needs 8 IP addresses and a Unity MediaNetwork needs 5 IP addresses. The following table provides a list of example names that you can use when configuring the cluster. The procedures in this chapter use these example names.
Chapter 2 Automatic Server Failover Installation Renaming Local Area Network Interface on Each Node When you rename the LAN interface on each node, make sure you use the same names. The names and network connections must match on both nodes. To rename the local area network connections: 1. Open the Network Connections window. a. Click Start and select Control Panel. b. Right-click Network Connections, and select Open. The Network Connections window opens. 2.
Before You Start: Preparation 3. Depending on your Avid Unity environment, type a new name for the network connection using the following table and press Enter. Left - PCI adapter network interface SR2400 back view Right - PCI adapter network interface Right - on board network interface This illustration shows Unity ISIS environment. c Left - on board network interface Both nodes must use identical network interface names.
Chapter 2 Automatic Server Failover Installation The following Network Connections window shows the new names used in an Avid Unity ISIS environment. 4. Close the Network Connections window.
Before You Start: Preparation 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. Open the Network Connections window. 2. Select Advanced > Advanced Settings. 3. In the Connections area, position the network connections in the following order: - For Unity ISIS environment use connection order listed in this illustration.
Chapter 2 Automatic Server Failover Installation Configuring Private Network Adapter on Each Node To configure the private network adapter for the heartbeat connection: 1. Open the Network Connections window. 2. Right-click the Private network connection and select Properties. The Private Properties dialog box opens. Select this check box. All others are unchecked. 3. On the General tab, click the Internet Protocol (TCP/IP) check box. Make sure all other components are unchecked. 4.
Before You Start: Preparation 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 27.
Chapter 2 Automatic Server Failover Installation The Advanced TCP/IP Settings dialog box opens. 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.
Before You Start: Preparation Join Both Servers to the Active Directory Domain Make sure you join the two servers to the Active Directory Domain. Setting Up a Cluster User Account Before you configure the Cluster service you need to create or have available, a domain user account that will become a member of the Local Administrators group on each node. This user account starts the Cluster service and the Interplay Engine services. For more information, see “Before You Start: Preparation” on page 26.
Chapter 2 Automatic Server Failover Installation Configure disks as shown 5. (First node only) Format the disks. 6. Verify you can access the disk and that it is working, by creating a file and deleting it. 7. Turn off the first node and turn on the second node. 8. Repeat this procedure on the second node, with the exception of formatting the disks because you only need to format the disks once.
Configuring the Cluster Service Configuring the Cluster Service List of steps to configure the cluster service: • Turn off the second node. • Configure the first node using the New Server Cluster Wizard. See “Configuring the Cluster Service on the First Node” on page 37. • Validate the cluster service installation on the first node. See “Validating the Cluster Service on the First Node” on page 42. • Turn on the second node. Leave first node turned on.
Chapter 2 Automatic Server Failover Installation 7. In the Cluster Name and Domain dialog box, do the following: - Domain: select the name of your Active Directory domain - Cluster name: type the Cluster service name, for example SECLUSTER — see “List of IP Addresses and Network Names” on page 27. Type the Cluster service name. 8. Click Next. n 38 You might be prompted for an account. This user account is not the account the cluster service uses to start.
Configuring the Cluster Service 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, SECLUSTER1, see “List of IP Addresses and Network Names” on page 27. 10. Click Advanced. The Advanced Configuration Options dialog box opens. 11. Select Advanced (minimum) configuration, and click OK.
Chapter 2 Automatic Server Failover Installation 12. 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.” This is ok. 13. Click Next after the analyze is complete and the Task Complete bar is green. 14. In the IP Address dialog box, type a unique Cluster Service ISIS IP address in the IP Address text box. See “List of IP Addresses and Network Names” on page 27. 15.
Configuring the Cluster Service 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. Click Next. 24.
Chapter 2 Automatic Server Failover Installation 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.
Configuring the Cluster Service 7. Click Advanced. The Advanced Configuration Options dialog box opens. 8. Select Advanced (minimum) configuration, and click OK.
Chapter 2 Automatic Server Failover Installation 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.” This is ok. 10. Click Next after the analyze is complete and the Task Complete bar is green. 11. Type the password for the cluster service account. This account is used to start the cluster service. 12. Click Next. 13.
Configuring Rules For The Cluster Networks 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.
Chapter 2 Automatic Server Failover Installation 6. In the Left-74 Properties dialog box, verify these options: - 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.
After Setting Up the Cluster 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 the quorum disk is using disk Q, set the startup times for each node, and test the cluster installation.
Chapter 2 Automatic Server Failover Installation 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. 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.
After Setting Up the Cluster Setting the Startup Times on Each Node Avid recommends that you offset the startup time of each node’s operating system used during the power up of the cluster. To set the time for displaying the list of operating systems: 1. 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.
Chapter 2 Automatic Server Failover Installation 4. Select “Time to display list of operating systems.” 5. Depending on the node you are settings, do one of the following: t First Node: Set the time to 15 seconds for the Select Time to display list of operating systems option. t Second Node: Set the time to 75 seconds for the Select Time to display list of operating systems option. 6. Click OK.
After Setting Up the Cluster 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.
Chapter 2 Automatic Server Failover Installation Installing the Distributed Transaction Coordinator Interplay Engine requires DCOM services in the cluster. To allow DCOM services in the cluster, create a resource group for the Distributed Transaction Coordinator. This resource group needs its own physical 5GB disk, an IP address and a network name (MSDTC). Finish the group by adding a resource of the Distributed Transaction Coordinator type.
Installing the Distributed Transaction Coordinator Creating a Resource Group for the Distributed Transaction Coordinator To create a resource group named MSDTC for the Distributed Transaction Coordinator: 1. Click Start and select Programs > Administrative Tools > Cluster Administrator. 2. Select File > New > Group. The New Group Wizard opens. 3. In the Name text box, type MSDTC. You can use any name for the group name, however Avid suggests you use MSDTC. 4. Click Next.
Chapter 2 Automatic Server Failover Installation 5. Select both owners in the Available nodes list and add them to the Preferred owners list. 6. Click Finish. 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. Complete the New Resource dialog box as follows: - Name: MSDTC IP - Resource Type: IP Address - Group: MSDTC 3.
Installing the Distributed Transaction Coordinator 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 27. - Subnet mask: displays subnet for the network - Network: select a network connection: Right-subnet, Left-subnet, or Public - Select Enable NetBIOS for this address 6. Click Next. Assigning a Network Name to the MSDTC Group To assign a network name to MSDTC group: 1.
Chapter 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: t Add the cluster node host names to the Possible owners lists.
Installing the Distributed Transaction Coordinator 4. Complete the Possible Owners dialog box as follows: t Add the cluster node host names to the Possible owners lists. For example, SECLUSTER1 and SECLUSTER2. See “List of IP Addresses and Network Names” on page 27. 5. Click Next. 6. Complete the Dependencies dialog box as follows: t Add MSDTC DISK R and MSDTC NAME to Resource dependencies list. 7. Click Finish.
Chapter 2 Automatic Server Failover Installation Disabling Any Web Servers n If you followed the procedures in the document no action is required, since the only web server install at this point is the IIS and is disabled. The Interplay Engine uses an Apache web server that can only be registered as a service if no other web server (for example, IIS) is serving the port 80 (or 443). Stop and disable or uninstall the other http services before you start the installation of the server.
Installing the Interplay Engine on the First Node You are ready to start the server installer. During setup you must enter the following cluster related information: n c For a list of example names, see “List of IP Addresses and Network Names” on page 27. • Virtual IP Address: the Interplay Engine service IP address of the resource group • Subnet Mask: the subnet mask • Public Network: the name of the public network connection. For example, Left-subnet, Right-subnet, Public.
Chapter 2 Automatic Server Failover Installation Preparing the Server for the Interplay Engine Installation Using Custom Mode The first time you install the Interplay Engine on a system, 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 Typical installation mode, installs the default components of the software.
Installing the Interplay Engine on the First Node Specify Cluster Mode During a Custom Installation 1. In the Specify Installation Type dialog box, select Custom. 2. Click Next. The Specify Cluster Mode dialog box opens.
Chapter 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 1. Type the following values: - Virtual IP address: This is the Interplay Engine services IP Address, not the Cluster IP address. - Subnet Mask: The subnet mask on the local network. Ask your system administrator for more information on this.
Installing the Interplay Engine on the First Node Specifying the Interplay Engine Name 1. Choose the public names for the Avid Interplay Engine by typing the following values: - The Network Name will be associated with the virtual IP Address that you've entered in the previous Interplay Engine Details dialog box. It is registered in the DNS so that clients can find the server without having to specify its address. The name must not exist yet.
Chapter 2 Automatic Server Failover Installation Specifying the Destination Location The Destination Location is the location of the Interplay Engine program files. 1. Do one of the following: c t Keep the default. t Type another location or use the Browse button to select another location.The installation needs to be on a local disk of the host and not on a shared cluster disk. It is also essential that the same location is used on the other machine.
Installing the Interplay Engine on the First Node Specifying the Default Database Folder Specify a default database folder. The database folder is the place where the database data is stored. 1. Type or browse to the database folder name. This folder should reside on the shared drive that is owned by the resource group of the server.
Chapter 2 Automatic Server Failover Installation Specifying the Share Name Specify a share name used by the File Share resource. 1. Type the share name. Avid recommends you use the default sharing name of "WG_Database$". This name is visible on all client platforms, such as Windows 98, Windows ME, Windows NT Windows 2000 and Windows XP. Other sharing names such as "Interplay Database" are only reachable from Windows NT, Windows 2000 and Windows XP.
Installing the Interplay Engine on the First Node Specifying the Configuration Server The configuration server setting indicates whether this server is to act as a Central Configuration Server. Set for both Interplay Engines Use this option for Interplay Archive Engine A Central Configuration Server (CCS) is an Avid Interplay Engine with a special module which is used to store server and database-spanning information.
Chapter 2 Automatic Server Failover Installation If you do 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. For example, use this option when using an Interplay Archive Engine as the CCS. If you specify the wrong 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.
Installing the Interplay Engine on the First Node 1. Type the Cluster Service Account user login information. The "Server Execution User" is the Windows domain user that runs the Interplay Engine and the cluster service. This user needs to have administrative access to the file server. This user must be the one that was used to set up the cluster service. See “Before You Start: Preparation” on page 26. c c The installer cannot check the username or password you type in this dialog.
Chapter 2 Automatic Server Failover Installation 2. Click Next. 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 - Type the administrator's email address and the email address of the server, which is the sender. If an event, such as "Resource Failure" "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.
Chapter 2 Automatic Server Failover Installation Preparing the Server for the Interplay Engine Installation Using Typical Mode The Typical installation mode, installs the default components of the software. If you have installed the Avid Interplay Engine previously, the settings from the previous installation are used. The Typical installation mode is usually used for upgrading the software.
Installing the Interplay Engine on the First Node 3. Do one of the following: t Select Cluster to continue the installation in cluster mode. t Select Standalone to install a standalone server (on the physical node) without cluster integration. If you select standalone mode, follow the standard installation procedure (see the Avid Interplay Installation Guide: Avid Interplay Engine, Avid Interplay Archive Engine, and Avid Interplay Access). 4. Click Next.
Chapter 2 Automatic Server Failover Installation 1. Type the following values: - Virtual IP address: This is the Interplay Engine services IP Address. - Subnet Mask: The subnet mask on the local network. Ask your system administrator for more information on this. - Public Network: The name of the public network connection. For example, Left-subnet, Right-subnet, Public. (the other adapter is used for the cluster heartbeat).
Installing the Interplay Engine on the First Node Specifying the Server User During a Typical Installation The Specify Server User dialog box opens. 1. Type the Cluster Service Account user login information. The "Server Execution User" is the Windows domain user that runs the Interplay Engine and the cluster service. This user needs to have administrative access to the file server. This user must be the one that was used to set up the cluster service. See “Before You Start: Preparation” on page 26.
Chapter 2 Automatic Server Failover Installation Beginning the Installation of Interplay Engine on the First Node When all of the settings have been entered, whether you used the Custom mode or Typical mode to prepare the installation, the Ready to Install dialog box opens. 1. Click Next to start the actual installation process of the Interplay Engine, or use Back to revisit the data you have entered.
Installing the Interplay Engine on the First Node 2. Do one of the following: t Click Finish. t Analyze and resolve any issues or failures reported. 3. 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.
Chapter 2 Automatic Server Failover Installation Avid Workgroup Disk is online The Avid Workgroup Disk resource should be online, 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. (Unity ISIS only) Add IP address on the second subnet for the Interplay Engine. a.
Installing the Interplay Engine on the First Node b. c. Complete the New Resource dialog box as follows: - Name: Avid Workgroup Address 2 - Resource Type: IP Address - Group: Avid Workgroup Server Complete the Possible Owners dialog box as follows: t 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 27. d. Complete the Dependencies dialog box as follows: t e. f.
Chapter 2 Automatic Server Failover Installation g. Right-click Avid Workgroup Address 2 and select Properties. h. Click the Advanced tab. i. Deselect Affect the Group as shown in the following illustration. 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 Interplay Engine on the Second Node” on page 80.
Bring the Interplay Engine Online 2. Perform the installation procedure for the second node as described in “Installing the Interplay Engine on the First Node” on page 58. 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. 3. Click OK. 4. The same installation dialog boxes will open that you saw before, except for the cluster related settings that only has to be entered once.
Chapter 2 Automatic Server Failover Installation 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 Cluster Administrator and review the different failover-related settings. To test the complete installation: 1. To start the server, bring the resource group online; this starts the Interplay Engine and its affiliated services.
Updating a Clustered Installation 5. Look at the related settings of the resource group. 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. Updating a Clustered Installation A major benefit of a clustered installation is that you can perform rolling upgrades.
Chapter 2 Automatic Server Failover Installation c Do not move the Avid Workgroup resource group over yet. 4. Make sure that first node is online. Update the installation on the first node using the WorkgroupServer.exe installer. Select the Typical mode so that all values are reused. This restarts the first node. 5. During installation, the installer asks you to move the resource groups to the second node. Move the resource groups. Then click OK in the installation dialog box to continue.
Uninstalling the Interplay Engine 3. When uninstalling a clustered installation, you are asked whether the cluster resources are to be removed. Typically you should select Yes to delete the resources only when uninstalling the second node, otherwise the other installation becomes useless. 4.
Chapter 2 Automatic Server Failover Installation 86
Chapter 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 directly. Refer to the projects using the "virtual" network name or IP address that has been assigned to the resource group; never use the actual physical names or IP addresses of the machines that are part of the cluster.
Chapter 3 Automatic Server Failover Tips and Rules Do Not Install the 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.
ABCDEFGHIJKLMNOPQRSTUVWXYZ Index A Antivirus software running on a cluster 25 Apache web server 58 Architecture 14 Avid Unity environment SR2400 server slot locations 16 B Binding order networks configuring 31 C Central Configuration Server specifying 67 Cluster group illustration 15 partition 23, 35 Cluster installation testing 50 Cluster Installation account defined 26 Cluster network configuring rules 45 Cluster service configuring 37 configuring on second node 42 defined 21 specify name 38 validatin
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ I Installation custom 61 Distributed Transaction Coordinator 52 testing 50 types 59 typical 72 Interplay Engine Central Configuration Server, specifying 67 cluster details 63 default database location 65 installation cluster information 62 installing on first node 58 server user, specifying 68 share name 66 SR2400 slot locations 16 Interplay Engine process 15 IP addresses assigning to MSDTC group 54 private network adapter 32 public network adapter 34 required 27 L Licens
ABCDEFGHIJKLMNOPQRSTUVWXYZ Resources defined 21 renaming 87 S Server setting startup time 49 SR2400 slot locations 16 Server cache Interplay Engine installation 69 Server Execution User changing 88 Service name examples 27 Services dependencies 88 Shared Drive 59, 62, 74 configuring 35 default configuration 25 Slot locations SR2400 server 16 Space requirements 25 Specify Installation Type dialog box 59 SR2400 server slot location 16 Subnet Mask 59, 62, 74 System monitoring 13 Index V Virtual IP address 6
Index 92 ABCDEFGHIJKLMNOPQRSTUVWXYZ
