Upgrading Avaya Aura Messaging

Transcription

1 Upgrading Avaya Aura Messaging 6.1 March 2012

2 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on its Hardware and Software ( Product(s) ). Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support Web site: Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. Hardware means the standard hardware originally sold by Avaya and ultimately utilized by End User. License types Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Named User License (NU). End User may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a Named User may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). Customer may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). (see Third-party Components for more information). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or Hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the 2 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

3 Third Party Terms that apply to them is available on the Avaya Support Web site: Preventing Toll Fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud Intervention If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya, Avaya one-x, Octel, and Avaya Aura are registered trademarks of Avaya Inc. All non-avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvalds. Downloading Documentation For the most current versions of Documentation, see the Avaya Support Web site: Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your Product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site: Upgrading Avaya Aura Messaging R6.1 March

4 4 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments?

5 Contents Chapter 1: Introduction... 7 Messaging upgrades... 7 Messaging templates overview... 7 Messaging servers overview... 8 Pre-upgrade requirements... 9 Server specifications Pre-upgrade data gathering Messaging documentation Chapter 2: Upgrading from Release 6.0 or to Release 6.1 for single-server configuration Overview Checklist Performing pre-upgrade tasks Verifying the version of System Platform Viewing current alarms Current Alarms field descriptions Backing up the System Platform Backing up the Messaging system Recording the operator (live attendant) properties Recording the installed language packs Performing upgrade tasks Logging in to the System Platform Web Console Upgrading the System Platform Platform upgrade field descriptions Upgrading the Messaging system Search Local and Remote Template field descriptions Installing patches Logging in to Messaging Setting operator (live attendant) properties Installing language pack Installing the voice message form Chapter 3: Upgrading from Release 6.0 or to Release 6.1 for multi-server configuration Overview Considerations for muti-server upgrades Checklist Upgrading the Messaging storage server Upgrading the Messaging application servers Index Upgrading Avaya Aura Messaging R6.1 March

6 6 Upgrading Avaya Aura Messaging R6.1 March 2012

7 Chapter 1: Introduction Messaging upgrades This guide provides information about the following: Upgrading Avaya Aura System Platform. Upgrading Avaya Aura Messaging from Release 6.0 or to Release 6.1 for singleserver and multi-server configuration on the following servers. - Avaya S8800 Server - Dell PowerEdge R610 Server - HP ProLiant DL360 G7 Server Messaging templates overview Avaya offers product-specific templates to install different products on System Platform. A template is a definition of a set of one or more applications to be installed on System Platform. Messaging offers the following templates: Msg_Standard. The Messaging template for the standard server. Msg_4x146GB_HDD. The Messaging template for the high capacity storage server. You can upgrade the Messaging system from one of the following locations. Avaya Downloads (PLDS): The template files are located on the Avaya PLDS Web site. The list contains all the templates to which your company is entitled. Each line in the list begins with the sold-to number that enables you to select the appropriate template for your site. You can hold the mouse pointer over the selection to view more information about the sold-to number. HTTP: You can copy the template files to an http server and install the template files from the http server to several System Platform servers. You must specify the template URL for the server. SP Server: You can copy the template files to the /vsp-template directory in the Console Domain of the System Platform server. Upgrading Avaya Aura Messaging R6.1 March

8 Introduction SP CD/DVD: The template files are located in a CD/DVD. This may be the CD/DVD supplied with the system or one created onsite. SP USB Disk: The template files are located in a USB flash drive connected to the server. Format of the USB flash drive must be ext3. You should consider carefully which location works best in a specific scenario. For more information, contact an Avaya-certified business partner or an Avaya technician. Messaging servers overview Messaging supports the following Avaya-provided hardware: Servers Dell PowerEdge R610 Server HP ProLiant DL360 G7 Server S8800 Server S8730 Server Notes For the server installation instructions, see Installing the Dell PowerEdge R610 Server. For the new installation of Messaging, see Implementing Avaya Aura Messaging. For the server installation instructions, see Installing the HP DL360 G7 Server. For the new installation of Messaging, see Implementing Avaya Aura Messaging. If you are an existing customer of Modular Messaging, you can install Messaging on your existing S8800 server after upgrading the S8800 server with the upgrade kit. After upgrading your S8800 server, refer to Implementing Avaya Aura Messaging for the installation of Messaging. If you are an existing customer of Modular Messaging, you can install Messaging on your existing S8730 server after upgrading the S8730 server with the required memory and hard drive upgrades. For more information on S8730 server upgrade, see Maintaining the S8730 server for Modular Messaging. After upgrading your S8730 server, refer to Implementing Avaya Aura Messaging for the installation of Messaging. For more information on supported hardware configuration, see Server specifications on page Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

9 Pre-upgrade requirements Pre-upgrade requirements Best practices For a successful upgrade, it is important that you are prepared well in advance. Make sure that a good current backup is onsite prior to attempting an upgrade. Before performing an upgrade, ensure that you have the following: CD/DVD of the current software release and/or Operating System. Current Service Pack on application. The required applications on the computer to perform the upgrade. Monitor, Mouse, and appropriate keyboard to connect to the server. Recent backup of configuration files. Paper copy of IP addresses and Naming information. Paper copy of worksheets. By instituting this best practice, you have the highest probability for a successful restore if for any reason you need to revert back to the initial software release. Hardware requirements You need the following hardware to complete the upgrade process: One of the following servers running Messaging Release 6.0 or Release S8800 Server - Dell PowerEdge R610 Server - HP ProLiant DL360 G7 Server For more information on server specification, see Server specifications on page 11. Required Ethernet CAT5 cables. Blank DVDs on which you burn the iso images. Software requirements Before you upgrade Messaging, confirm that the version of System Platform you are running is compatible with Messaging Release 6.1. To obtain information on the supported version, see Avaya Aura Messaging Release Notes on the Avaya Support Web site at P0792. To verify currently installed version of System Platform, see Verifying the version of System Platform on page 19. If the software on your system does not match the software components in the release notes, you must download the needed software before proceeding. Upgrading Avaya Aura Messaging R6.1 March

10 Introduction You need to download the following software: System Platform from the Product Licensing and Delivery System (PLDS). For more information, refer to the Software download section of Implementing Avaya Aura Messaging. The Messaging templates from PLDS. For more information, refer to the Software download section of Implementing Avaya Aura Messaging. Service packs available on the Avaya Support Web site, Products/P0792. After upgrading the System Platform software, you must update the System Platform software with the latest approved patches and service packs. Ensure that these patches and service packs are verified for use with Messaging. You can download the latest patches from the Avaya support Web site. For information on the latest patches, see Avaya Aura Messaging Release Notes available on the Avaya support Web site, For more information on downloading and installing patches and Service Packs, see Installing patches on page 35. Alarms Before you upgrade Messaging, make sure that there are no active alarms in the system. To view current alarms, see Viewing current alarms on page 19. For Messaging alarms repair procedure, see Avaya Aura Messaging Alarms and Events. For System Platform alarms and events, see Administering Avaya Aura System Platform. Language packs Record the currently installed language packs that you need to re-install after the upgrade process. For more information, see Recording the installed language packs on page 26. Download the required language packs before the upgrade. You can download language packs from Ensure that these language packs are compatible with the software that you are upgrading. See Administering Avaya Aura Messaging for information about the language packs. Application requirements You must install the following applications on your computer: Internet Explorer 7.x browser. Firefox 2.x or 3.x browser (supported by System Platform only). A Secure Shell application such as PuTTY. 10 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

11 Server specifications Server specifications The following servers support Messaging. Table 1: Dell PowerEdge R610 Server Names of components Standard Server High Capacity Storage Server Chassis 1U 1U Processor speed E Ghz 4-core E Ghz 4-core Number of processors 1 1 System memory 12 GB 12 GB Ethernet ports 2 2 RAID type RAID 5 RAID 5 Disk 3 x 146 GB 10k 4 x 146 GB 10k Standard power supply 1 x 502 W 2 x 502 W Table 2: HP ProLiant DL360 G7 Server Names of components Standard Server High Capacity Storage Server Chassis 1U 1U Processor speed E Ghz 4-core E Ghz 4-core Number of processors 1 1 System memory 12 GB 12 GB Ethernet ports 2 2 RAID type RAID 5 RAID 5 Disk 3 x 146 GB 10k 4 x 146 GB 10k Standard power supply 1 x 460 W 2 x 460 W Table 3: S8800 Server Names of components Standard Server High Capacity Storage Server Chassis 1U 1U Upgrading Avaya Aura Messaging R6.1 March

12 Introduction Names of components Standard Server High Capacity Storage Server Processor speed E5520 Quad-core 2.26 Ghz processor Number of processors 1 1 System memory 12 GB 12 GB Ethernet ports 2 2 RAID type RAID 5 RAID 5 Disk 3 x 146 GB 10k rpm SAS hard disk drives E5520 Quad-core 2.26 Ghz processor 4 x 146 GB 15k rpm SAS hard disk drives Standard power supply Dual power supply Dual power supplies Table 4: S8730 Server Note: For new installation only. For more information, see Messaging servers overview on page 8. Names of components Standard Server High Capacity Storage Server Processor speed AMD 2352 QUAD core processor System memory 12 GB 12 GB Ethernet ports 2 2 RAID type RAID 5 RAID 5 Disk Standard power supply 3 x 146 GB 15k 2.5 inch SAS hot-plug hard disk drives 800 Watt, CE Mark Compliant hot-plug power supply AMD 2352 QUAD core processor 4 x 146 GB 15k 2.5 inch SAS hot-plug hard disk drives 800 Watt, CE Mark Compliant hot-plug power supply Additional hot-plug redundant power supply Pre-upgrade data gathering Before you upgrade Messaging: 12 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

13 Messaging documentation Distribute the appropriate checklists and worksheets to your network administrator. Verify that your network infrastructure fulfills the hardware and software prerequisites. Complete the infrastructure and upgrade worksheets. Messaging documentation You can download the document you need from the Avaya Support Web site at support.avaya.com/css/products/p0792. The following table lists all the documents pertaining to Messaging: Planning Title Description Audience Avaya Aura Messaging Overview and Planning Avaya Aura Messaging Security Design Installation Implementing Avaya Aura Messaging Upgrading Avaya Aura Messaging Contains information on the concepts underlying Messaging. Topics include features, components, addressing, telephony, deployment options, and planning data. Discusses the multilayer security philosophy of Avaya, network security integration, and toll fraud security resources. Elaborates on the security issues that customers must consider before designing and implementing a corporate security strategy into the Avaya enterprise. Also provides recommendations on maintaining and monitoring security in an Avaya enterprise. Provides procedures to install Messaging. Topics include installing System Platform, Messaging, and patches. Also contains Secure Access Link configuration procedures, installation prerequisites, planning forms, and checklists. Explains procedures for upgrading Messaging from Releases 6.0 or Release to Release 6.1 for single-server and multiserver configuration. All Planner, Administrator, Technician Technician Technician Upgrading Avaya Aura Messaging R6.1 March

14 Introduction Installing the Dell PowerEdge R610 Server Title Description Audience Installing the HP DL360 G7 Server Maintenance Maintaining the Avaya S8800 1U Server for Avaya Aura Messaging Maintaining and Troubleshooting the Dell PowerEdge R610 Server Maintaining and Troubleshooting the HP ProLiant DL360 G7 Server Administration Administering Avaya Aura Messaging Help for Administrators Job aid for Administering Avaya Aura Messaging End user Using Avaya Aura Messaging Describes the components, specifications, and configurations of the Dell PowerEdge R610 server. Describes the components, specifications, and configurations of the HP DL360 G7 server. Illustrates S8800 support for Messaging. Also describes the procedure required for multiple maintenance tasks for the S8800 1U model. Describes how to add, replace, or repair the Dell PowerEdge R610 hardware components. Also provides information about LCD status messages. Describes how to add, replace, or repair the HP DL360 G7 hardware components. Describes the administration of the Messaging system. Provides information about administering Messaging, administering server, managing software, and using diagnostic tools. Contains online help topics that explain the procedures to administer the application server and the storage server. Provides common day-to-day administration procedures for Messaging. The topics include reboot procedures, checking application and storage alarms, adding and deleting mailboxes, getting performance indicators, and unlocking, resetting, and changing mailbox passwords. Describes common end-user tasks, such as initial setup and using the User Preferences and Messaging toolbar. Technician Technician Technician Technician Technician Administrator Administrator Administrator User 14 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments?

15 Messaging documentation Title Description Audience Avaya Aura Messaging Quick Reference (Aria) Avaya Aura Messaging Quick Reference (AUDIX) Using Avaya Aura Messaging Online Help Additional resources Documentation library Describes how to perform common tasks and use Messaging features through the Aria telephone user interface. Describes how to perform common tasks and use Messaging features through the AUDIX telephone user interface. Explains the common end-user tasks, such as initial setup and using the User Preferences and Messaging toolbar. Provides the entire documentation set for Messaging that includes administration, implementation, general reference, and user information. User User User All Upgrading Avaya Aura Messaging R6.1 March

16 Introduction 16 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments?

17 Chapter 2: Upgrading from Release 6.0 or to Release 6.1 for singleserver configuration Overview This section describes the procedure to upgrade the Messaging software from Release 6.0 or to Release 6.1 for single-server configuration. You can perform this software-only upgrade using one of the following methods: Onsite by connecting the laptop to the services port on the server. Remotely by accessing the server through the corporate network. The upgrade procedure involves: Upgrading System Platform and the Messaging template. Installing the required patches. Checklist Task References Notes Download the required documentation. Gather pre-upgrade data. Verify the version of System Platform. Verify that there are no active alarms in the system. See Messaging documentation on page 13. See Pre-upgrade data gathering on page 12. See Verifying the version of System Platform on page 19. See Upgrading Avaya Aura Messaging R6.1 March

18 Upgrading from Release 6.0 or to Release 6.1 for single-server configuration Task References Notes To view current alarms, see Viewing current alarms on page 19. For Messaging alarms repair procedure, see Avaya Aura Messaging Alarms and Events. For System Platform alarms and events, see Administering Avaya Aura System Platform. Obtain System Platform and Messaging software. Backup the System Platform configuration information. Backup Messaging system files and application files. Record the operator (live attendant) properties. Record the currently installed language packs that you need to re-install after the upgrade process. Upgrade the System Platform software. Upgrade the Messaging software. Install Communication Manager patches. Install Messaging patches. For more information, see the Software download section of Implementing Avaya Aura Messaging. See Backing up the System Platform on page 21. See Backing up system files on page 23. Backing up application files on page 22. See Recording the operator (live attendant) properties on page 25. See Recording the installed language packs on page 26. See Upgrading the System Platform on page 27. See Upgrading the Messaging system on page 31. See Patch installation overview on page 35. See Patch installation overview on page Upgrading Avaya Aura Messaging R6.1 March 2012 Comments?

19 Performing pre-upgrade tasks Task References Notes Set operator (live attendant) properties. Install language pack Install the voice message form. See Setting operator (live attendant) properties on page 41. See Installing language pack on page 42. See Installing the voice message form on page 43. Performing pre-upgrade tasks Verifying the version of System Platform Procedure 1. Log on to the System Platform Web Console. 2. Click Virtual Machine Management > Manage. 3. Verify the version of Domain-0 and cdom. Viewing current alarms Procedure 1. Log on to the System Management Interface. For more information, see Logging in to Messaging on page On the Administration menu, click Server (Maintenance) > Alarms > Current Alarms. 3. Check if there are alarms in the Messaging Alarms section. 4. Resolve if there are any active alarms. For Messaging alarms repair procedure, see Avaya Aura Messaging Alarms and Events. Upgrading Avaya Aura Messaging R6.1 March

20 Upgrading from Release 6.0 or to Release 6.1 for single-server configuration For System Platform alarms and events, see Administering Avaya Aura System Platform. Current Alarms field descriptions Field Name Product ID Messaging Product ID ID APP Source EvtID Lvl Ack Location Description A number that uniquely identifies the server. A number that uniquely identifies the Messaging product. A unique identification number assigned to the alarm. The name of the application. The abbreviated name of the software module that generated the alarm. EL: Enhanced List Application IM: Internet Messaging LD: LDAP MT: Maintenance SM: Station Manager VM: Messaging VP: Voice Platform The event identification number for each alarm that is used to identify a particular event from a source that generated the alarm. The level of the alarm. MIN MAJ WARN Displays a Y (yes) or N (no) to indicate whether the alarm has been acknowledged by the Initialization and Administration System (INADS). The location where the alarm originated. 20 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

21 Performing pre-upgrade tasks Field Name Date Description A time stamp assigned to the alarm at the time of origination. Backing up the System Platform Backing up the System Platform About this task Use this procedure to back up configuration information for System Platform and the Messaging template. Use the System Platform Web Console to back up the files. Important: The backup file size can reach 3 GB. Ensure that you have that much free space at the location where you are storing the backup archive. Procedure 1. Log on to the System Platform Web Console. 2. Click Server Management > Backup/Restore. 3. Click Backup. 4. On the Backup page, select the Backup Now option to start the backup operation immediately. 5. Select where to store or send the backup files: Local: Stores the backup archive file on System Platform in the /vspdata/ backup/archive directory. SFTP: Stores the backup archive file on the designated SFTP host server as well as on the System Platform server. Sends the backup archive file to the address that you specify as well as stores the file on the System Platform server. Note: Avaya does not recommend that you use the option due to the large size of backup files. The backup file size can reach 3 GB. 6. Enter other information as appropriate. 7. Click Backup Now. Upgrading Avaya Aura Messaging R6.1 March

22 Upgrading from Release 6.0 or to Release 6.1 for single-server configuration Backup field descriptions Field Names Backup Method Descriptions Select a location to send the backup file: Local: Stores the backup archive file on System Platform in the /vspdata/backup/ archive directory. SFTP: Stores the backup archive file on the designated SFTP host server as well as on the System Platform server. Enter the hostname, directory, user name, and password for the SFTP server. Sends the backup archive file to the address that you specify as well as stores the file on the System Platform server. Enter the address and the server address of the recipient. Backup Now Starts the backup operation. Backing up the Messaging system Backing up application files Before you begin Your IT network includes an FTP server for storing the backed-up data. Procedure 1. Log on to the System Management Interface. For more information, see Logging in to Messaging on page On the Administration menu, click Messaging > Utilities > Stop Messaging. The system displays the Stop Messaging Software Web page and begins a 3 minute countdown to the shutdown routine. 3. If you want to initiate a delayed shutdown, click Stop. 4. On the Administration menu, click Server (Maintenance) > Data Backup/Restore > Backup Now. 5. Under the Data Sets heading, select Messaging Application. 22 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

23 Performing pre-upgrade tasks 6. Under the Backup Method heading, click Network Device and then choose a location for the backed-up files by completing the following fields: Method User Name Password Host Name: Enter the host name or IP address. Directory: Enter the full directory path where your backup will be stored. You will need this information when you restore the data set to other servers. 7. Click Start Backup. For more information, see Backup Now field descriptions on page 24. Backing up system files Procedure 1. On the Administration menu, click Server (Maintenance) > Data Backup/Restore > Backup Now. The system displays the Backup Now Web page. 2. Under the Data Sets heading, select Specify Data Sets. Then select: Server and System Files Security File Messaging 3. Under the Messaging heading, select: Messaging Application, Translations, Names, and Messages. 4. Under the Backup Method heading, select Network Device and then complete the following fields: a. Method b. User Name c. Password d. Host Name e. Directory 5. Under the Encryption heading, select Encrypt backup using pass phrase and then enter a phrase. 6. Under the Download Size heading, enter a value from 1 to 200 to limit the size of a transferable file over the network, and ensure a successful backup of the Messaging data. Upgrading Avaya Aura Messaging R6.1 March

24 Upgrading from Release 6.0 or to Release 6.1 for single-server configuration Ensure that the number you enter is less than or equal to the maximum size that the network allows for transferring files. The system creates a backup image that can have more than one file. No files can exceed the size that you specify. 7. Click Start Backup. For more information, see Backup Now field descriptions on page 24. Backup Now field descriptions Settings Data Set Description Indicates the data sets to be backed up. The available options are: Server and System Files: Back up the variable information to configure the server for a particular installation. Security File: Back up the variable information to maintain security for the server. Messaging Back up one of the following Messaging options: - Messaging Application, Translations and Messages - Messaging Application, Translations, Names, and Messages - Messaging Application, Translations and Names - Messaging Application and Translations - Messaging Application Full Backup Backup Method A full backup includes security data sets and files that configure both the Linux operating system and the applications. A Full Backup does not include any of the Messaging data sets. The following methods are available for backup: SCP: A means of securely transferring computer files between a local and a 24 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

25 Performing pre-upgrade tasks Settings Description remote host, or between two remote hosts, using the Secure Shell (SSH) protocol. FTP: When you choose this selection, you must also enter a user name, password, host name, and directory. The default directory for backup data on the FTP server is /var/home/ftp. If you want to use the default directory, enter a forward slash (/) in the directory field. You must start the FTP server before backing up data. SFTP: A network protocol that provides file transfers over data streams. The SFTP client is added to all Linux platforms. Encryption Download Size Defines if you have to encrypt the backup data. The pass phrase can be an arbitrary string of 15 to 256 characters. The pass phrase can contain any characters except the following: single quote ('), amersand (&), back slash (\ ), single back quote (`), quote ("), percent sign (%). Indicates the maximum file transfer size in the Download size for the data being transferred field. The download size ensures the backup of large data (such as the backups that contain messages) over the networks that limit the size of a transferable file. The maximum size of an individual backup file is the value specified in the Download size for the data being transferred field multiplied by 100 MB. Valid values range from 1 to 200, indicating 100 MB to 20 GB. The default value is 5 (500 MB). The specified value in the Download size for the data being transferred field should be less than or equal to the maximum file transfer size allowed on the network. Recording the operator (live attendant) properties About this task Before upgrading the Messaging system, record the currently set properties for operator that you need to re-enter after the upgrade process. Upgrading Avaya Aura Messaging R6.1 March

26 Upgrading from Release 6.0 or to Release 6.1 for single-server configuration Procedure 1. Log on to the System Management Interface. For more information, see Logging in to Messaging on page On the Administration menu, click Messaging > Server Settings (Application) > Attendant/Operator. 3. Record the currently set properties for operator. From the Release 6.1, these properties are managed from Messaging > Messaging System (Storage) > Sites. Note: If a site is served by multiple application servers (that is an application server cluster), this setting are identical on all of them. You only need to record it from one of the application servers in the cluster. Recording the installed language packs About this task Before upgrading the Messaging system, record the currently installed language packs that you need to re-install after the upgrade process. Procedure 1. Log on to the System Management Interface. For more information, see Logging in to Messaging on page On the Administration menu, click Messaging > Server Settings (Application) > Languages. 3. From the Language Packs: Installed Languages, record the name of all installed language packs. Performing upgrade tasks Logging in to the System Platform Web Console You can gain access to the System Platform Web Console from a Web browser on your laptop or another computer connected to the same network as the System Platform server. 26 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

27 Performing upgrade tasks Before you begin The IP address of the Console Domain that you configured during the installation of System Platform. A valid user ID. If you use an Avaya services login that is Access Security Gateway (ASG)- protected, you must have an ASG tool to generate a response for the challenge that is generated by the login page. Many ASG tools are available such as Avaya Token Mobile, Avaya Web Mobile, and Site Manager. The first two ASG tools must be able to reach the ASG manager servers behind the Avaya firewall. An Avaya Services representative will use Site Manager to pull the keys specific to a site before visiting that site. At the site, the Avaya Services representative will use those keys to generate the response for the challenge generated by the login page. Procedure 1. Open a compatible Internet browser on your computer. System Platform supports Microsoft Internet Explorer 7 and Firefox 2 and Type the URL of the Console Domain in the Internet browser. For example: The Console Domain is a secure site. If you get a certificate error, then follow the instructions in your browser to install a valid certificate on your computer. 3. Enter a valid User ID. Use the advanced administrator login. 4. Click Continue. 5. Enter a valid password. 6. Click Log On. The system displays the License Terms page when you log in for the first time. 7. Click I Accept to accept the end user license agreement. The system displays the Virtual Machine List page in the System Platform Web Console. Upgrading the System Platform Procedure 1. Log on to the System Platform Web Console. 2. Click Server Management > Platform Upgrade. The system displays the Platform Upgrade page. 3. From the Upgrade Platform From drop-down list, select the medium to search for the System Platform image files for the platform upgrade. The system searches for Upgrading Avaya Aura Messaging R6.1 March

28 Upgrading from Release 6.0 or to Release 6.1 for single-server configuration an upgrade description file that has a.ovf extension. The following table lists the available options. If you select Avaya Downloads (PLDS) HTTP SP Server SP CD/DVD SP USB Disk then provide SSO Login and SSO Password and then click Search. specify the Platform Upgrade URL and click Search. If the upgrade files are located in a different server, configure a proxy depending on your network. Click Configure Proxy to specify a proxy server if required. specify the Platform Upgrade URL to download the platform upgrade files located in the /vsp-template directory in the Console Domain of the System Platform server and click Search. click Search. click Search. For more information, see Platform upgrade field descriptions on page Select the appropriate description file for the platform upgrade, and then click Select. The system displays the version and additional information for the current and the new platform (System Domain and Console Domain) on the Platform Upgrade page. Important: As part of the upgrade process, the System Domain and Console Domain are rebooted, and consequently, Messaging will be rebooted. During the platform upgrade process, all operations on the System Platform Web Console are blocked. All links (including menu items) are disabled until the system is booted up into the new platform for you to commit or rollback the upgrade. 5. On the Platform Upgrade page, click Upgrade. A dialog box appears to confirm that the template has been qualified for the platform version that you are about to upgrade and both System Domain and System Platform Web Console will reboot on completing the upgrade 6. In the dialog box, click OK to confirm the upgrade. The upgrade process starts and the system displays the Platform Upgrade workflow status page. During the upgrade process, the System Domain (Domain-0) and the Console Domain are rebooted. Therefore, the Platform Upgrade workflow status page does not show any updates until it reboots in the new Console Domain. After the Web 28 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

29 Performing upgrade tasks Console is rebooted, the system automatically redirects you to the login page. The upgrade process takes approximately 20 minutes. 7. Log on to the System Platform Web Console. You can view the time remaining for Auto Rollback of the Platform Upgrade on the Commit or Rollback platform upgrade page. You can also check the Web Console to ensure that the upgrade process is running alright. 8. On the Commit or Rollback platform upgrade page, do one of the following: Click Commit to continue the upgrade process by committing to the newlyupgraded platform. You are allowed a 4-hour period to log in to the System Platform Web Console. If you do not login during this period, the system will reboot using the previous release of System Platform. If a user logs in to System Platform Web Console within the 4-hour period, the user can be sure that System Platform is reachable and the timer is cancelled. However, you still need to verify and commit the upgrade. Click Rollback to cancel the upgrade process and go back to the previous version of the software. Next steps Update System Platform with the latest approved patches and service packs. Ensure that these patches and service packs are verified for use with Messaging. You can download the latest patches from the Avaya support Web site. Go to Products/P0792 For information on the latest patches, see Avaya Aura Messaging Release Notes available on the Avaya support Web site, P0792. For more information on downloading and installing patches and Service Packs, see Installing patches on page 35. Upgrade the Messaging system. See Upgrading the Messaging system on page 31. Platform upgrade field descriptions Names Upgrade Platform From Descriptions Lets you select a platform upgrade file for the platform upgrade from the available options. The available options are: Avaya Downloads (PLDS) To download the platform upgrade files located on the Avaya Product Licensing Upgrading Avaya Aura Messaging R6.1 March

30 Upgrading from Release 6.0 or to Release 6.1 for single-server configuration Names Descriptions and Delivery System (PLDS) Web site, you must enter an Avaya SSO login and password to access this site. The list on this site contains all the platform upgrade files to which your company is entitled. Each line in the list begins with the sold-to number. Using the sold-to number, you can select the appropriate platform upgrade files for your site. To view more information about the sold-to number, hold the mouse pointer over the selection. HTTP To download the platform upgrade files located on an HTTP server, you must enter the Platform Upgrade URL. SP Server To download the platform upgrade files located in the /vsp-template directory in the Console Domain of the System Platform server, you must specify the Platform Upgrade URL. You must copy the platform upgrade files in this directory using a file transfer program and change their permissions as follows: chmod 644 <files-copied> SP CD/DVD To download the platform upgrade files located on a CD-ROM or DVD in the CD/ DVD drive on the System Platform server. SP USB Disk To download the platform upgrade files located on a USB flash drive connected to the server, format the USB flash drive as ext3. SSO Login SSO Password Platform Upgrade URL The log-in ID to log on to Single Sign On. The system activates this field only when you select the Avaya Downloads (PLDS) option to search for a platform upgrade file. The password for Single Sign On. The system activates this field only when you select the Avaya Downloads (PLDS) option to search for a platform upgrade file. The URL of the server where the template files are located. The system activates this 30 Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com

31 Performing upgrade tasks Names Descriptions field only when you select the HTTP or SP Server option to search for a platform upgrade file. Upgrading the Messaging system Before you begin You must confirm that the version of System Platform you are running is compatible with Messaging Release To obtain information on the supported version, see Avaya Aura Messaging Release Notes on the Avaya Support Web site at Products/P To verify the currently installed version of System Platform, see Verifying the version of System Platform on page 19. Update System Platform with the latest approved patches and service packs. Ensure that these patches and service packs are verified for use with Messaging. You can download the latest patches from the Avaya support Web site. Go to Products/P0792 For information on the latest patches, see Avaya Aura Messaging Release Notes available on the Avaya support Web site, P0792. For more information on downloading and installing patches and Service Packs, see Installing patches on page 35. Record the currently installed language packs that you need to re-install after the upgrade process. For more information, see Recording the installed language packs on page 26. Procedure 1. Log on to the System Platform Web Console. 2. Click Virtual Machine Management > Solution Template. The system displays the Search Local and Remote Template page. 3. From the Install Template From drop-down list, select the medium to search for the Messaging image files. The following table lists the available options. If you select Avaya Downloads (PLDS) HTTP then provide SSO Login and SSO Password and then click Upgrade. specify the Template Location and click Upgrade. Upgrading Avaya Aura Messaging R6.1 March

32 Upgrading from Release 6.0 or to Release 6.1 for single-server configuration If you select SP Server SP CD/DVD SP USB Disk then If the template files are located in a different server, you may be required to configure a proxy depending on your network. Click Configure Proxy to specify a proxy server if required. specify the Template Location and click Upgrade. click Upgrade. click Upgrade. For more information, see Search Local and Remote Template field descriptions on page Click Upgrade to display a list of template descriptor files (each available template has exactly one template descriptor file). A dialog bog appears to confirm the upgrade. 5. Click OK in the dialog box to confirm the upgrade. The system displays the Select Template page with the current template installed. 6. From the Select Template list, select the template that matches the current system configuration. Select one of the following displayed templates: Msg_Standard. The Messaging template for the standard server. Msg_4x146GB_HDD. The Messaging template for the high capacity storage server. 7. Click Select. 8. On the Template Details page, click Upgrade. The system displays the Template Network Configuration page that shows network configuration you have entered while installing System Platform. 9. Verify the network configuration and click Save to continue. The system displays the Template Details page that lists the system properties you have entered while installing Messaging. 10. Verify the system properties. a. MSG IPv4 Address: IPv4 address of the Messaging virtual machine. b. MSG IPv6 Address: Messaging does not support IPv6. c. MSG Hostname : Host name must be the Fully Qualified Domain Name (FQDN) of the Messaging virtual machine. 11. Click Upgrade. The Template Installation page displays the progress of the template installation. 12. When the System Platform Web Console prompts to Commit or RollBack the installation, verify that the Messaging system is up and running before proceeding to Step Upgrading Avaya Aura Messaging R6.1 March 2012 Comments? infodev@avaya.com