1 / 13

Upgrade to Communication Manager 2.0 with Migration to Linux 8.0

Upgrade to Communication Manager 2.0 with Migration to Linux 8.0. Purpose:

mitchells
Download Presentation

Upgrade to Communication Manager 2.0 with Migration to Linux 8.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Upgrade to Communication Manager 2.0with Migration to Linux 8.0 Purpose: This presentation was prepared to help you solve problems that you might encounter when you migrate a media server that is running Communication Manager 1.X to a media server that is running Communication Manager 2.0. This presentation does not replace the installation and the upgrade manuals for the S8X00 media servers, but highlights a new Web interface function that is introduced with the addition of a patch to Communication Manager 1.X. The normal backup and restore methods do not apply to a migration. For more information, see the release notes for the migration patch.

  2. Migration process Beforeyou start the migration, you must perform the following actions, and procure the items that are listed. • Download the latest Migration Update for Communication Manager 2.0 from http://support.avaya.com.Updates are available for migrations to Communication Manager 2.0 from both Communication Manager 1.2 and 1.3 (Note: the update is not needed for 1.3.1). Ensure that you download the correct update. • Procure the following items: • A laptop computer that is running Windows 2000 or Windows XP • A valid FTP login, and a password on the customer’s FTP server • The S8X00 media server installation and upgrade manuals for Communication Manager 2.0 • The latest available version of the Unity CD-ROM for Communication Manager 2.0 • A USB CD-ROM drive for the S8300 media server, where applicable

  3. Backup process for the migration NOTE: The backup process for the migration is significantly different from the standard backup and restore process. This migration does not use the standard Backup/Restore Links. • Complete the following procedure to install the migration patch for the version of Communication Manager that you are migrating from, either 1.2 or 1.3 (Note: the patch is not needed for 1.3.1). • Use the Upload function in the Web browser to upload the patch file from your laptop computer to the S8X00 media server. • From the Linux command prompt, “cd” (change directory) to the FTP directory. • Run sudo patch_install <patch_filename> • Run sudo patch_apply <patch_filename> Communication Manager shuts down and restarts. • Exit and restart the browser. A new link, Linux Migration – Backup, is added in the Server Configuration and Upgrades section of the Web interface. To migrate to Communication Manager 2.0, you must use this link to perform a successful migration backup.

  4. Web interface after the update is applied New Web link for the migration backup

  5. The next several steps identify the various screens • that the Linux migration backup uses: • Click the link Linux Migration – Backup to display the screen shown. • Note the warning that is shown at the top of the page. • Perform one of the following actions: • Click Initiate new backup, and then click Submit to start the backup. • Click Display status, and then click Submit to see the status. Linux migration – backup steps

  6. Type the login of the FTP server. • Type the password for that login. • Type the host name or the IP address of the server. • Type the directory or the directory path from the root of the FTP server. A “/” saves the file into the root directory of the FTP server. • NOTE: If you are performing this migration backup on a server that is running Communication Manager 2.0, you must set the Directory field to /pub. Security restrictions on the FTP server that is running Communication Manager 2.0 block uploads to the ~ftp/var/home/ftp directory. • Click Submit to start the backup. FTP authentication

  7. Click Status to see the status of the backup. The system displays the Backup History screen (next page). Backup status

  8. Click the current backup set. The first entry is the most current backup. Backup history

  9. The output shows: • That the backup finished, and completed successfully. • NOTE: If the backup is not finished, click Refresh to update the screen. • The backup location information. • A message that the backup excluded some files or directories. This is an expected and normal message. • The backup filename, which is stored in the following format: • upgrade-2.0_<hostname>_<time of day>_<date of backup>.tar.gz Linux migration – backup status

  10. Communication Manager 2.0 Web interface • Perform the following steps after the system is completely migrated to Communication Manager 2.0: • Apply any available Communication Manager Updates. • Use the link Linux Migration (Backup/Restore)to restore the backup that you made before the migration.

  11. Restore FTP Screen Restore FTP • In the Restore Method area: • Click FTP. • Type the appropriate FTP server login, password, IP address, and directory path. • Click Submit to start the restore. • Continue with the next screen.

  12. Under File Name, click the name of the backup file to restore. • Note: If more than one backup file is listed, ensure that you select the correct file. • Select both check boxes to force the restore. • Click Restore. Restore file selection

  13. The warning “backup: 60:” indicates the version that you were migrating from. The “backup: 0:” message indicates the successful restore of the files to the server that is running Communication Manager 2.0. Successful restore

More Related