Avid MediaCentral Platform Services Upgrade Guide Version 2.
Legal Notices Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be used in accordance with the license agreement. This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents. This guide is protected by copyright.
THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. This product includes software developed by the University of California, Berkeley and its contributors. The following disclaimer is required by Paradigm Matrix: Portions of this software licensed from Paradigm Matrix.
Contents Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(if applicable) Removing the Gluster Metadata Cache Replication Volume. . . . . . . . . . . 36 Chapter 3 Upgrades for RHEL v6.3 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Upgrading a RHEL 6.3 Single Server to MCS v2.9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Backing-up System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Installing RHEL 6.5 and MCS 2.9 . . . . . . . . . . . . . . . .
Completing a Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using This Guide This document provides instructions for upgrading to MediaCentral Platform Services (MCS) v2.9.0 from a previous version of MCS or Interplay Central Services (ICS). To complete a new installation of MediaCentral Platform Services, see the MediaCentral Platform Services Installation and Configuration Guide. For administrative information for MediaCentral | UX, see the Avid MediaCentral | UX Administration Guide.
If You Need Help If You Need Help If you are having trouble using your Avid product: 1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow. 2. Check the latest information that might have become available after the documentation was published. You should always check online for the most up-to-date release notes or ReadMe because the online version is updated whenever new information becomes available.
1 Overview and Prerequisites Avid recommends that you read all the information in the Avid MediaCentral Platform Services ReadMe and the Avid MediaCentral Platform Services Upgrade Guide thoroughly before installing or using the corresponding software release. Important: Check the v2.9 documentation landing page for the latest updates to this guide and all related documentation for Avid MediaCentral Platform Services: http://avid.force.
Overview Overview The MediaCentral Platform Services (MCS) upgrade process includes a migration of custom settings, databases and system files. Depending on your upgrade path, the migration of settings and data is either manual or automated. There are two main upgrade paths to MCS v2.9, depending on the currently installed version of the Red Hat Enterprise Linux (RHEL) operating system: • RHEL v6.
Mounting the Operating System Mounting the Operating System Whether performing an upgrade or a full installation, the MCS installer requires the RHEL ISO to be mounted to the /sysinstall directory on the MCS server. This is true, even when performing an upgrade where the operating system does not change. The body of this guide assumes that you are completing the upgrade using the MCS Installation USB Drive. In this case the RHEL ISO is automatically mounted during the upgrade procedure.
Upgrading Multi-Zone Deployments Upgrading Multi-Zone Deployments If your system is configured for a multi-zone environment, note the following: • • As multi-zone configurations often span WAN (wide area network) environments, special attention should be paid to ensure that the correct network ports are open between the zones. Review the Avid Networking Port Usage Guide on the Avid Knowledge Base for more information on the ports required for multi-zone. If you are upgrading from MCS v2.3.
Upgrading Media | Index Deployments Upgrading Media | Index Deployments If your deployment is configured for Media Index, note the following: • If your upgrade includes an index schema migration, note that the process can take multiple hours to complete on large systems. During this time, indexed searching (with the exception of marker searches) is functional, but slow. Additionally, systems cannot add data to the index through the indexing agents while the migration occurs.
Upgrading the Avid Shared Storage Client • If your system is already running the Avid ISIS client, the latest version of the Avid ISIS client is automatically installed if necessary. No additional steps are required. • If you are upgrading a system running the Avid ISIS client and you plan to either add Avid NEXIS shared storage to the configuration or transition from Avid ISIS to Avid NEXIS, you must manually upgrade the Avid shared storage client.
Upgrading the MediaCentral Distribution Service Upgrading the MediaCentral Distribution Service The MediaCentral Distribution Service (MCDS) is used in MediaCentral UX configurations which employ a Send To Playback (STP) workflow. Consult the version compatibility chart on the Avid Knowledge Base for the correct version of MCDS for your installation and upgrade the software if necessary. http://avid.force.
An Important Note on SSL Certificates An Important Note on SSL Certificates MediaCentral Platform Services uses the Secure Sockets Layer (SSL) for its server to browser connections. MCS v2.5 uses a different SSL certificate format than found in previous releases. If you are upgrading to MCS v2.5 or later and using a Self-Signed or Trusted-CA certificate, refer to the following article on the Avid Knowledge Base to create or in some cases upgrade your SSL certificate: http://avid.force.
Migrating User Settings from UMS to USS During an Upgrade Migrating User Settings from UMS to USS During an Upgrade MediaCentral Platform Services v2.0 introduced a new user database scheme. Upgrades of systems running MCS v2.0 or earlier must complete a user database migration using the supplied avid-ussimport script. n • For upgrades from v1.8.0 (RedHat v6.3) or earlier, a backup and restore of the MCS database is required.
Upgrade Paths Upgrade Paths Refer to one of the following sections to upgrade MediaCentral Platform Services: Upgrades for systems already running Red Hat Enterprise Linux (RHEL) v6.5 For upgrading instructions: • “Upgrading to MCS v2.9” on page 19 • “Upgrading a RHEL 6.5 Cluster System to MCS v2.9” on page 25 Upgrades for systems running Red Hat Enterprise Linux (RHEL) v6.3 For upgrading instructions: • “Upgrading a RHEL 6.3 Single Server to MCS v2.9” on page 37 • “Upgrading a RHEL 6.
2 Upgrades for RHEL v6.5 Systems If upgrading a MediaCentral Platform Services system already running RHEL v6.5, refer to one of the following two processes: • Upgrading a RHEL 6.5 Single Server to MCS v2.9 • Upgrading a RHEL 6.5 Cluster System to MCS v2.9 Prior to upgrading, ensure you have verified the “Upgrade Prerequisites” on page 17. n As a reminder, MCS v2.6.0 and later requires sharded Mongo to be configured on all systems configured in a Corosync cluster or a multi-zone configuration.
Upgrading a RHEL 6.5 Single Server to MCS v2.9 3. Although the upgrade is non-destructive, it is a good idea to back-up the MCS database. This is an optional, but recommended step. Create a back-up of the MCS settings and database using the script located on the USB drive: ./system-backup.sh -b For additional detail on using this script, see “Backing Up and Restoring System Settings and the ICS/MCS Database” on page 69. 4. (Media Index configurations only) If you are upgrading from MCS v2.2.x or v2.3.
Upgrading a RHEL 6.5 Single Server to MCS v2.9 MCS v2.9 requires the RHEL OpenSSL security patch to be installed. If this patch was not installed prior to the upgrade, the following message is displayed: A required openssl patch is missing on this system. Please install this patch (openssl-1.0.1e-30.el6_6.5) so that the system is fully functional. To check for other missing security fixes execute the avid-security-check script. If this message is displayed, install the patch now.
Upgrading a RHEL 6.5 Single Server to MCS v2.9 /opt/avid/cluster/bin/pgpool_remote_start This step is not required and should not be completed if upgrading from MCS v2.4 or later. 3. If you are connecting to either an Avid ISIS or Avid NEXIS shared storage system, verify the shared storage client required for your environment and upgrade the client software if necessary. For more information, see “Upgrading the Avid Shared Storage Client” on page 13. 4. If additional components (e.g.
Upgrading a RHEL 6.5 Single Server to MCS v2.9 For more information on using the Interplay MAM Sync Service Administrator, see “Setting Up Interplay | MAM Sync Service” the Avid Media | Index Configuration Guide or reference the Interplay | MAM Sync Service Administrator User’s Guide. 7. MediaCentral Platform Services v2.
Upgrading a RHEL 6.5 Single Server to MCS v2.9 10. (Multi-Zone configurations only) If you have upgraded a zone running MCS v2.5 or earlier, reconfigure the multi-zone configuration for sharded Mongo. If you are running a multi-zone configuration consisting of zones with mixed software versions, only zones that have been upgraded to MCS v2.6 or later can exist in a sharded Mongo configuration.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 Upgrading a RHEL 6.5 Cluster System to MCS v2.9 Installing MCS v2.9 on a cluster already operating under RHEL v6.5 involves an automated update of the affected packages. All MCS system settings are preserved. All nodes must be taken offline to perform the update.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 3. To identify the load-balancing nodes, look for the line containing “Clone Set”. For example: Clone Set: AvidAllEverywhere [AvidAll] Started: [ wavd-mcs01 wavd-mcs02 wavd-mcs03 wavd-mcs04] In this example, the load-balancing nodes are wavd-mcs03 and wavd-mcs04. 4. Exit crm_mon by pressing CTRL-C on the keyboard. Backing-up the User Database and System Settings Although the upgrade is non-destructive, it is a good idea to back-up the MCS database.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 Taking the Cluster Offline Corosync and RabbitMQ maintain independent clustering mechanisms. Corosync clusters operate in a master/slave relationship whereas RabbitMQ clusters run in an Active/Active state where any node in the cluster could be the owner of a RabbitMQ “queue”. This means that the order in which the nodes disconnect and reconnect to the RabbitMQ cluster is particularly important.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 2. Mount the USB drive and change to the mount point. For details, see “Mounting and Unmounting a USB Drive” on page 53. 3. Start the installation script. ./install.sh n Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the installation script in the current directory. Otherwise you will receive the following error message: -bash: install.sh: command not found If you are upgrading from MCS v2.2 or v2.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 n If you receive a “command not found” error, logout and log back into the server or SSH session (PuTTY). This refreshes the login for the upgraded system and should allow the command to run properly. 5. In some cases, the installer alerts the user to the creation of .rpmnew files when it encounters a configuration file with custom modifications. In other cases, the system administrator must manually check for updated configuration files.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 5. Once all nodes have been rebooted and RabbitMQ has been started on each node, verify the status of the RabbitMQ cluster as detailed in the following process. Verifying the RabbitMQ Cluster Prior to restoring the Cosrosync cluster, you should first verify that the RabbitMQ cluster is functioning normally. Complete the following two steps on each cluster node. To verify the status of RabbitMQ: 1.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 To bring the cluster back online: 1. Reactivate the cluster by running the following command on the master node only: /opt/avid/cluster/bin/reactivate-cluster The script will begin collecting information about your system. 2. The script creates a backup copy of the cluster configuration file. If you have previously upgraded your MCS server, a configuration backup file already exists.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 For example, to reset the fail count for AvidAll resource, issue the following command: crm resource cleanup AvidAllEverywhere n You can address the services contained in the postgres resource group (postgres_fs, AvidClusterIP and pgsqlDB) individually, or as a group. Continuing the Upgrade Review and complete the steps in this section as they apply to your environment. To continue the upgrade: 1.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 4. (Media Index configurations only) Systems configured with Media Index for MAM that have upgraded from MCS v2.4.x or v2.5.x must re-sync the legal list using the MAM CentralSyncAgent to resend dictionary data to the Media Index.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 Repeat this step for each cluster node. i. Use the Cluster resource Monitor to check for failed services: crm_mon -f Clean up any failed resources, starting with the AvidGateway resource: crm resource cleanup AvidGatewayEverywhere 8. If you have upgraded from MCS v2.5 or earlier, reconfigure the configuration for sharded Mongo. This step is required for all Corosync cluster configurations that have upgraded from v2.5 or earlier.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 10. If your system includes Media Distribute, Customizable Logger, or the Assignments Pane, upgrade those software components at this time. For upgrade instructions for each of these components, see the MediaCentral Platform Services Installation and Configuration Guide. 11. Once the upgrade is complete, you should verify basic functionality.
Upgrading a RHEL 6.5 Cluster System to MCS v2.9 3. Obtain the group ID (gid) of the user maxmin (this might be different on each machine): id -g maxmin 4. Change the group ownership of the gluster volume to maxmin using the group ID: gluster volume set gl-cache-dl storage.owner-gid gluster volume set gl-cache-fl storage.owner-gid n Do not alter the gl-cache-mcam (multicam) volume. It uses the default root ownership. 5.
3 Upgrades for RHEL v6.3 Systems If upgrading a MediaCentral Platform Services system running RHEL v6.3, refer to one of the following two processes: n • Upgrading a RHEL 6.3 Single Server to MCS v2.9 • Upgrading a RHEL 6.3 Cluster System to MCS v2.9 Before proceeding, back up any private key used to generate a Certificate Signing Request. For details, see “Backing Up and Restoring SSL Private Keys” on page 16. Upgrading a RHEL 6.3 Single Server to MCS v2.9 The upgrade to MCS v2.9 on a RHEL v6.
Upgrading a RHEL 6.3 Single Server to MCS v2.9 Installing RHEL 6.5 and MCS 2.9 Once the system settings have been backed-up and stored in a safe location, the MCS server can be re-imaged with a fresh installation of RHEL v6.5 and MediaCentral Platform Services. To install RHEL v6.5 and MCS: 1. Unmount the USB drive (if you have not already done so). For details, see “Mounting and Unmounting a USB Drive” on page 53. 2. If your configuration includes a RAID 5 array, delete and recreate the RAID 5.
Upgrading a RHEL 6.3 Single Server to MCS v2.9 Restoring System Settings and Migrating the User Database Now that RHEL v6.5 and MediaCentral Platform Services has been installed on the server, the custom MCS settings must be restored from the USB backup. To restore the MCS settings: 1. Re-insert and re-mount the USB drive. For details, see “Mounting and Unmounting a USB Drive” on page 53. c The MCS Installation USB Drive contains all software used to image a new MediaCentral server.
Upgrading a RHEL 6.3 Single Server to MCS v2.9 Additional Upgrade Procedures The backup and restore procedure saves many system settings which provides the user with a more streamlined upgrade. However, some configuration steps must be manually recreated. Refer to the appropriate section of the MediaCentral Platform Services Installation and Configuration Guide for details on each of the following procedures. To complete the upgrade: 1. If your configuration includes a RAID 5, recreate the file cache.
Upgrading a RHEL 6.3 Single Server to MCS v2.9 7. If you are connecting to either an Avid ISIS or Avid NEXIS shared storage system, verify the shared storage client required for your environment and upgrade the client software if necessary. See “Upgrading the Avid Shared Storage Client Software”. 8. Test the system. See the “Verifying the Installation” chapter. If you experience any issues that you suspect could be related to the browser, see “Clearing the Browser Cache” on page 52 for assistance. 9.
Upgrading a RHEL 6.3 Cluster System to MCS v2.9 Upgrading a RHEL 6.3 Cluster System to MCS v2.9 The upgrade to MCS v2.9 on a RHEL v6.3 system involves a fresh installation of the operating system and of MediaCentral Platform Services.
Taking the Cluster Offline n Ensure that the master node is not in standby when you run the backup script. If it is in standby, only the system settings will be backed up – not the database. All other nodes can be in standby if desired. To back up the system settings: 1. Prepare the v2.9 MCS Installation USB Drive and connect it to the cluster’s master node. For details, see “Creating the MCS Installation USB Drive” in the MediaCentral Platform Services Installation and Configuration Guide. 2.
Upgrading the Software Upgrading the Software Complete this process for each cluster node (in any order). To upgrade the software: 1. Unmount the USB drive (if you have not already done so). For details, see “Mounting and Unmounting a USB Drive” on page 53. 2. If your configuration includes a RAID 5 array, delete and recreate the RAID 5. Destroying and re-creating the RAID 5 eliminates (in advance) any problems with cache permissions that can arise as a result of the RHEL update.
Restoring System Settings and Migrating the User Database Restoring System Settings and Migrating the User Database Now that RHEL v6.5 and MediaCentral Platform Services has been installed on the servers, the custom MCS settings must be restored from the USB backup. To restore the MCS settings: 1. Insert and Mount the USB drive on the master node. For details, see “Mounting and Unmounting a USB Drive” on page 53.
Additional Upgrade Procedures The system returns the following: Loading properties.. Fetching zone UUID.. Importing settings for zone UUID: 00000000-0000-0000-0000-000000000000 Importing setting_domain_class.. Importing setting_class.. Importing setting_instance.. SUCCESS 8. Repeat steps 1 through 6 on the slave and load balancing nodes to restore the system settings for each node. Step 7 is completed on the master node only.
Additional Upgrade Procedures Since some entries in the file are assigned UUIDs dynamically by Linux, the restore script does not place the fstab file in its original location. These UUIDs can change from one RHEL installation to the next, even if they underlying hardware remains the same. Therefore it is important to manually compare the contents of the restored file to the original file to ensure all system settings are migrated.
Additional Upgrade Procedures 16. If you added additional components or made any configuration changes, test the system again. See the “Verifying the Installation” chapter. If you experience any issues that you suspect could be related to the browser, see “Clearing the Browser Cache” on page 52 for assistance. 17. Once the cluster is running to your satisfaction, Avid suggests creating a final backup of the system settings and MCS database.
A Post Upgrade Notes The following notes may or may not apply to your configuration. Configuring MCS System Settings Updated versions of MediaCentral Platform Services often introduce new features and configuration options. Once the upgrade is complete, system administrators should review the MediaCentral UX System Settings and verify the values for all settings. For more information, see the “New Features” section of the MediaCentral Platform Services ReadMe.
Reconfiguring MCS for Upgrades from ICS v1.7 or Earlier Reconfiguring MCS for Use with Media Composer | Cloud 1. With the MCS server up and running, sign in to MediaCentral UX as a user with administratorlevel access. 2. Select System Settings from the Layout selector. 3. In the Settings pane, select MCPS > Player. 4. Media Composer | Cloud User: Enter the user name and password for the Cloud user.
Resetting Layouts After Upgrading from v2.0 to v2.9 10. Click Save to save your changes. The new MAM user is added to the User Tree, as a top-level user. 11. Ensure the System Settings on the Interplay | MAM system are configured to make use of the assigned user name and password. Example: See the Avid MediaCentral | UX Administration Guide for more information about user creation and role assignment. Resetting Layouts After Upgrading from v2.0 to v2.9 Three panes used in MediaCentral UX v2.
Clearing the Browser Cache Clearing the Browser Cache If the user experiences strange behavior or panes with stale data after upgrading MediaCentral, Avid recommends clearing the browser cache as an initial troubleshooting step. Once the client’s local cache is cleared, the browser is forced to obtain a new copy of the data from the upgraded MCS server.
B Mounting and Unmounting a USB Drive Refer to the following instructions to mount and unmount a USB drive from the MCS server. To mount a USB drive: 1. Connect the drive to an available USB port on the MCS server. 2. Through a Linux command prompt, verify the name of the device using the dmesg command: dmesg Information related to the USB drive will appear near the end of the output (close to the list of SCSI devices). The name of the USB drive is found inside square brackets (e.g. [sdc]).
n In Linux the cd command without any arguments takes you directly to the user’s home directory. If you are logged in as root, it takes you to the /root directory. You must be off the USB drive to unmount it. 2. Unmount the USB drive: umount /media/usb The USB drive is now available for use in another server. If you receive an error message indicating that the USB device is busy, it typically means that the Linux ISO on the USB drive was auto-mounted.
C Copying Software to the MCS Server At various times during the upgrade, you will need to copy software to the MCS server. The following two processes are provided as examples of how to complete this task: • Using a Windows system and a SFTP tool such as WinSCP • Connecting a USB drive directly to the server Copying Software Using WinSCP To copy software using WinSCP: 1. Download and install the WinSCP software on a Windows system that has network access to the MCS server.
Copying Software Using a USB Drive 7. Navigate to the /media folder on the MCS server in the right pane. 8. Create a directory structure for the MCS installer on the MCS server: a. Right-click in the right pane and select New > Directory. b. In the “New folder name” field, type installers and click OK. c. Double-click on the new installers folder in the right pane. d. When copying the MCS installer to the server, the software must be contained in its own folder.
D Deleting the RAID 5 Array When upgrading from one version of RHEL to another, such as an upgrade from RHEL v6.3 to RHEL v6.5, you must delete the RAID 5 prior to installing the new operating system and MCS software. Deleting and re-creating the RAID 5 eliminates (in advance) any problems with cache permissions that can arise as a result of the RHEL update. This section provides instructions for deleting the RAID 5.
Deleting the RAID 5 on an HP Gen8 4. At the “Welcome to HP Smart Storage Administrator” screen, select Smart Array P840 from the Available Devices menu on the left. 5. Use the Smart Array utility to delete the existing RAID5. Deleting the RAID 5 on an HP Gen8 To delete the RAID 5 on an HP Gen8 server: 1. Reboot the MCS server. 2. Press any key when prompted (space-bar recommended) to display the HP ProLiant “Option ROM” messages.
Deleting the RAID 5 on an HP Gen8 3. As soon as you see the prompt to enter the Option ROM Configuration for Arrays utility, press F8. n The prompt to press F8 can flash by very quickly. If you miss it, reboot and try again. 4. From the Main Menu, select Delete Logical Drive and press Enter.
Deleting the RAID 5 on an HP Gen8 5. Select the RAID 5 and press F8 to delete. 6. A warning appears asking you to confirm your choice. Press F3 to delete the RAID. 7. The RAID 5 is removed, and can now be re-created. For more information, see “Configuring the Onboard RAID” in the MediaCentral Platform Services Installation and Configuration Guide.
Deleting the RAID 5 on a Dell Server Deleting the RAID 5 on a Dell Server Deleting and recreating the RAID sets using the DELL BIOS utility does not erase data, nor does it delete existing partitions. That is, deleting a RAID does not delete the partition table — unless you initialize the disk at the same time. However, initializing the disk is a slow process.
Deleting the RAID 5 on a Dell Server 5. Select the “/dev/sda1” partition (the USB drive) and select OK. Leave the “Directory holding image” field blank. 6. Select No in the Setup Networking window and press Enter on the keyboard. Networking support is not required at this time. 7. Select “Skip” in the Rescue window and press Enter on the keyboard.
Deleting the RAID 5 on a Dell Server 8. At the next screen, choose “shell Start shell” and select OK. 9. At the system prompt, use the RHEL fdisk utility to examine the current partitions: fdisk -cul This command will display the available disks and partitions on the system. Since scroll bars will not be present in the rescue shell, use Shift-Pg Up and Shift-Pg Down to view the entire output.
Deleting the RAID 5 on a Dell Server Delete any partitions on the RAID 1 volume and the RAID 5 volume (if applicable). The remaining steps in this process will assume “sdb” is the RAID 1 and “sdc” is the RAID 5. 10. Use the RHEL fdisk utility to select the sdb volume: fdisk /dev/sdb 11. Type: p to print the current file system partition table. This will show you a similar output as the fdisk –cul command you used earlier. 12. Type: d to begin deleting the partitions. 13.
E Working with Media Index This section covers additional topics related to upgrades that include Media Index. Verifying the Media Index Status Before you upgrade a MediaCentral system configured with Media Index, you need to ensure that there is no active schema migration currently affecting Media Index. When you change a field set of the system (Interplay Production, iNEWS, or Interplay Archive) and the change propagates to Media Index, any existing data is automatically migrated to reflect the changes.
Stopping and Starting the PEBCo Agent Stopping and Starting the PEBCo Agent Some upgrade paths require the user to stop the indexing of the Interplay Production or Interplay Archive database prior to upgrading MediaCentral Platform Services. Once the upgrade is complete, the process must be manually restarted. Complete the single-server or cluster process below if it applies to your upgrade.
F Verifying System Configuration Files MediaCentral Platform Services includes multiple configuration files which govern the behavior of the system services. Some of these files can be modified to include custom modifications. During a system upgrade, the MCS installer checks the configuration files to determine if any custom modifications have been made. If no modifications are found, the files are overwritten.
7. Compare the contents of the files and migrate any custom modifications to the .rpmnew file. n Different versions of the same file might include additional variations beyond the custom modifications. Only migrate the custom data to the new file. If you are unsure what data should be migrated to the new file, contact Avid Customer Care. 8. Once the edits are complete, save and exit the vi session. Press and type: :wq 9. Rename the existing to .old: mv .
G Backing Up and Restoring System Settings and the ICS/MCS Database Before performing an upgrade it is recommended — and sometimes required — that you back up the ICS/MCS system settings and database using the system-backup script. Depending on the upgrade path, you may also be required to restore the data once the upgrade is complete. The system-backup script backs up important files and directories, including network settings, cluster configuration files, and more.
Completing a Backup Directory/File Description /etc/elasticsearch/ Settings related to Media Index /etc/elasticsearch-tribe/ /etc/pgpool-II/ Settings related to Multi-Zone configs /etc/rsyslog.d/ Configuration file pertaining to the ICPS service /etc/security/ /etc/snmp/ Simple Network Management Protocol (network monitor) /etc/sudoers.d/ List of users with sudo privileges /etc/sysconfig/ Network settings and more /etc/udev/rules.d/70-persistentnet.
Completing a Restore 3. Back up the ICS/MCS settings and database using the backup script: ./system-backup.sh -b In this case the script is used with the “-b” option which indicates you want to backup the data. n If the following message appears, it indicates that a copy of the pcmk.conf file already exists: File /root/pcmk.conf exists. Do you want to overwrite it (y/n)? This file contains information about the Corosync cluster.
Completing a Restore 3. If you made a renamed copy of the backup, restore the original folder name: cp -r sys-backup- sys-backup 4. Restore the ICS/MCS settings and database using the backup script: ./system-backup.sh -r In this case the script is used with the “-r” option which indicates you want to restore data. You are asked to confirm the restoration of the ICS/MCS database: Would you like to restore the database now? (y/n) 5. Type “y” (without the quotes) to confirm the action.
Avid Technical Support (USA) Product Information 75 Network Drive Burlington, MA 01803-2756 USA Visit the Online Support Center at www.avid.com/support For company and product information, visit us on the web at www.avid.
