Migrating Avid® Interplay® Applications to AS3000 Servers ReadMe Date Revised Changes Made 6/24/2011 Added the following: • “Changing System Settings on Windows Server 2008 Standard Systems” on page 12 • “Migrating a General Purpose Server” on page 39 The document describes how to migrate Interplay applications to the AS3000 servers. For additional information, see the following documents: • AS3000 Setup Guide • Avid Interplay Software Installation and Configuration Guide • Interplay v2.
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.
Adobe and Photoshop are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Apple and 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.
Contents Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Qualified Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 AS3000 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Loading Application Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Usage on the Interplay Transfer Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 For Installation and Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Copying the TMServer.ini file to the AS3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Migrating DET Configuration Files to Another Server . . . . . . . . . . . . . . . . . . . . 25 Migrating Generic FTP Profiles to Another Server . . . . . . . . . . . . . . . . . . . . . . .
Checklist for Migrating the Media Services Database to an AS3000 Server. . . 40 Deleting the Media Services Database on the Media Services Engine. . . . . . . 41 Migrating the Older Media Services Database to the New Media Services Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Recreating the dms User in the Updated Database . . . . . . . . . . . . . . . . . . . . .
Limitations The id Interplay ReadMe Limitations The following limitations exist for migrating Interplay applications to AS3000 servers: • The AS3000 servers are currently qualified on Interplay v2.3. • The servers running Windows Server 2008 Standard require additional system settings changes. See “Changing System Settings on Windows Server 2008 Standard Systems” on page 12. • As of this writing, Interplay Transfer is not supported on MediaNetwork on an AS3000. Reference problem UDEVC00152485.
Qualified Software The following software versions are qualified on the AS3000. Qualified Software for Interplay Components and Related Software Product Version Avid Interplay products Avid Interplay Installer USB flash drives (Server and Client v2.3 versions). See “Loading Application Software” on page 10. Avid Interplay Engine and Archive Engine standalone (non-cluster systems) v2.3 Avid Interplay Engine and Archive Engine cluster See “Limitations” on page 7. Avid Interplay Media Indexer v2.
AS3000 Configurations AS3000 Configurations The following table lists the configurations that apply to Interplay server applications. All configurations have two processors and 12 GB RAM standard. For information on other Avid servers and the most up to date information on requirements for specific products, see the related Avid server product documentation. For information on adding PCIe cards, see the AS3000 Setup Guide.
Loading Application Software The AS3000 does not have a DVD reader. Software is loaded onto the system using a USB flash drive. The system ships with two or more USB flash drives as follows: • One (or two in the case of the Interplay Engine) 4 GB USB flash drives loaded with the Avid application software. • One 16 GB USB flash drive intended to be used as a bootable USB flash drive with an Avid Product Recovery image.
Best Practices for Migrating to AS3000 Servers Best Practices for Migrating to AS3000 Servers This topic presents a best practices method for moving your entire Interplay environment to AS3000 servers. To move your Interplay environment to AS3000 servers: 1. Upgrade your Interplay environment to Interplay v2.3 and make sure media is online and ensure that you can check clips and sequences in and out of the Interplay database. This ensures that you have a stable environment before you begin the upgrade. 2.
Changing System Settings on Windows Server 2008 Standard Systems The default image for the AS3000 Windows Server 2008 R2 Standard x64 image has several system settings that should be changed for Interplay servers. The following table lists the settings that should be changed.
Changing System Settings on Windows Server 2008 Standard Systems To switch the Server Role to Application Server: 1. Click Control Panel > System and Security > System. The System control panel opens. 2. Click “Advanced system settings” on the left of the window. The System Properties dialog box opens. 3. Click the Advanced tab and click Settings in the Performance area. The Performance Options dialog box opens, 4. Click the Advanced tab. 5.
6. Click Apply and click OK to close the window. 7. Click OK to close the System properties window and close the System window. Migrating Interplay Capture For information on configuring an Interplay Capture server on an AS3000, see the Interplay Capture Installation and Administration Guide. The guide contains specific details on configuring the Adrienne Electronics PCIe card.
Migrating an Interplay Engine Standalone System Migrating an Interplay Engine Standalone System Interplay Engine standalone systems (non-cluster systems) are supported on the AS3000 server. The Interplay Engine runs Windows Server 2008 R2 Standard 64-bit. No additional PCIe cards are required. Use one of the Intel Pro/1000 PT ports for your network connection.
Upgrade the Interplay Engine to Interplay v2.3 If you are upgrading your entire site to AS3000 systems, Avid recommends that you upgrade to Interplay v2.3 before you start migrating to the new servers. See “Best Practices for Migrating to AS3000 Servers” on page 11. Back Up the Interplay Database You use the Interplay Administrator to create backups of the database. Make sure that you have a recent Full backup before you begin the move.
Best Practices for Migrating an Interplay Engine to Another Server Restart the Interplay Engine Before Moving the Database While not required, this is a good test of the health of the system. In particular, it is useful to perform a failover of an Interplay cluster system. This can expose any problems with the cluster services. If there are any problems restarting the system, fix the problems before you begin moving the database.
Examine and Archive the Logs After Moving the Database If you use the Collect tool, examine the Base Analyzer portion after moving the database and users to the AS3000. This portion should run successfully without any errors. Archive the output of the tool as a record of the state of the system after the move. Migrating a Media Indexer You can replace Intel SR2400 and SR2500 Media Indexers with AS3000 systems. The Media Indexer runs Windows Server 2008 R2 Standard 64-bit.
Migrating a Media Indexer • Export the storage configuration from the SR2500 MI leader (primary) of the HAG and import it to the new AS3000 MI • After the AS3000 MI finishes scanning the storage locations, add it to the HAG with a lower priority than the SR2500 leader • Remove any backup MIs from the HAG and then remove the SR2500 leader • The AS3000 takes over as leader of the HAG It is important not to make the AS3000 MI the leader of the HAG until it has finished indexing the storage locations.
3. Click the Commit Immediately button to force a flush out to disk of the Media Indexer cache. The following illustration shows the Commit Immediately button. 4. In Windows Explorer, navigate to the following location on the SR2500 Media Indexer: C:\Program Files\Avid\AvidMI\state 5. Copy the contents of the state folder to another folder or to another computer. Now you have a backup of the Media Indexer’s cache files. To replace the SR2500 Media Indexers with an AS3000 Media Indexer 1.
Migrating a Media Indexer 3. Click the Configure button at the bottom of the Avid Interplay Media Indexer area. The Configure Storage window opens. 4. Click the Export Config button, name the file, and select a location for the file. 5. Copy the configuration file to the AS3000 MI system. For example, copy it to the desktop. 6. Locate the AS3000 MI in the Service Configuration tool and select the Media Indexer process. n Do NOT add the MI to the HAG at this time. 7.
10. After the MI returns a Normal status for all of the shared storage locations, do the following: a. Open the Service Configuration tool, locate the AS3000 MI, and select the Media Indexer process. b. Enter a low priority value (lower than the leader) and enter the name of the HAG in the Group Name text box. c. Click the Join High Availability Group button and click Apply at the top of the window. 11.
Migrating an Interplay Transfer Server This will force an election and the Service Framework will make the AS3000 MI the leader of the HAG. If you are watching the Health Monitor application, the Redundancy Status will show Election in Progress during the election. Finally, the AS3000 MI Redundancy State will show as the Primary. 14. (Option) Use the Service Configuration tool to add a second AS3000 Media Indexer to the HAG as a backup (with a lower weight than the leader).
ISIS and Network Connections The following table shows the connections for ISIS 5000 and ISIS 7000. Connection Type ISIS 5000 ISIS 7000 First ISIS connection Pro/1000 PT Port Pro/1000 PT Port Second ISIS connection NA Pro/1000 PT Port Network connection Pro/1000 PT Port Port 1 or 3. If you have only one ISIS connection, use the second Pro/1000 PT Port for the network connection. External devices should communicate with the Interplay Transfer engine via the DNS entry of the network connection.
Migrating an Interplay Transfer Server Interplay Transfer uses ports 6432 and 6535 to communicate with the sending or receiving device. After the Transfer Engine establishes the connection, the OS on the external device assigns a port and notifies the Transfer Engine of the new port number. Then the external device starts listening on that port. Transfer Engine uses the new port number for sending or receiving data.
To copy the DET folder to the AS3000: 1. Navigate to the following location on the Windows XP Interplay Transfer server: C:\Documents and Settings\All Users\Application Data\Avid\Avid Interplay Transfer Engine 2. Copy the DET folder to the following folder on the AS3000: C:\ProgramData\All Users\Avid\Avid Interplay Transfer Engine n For third party DET and DHM implementations you will need to reinstall any third party DET or DHM.
Migrating an Interplay Transfer Server FTP folder n This is the path used on a Windows XP Transfer Engine system. 3. Right-click the FTP folder and select Export. Export the file to the Desktop and give it a recognizable name such as FTP-regedit-export.reg. 4. Copy the file to the AS3000 Interplay Transfer system. 5. Log onto the AS3000 system and start Regedit. n This assumes that you have already installed Interplay Transfer on the AS3000. 6.
8. The exported file contains the path from the old Windows XP system. You must add the additional Wow6432Node level. 9. Perform a replace/edit to replace SOFTWARE\Avid with the following. SOFTWARE\Wow6432Node\Avid The following illustration shows the open file and the replace window. 10. Save and close the registry file. 11. Right-click the registry file (FTP-regedit-export.reg) and select Merge. The system merges the data with the existing FTP key. 12.
Migrating a Media Services Engine Port Usage for the Media Services Engine To enable the Media Services Engine to communicate with the editors and the provider clients, the network must allow TCP traffic on the following ports: • Listen for editor clients (SOAP): 8080 TCP • Listen; RMI protocol for providers and Status/Admin tool: 1099 TCP • If 1099 is not available: 42000 - 42060 TCP Determining Whether to Migrate the Media Services Engine Database The only way to move your old Media Services Provid
Each service has its own set of profiles 2. Select representative profiles from each group and either write down the values or take screen captures of the windows for future reference. For example, the following Transcode profiles all save to the same workspace and differ mainly in the target resolution. In this case you could write down the values for one profile and then write down the names of the other profiles so that you would know how many others to create at the different resolutions.
Migrating a Copy Provider Migrating a Copy Provider The Copy Provider on an AS3000 uses two Myricom PCIe cards for the same purposes as the Chelsio cards on the Intel SR2500. The following illustration shows the rear view of the AS3000. 1 2 3 4 PRO/1000 PT ports Two PCIe slots The AS3000 has two PCIe slots and they both support the Myricom cards. The appropriate drivers are pre-loaded onto the AS3000 image for Windows 7 Pro 64-bit. To install the Myricom cards: 1.
The system automatically recognizes the Myricom cards because the drivers are pre-loaded on the Windows 7 Pro 64-bit image. If you find it necessary to locate the Myricom drivers, the Myricom drivers folder is located in the following location: C:\Installables\drivers\nic The following illustration shows the Myricom entries in the Windows Device Manager. Making the ISIS Connections This topic describes two different kinds of network connections.
Migrating a Copy Provider The following illustration shows the Myricom connections to two different ISIS systems named Big ISIS and WG6. n Unused network connections are disabled in the above illustration. This not required and depends on your site policies. Some sites disable all unused NICs.
ISIS Client Manager Settings The Interplay Software Installation and Configuration Guide describes how to set ISIS Client Manager settings and how to configure a Chelsio card as the default network connection. These operations are NOT required for the Myricom cards. Migrating a Move Provider This topic describes how to set up the hardware and ISIS client information for a Move Provider on an AS3000 server. The Move provider is used to move files from one ISIS workspace to another.
Migrating an Archive Provider Using a 1Gb Onboad NIC on the Move Provider When using a 1 Gb onboard NIC on the Move Provider, connect one of the Pro/1000 PT ports labeled 2 or 4 on the Move Provider directly into any 1 Gb port on the Avid ISIS Engines. Avid does not recommend using the onboard NICs because performance is better using the Myricom cards. ISIS Connections and Client Software Installation The Move Provider must be directly connected to the ISIS system, using a 10 Gb Ethernet connection.
Use the network connection to connect to the FlashNet server. MediaNetwork Connection For connection to Avid Unity MediaNetwork, insert the qualified Fibre Channel card in either the top or bottom PCIe slot. See “MediaNetwork Connections” on page 39.
Migrating a Stream Server ISIS Connections The Interplay Stream Server has been qualified with one network connection and with two network connections. Connections to the ISIS network should be through PRO/1000 PT port 2, port 4, or both. There is no performance benefit to dual-connecting the Interplay Stream Server to an ISIS network, since there is enough bandwidth to support 100 simultaneous clients.
Migrating, Renaming, or Adding a Stream Server If you already have a Stream Server in your Interplay environment, you can do one of the following: • Replace an existing Stream Server with an AS3000 that uses the same hostname • Replace an existing Stream Server with an AS3000 that uses a different hostname • Install a new Stream Server on an AS3000 and add it as an additional Stream Server To migrate a Stream Server and keep the same hostname: 1.
Migrating a General Purpose Server To add a Stream Server: t Install a new Stream Server on an AS3000 by following the instructions in the “Installing and Configuring the Stream Server Software” section of the Avid Interplay Software Installation and Configuration Guide but do not install the Framework, Auto-Publish service or Workflow Engine on the same system.
To install the Fibre channel card: 1. Install the card in the either of the two PCIe slots as described in the AS3000 Setup Guide. For convenience, use the bottom slot in case you need to add a second card at a later time. 2. Reconnect and restart the system. See “Fibre Channel Card Drivers” on page 40. 3. If necessary, use one of the Pro/1000 PT ports for a network connection.
Migrating a Media Services Database This topic is not required if you are setting up a new Media Services Engine and do not require the old database. In that case, proceed to the instructions in the Avid Interplay Software Installation and Configuration Guide. Migrating the Media Services Engine Check List Task Section Reference Add the AS3000 Interplay Media Services server to the Interplay environment.
The following illustration shows the dms user in the Microsoft SQL Server Management Studio Express user interface. 3. Right-click dmsdb and select Delete. Follow the system prompts to delete the database. 4. Exit the application. c You will not be able to log in to the Media Services Engine until you migrate the old database. Migrating the Older Media Services Database to the New Media Services Engine n This is an advanced procedure that requires experience working with SQL databases.
Migrating a Media Services Database After you move the database, delete and recreate the dms user in the SQL database as described in the following procedure. Recreating the dms User in the Updated Database This procedure is only required if you are migrating an existing database to the AS3000. The Media Services Engine automatically creates a user named “dms.” After you migrate the database you must delete this user and recreate it. To delete and recreate the dms user: 1.
4. Right-click the Users folder and add a new user named dms. Use the schema and roles as shown in the following illustration. 5. In the application folder structure, right-click Security/Logins/dms and select Properties. Then set the dms login default database to dmsdb.
Migrating a Media Services Database n Do not change the default password. This password is automatically created by the Media Services installer and should not be changed,. 6. Exit the application. 7. To verify that the database was successfully migrated, log in to the Media Services engine and check for your old profiles and users.
