Using Avaya Call Management

System LAN Backup

Release 19.2
Issue 1
March 2021
© 2020-2021 Avaya Inc. OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT
All Rights Reserved. EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM
ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA
Notice CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL
While reasonable efforts have been made to ensure that the information in this ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE
document is complete and accurate at the time of printing, Avaya assumes no SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
liability for any errors. Avaya reserves the right to make changes and USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,YOU, ON
corrections to the information in this document without the obligation to notify BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE
any person or organization of such changes. INSTALLING, DOWNLOADING OR USING THE SOFTWARE
(HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END
Documentation disclaimer USER”), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
“Documentation” means information published in varying mediums which may BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
include product information, operating instructions and performance APPLICABLE AVAYA AFFILIATE (“AVAYA”).
specifications that are generally made available to users of products. Avaya grants You a license within the scope of the license types described
Documentation does not include marketing materials. Avaya shall not be below, with the exception of Heritage Nortel Software, for which the scope of
responsible for any modifications, additions, or deletions to the original the license is detailed below. Where the order documentation does not
published version of Documentation unless such modifications, additions, or expressly identify a license type, the applicable license will be a Designated
deletions were performed by or on the express behalf of Avaya. End User System License as set forth below in the Designated System(s) License (DS)
agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and section as applicable. The applicable number of licenses and units of capacity
employees against all claims, lawsuits, demands and judgments arising out of, for which the license is granted will be one (1), unless a different number of
or in connection with, subsequent modifications, additions or deletions to this licenses or units of capacity is specified in the documentation or other materials
documentation, to the extent made by End User. available to You. “Software” means computer programs in object code,
provided by Avaya or an Avaya Channel Partner, whether as stand-alone
Link disclaimer products, pre-installed on hardware products, and any upgrades, updates,
Avaya is not responsible for the contents or reliability of any linked websites patches, bug fixes, or modified versions thereto. “Designated Processor”
referenced within this site or Documentation provided by Avaya. Avaya is not means a single stand-alone computing device. “Server” means a set of
responsible for the accuracy of any information, statement or content provided Designated Processors that hosts (physically or virtually) a software application
on these sites and does not necessarily endorse the products, services, or to be accessed by multiple users. “Instance” means a single copy of the
information described or offered within them. Avaya does not guarantee that Software executing at a particular time: (i) on one physical machine; or (ii) on
these links will work all the time and has no control over the availability of the one deployed software virtual machine (“VM”) or similar deployment.
linked pages.
License type(s)
Warranty Designated System(s) License (DS). End User may install and use each copy
Avaya provides a limited warranty on Avaya hardware and software. Refer to or an Instance of the Software only: 1) on a number of Designated Processors
your sales agreement to establish the terms of the limited warranty. In addition, up to the number indicated in the order; or 2) up to the number of Instances of
Avaya's standard warranty language, as well as information regarding support the Software as indicated in the order, Documentation, or as authorized by
for this product while under warranty is available to Avaya customers and other Avaya in writing. Avaya may require the Designated Processor(s) to be
parties through the Avaya Support website: identified in the order by type, serial number, feature key, Instance, location or
https://support.avaya.com/helpcenter/getGenericDetails?detailId=C200911201 other specific designation, or to be provided by End User to Avaya through
12456651010 under the link “Warranty & Product Lifecycle” or such successor electronic means established by Avaya specifically for this purpose.
site as designated by Avaya. Please note that if You acquired the product(s) Concurrent User License (CU). End User may install and use the Software on
from an authorized Avaya Channel Partner outside of the United States and multiple Designated Processors or one or more Servers, so long as only the
Canada, the warranty is provided to You by said Avaya Channel Partner and licensed number of Units are accessing and using the Software at any given
not by Avaya. 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
“Hosted Service” means an Avaya hosted service subscription that You acquire e-mail or voice mail account in the name of a person or corporate function
from either Avaya or an authorized Avaya Channel Partner (as applicable) and (e.g., webmaster or helpdesk), or a directory entry in the administrative
which is described further in Hosted SAS or other service description database utilized by the Software that permits one user to interface with the
documentation regarding the applicable hosted service. If You purchase a Software. Units may be linked to a specific, identified Server or an Instance of
Hosted Service subscription, the foregoing limited warranty may not apply but the Software.
You may be entitled to support services in connection with the Hosted Service Shrinkwrap License (SR). You may install and use the Software in accordance
as described further in your service description documents for the applicable with the terms and conditions of the applicable license agreements, such as
Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for “shrinkwrap” or “clickthrough” license accompanying or applicable to the
more information. Software (“Shrinkwrap License”).

Hosted Service Heritage Nortel Software

THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED “Heritage Nortel Software” means the software that was acquired by Avaya as
SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL part of its purchase of the Nortel Enterprise Solutions Business in December
PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED 2009. The Heritage Nortel Software is the software contained within the list of
SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, Heritage Nortel Products located at https://support.avaya.com/licenseinfo
HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER THE LINK “Avaya under the link “Heritage Nortel Products” or such successor site as designated
Terms of Use for Hosted Services” OR SUCH SUCCESSOR SITE AS by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to
DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO use Heritage Nortel Software provided hereunder solely to the extent of the
ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING authorized activation or authorized usage level, solely for the purpose specified
THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON in the Documentation, and solely as embedded in, for execution on, or for
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING communication with Avaya equipment. Charges for Heritage Nortel Software
SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND may be based on extent of activation or use authorized as specified in an order
“END USER”), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING or invoice.
THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY,
YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH Copyright
ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH Except where expressly stated otherwise, no use should be made of materials
AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF on this site, the Documentation, Software, Hosted Service, or hardware
USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR provided by Avaya. All content on this site, the documentation, Hosted Service,
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. 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
Licenses by copyright and other intellectual property laws including the sui generis rights
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, relating to the protection of databases. You may not modify, copy, reproduce,
HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO, UNDER THE LINK “AVAYA republish, upload, post, transmit or distribute in any way any content, in whole
SOFTWARE LICENSE TERMS (Avaya Products)” OR SUCH SUCCESSOR or in part, including any code and software unless expressly authorized by
SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO Avaya. Unauthorized reproduction, transmission, dissemination, storage, and
DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, or use without the express written consent of Avaya can be a criminal, as well
PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA as a civil offense under the applicable law.
CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS
Virtualization Avaya Toll Fraud intervention
The following applies if the product is deployed on a virtual machine. Each If You suspect that You are being victimized by Toll Fraud and You need
product has its own ordering code and license types. Unless otherwise stated, technical assistance or support, call Technical Service Center Toll Fraud
each Instance of a product must be separately licensed and ordered. For Intervention Hotline at +1-800-643-2353 for the United States and Canada. For
example, if the end user customer or Avaya Channel Partner would like to additional support telephone numbers, see the Avaya Support website:
install two Instances of the same type of products, then two products of that https://support.avaya.com or such successor site as designated by Avaya.
type must be ordered.
Security Vulnerabilities
Third Party Components
Information about Avaya's security support policies can be found in the
“Third Party Components” mean certain software programs or portions thereof Security Policies and Support section of https://support.avaya.com/security.
included in the Software or Hosted Service may contain software (including
Suspected Avaya product security vulnerabilities are handled per the Avaya
open source software) distributed under third party agreements (“Third Party
Product Security Support Flow
Components”), which contain terms regarding the rights to use certain portions
(https://support.avaya.com/css/P8/documents/100161515).
of the Software (“Third Party Terms”). As required, information regarding
distributed Linux OS source code (for those products that have distributed Downloading Documentation
Linux OS source code) and identifying the copyright holders of the Third Party
For the most current versions of Documentation, see the Avaya Support
Components and the Third Party Terms that apply is available in the products,
Documentation or on Avaya's website at: https://support.avaya.com/Copyright website: https://support.avaya.com, or such successor site as designated by
or such successor site as designated by Avaya. The open source software Avaya.
license terms provided as Third Party Terms are consistent with the license
Contact Avaya Support
rights granted in these Software License Terms, and may contain additional
rights benefiting You, such as modification and distribution of the open source See the Avaya Support website: https://support.avaya.com for product or
software. The Third Party Terms shall take precedence over these Software Hosted Service notices and articles, or to report a problem with your Avaya
License Terms, solely with respect to the applicable Third Party Components to product or Hosted Service. For a list of support telephone numbers and contact
the extent that these Software License Terms impose greater restrictions on addresses, go to the Avaya Support website: https://support.avaya.com (or
You than the applicable Third Party Terms. such successor site as designated by Avaya), scroll to the bottom of the page,
and select Contact Avaya Support.
The following applies only if the H.264 (AVC) codec is distributed with the
product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT Trademarks
PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR
The trademarks, logos and service marks (“Marks”) displayed in this site, the
OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i)
Documentation, Hosted Service(s), and product(s) provided by Avaya are the
ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC
registered or unregistered Marks of Avaya, its affiliates, its licensors, its
VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A
suppliers, or other third parties. Users are not permitted to use such Marks
CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS
without prior written consent from Avaya or such third party which may own the
OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC
Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and
VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY
product(s) should be construed as granting, by implication, estoppel, or
OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM
otherwise, any license or right in and to the Marks without the express written
MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.
permission of Avaya or the applicable third party.
Service Provider Avaya is a registered trademark of Avaya Inc.
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER'S HOSTING All non-Avaya trademarks are the property of their respective owners. Linux®
OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED is the registered trademark of Linus Torvalds in the U.S. and other countries.
SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD
PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE
INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY
SUPPLIER. AN AVAYA CHANNEL PARTNER'S HOSTING OF AVAYA
PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF
THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY
SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE
OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO
INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT
THE AVAYA CHANNEL PARTNER'S EXPENSE, DIRECTLY FROM THE
APPLICABLE THIRD PARTY SUPPLIER.
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS
HOSTING ANY PRODUCTS THAT USE OR EMBED THE H.264 CODEC OR
H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND
AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY
AND ALL RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC) CODEC
IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE
PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES
NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE
WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (II) DECODE AVC
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE
OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.

Compliance with Laws

You acknowledge and agree that it is Your responsibility for complying with any
applicable laws and regulations, including, but not limited to laws and
regulations related to call recording, data privacy, intellectual property, trade
secret, fraud, and music performance rights, in the country or territory where
the Avaya product is used.

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.
 Contents

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2: Overview of the LAN backup feature . . . . . . . . . . . . . . . . . . . . 11

Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Required hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
LAN Backup in High Availability configurations. . . . . . . . . . . . . . . . . . . 13
General roles and responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3: Software configuration for LAN backups . . . . . . . . . . . . . . . . . . 15

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Initial configuration of the CMS software for LAN backup . . . . . . . . . . . . . 16
Recommended ON-Bar configurations. . . . . . . . . . . . . . . . . . . . . . . . 17
Recommended network backup client configurations for CMS . . . . . . . . . . 20
Recommended IBM Spectrum Protect client configurations for CMS . . . . . 20
Verifying dsm.opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Verifying dsm.sys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Specifying the location of the XBSA library . . . . . . . . . . . . . . . . . . . 24
Initializing the IBM Spectrum Protect password. . . . . . . . . . . . . . . . . 24
Generating the IBM Spectrum Protect password file . . . . . . . . . . . . . . 24
Verifying the presence of the include and exclude list . . . . . . . . . . . . . 25
Setting up the Informix login permissions to run onbar . . . . . . . . . . . . 26
Recommended Netbackup client configurations for CMS . . . . . . . . . . . 26
Verifying bp.conf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Specifying the location of the XBSA library . . . . . . . . . . . . . . . . . . . 27
Setting up Netbackup policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Recording network information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 4: Backing up and restoring data . . . . . . . . . . . . . . . . . . . . . . . . 31

Recommendations for backing up data . . . . . . . . . . . . . . . . . . . . . . . 31
Doing a CMS system data backup . . . . . . . . . . . . . . . . . . . . . . . . . . 32
When to do a CMS system data backup . . . . . . . . . . . . . . . . . . . . . 33
Setting up automated CMS system data backups . . . . . . . . . . . . . . . . 33
Backing up CMS system data on demand using IBM Spectrum Protect. . 33
Backing up the CMS system data on demand using NetBackup . . . . . . 34
Doing a data backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
When to do a data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Setting up automated data backups . . . . . . . . . . . . . . . . . . . . . . . 35
Backing up data on demand . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Backing up data on demand using IBM Spectrum Protect . . . . . . . . . 35

Using Avaya CMS LAN Backup March 2021 5

Contents

Backing up data on demand using NetBackup . . . . . . . . . . . . . . . 36

Doing a migration data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Backup migration data on demand using IBM Spectrum Protect . . . . . . . 37
Backup migration data on demand using Netbackup . . . . . . . . . . . . . . 38
Restoring from a migration data backup. . . . . . . . . . . . . . . . . . . . . . . 38
Restore migration data on demand using IBM Spectrum Protect . . . . . . . 38
Restore migration data on demand using Netbackup. . . . . . . . . . . . . . 39
Migrating customer data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Before migrating data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Migrating system administration data to the new system . . . . . . . . . . . 40
Migrating agent and call center administration to the new system . . . . . . 41
Migrating historical data to the new system . . . . . . . . . . . . . . . . . . . 42
Restoring CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Before restoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Restoring CMS data from a data backup . . . . . . . . . . . . . . . . . . . . . 44
Restoring CMS data from data backup using IBM Spectrum Protect . . . 44
Restoring CMS data from data backup using NetBackup. . . . . . . . . . 45
Restoring specific files from a data backup . . . . . . . . . . . . . . . . . . . 46
Restoring the CMS server, software and data . . . . . . . . . . . . . . . . . . . . 46
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Restoring a CMS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Recovering the CMS software installation . . . . . . . . . . . . . . . . . . . . 47
Software recovery for Dell or HPE hardware. . . . . . . . . . . . . . . . . 47
Software recovery for VMware hardware. . . . . . . . . . . . . . . . . . . 48
Restoring the CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Restoring the CMS data using IBM Spectrum Protect . . . . . . . . . . . 48
Restoring the CMS data using NetBackup . . . . . . . . . . . . . . . . . . 53

Chapter 5: Troubleshooting the LAN backup feature . . . . . . . . . . . . . . . . . . 57

Basic troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Backup logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
backup.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
bar_act.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
dsierror.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
dsmerror.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
nbuerror.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
IBM Spectrum Protect additional troubleshooting . . . . . . . . . . . . . 63
restore.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring the network settings on a CMS server . . . . . . . . . . . . . . . . . 64

Using Avaya CMS LAN Backup March 2021 6

 Contents

Troubleshooting the IBM Spectrum Protect include and exclude list . . . . . . . 65

IBM Spectrum Protect Storage pool variable error messages . . . . . . . . . . . 67
Verifying the network card settings . . . . . . . . . . . . . . . . . . . . . . . . . 67
Checking shared memory parameters . . . . . . . . . . . . . . . . . . . . . . . . 69
Restarting a IBM Spectrum Protect restore after it has stopped . . . . . . . . . . 70

Chapter 6: Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
CMS and CMS Supervisor Documents . . . . . . . . . . . . . . . . . . . . . . 73
Avaya Solutions Platform Documents . . . . . . . . . . . . . . . . . . . . . . 76
WebLM Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
VMware Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Finding documents on the Avaya Support website . . . . . . . . . . . . . . . 77
Accessing the port matrix document. . . . . . . . . . . . . . . . . . . . . . . 78
Avaya Documentation Portal navigation . . . . . . . . . . . . . . . . . . . . . 78
Viewing Avaya Mentor videos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Using the Avaya InSite Knowledge Base . . . . . . . . . . . . . . . . . . . . 80

Appendix A: Mirrored system disk pairs. . . . . . . . . . . . . . . . . . . . . . . . . 83

Appendix B: Example IBM Spectrum Protect policy domain . . . . . . . . . . . . . . 85

Appendix C: Example CMS scheduler policy for IBM Spectrum Protect . . . . . . . 87

Appendix D: Example CMS policies for Netbackup . . . . . . . . . . . . . . . . . . . 91

Example policy for data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Example policy for File systems (OS) . . . . . . . . . . . . . . . . . . . . . . . . 93

Appendix E: Changing the root user ID permissions to install software using FTP . 95

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Using Avaya CMS LAN Backup March 2021 7

Contents

Using Avaya CMS LAN Backup March 2021 8

Chapter 1: Introduction

Purpose
The document describes how to use the LAN backup feature with Avaya Call Management
System (CMS). This document is intended for:
● Avaya support personnel
● Contact center administrators
● IBM Spectrum Protect administrators
Users of this document must be familiar with IBM Spectrum Protect and Veritas Netbackup
(formerly known as Symantec Netbackup).

Using Avaya CMS LAN Backup March 2021 9

Chapter 1: Introduction

Using Avaya CMS LAN Backup March 2021 10

Chapter 2: Overview of the LAN backup
feature

The Avaya Call Management System (CMS) LAN backup feature provides an alternative to the
traditional method of backing up and restoring data. In the past, the only way to backup and
restore data was to use a tape device located with CMS. LAN backup allows you to back up
CMS data and system information over a local area network (LAN) to a network backup server.
The network backup server has a software package that can control where, how, and when the
data is stored.
The benefits of using the CMS LAN backup feature are:
● Automated data backups
● Centralized storage location for backing up multiple CMS servers
● Faster data backups and restores (dependent on network configuration and traffic)
This section includes the following topics:
● Required software on page 11
● Required hardware on page 12
● LAN Backup in High Availability configurations on page 13
● General roles and responsibilities on page 13

Required software
The following software has been certified by Avaya for use with the LAN backup feature:
● CMS software, including any software associated with CMS.
● IBM Spectrum Protect Client Software Version 8.1.6 and IBM Spectrum Protect Server
Version 7.1.x.

Using Avaya CMS LAN Backup March 2021 11

Chapter 2: Overview of the LAN backup feature

! Important:
Important: IBM Spectrum Storage Protect was formerly known as Tivoli Storage Manager
(TSM). In this document, all references to TSM have been changed to IBM
Spectrum Protect. However, you will still see references to Tivoli and TSM in the
screen examples and file path names in this document, and you will still see
references to the TSM product on the IBM documentation websites referenced
from this document.
Installation of the IBM Spectrum Protect API and BA packages for Linux are required on
the CMS server. The CMS OVA includes the appropriate gskcrypt and gskssl
packages that are required on the CMS server.
Use IBM Spectrum Protect version 8.1.6 for Linux x86_64 for the Backup/Archive client
software.
Use IBM Spectrum Protect server version 7.1.x or later versions for the IBM Spectrum
Protect server software.
● Veritas Netbackup 7.7.3 client and Veritas Netbackup 7.7.3 server.
Installation of the Netbackup 7.7.3 client software for Linux is required on the CMS server.

! Important:
Important: CMS is only certified on IBM Spectrum Protect 8.1.6 client software and IBM
Spectrum Protect 7.1.x server software. Any reference to IBM Spectrum Protect
in this document means Version 8.1.6 client software and Version 7.1.x server
software.

! Important:
Important: Any reference to Netbackup in this document means Veritas Netbackup Version
7.7.3 (formerly known as Symantec Netbackup).

Required hardware
The following hardware is required to use the LAN backup feature:
● A storage device that is capable of interfacing with the storage manager software
● A network server for the storage manager server software
Note:
Note: A CMS server cannot be used as a network backup server.
● Any additional hardware required by CMS if you are running CMS on the existing
supported hardware. No additional hardware is needed if your CMS is a virtual system.

Using Avaya CMS LAN Backup March 2021 12

 LAN Backup in High Availability configurations

LAN Backup in High Availability configurations

LAN Backup can be used with the CMS High Availability configuration with the following
consideration:
● The LAN backup cannot be used to transfer data between the two HA CMS servers.
● The LAN backup can be used to back up each individual HA server.
● The LAN backup can be used for data migration, but requires adequate storage space for
the migration. See the hardware requirements section above.
● A Professional Services offer is required to transfer and sync data between the two HA
servers.

General roles and responsibilities

The IBM Spectrum Protect product is very sophisticated. You must be familiar with the IBM
Spectrum Protect software product before using the CMS LAN backup feature. This document
is not intended to replace the IBM Spectrum Protect documentation. For more information, see
the following IBM website:
https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.6/tsm/welcome.html
Note:
Note: A useful IBM Spectrum Protect document is:
- IBM Spectrum Protect Installing the Clients
A useful Informix document is:
- Informix Backup and Restore Guide
Some useful Netbackup documents are
- Veritas NetBackup™ 7.7 Installation Guide for Unix and Windows
- Veritas NetBackup™ 7.7 for Informix Administrator's Guide for Unix and Linux.
The following table summarizes the various tasks and responsibilities involved with setting up
and maintaining a CMS server that is using the LAN backup feature.

Task Customer Avaya support1

Obtaining the network backup client and server software X N/A

Obtaining a network server for the network backup server X N/A
software

Using Avaya CMS LAN Backup March 2021 13

Chapter 2: Overview of the LAN backup feature

Task Customer Avaya support1

Installing the network backup client and server software X N/A

Obtaining a storage device capable of interfacing with the X N/A
network backup server
Installing the Data Protection for Informix X N/A
Configuring the server software for LAN backups X N/A
Configuring the CMS software for LAN backup X X
Backing up CMS data X N/A
Backing up the CMS server X N/A
Restoring CMS data X N/A
Enabling the CMS server to boot for a system restore N/A X
Preparing the system for a restore over the LAN X N/A
Restoring the CMS server data X N/A
Troubleshooting the network backup server software X N/A
Troubleshooting the network backup server X N/A
Troubleshooting the LAN X N/A
Troubleshooting the network backup client software X N/A
1. Additional support provided by Avaya could result in additional time and material expenses.

Using Avaya CMS LAN Backup March 2021 14

Chapter 3: Software configuration for LAN
backups

This section contains the procedures for configuring an Avaya Call Management System (CMS)
for use with the LAN backup feature. The customer is responsible for the installation of the
network backup software and the configuration of the network backup server software.
This section includes the following topics:
● Prerequisites on page 15
● Initial configuration of the CMS software for LAN backup on page 16
● Recommended ON-Bar configurations on page 17
● Recommended network backup client configurations for CMS on page 20
● Recording network information on page 29

Prerequisites
Before configuring any CMS software for the LAN backup, the customer must do the following
tasks:
● Be familiar with the network backup software product.
● Install the network backup software client software on the CMS server.
Note:
Note: If you want to install the Netbackup client software on the CMS server using the
FTP method as documented in Veritas Netbackup™ Installation Guide: Unix and
Windows, you must change the CMS root user ID permissions to allow remote
access. After you have installed the Netbackup client software, the root login
remote access permission must be reconfigured to the original setting. For
information about this procedure, see Changing the root user ID permissions to
install software using FTP on page 95.
● Install the network backup server software.
● Register the network backup licenses.
● Do any customization required by the network backup server software.
● Verify that the storage manager server can detect network backup clients.
● Verify the node name of the server where the network backup server software resides

Using Avaya CMS LAN Backup March 2021 15

Chapter 3: Software configuration for LAN backups

● Register the client node of CMS with the server software.

● If using the IBM Spectrum Protect, obtain the password and user ID for the client node of
CMS. This password and user ID was created when the CMS client node was registered
with the server software.
● Verify that the sm_versions file contains the correct storage manager version. The file is
located at $INFORMIX/etc/sm_versions.
● For IBM Spectrum Protect Client software, copy /opt/informix/etc/sm_versions.std to /
opt/informix/etc/sm_versions, then add "1|8.1.6|tsm|8.1.6" to the end of the /opt/
informix/etc/ sm_versions file.
● For Netbackup, the /usr/openv/netbackup/bin/informix_config script will set the values
in the sm_versions file. If not set properly by the script (below), the file should have one
line with the following text:
1|1.1.0|Veritas-Netbackup|1|
● Verify that /cms/install/logdir/dsmerror.log (for IBM Spectrum Protect Client software) or
/cms/install/logdir/nbuerror.log (for Netbackup server) has permissions set to 660.
● Create a policy domain for the CMS client node.
The procedures for doing these prerequisites can be found in the IBM Spectrum Protect or
Netbackup documentation. For more information about the IBM Spectrum Protect software
installation, see IBM Spectrum Protect Installing Backup-Archive Clients (Linux x86_64).
For more information about the Netbackup software installation, see Veritas NetBackup™ 7.7.3
Installation Guide for Unix.

Initial configuration of the CMS software for LAN backup

If you are using Netbackup server for your backups and if the Firewall Security feature is
activated on the CMS, you must ensure to open ports 1556 and 13734 for use by Netbackup.
To open ports 1556 and 13734 do the following: use cmssvc option 11. Choose option 2,
Firewall, and choose option 1.

Using Avaya CMS LAN Backup March 2021 16

 Recommended ON-Bar configurations

Recommended ON-Bar configurations

About this task
The ON-Bar configuration should already be correctly configured for your CMS. Use the
following procedure to check the current ON-Bar configuration and make any necessary
adjustments.

Procedure
1. Set the IDS environment by entering:
. /opt/informix/bin/setenv
2. Enter:
cat /opt/informix/etc/onconfig.cms| grep BAR_ACT_LOG
3. Verify that the Informix configuration parameters for CMS have been set up.
For more information, see “Setting the Informix configuration parameters for CMS” in
Maintaining and Troubleshooting Avaya Call Management System.

Using Avaya CMS LAN Backup March 2021 17

Chapter 3: Software configuration for LAN backups

4. Verify that the BAR_ACT_LOG setting is:

/cms/install/logdir/bar_act.log
Example:

###################################################################
# Licensed Material - Property Of IBM
#
# "Restricted Materials of IBM"
#
# IBM Informix Dynamic Server
# Copyright IBM Corporation 1996, 2009. All rights reserved.
#
# Title: onconfig.std

# Description: IBM Informix Dynamic Server Configuration Parameters

#
# Important: $INFORMIXDIR now resolves to the environment
# variable INFORMIXDIR. Replace the value of the INFORMIXDIR
# environment variable only if the path you want is not under
# $INFORMIXDIR.
#
# For additional information on the parameters:
# http://publib.boulder.ibm.com/infocenter/idshelp/v115/index.jsp
###################################################################
#……………………………………………………………………….
#……………………………………………………………………….
#……………………………………………………………………….
##################################################################
# Backup and Restore Configuration Parameters
###################################################################
# BAR_ACT_LOG - The ON-Bar activity log file location.
# Do not use the /tmp directory. Use a
# directory with restricted permissions.
# BAR_DEBUG_LOG - The ON-Bar debug log file location.
# Do not use the /tmp directory. Use a
# directory with restricted permissions.
# BAR_DEBUG - The debug level for ON-Bar. Acceptable
# values are 0 (off) through 9 (high).
# BAR_MAX_BACKUP - The number of backup threads used in a
# backup. Acceptable values are 0 (unlimited)
# or any positive integer.
# BAR_RETRY - Specifies the number of time to retry a
# backup or restore operation before reporting
# a failure
# BAR_NB_XPORT_COUNT - Specifies the number of data buffers that
# each onbar_d process uses to communicate
# with the database server

Using Avaya CMS LAN Backup March 2021 18

 Recommended ON-Bar configurations

# BAR_XFER_BUF_SIZE - The size, in pages, of each data buffer.

# Acceptable values are 1 through 15 for
# 4 KB pages and 1 through 31 for 2 KB pages.
# RESTARTABLE_RESTORE - Enables ON-Bar to continue a backup after a
# failure. Acceptable values are OFF or ON.
# BAR_PROGRESS_FREQ - Specifies, in minutes, how often progress
# messages are placed in the ON-Bar activity
# log. Acceptable values are: 0 (record only
# completion messages) or 5 and above.
# BAR_BSALIB_PATH - The shared library for ON-Bar and the
# storage manager. The default value is
# $INFORMIXDIR/lib/ibsad001 (with a
# platform-specific file extension).
# BACKUP_FILTER - Specifies the pathname of a filter program
# to transform data during a backup, plus any
# program options
# RESTORE_FILTER - Specifies the pathname of a filter program
# to transform data during a restore, plus any
# program options
# BAR_PERFORMANCE - Specifies the type of performance statistics
# to report to the ON-Bar activity log for backup
# and restore operations.
# Acceptable values are:
# 0 = Turn off performance monitoring (Default)
# 1 = Display the time spent transferring data
# between the IDS instance and the storage
# manager
# 2 = Display timestamps in microseconds
# 3 = Display both timestamps and transfer
# statistics
###################################################################
# BAR_ACT_LOG /cms/install/logdir/bar_act.log
# BAR_DEBUG_LOG $INFORMIXDIR/tmp/bar_dbug.log
# BAR_DEBUG 0
# BAR_MAX_BACKUP 0
# BAR_RETRY 1
# BAR_NB_XPORT_COUNT 20
# BAR_XFER_BUF_SIZE 31
# RESTARTABLE_RESTORE ON
# BAR_PROGRESS_FREQ 0
# BAR_BSALIB_PATH
# BACKUP_FILTER
# RESTORE_FILTER
# BAR_PERFORMANCE 0
###################################################################
# Informix Storage Manager (ISM) Configuration Parameters
###################################################################
# ISM_DATA_POOL - Specifies the name for the ISM data pool
#……………………………………………………………………….
#……………………………………………………………………….
#……………………………………………………………………….

Using Avaya CMS LAN Backup March 2021 19

Chapter 3: Software configuration for LAN backups

5. Choose one of the following:

● If the settings are correct, continue with Recommended network backup client
configurations for CMS on page 20.
● If the settings are not correct, do the following:
a. Enter:
vi /opt/informix/etc/onconfig.cms
b. Change any required settings in the onconfig.cms file.
c. When finished press Esc. Then enter:
:wq!
6. Continue with Recommended network backup client configurations for CMS on page 20.

Recommended network backup client configurations for

CMS
Do the procedure based on the type of LAN backup feature being used.
● If you are using IBM Spectrum Protect as the LAN backup feature, continue with
Recommended IBM Spectrum Protect client configurations for CMS on page 20.
● If you are using NetBackup client as the LAN backup feature, continue with
Recommended Netbackup client configurations for CMS on page 26.

Recommended IBM Spectrum Protect client configurations for

CMS
Information on installing the IBM Spectrum Protect client can be found in Tivoli Storage
Manager Installing the Clients or the appropriate IBM Spectrum Protect quick-start guide.
This information is all specific to IBM Spectrum Protect Client software configurations.This
section includes the following topics:
● Verifying dsm.opt on page 21
● Verifying dsm.sys on page 22
● Specifying the location of the XBSA library on page 24
● Initializing the IBM Spectrum Protect password on page 24
● Generating the IBM Spectrum Protect password file on page 24

Using Avaya CMS LAN Backup March 2021 20

 Recommended network backup client configurations for CMS

● Verifying the presence of the include and exclude list on page 25

Verifying dsm.opt
Procedure
1. Verify that the dsm.opt file exists. Enter:
ls -l /opt/tivoli/tsm/client/ba/bin/dsm.opt
If the dsm.opt file exists, continue with Step 3.
2. To create the dsm.opt file, enter:
cp -rp /opt/tivoli/tsm/client/ba/bin/dsm.opt.smp /opt/tivoli/tsm/
client/ba/bin/dsm.opt
3. Verify that the dsm.opt file has been set up correctly. Enter:
cat /opt/tivoli/tsm/client/ba/bin/dsm.opt
4. Verify that the file contains the SErvername setting. The SErvername setting should
contain the host name of the server running the storage manager server software.
Example:

************************************************************************
* Tivoli Storage Manager *
* *
* Sample Client User Options file for UNIX (dsm.opt.smp) *
************************************************************************
................
................
................
* SErvername A server name defined in the dsm.sys file
SErvername server_1

5. Choose one of the following:

a. If the setting is correct, continue with Step 6.
b. If the setting is not correct, do the following steps:
1. Enter:
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
2. Change any required settings in the dsm.opt file.
3. Press Esc. Then enter:
:wq!

Using Avaya CMS LAN Backup March 2021 21

Chapter 3: Software configuration for LAN backups

6. Link the dsm.opt file. Enter:

ln -s /opt/tivoli/tsm/client/ba/bin/dsm.opt /opt/tivoli/tsm/
client/api/bin64/dsm.opt
7. Continue with Verifying dsm.sys on page 22.

Verifying dsm.sys
Procedure
1. Verify the dsm.sys file exists. Enter:
ls -l /opt/tivoli/tsm/client/ba/bin/dsm.sys
If the dsm.sys file exists, continue with Step 3.
2. To create the dsm.sys file, enter:
cp -rp /opt/tivoli/tsm/client/ba/bin/dsm.sys.smp /opt/tivoli/tsm/
client/ba/bin/dsm.sys
3. To verify that the dsm.sys file has been set up correctly, enter:
cat /opt/tivoli/tsm/client/ba/bin/dsm.sys
The file must contain the following settings:
● SErvername must contain the host name of the server running the storage manager
server software.
● COMMmethod must be set to TCPip.
● TCPServeraddress must contain the host and domain name of the IBM Spectrum
Protect server.
● PasswordAccess must be set to generate.
● inclexcl must contain the correct path for the include/exclude lists for the LAN
backup. The path is /cms/LANbkup/incl_excl/backup_excl.tivoli.
● errorlogname must contain the correct path for the IBM Spectrum Protect error log.
The path is /opt/informix/etc/dsmerror.log.
● schedlogname must contain the correct path for the IBM Spectrum Protect schedule
log. The path is /opt/informix/etc/dsmsched.log.
● schedlogretention must be set to 60.
● passworddir must be set to /opt/informix/etc/tsm.

Using Avaya CMS LAN Backup March 2021 22

 Recommended network backup client configurations for CMS

Example:

************************************************************************
* Tivoli Storage Manager
*
*Sample Client System Options file for UNIX (dsm.sys.smp)
************************************************************************

*This file contains the minimum options required to get started

*using TSM. Copy dsm.sys.smp to dsm.sys. In the dsm.sys file,
*enter the appropriate values for each option listed below and remove the leading
*asterisk (*) for each one.

*If your client node communicates with multiple TSM servers, be sure to add a
*stanza, beginning with the SERVERNAME option, for each additional server.

**************************************************************************
SErvername fritos

COMMmethod TCPip
TCPPort 1500
TCPServeraddress fritos.dr.avaya.com
PasswordAccess generate
inclexcl /cms/LANbkup/incl_excl/backup_excl.tivoli
errorlogname /opt/informix/etc/tsm/dsmerror.log
schedlogname /opt/informix/etc/tsm/dsmsched.log
schedlogretention 60
passworddir /opt/informix/etc/tsm

4. Choose one of the following:

a. If the settings are correct, continue with step 5.
b. If the settings are not correct, do the following procedure:
1. Enter:
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys
2. Change any required settings in the dsm.sys file.
3. Press Esc. Then enter:
:wq!
5. Link the dsm.sys file. Enter:
ln -s /opt/tivoli/tsm/client/ba/bin/dsm.sys /opt/tivoli/tsm/
client/api/bin64/dsm.sys
6. Continue with Specifying the location of the XBSA library on page 24.

Using Avaya CMS LAN Backup March 2021 23

Chapter 3: Software configuration for LAN backups

Specifying the location of the XBSA library

Procedure
1. Enter the following command:
ln -s /opt/informix/lib/libtxbsa.so /opt/informix/lib/ibsad001.so
2. Continue with Initializing the IBM Spectrum Protect password on page 24.

Initializing the IBM Spectrum Protect password

Procedure
1. To initialize the IBM Spectrum Protect password enter:
/opt/informix/bin/txbsapswd
Note:
Note: If the system nodename has previously been administered on the server, you
may have to reset the password using "update node <nodename> <password>"
on the IBM Spectrum Protect server.
2. Continue with Generating the IBM Spectrum Protect password file on page 24.

Generating the IBM Spectrum Protect password file

About this task
A IBM Spectrum Protect password file must be generated on CMS. If this file is not created,
system restores will fail. The password was set up when the CMS client node was registered
with the storage manager server software. This password is controlled by the customer but the
customer is required to provide this password to technical support personnel as needed. This
password grants access to only the CMS node, not to any other client nodes. This file needs to
be created only during a new client software installation, or if the storage manager client
password has changed.

Procedure
1. Enter:
cd /tmp

Using Avaya CMS LAN Backup March 2021 24

 Recommended network backup client configurations for CMS

2. Access the command line mode of the storage manager by entering:

dsmc
The system attempts to query any data that is backed up, and then displays the following
message:

Please enter your user ID (default):

3. Enter the user ID.

The system displays the following message:

Please enter password for user ID "default"

4. Enter the password for the IBM Spectrum Protect server software.

! Important:
Important: Ignore any error messages about the backup.
5. Enter:
quit
6. Continue with Verifying the presence of the include and exclude list on page 25.

Verifying the presence of the include and exclude list

Procedure
1. Enter:
cd /cms/LANbkup/incl_excl
2. Enter:
ls
The system displays the following message:

backup_excl.tivoli

3. If the include and exclude list does not exist, contact Avaya technical support or your
product representative for more information.
4. Continue with Recording network information on page 29.

Using Avaya CMS LAN Backup March 2021 25

Chapter 3: Software configuration for LAN backups

Setting up the Informix login permissions to run onbar

Procedure
1. Run the following command to go to the /opt/informix/etc location:
cd /opt/informix/etc
2. Run the following commands to create a new directory named tsm:
mkdir tsm
chown -R informix:informix tsm
3. Run the following commands to add the shell variable DSM_OPT to the Informix login's
bash profile:
cd /opt/informix
vi .bash_profile
4. Search for the string DSM_OPT.
5. If the string does not exist, add the following at the end of the file:
DSM_OPT=/opt/informix/etc/tsm
export DSM_OPT
6. Press Esc, and then enter:
:wq!

Recommended Netbackup client configurations for CMS

Information on installing the Netbackup client can be found in Veritas NetBackup™ 7.7.3
Installation Guide for Unix. This information is all specific to Netbackup client configurations.
This section includes the following topics:
● Verifying bp.conf on page 27
● Specifying the location of the XBSA library on page 27

Using Avaya CMS LAN Backup March 2021 26

 Recommended network backup client configurations for CMS

Verifying bp.conf
After installation of the Netbackup client software, a file named /usr/openv/netbackup/
bp.conf should be created. The format of this file is simple. See the example below:

cuckoo# more /usr/openv/netbackup/bp.conf

SERVER = tofu
CLIENT_NAME = cuckoo

In this simple form, the bp.conf file has the minimum information of showing the Netbackup
server name and the Netbackup client name. Customers experienced with Netbackup may
include additional options in the file, if needed.

! Important:
Important: The client name in bp.conf for CMS use of NetBackup must match the uname
of the CMS server. Run the command uname -n on the CMS server to get the
correct name to use.
Note:
Note: All Netbackup servers used for customer's implementation must be included in
the bp.conf file.

Specifying the location of the XBSA library

About this task
Netbackup provides a script that does some setup work for the XBSA connection.

Procedure
1. Enter the following command:
/usr/openv/netbackup/bin/informix_config
The system requests the Informix instance home path.

Using Avaya CMS LAN Backup March 2021 27

Chapter 3: Software configuration for LAN backups

2. Enter:
/opt/informix
The system responds with output shown in the following example:

Changing Informix scripts’ file ownership and group

Adding NetBackup to /opt/informix/etc/sm_versions

Linking /usr/lib/ibsad001.so to
/usr/openv/netbackup/bin/infxbsa.so64

Now specify the location of the XBSA file for the CMS setup.
3. Verify that the XBSA library location exists. Enter:
ls -l /opt/informix/lib/ibsad001.so
If the XBSA library location does not exist, continue with Step 6.
4. Verify that the XBSA library location is linked to the correct library:
Example:
<fileproperties> <timestamp> /opt/informix/lib/ibsad001.so -> /
usr/openv/netbackup/bin/infxbsa.so64
● If the link points to the correct library location, continue with Setting up Netbackup
policies on page 28.
● If the link does not point to the correct library location, continue with Step 5.
5. If the linked file /opt/informix/lib/ibsad001.so exists, enter:
rm /opt/informix/lib/ibsad001.so
6. Enter the following command:
ln -s /usr/openv/netbackup/bin/infxbsa.so64 /opt/informix/lib/
ibsad001.so

Setting up Netbackup policies

There need to be two policies set up for Netbackup - one for the data backup and another for
the filesystem backup. See Appendix D for examples of setting the Netbackup policies. See the
Veritas NetBackup™ 7.7.3 Installation Guide for Unix for more information and options on
Netbackup Policies.

Using Avaya CMS LAN Backup March 2021 28

 Recording network information

! Important:
Important: Avaya support personnel are not responsible for configuring policies or providing
Netbackup support.

Recording network information

Some networking information is specific for the individual CMS server. This information can be
very helpful for technical support personnel who may be troubleshooting your system. Use the
following table to record your network information:

CMS network information

Host name
IP address
Subnet mask
IP address of the gateway
(also called the default router)
IP address of the DNS server

IBM Spectrum Protect or Netbackup

Server host name

Node name
(also called the host name)

Using Avaya CMS LAN Backup March 2021 29

Chapter 3: Software configuration for LAN backups

Using Avaya CMS LAN Backup March 2021 30

Chapter 4: Backing up and restoring data

This section contains the procedures used to back up and restore data on your CMS. The CMS
LAN backup feature works two ways, depending on the type of data to be backed up.

Data backup: Runs through the Informix tool ON-Bar. ON-Bar interfaces with the storage
manager using the X/Open Backup Services Application Programmer's Interface (XBSA
interface). ON-Bar backs up the data in the Informix database and the system tables. This is a
binary data backup and cannot be used for data migration purposes. For details on migration,
see Migration data backup on page 31.

Migration data backup: Creates an ASCII output file that is sent to the LAN backup server as
a regular file. Do not use this for daily backup. This method is for use in preparing for a data
migration only.

System backup: Uses a storage manager to manage the backup and restore. The storage
manager backs up the CMS operating-system files.
This section includes the following topics:
● Recommendations for backing up data on page 31
● Doing a CMS system data backup on page 32
● Doing a data backup on page 34
● Doing a migration data backup on page 37
● Restoring from a migration data backup on page 38
● Restoring CMS data on page 43
● Restoring the CMS server, software and data on page 46

Recommendations for backing up data

Avaya recommends the following:
● Routine backups should be scheduled to occur when network traffic is low.
● CMS data should be backed up with a full backup on a weekly basis.
● CMS data should be backed up with an incremental backup on a daily basis.
● CMS migration data should be backed up when a system upgrade or other data migration
event is expected to take place.

Using Avaya CMS LAN Backup March 2021 31

Chapter 4: Backing up and restoring data

● CMS information should be backed up with a full backup on a monthly basis.

● CMS information should be backed up with an incremental backup on a weekly basis.
● The three most recent system backups should be maintained for every CMS server.
● Schedule the CMS data backup to occur immediately after the system backup.
● If using LAN backup for migration purposes, you should backup only when needed for a
specific migration task. LAN data backup/restore will be your primary data backup/restore
strategy.
● If using tape for migrations, LAN data backup/restore will still be your primary data backup/
restore strategy.
● For IBM Spectrum Protect server software, create a separate policy domain for the CMS
servers.
● For Netbackup configurations, DO NOT setup automatic backups on the Netbackup
server. You will need a policy and a user schedule, but do not schedule any automatic
backups. Use cron jobs to run the CMS scripts for doing your backups. Create a “User
Backup” for use by the CMS scripts.
● Verify that your LAN backup is correctly backing up your data before you discontinue using
a tape device for backups.
Note:
Note: For IBM Spectrum Protect if backup fails and the message ANR1890W displays,
check if “backupinitiationroot” is set to YES through the IBM Spectrum Protect
server command “query option”. Log in as a root user for doing backup/archive or
revert by setting “backupinitiationroot” to No with the server command “setopt
backupinitiationroot No”.

Doing a CMS system data backup

This section describes how to back up the CMS system data. The CMS system data backup is
a backup option you can use instead of the CMSADM tape backup. The system data backup
saves all of the file systems on the computer, including CMS programs.
The system backup does not save CMS data tables or remote file systems.
This section includes the following topics:
● When to do a CMS system data backup on page 33
● Setting up automated CMS system data backups on page 33
● Backing up CMS system data on demand using IBM Spectrum Protect on page 33

Using Avaya CMS LAN Backup March 2021 32

 Doing a CMS system data backup

When to do a CMS system data backup

Do a CMS system data backup:
● After the CMS is provisioned
This backup contains the CMS configuration data placed on the computer by TSC
provisioning personnel.
● Before and after the CMS software is upgraded
● Once a month

Setting up automated CMS system data backups

See IBM Protect Spectrum documentation at https://www.ibm.com/support/knowledgecenter/
SSEQVQ_8.1.6/tsm/welcome.html for information how to automate system backups. See
Recommendations for backing up data on page 31 for more information.
Automated backups for Netbackup are not to be pulled by the Netbackup server. Instead, the
backups should be scheduled using the CMS provided scripts and cron.

Backing up CMS system data on demand using IBM Spectrum Protect

Procedure
1. Enter:
/cms/LANbkup/bin/backup.tivoli X
where X is one of the following:
● 0 for a full system backup
● 1 for an incremental system backup
Note:
Note: The IBM Spectrum Protect documentation refers to the full data backup as a
selective backup.
2. Verify that the backup has completed successfully by entering:
cat /cms/install/logdir/backup.log
For more information, see Backup logs on page 58.
3. Do a data backup. For more information, see Doing a data backup on page 34.

Using Avaya CMS LAN Backup March 2021 33

Chapter 4: Backing up and restoring data

Additional references
For information about backing up data, see Tivoli Storage manager Quick Reference for the
Backup-Archive Clients.

Backing up the CMS system data on demand using NetBackup

Procedure
1. Enter:
/cms/LANbkup/bin/backup.netbackup X
where X is one of the following:
● 0 for a full system backup
● 1 for an incremental system backup
2. Verify that the backup has completed successfully by entering:
cat /cms/install/logdir/backup.log
For more information, see Backup logs on page 58.
Note:
Note: When a backup using Netbackup completes, the system may display the
following message:

EXIT STATUS 1: the requested operation was partially successful

This message is normal. The system generates this message because Netbackup
attempts to modify file timestamps after it backs up a file.
3. Do a data backup. For more information, see Doing a data backup on page 34.
Note:
Note: For information about backing up data, see Veritas NetBackup™ 7.7.3 for
Informix Administrator's Guide.

Doing a data backup

This section describes how to backup the CMS data in the Informix database and the system
tables. The CMS data backup, is a backup option you can use instead of the CMS maintenance
tape backup. You can do a full or incremental backup of the CMS data. The data backup does
not back up the CMS operating system files.
This section includes the following topics:
● When to do a data backup on page 35

Using Avaya CMS LAN Backup March 2021 34

 Doing a data backup

● Setting up automated data backups on page 35

● Backing up data on demand on page 35

When to do a data backup

Do the data backup:
● Immediately after a system backup
● Before and after the CMS software is upgraded
● On a daily basis

Setting up automated data backups

See IBM Protect Spectrum documentation at https://www.ibm.com/support/knowledgecenter/
SSEQVQ_8.1.6/tsm/welcome.html for information how to automate system backups.See
Recommendations for backing up data on page 31 for more information.
Automated backups for Netbackup are not to be pulled by the Netbackup server. Instead, the
backups should be scheduled using the CMS provided scripts and cron.

Backing up data on demand

Backing up data on demand using IBM Spectrum Protect

Procedure
1. Enter:
/cms/LANbkup/bin/onbar_backup.tivoli X
where X is one of the following:
● 0 for a full data backup
● 1 for an incremental data backup
Note:
Note: The IBM Spectrum Protect documentation refers to the full data backup as a
selective backup.

Using Avaya CMS LAN Backup March 2021 35

Chapter 4: Backing up and restoring data

2. Verify that the backup has completed successfully by entering the following commands:
cat /cms/install/logdir/backup.log
cat /cms/install/logdir/bar_act.log
For more information, see Backup logs on page 58.
Note:
Note: Ignore the following message that occurs the first time the data backup is
executed. The file '/opt/informix/etc/ixbar.1' is created when the first data
backup completes.
Open or close failed on file '/opt/informix/etc/ixbar.1', errno =2. No such file or
directory

Additional references
For more information about backing up data, see the Informix Backup and Restore Guide.

Backing up data on demand using NetBackup

Procedure
1. Enter:
/cms/LANbkup/bin/onbar_backup.netbackup X
where X is one of the following:
● 0 for a full data backup
● 1 for an incremental data backup
The system may display the following message:

Open or close failed on the file /opt/informix/etc/ixbar.1, errno=2. No such

file or directory.

Note:
Note: The file /opt/informix/etc/ixbar.1 is created when the first data backup
completes. Ignore the message that the system displays for the first time the data
backup is executed.
2. Verify that the backup has completed successfully by entering the following commands:
cat /cms/install/logdir/backup.log
cat /cms/install/logdir/bar_act.log
For more information, see Backup logs on page 58

Using Avaya CMS LAN Backup March 2021 36

 Doing a migration data backup

Note:
Note: Ignore the following message WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled. The onbar backup forks the dbs backup processes in a
different order each time. If the cmsdbs happens to go before any other dbs
backup, it may easily take more than the timeout value for the other dbs backup
processes. Check the Netbackup server for problems if you suspect the backup
has actually stalled.

Additional references
For more information about backing up data, see the Veritas NetBackup™ 7.7.3 for Informix
Administrator's Guide.

Doing a migration data backup

This section contains the following topics:
● Backup migration data on demand using IBM Spectrum Protect on page 37
● Backup migration data on demand using Netbackup on page 38
Note:
Note: This backup type is NOT to be used for daily backups. It is intended only for doing
backups before a data migration event.

Backup migration data on demand using IBM Spectrum Protect

Procedure
1. Enter:
/cms/LANbkup/bin/backup_maint.tivoli
2. Verify that the backup has completed successfully by entering the following command:
cat /cms/install/logdir/backup.log
3. For more information, see Backup logs on page 58.

Using Avaya CMS LAN Backup March 2021 37

Chapter 4: Backing up and restoring data

Backup migration data on demand using Netbackup

Procedure
1. Enter:
/cms/LANbkup/bin/backup_maint.netbackup
2. Verify that the backup has completed successfully by entering the following command:
cat /cms/install/logdir/backup.log
3. For more information, see Backup logs on page 58.

Restoring from a migration data backup

This section contains the following topics:
● Restore migration data on demand using IBM Spectrum Protect on page 38
● Restore migration data on demand using Netbackup on page 39
Note:
Note: This backup type is NOT to be used for daily backups. It is intended only for doing
backups before a data migration event.

Restore migration data on demand using IBM Spectrum Protect

Procedure
1. Enter:
/cms/LANbkup/bin/restore_maint.tivoli
2. Verify that the restore has completed successfully by entering the following command:
cat /cms/install/logdir/restore.log
3. For more information, see Backup logs on page 58.

Using Avaya CMS LAN Backup March 2021 38

 Migrating customer data

Restore migration data on demand using Netbackup

Procedure
1. Enter:
/cms/LANbkup/bin/restore_maint.netbackup
2. Verify that the restore has completed successfully by entering the following command:
cat /cms/install/logdir/restore.log
3. For more information, see Backup logs on page 58

Migrating customer data

This section includes the following topics:
● Before migrating data on page 39
● Migrating system administration data to the new system on page 40
● Migrating agent and call center administration to the new system on page 41
● Migrating historical data to the new system on page 42

Before migrating data

The following items should be read and understood before migrating data:
● Attempting to migrate Agent and Call Center Administration data more once might cause
serious errors from which recovery is difficult. A re-migration of ACD administration data
requires you to do a second setup of the CMS software.
● To migrate Agent and Call Center Administration data, CMS must be in single-user mode.
● Migrations of system administration data cannot be done in phases. Migrating some user
IDs at one time and others at a later time results in two separate sets of data. Only one set
of data can be used and cannot be migrated into another set.
● When migrating or restoring a non-LDAP user from a maintenance backup, and the “logid”
(logon ID) for a user does not exist in /etc/passwd, the user is created as a new logid.
That logid requires password administration just as if the user was created as a new user
as described in Administering Avaya Call Management System.
When this happens, the migration and restore logs contain messages similar to the
following examples:

Using Avaya CMS LAN Backup March 2021 39

Chapter 4: Backing up and restoring data

- /cms/maint/r3mig/mig.log
INFO: New UNIX user normusr1: name, room and telephone will not
be migrated.
- /cms/maint/restore/rest.log
Created UNIX login 'normusr1'.
Warning: Name, Telephone, and Room will not be restored for
normusr1.

Migrating system administration data to the new system

About this task
This procedure supports the standard like-for-like ACD migration from the old system to a new
system. That is, ACD 1 migrates to ACD 1, ACD 2 migrates to ACD 2, ACD 3 migrates to ACD
3 and so on. Any variations on this standard migration scheme are supported by Avaya
Professional Services in the United States or the International Avaya Professional Services or
COE outside of the United States.

! CAUTION:
CAUTION: Do this procedure only once. Attempting to migrate system administration data
more than once causes catastrophic errors from which you are unable to recover.
Failure to heed to this warning can irretrievably destroy data.

Procedure
1. Log on to CMS.
The system displays the CMS main window.
2. From the CMS main menu, select System Setup > CMS State to put CMS into single-user
mode.
3. From the CMS main menu, select System Setup > R3 Migrate Data.
The system displays the R3 Migrate Data window.

Using Avaya CMS LAN Backup March 2021 40

 Migrating customer data

4. In the R3 Migrate Data window, enter the values and select the options that are indicated
in the following table:
For the device name in the System Setup > R3 Migrate Data screen, use the device
name: "DO NOT USE".

Field Value to enter or option to select

Device Name The device name

Data Type System Administration data
Specify ACD(s) All ACDs

5. Press Enter to access the action list in the top right corner.
6. Select Run and press Enter.
The system displays the progress of the migration in the Status: field. When the migration
ends, the system indicates the success or failure of the migration in this field.
Note:
Note: After the migration is complete, you will receive a message if the migration of any
custom reports fail. Information about the failed reports are written to the
r3mig.log file. After you acknowledge the message, contact Avaya
Professional Services to have the custom report migrated to the new system.
7. Press F3 (commands) and select the UNIX option to display the UNIX prompt.
8. Enter:
pg /cms/migrate/r3mig.log
This command displays the customer migration log.
9. Look at the contents of the customer migration log and take any necessary corrective
action. Note that the migration log file can be large. For help with interpreting the log,
contact technical support or your customer representative.
10. To exit the UNIX window, enter:
exit

Migrating agent and call center administration to the new system

Procedure
1. Verify that the full maintenance backup tape created earlier is in the tape drive.
2. From the CMS main menu, select System Setup > R3 Migrate Data.
The system displays the R3 Migrate Data window.

Using Avaya CMS LAN Backup March 2021 41

Chapter 4: Backing up and restoring data

3. In the R3 Migrate Data window, enter the values and select the options that are indicated
in the following table:
For the device name in the System Setup > R3 Migrate Data screen, use the device
name: DO NOT USE.

Field Value to enter or option to select

Device Name The device name

Data Type Agent/Call Center Admin data
Specify ACD(s) All ACDs

4. Press Enter to access the action list in the top right corner.
5. Select Run and press Enter.
The system displays the progress of the migration in the Status: field. When the migration
ends, the system indicates the success or failure of the migration in this field.
6. Press F3 (commands) and select the UNIX option to display the UNIX prompt.

Migrating historical data to the new system

About this task
This procedure supports the standard like-for-like ACD migration from the old system to a new
system. That is, ACD 1 migrates to ACD 1, ACD 2 migrates to ACD 2, ACD 3 migrates to ACD
3 and so on. Any variations on this standard migration scheme are supported by Avaya
Professional Services in the United States or the International Avaya Professional Services or
COE outside of the United States.

Procedure
1. Log on to CMS.
The system displays the CMS main window.
2. Verify that the full maintenance backup tape created earlier is in the tape drive.
3. From the CMS main menu, select System Setup > R3 Migrate Data.
The system displays the R3 Migrate Data window.

Using Avaya CMS LAN Backup March 2021 42

 Restoring CMS data

4. Enter the values and select the options that are indicated in the following table:
For the device name in the System Setup > R3 Migrate Data screen, use the device
name: DO NOT USE.

Field Value to enter or option to select

Device Name The device name

Data Type Historical data
Stop Date Leave blank
Stop Time 11:59 PM
Specify ACD(s) All ACDs or a specific ACD if not moving all ACDs

5. Press Enter to access the action list in the top right corner.
6. Select Run and press Enter.
The system displays the progress of the migration in the Status: field. When the migration
ends, the system indicates the success or failure of the migration in this field.
Note:
Note: A full historical migration can take several hours. It runs in the background, so
you can exit the migration window and do other tasks. If you do that, bring up the
migration window periodically to check on the progress.
7. Press F3 (commands) and select the UNIX option to display the UNIX prompt.
8. Enter:
pg /cms/migrate/r3mig.log
This command displays the customer migration log.
9. Look at the contents of the customer migration log and take any necessary corrective
action. Note that the migration log file can be large. For help with interpreting the log,
contact technical support or your customer representative.
10. Repeat this procedure using the incremental backup tape if one was created.
11. To exit the UNIX window, enter:
exit

Restoring CMS data

Use the restore command to obtain copies of backed up files from the server. To restore the
files, you must specify the correct path and directory.

Using Avaya CMS LAN Backup March 2021 43

Chapter 4: Backing up and restoring data

This section includes the following topics:

● Before restoring data on page 44
● Restoring CMS data from a data backup on page 44
● Restoring specific files from a data backup on page 46

Before restoring data

The following items should be read and understood before restoring data:
● Data must be backed up before it can be restored. To ensure the safety of your data, you
should frequently back up your system.
● When migrating or restoring a non-LDAP user from a maintenance backup, and the “logid”
(logon ID) for a user does not exist in /etc/passwd, the user is created as a new logid.
That logid requires password administration just as if the user was created as a new user
as described in Administering Avaya Call Management System.
When this happens, the migration and restore logs contain messages similar to the
following examples:
- /cms/maint/r3mig/mig.log
INFO: New UNIX user normusr1: name, room and telephone will not
be migrated.
- /cms/maint/restore/rest.log
Created UNIX login 'normusr1'.
Warning: Name, Telephone, and Room will not be restored for
normusr1.

Restoring CMS data from a data backup

This section includes the following topics:
● Restoring CMS data from data backup using IBM Spectrum Protect on page 44
● Restoring CMS data from data backup using NetBackup on page 45

Restoring CMS data from data backup using IBM Spectrum Protect

Procedure
1. Enter:
cd /

Using Avaya CMS LAN Backup March 2021 44

 Restoring CMS data

2. Enter:
/cms/LANbkup/bin/onbar_restore.tivoli
Note:
Note: If the CMS software is on, the restore script will automatically turn the CMS
software off and Informix IDS off.
The system displays the following message:

Do you want to continue? (y/n)

3. Enter: y
The system restores the data.

! Important:
Important: Some storage devices require the media to be changed manually. It may be
necessary to have someone change the storage media.
4. Verify that the restore has completed successfully by entering:
cat /cms/install/logdir/restore.log
The system displays the CMS restore log.

Restoring CMS data from data backup using NetBackup

Procedure
1. Enter:
cd /
2. Enter:
/cms/LANbkup/bin/onbar_restore.netbackup
Note:
Note: If the CMS software is on, the restore script will automatically turn the CMS
software off and Informix IDS off.
The system displays the following message:

Do you want to continue? (y/n)

3. Enter: y
The system restores the data.

! Important:
Important: Some storage devices require the media to be changed manually. It may be
necessary to have someone change the storage media.

Using Avaya CMS LAN Backup March 2021 45

Chapter 4: Backing up and restoring data

4. Verify that the restore has completed successfully by entering:

cat /cms/install/logdir/restore.log
The system displays the CMS restore log.
For more information about restoring files, see Veritas NetBackup™ 7.7.3 for Informix
Administrator's Guide.

Restoring specific files from a data backup

For information about restoring specific files, see Tivoli Storage Manager for UNIX Using the
Backup-Archive Clients.

Restoring the CMS server, software and data

This section describes how to restore an entire system. A restore maybe required if a pair of
disks fail or data becomes corrupt on the system.
This section includes the following topics:
● Prerequisites on page 46
● Restoring a CMS server on page 47
● Recovering the CMS software installation on page 47
● Restoring the CMS data on page 48

Prerequisites
Before you begin restoring the system, do the following tasks:
● Locate the most recent system backup on the storage manager.
● Locate the most recent data backup on the storage manager.
● Do any necessary hardware repairs.
● Obtain the storage manager client software:
- IBM Spectrum Protect Linux x86_64 Backup/Archive Clients
- Netbackup Unix Clients

Using Avaya CMS LAN Backup March 2021 46

 Restoring the CMS server, software and data

Restoring a CMS server

You must re-enable the system to boot and then restore the system software.

Prerequisites
Before you begin the installation procedures, do the following tasks:
● Identify the host name of the system, which is designated by the Technical Service Center
(TSC).
● Identify the Internet Protocol (IP) address of the system (this is usually the address in a
customer’s network).
● Identify the default router for the system (this is usually the address in a customer’s
network).
● Identify the subnet mask for the system (this is usually the address in a customer’s
network).
For information about restoring a CMS server, see Recovering a hardware CMS server in
Maintaining and Troubleshooting Avaya Call Management System.

Recovering the CMS software installation

When recovering a CMS deployment, there are different methods you must use depending on
the model of hardware you are using on your current system:
● Software recovery on Dell or HPE hardware - You must redeploy the RHEL OS and CMS
software on the server and reconfigure some system options.
● Software recovery on VMware hardware - You must redeploy the OVA on the server and
reconfigure some options.
For each of these scenarios, you must do the referenced procedures shown below that are
found in Deploying Avaya Call Management System before returning to the this document to
complete the recovery as shown in Restoring the CMS data on page 48.

Software recovery for Dell or HPE hardware

For Dell or HPE hardware, do the following procedures from Deploying Avaya Call Management
System:
● Appendix B - Deploying CMS software on a Dell or HPE hardware server
● Chapter 5 - Configuring system features

Using Avaya CMS LAN Backup March 2021 47

Chapter 4: Backing up and restoring data

Software recovery for VMware hardware

For a VMware server, do the following procedures from Deploying Avaya Call Management
System:
● Chapter 4 - Deploying CMS software using an OVA file
● Chapter 5 - Configuring system features

Restoring the CMS data

Do one of the following:
● If using IBM Spectrum Protect, continue with Restoring the CMS data using IBM Spectrum
Protect on page 48.
● If using Netbackup continue with Restoring the CMS data using NetBackup on page 53.

Restoring the CMS data using IBM Spectrum Protect

Procedure
1. Obtain the IBM Spectrum Protect client from IBM Passport Advantage or IBM Fix Central
and download it to the CMS server. The required packages are gskcrypt, gskssl,
TIVsm-API64, TIVsm-BA, and TIVsm-BAhdw. Use rpm -U to update gskcrypt and gskssl,
as both are already installed with CMS. Use a single rpm -Uvh to install TIVsm-API64,
TIVsm-BA, and TIVsm-BAhdw.
Example:
rpm -U gskcrypt64-8.0.55.2.linux.x86_64.rpm
rpm -U gskssl64-8.0.55.2.linux.x86_64.rpm
rpm -Uvh TIVsm-API64.x86_64.rpm TIVsm-BA.x86_64.rpm
TIVsm-BAhdw.x86_64.rpm
2. Do any customization required for communication with the server software. The CMS
server must be on the network. For more information, see Configuring the network settings
on a CMS server on page 64.
3. Do the following tasks:
● Verifying dsm.opt on page 21
● Verifying dsm.sys on page 22

Using Avaya CMS LAN Backup March 2021 48

 Restoring the CMS server, software and data

4. Access the command line mode of the storage manager by entering:

dsmc
The system attempts to query any data that is backed up, and then displays the following
message:

Please enter your user ID (default):

5. Enter the user ID.

The system displays the following message:

Please enter password for user ID "default"

6. Enter the password for the IBM Spectrum Protect server software.

! Important:
Important: Ignore any error messages about the backup.
7. Enter:
quit
8. Restore CMS by entering the following command on a single line at the command prompt:
dsmc restore /cms/ -subdir=yes -latest 2>&1 | tee -a /tmp/tmp.log
Note:
Note: You can check for error messages from the restore in /tmp/tmp.log. This log will
not be present if the system is rebooted.
● If a User Action is requested for a write-protected file, choose to Force an overwrite on
all objects that are write protected.
● If a User Action is requested for an existing file, choose to Replace all objects that
already exist.
9. Restore the system data by entering:
/cms/LANbkup/bin/restore.tivoli

! Important:
Important: Some storage devices require the media to be changed manually. Someone may
have to change the storage media.
The system displays the following message:

/cms/LANBkup/bin/restore.tivoli will overwrite the root file system and requires

Linux and Tivoli client software to be installed first!!!

Do you want to continue? (y/n)

10. Enter: y. The system data is restored.

Using Avaya CMS LAN Backup March 2021 49

Chapter 4: Backing up and restoring data

Note:
Note: The IBM Spectrum Protect may prompt you to enter the user ID and user
password.
Note:
Note: If the system prompts to replace or skip any objects, choose Option 2, Replace
all objects that already exist.
If the system prompts to force an overwrite or skip any objects, choose Option 2,
Force an overwrite on all objects that are write protected.
Note:
Note: Depending on the platform and hardware, the restore.tivoli process can
take a few hours to complete. Do not interrupt the restore.
● The state of FIPS 140-2 will be checked after the restore. If the backup indicates that
FIPS 140-2 needs to be turned on, the script will automatically activate it and do a
reboot. If the backup indicates that FIPS 140-2 was not turned on, you must reboot the
system manually. Continue with Step 11.
11. Manually reboot the system. Enter:
shutdown -r now
12. Log in to the system as root.

! Important:
Important: You cannot directly log on as root from a remote connection. You must log on
using an administered CMS user ID, then use su - root to log on with root
privileges.
13. Restore the CMS data by entering:
/cms/LANbkup/bin/onbar_restore.tivoli
The system displays the following message:

Do you want to continue? (y/n)

14. Enter: y
Note:
Note: Depending on the amount of data, the data restore could take several minutes or
several hours to complete.
15. If the system prompts for a user ID, enter the IBM Spectrum Protect server user ID.
16. If the system prompts for a user password, enter the IBM Spectrum Protect server user
password.

Using Avaya CMS LAN Backup March 2021 50

 Restoring the CMS server, software and data

17. Verify that the restore has completed successfully by entering:

cat /cms/install/logdir/restore.log
The restore log will contain messages similar to the following as the restore process
progresses.

===== LAN SYSTEM RESTORE STARTED Thu Nov 21 22:11:13 EST 2019

Cleanup /storage/r_root, please wait...

Turning off and disabling CMS and IDS...
Restore root file system, please wait...
dsmc restore / /storage/r_root -subdir=yes -preserv=complete started Thu
Nov 21 22:11:14 EST 2019
dsmc command return code = 0
dsmc Server Version is "7".1
dsmc restore / /storage/r_root -subdir=yes -preserv=complete finished
Thu Nov 21 22:12:10 EST 2019
Restore /opt file system, please wait...
dsmc restore /opt/ /storage/r_root/opt/ -subdir=yes -preserv=complete
started Thu Nov 21 22:12:10 EST 2019
dsmc command return code = 0
dsmc Server Version is "7".1
Restore /var file system, please wait...

. . .

Restore /export/home file system, please wait...

dsmc restore /export/home/ /storage/r_root/export/home/ -subdir=yes
-preserv=complete started Thu Nov 21 22:12:56 EST 2019
dsmc command return code = 0
dsmc Server Version is "7".1

//./etc/request-key.conf
//./etc/vmware-tools/vgauth/schemas/xmldsig-core-schema.xsd
//./etc/vmware-tools/vgauth/schemas/datatypes.dtd
//./etc/vmware-tools/vgauth/schemas/XMLSchema-instance.xsd

. . .

//./export
//./media
6069818 blocks

. . .

Using Avaya CMS LAN Backup March 2021 51

Chapter 4: Backing up and restoring data

===== LAN SYSTEM RESTORE SUCCESSFULLY FINISHED Thu Nov 21 22:17:24 EST 2019

+++++ ON-Bar RESTORE STARTED Thu Nov 21 22:25:23 EST 2019

IBM Spectrum Protect

Command Line Backup-Archive Client Interface
Client Version 8, Release 1, Level 6.1
Client date/time: 11/21/2019 22:25:25
(c) Copyright by IBM Corporation and other(s) 1990, 2018. All Rights Reserved.

Node Name: CMSVM8

Session established with server FRITOS: Linux/x86_64
Server Version 7, Release 1, Level 1.100
Server date/time: 11/21/2019 03:08:43 Last access: 11/21/2019 02:56:14

Restore function invoked.

ANS1247I Waiting for files from the server...

Restoring 4,225 /opt/informix/etc/ixbar.1.20190723.223701 --> /opt/informix/
etc/ixbar.1.20190723.223701 [Done]
Restoring 133 /opt/informix/etc/sqlhosts_2019_07_23_22:36:45 --> /opt/
informix/etc/sqlhosts_2019_07_23_22:36:45 [Done]
Restoring 4,096 /opt/informix/etc --> /opt/informix/etc [Done]
Restoring 4,096 /opt/informix/etc/conv --> /opt/informix/etc/conv [Done]

. . .

onbar -r -w -p started Thu Nov 21 22:26:25 EST 2019

onbar -r -w -p finished Thu Nov 21 22:26:54 EST 2019

Rolling forward the logical logs. Please wait...

onmode -sy started Thu Nov 21 22:26:54 EST 2019

+++++ ON-Bar RESTORE SUCCESSFULLY FINISHED Thu Nov 21 22:28:24 EST 2019

! Important:
Important: Some storage devices require the media to be changed manually. It may be
necessary to have someone change the storage media.
18. To verify the server’s Firewall settings:
a. Run:
cmssvc
b. Enter the number associated with security.
The system displays the following:

Select one of the following:

1)FIPS 140-2 mode
2)Firewall
3)Enhanced Access Security Gateway(EASG)

Using Avaya CMS LAN Backup March 2021 52

 Restoring the CMS server, software and data

c. Enter the number associated with Firewall.

The system displays the firewall settings for ipv4 and ipv6.
19. Verify that the Informix configuration parameters for the CMS software are correct.
For more information, see Setting the Informix configuration parameters for Avaya CMS in
the appropriate version of the Maintaining and Troubleshooting Avaya Call Management
System Guide.
20. Turn on the CMS software.
a. Enter:
cmsadm
The system displays the CMSADM menu.
b. Enter the number associated with the run_cms option.
c. Enter the number associated with the Turn on CMS option.

Restoring the CMS data using NetBackup

Procedure
1. Install the Netbackup client software on the CMS server.
For more information on installing the client software, see the appropriate section in the
Veritas NetBackup™ 7.7.3 Installation Guide for Unix.
2. Do any customization required for communication with the server software. The CMS
server must be on the network. For more information, see the Configuring the network
settings on a CMS server on page 64.
3. Enter:
ksh -o vi
4. Restore CMS by entering the following command on a single line at the command prompt:
/usr/openv/netbackup/bin/bprestore -L /tmp/tmp.log -C {clientname}
-t 0 -k "CMS_*" -w 8:00:00 /cms/
Note:
Note: You can check for error messages from the restore in /tmp/tmp.log.
5. Change to the root directory. Enter:
cd /
6. Restore the system by entering:
/cms/LANbkup/bin/restore.netbackup

Using Avaya CMS LAN Backup March 2021 53

Chapter 4: Backing up and restoring data

! Important:
Important: Some storage devices require the media to be changed manually. It may be
necessary to have someone change the storage media.
The system displays the following message:

Do you want to continue? (y/n)

7. Enter y. The system is restored.

! CAUTION:
CAUTION: If this is a restore to hardware, then depending upon the platform, the
restore.netbackup process can take a few hours to complete. Do not
interrupt the restore.
● The state of FIPS 140-2 will be checked after the restore. If the backup indicates that
FIPS 140-2 needs to be turned on, the script will automatically activate it and do a
reboot. If the backup indicates that FIPS 140-2 was not turned on, you must reboot the
system manually. Continue with Step 11.
● If the system does not boot automatically, you must reboot the system manually.
Continue with Step 8.
8. Manually reboot the system. Enter:
shutdown -r now
Note:
Note: During the shutdown process of the system, the state of some services can be
displayed as FAILED. This is normal and you can ignore them.
9. During the boot process, the system can display the following WARNING message. This
message is acceptable.

*** Warning – SELinux targeted policy relabel is required

*** Relabeling could take a very long time, depending on the file
*** system size and speed of the hard drives.

The system automatically reboots after the SELinux relabeling is complete.

10. Log in to the system as root.

! Important:
Important: You cannot directly log on as root from a remote connection. You must log on
using an administered CMS user ID, then use su - root to log on with root
privileges.

Using Avaya CMS LAN Backup March 2021 54

 Restoring the CMS server, software and data

11. Verify that the restore has completed successfully by entering:

tail -20 /cms/install/logdir/restore.log
The system displays the CMS restore log.

===== LAN SYSTEM RESTORE SUCCESSFULLY FINISHED Mon Aug 26 16:02:19 MDT 2013

● If the system restore is successful, continue with Step 12.

● If the system restore is not successful, escalate through normal channels.
12. Check to see if the /cms/install/logdir/bar_act.log exists. Enter:
ls -l /cms/install/logdir/bar_act.log
The system displays the following messages:

-rw-rw---- 1 informix informix <filesize> <timestamp> /cms/install/logdir/bar_act.log

13. Review the file properties of the /cms/install/logdir/bar_act.log file.

● If the /cms/install/logdir/bar_act.log exists and the file properties are
correct, continue with Step 16.
● If the /cms/install/logdir/bar_act.log does not exist, continue with Step 14.
● If the /cms/install/logdir/bar_act.log exists but the file properties are not
correct, continue with Step 15.
14. Enter:
touch /cms/install/logdir/bar_act.log
15. Enter:
chmod 660 /cms/install/logdir/bar_act.log
chown informix:informix /cms/install/logdir/bar_act.log
16. Restore the CMS data by entering:
/cms/LANbkup/bin/onbar_restore.netbackup
The system displays the following message:

/cms/LANbkup/onbar_restore.netbackup will overwrite IDS to the last

backup and requires CMS and IDS to be shutdown!!!

Do you want to continue? (y/n)

17. Enter: y
Note:
Note: Depending on the amount of data, the data restore could take several minutes or
several hours to complete.

Using Avaya CMS LAN Backup March 2021 55

Chapter 4: Backing up and restoring data

18. Verify that the restore has completed successfully by entering:

tail -20 /cms/install/logdir/restore.log
The restore log contains messages similar to the following as the restore process
progresses.
.
.
.
onbar -r -w -p started <timestamp>
onbar -r -w -p finished <timestamp>
Rolling forward the logical logs. Please wait...
onmode -sy started <timestamp>
+++++ ON-Bar RESTORE SUCCESSFULLY FINISHED <timestamp>

● If the data restore is successful, continue with Step 19.

● If the data restore is not successful, escalate through normal channels.
19. Verify that the Informix configuration parameters for the CMS software are correct.
For more information, see Setting the Informix configuration parameters for Avaya CMS in
Maintaining and Troubleshooting Avaya Call Management System.
20. Turn on the CMS software.
a. Enter:
cmsadm
The system displays the CMSADM menu.
b. Enter the number associated with the run_cms option.
c. Enter the number associated with the Turn on CMS option.
21. If problems occurred using the LAN backup feature, continue with Troubleshooting the
LAN backup feature on page 57.

Additional Information
For more information, see Veritas NetBackup™ 7.7.3 Installation Guide for Unix.

Using Avaya CMS LAN Backup March 2021 56

Chapter 5: Troubleshooting the LAN
backup feature

This section provides solutions for common problems with the Avaya Call Management System
(CMS) LAN backup feature.
This section includes the following topics:
● Basic troubleshooting on page 57
● Backup logs on page 58
● Configuring the network settings on a CMS server on page 64
● Troubleshooting the IBM Spectrum Protect include and exclude list on page 65
● IBM Spectrum Protect Storage pool variable error messages on page 67
● Verifying the network card settings on page 67
● Checking shared memory parameters on page 69
● Restarting a IBM Spectrum Protect restore after it has stopped on page 70

Basic troubleshooting
When trying to determine why a backup or restore is not working, there are some basic steps
you should do first:
1. Verify that the CMS server, backup server, and storage device has power and is online.
2. Verify that the appropriate storage media is loaded in the storage device.
3. Check the cabling on the CMS server. Make sure all the cables and connectors are
securely attached.
4. Verify that the CMS server can detect the backup server over the network.
5. Verify that the backup server can detect the CMS server over the network.

Using Avaya CMS LAN Backup March 2021 57

Chapter 5: Troubleshooting the LAN backup feature

Backup logs
There are five backup logs that can be used to monitor the status of a backup. The backup logs
are found in /cms/install/logdir
This section includes the following topics:
● backup.log on page 58
● bar_act.log on page 61
● dsierror.log on page 61
● dsmerror.log on page 61
● nbuerror.log on page 62
● restore.log on page 63
For more information on error codes, see the appropriate IBM Spectrum Protect website: https:/
/www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.6/tsm/welcome.html.

backup.log
The backup.log file contains the most information about the status of backups. This log
includes information on:
● When the backup started and ended
● The type of backup performed
● Connection to the storage manager server
● Level of the backup
● Files included in the backup

Using Avaya CMS LAN Backup March 2021 58

 Backup logs

● Network status

===== LAN SYSTEM BACKUP STARTED Thu Jul 25 21:11:02 EDT 2019
./backup.tivoli 0
Converter started Thu Jul 25 21:11:02 EDT 2019
Converter completed successfully Thu Jul 25 21:11:03 EDT 2019
Tivoli Storage Manager started Thu Jul 25 21:11:03 EDT 2019
IBM Spectrum Protect
Command Line Backup-Archive Client Interface
Client Version 8, Release 1, Level 6.0
Client date/time: 07/25/2019 21:11:04
(c) Copyright by IBM Corporation and other(s) 1990, 2018. All Rights
Reserved.

Node Name: CMSVM8

Session established with server FRITOS: Linux/x86_64
Server Version 7, Release 1, Level 1.100
Server date/time: 07/25/2019 02:59:14 Last access: 07/23/2019 04:08:58

ANS1115W File '/cms/tmp/.gateway' excluded by Include/Exclude list

ANS1115W File '/cms/tmp/.cms_netconfig.eth0' excluded by Include/Exclude
list
ANS1115W File '/cms/tmp/.ifcfg-eth0.tmp' excluded by Include/Exclude list
ANS1115W File '/cms/tmp/.ifcfg-eth0' excluded by Include/Exclude list
ANS1115W File '/var/tmp/RT_lock' excluded by Include/Exclude list
ANS1115W File '/var/tmp/lnklog^Hlock' excluded by Include/Exclude list
ANS1115W File '/var/tmp/cmsql.data' excluded by Include/Exclude list
ANS1115W File '/var/tmp/.cp_lock' excluded by Include/Exclude list
ANS1115W File '/var/tmp/pbxdblock' excluded by Include/Exclude list

Total number of objects inspected: 55,390

Total number of objects backed up: 55,380
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of objects encrypted: 0
Total number of objects grew: 0
Total number of retries: 6
Total number of bytes inspected: 3.42 GB
Total number of bytes transferred: 3.43 GB
Data transfer time: 23.75 sec
Network data transfer rate: 151,297.06 KB/sec
Aggregate data transfer rate: 20,821.39 KB/sec
Objects compressed by: 0%
Total data reduction ratio: 0.00%
Elapsed processing time: 00:02:52
dsmc command return code = 4

dsmc Server Version is "7".1

Using Avaya CMS LAN Backup March 2021 59

Chapter 5: Troubleshooting the LAN backup feature

===== LAN SYSTEM BACKUP SUCCESSFULLY FINISHED Thu Jul 25 21:13:57 EDT 2019

+++++ ON-Bar BACKUP STARTED Thu Jul 25 21:15:49 EDT 2019

./onbar_backup.tivoli 0

onbar -b -w -L 0 started Thu Jul 25 21:15:50 EDT 2019

onbar -b -w -L 0 successfully finished Thu Jul 25 21:16:01 EDT 2019
Use Tivoli to backup CMS database related files.
IBM Spectrum Protect
Command Line Backup-Archive Client Interface
Client Version 8, Release 1, Level 6.0
Client date/time: 07/25/2019 21:16:01
(c) Copyright by IBM Corporation and other(s) 1990, 2018. All Rights
Reserved.

Node Name: CMSVM8

Session established with server FRITOS: Linux/x86_64

Server Version 7, Release 1, Level 1.100
Server date/time: 07/25/2019 03:04:11 Last access: 07/25/2019 03:04:10

ANS1228E Sending of object '/opt/informix/etc/tsm/Nodes/CMSVM8/

spclicert.lock' failed.
ANS4005E Error processing '/opt/informix/etc/tsm/Nodes/CMSVM8/
spclicert.lock': file not found
ANS1804E Selective Backup processing of '/opt/informix/etc/*' finished with
failures.

Total number of objects inspected: 326

Total number of objects backed up: 292
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 1
Total number of objects encrypted: 0
Total number of objects grew: 0
Total number of retries: 1
Total number of bytes inspected: 17.09 MB
Total number of bytes transferred: 29.86 MB
Data transfer time: 0.23 sec
Network data transfer rate: 130,454.83 KB/sec
Aggregate data transfer rate: 14,899.50 KB/sec
Objects compressed by: 0%
Total data reduction ratio: 0.00%
Elapsed processing time: 00:00:02
dsmc command return code = 4
dsmc Server Version is "7".1

+++++ ON-Bar BACKUP SUCCESSFULLY FINISHED Thu Jul 25 21:16:03 EDT 2019

Using Avaya CMS LAN Backup March 2021 60

 Backup logs

bar_act.log
The bar_act.log file contains information about the status of the Informix On-Bar data backups.
For more information, see the Informix documentation.
Example:

2002-02-15 12:04:59 793 791 /opt/informix/bin/onbar_d -r -w -p

2002-02-15 12:05:14 793 791 Successfully connected to Storage Manager.
2002-02-15 12:05:14 793 791 Begin cold level 0 restore rootdbs (Storage Manager copy
ID: 0 1423128).
2002-02-15 12:05:55 793 791 Completed cold level 0 restore rootdbs.
2002-02-15 12:05:55 793 791 Begin cold level 0 restore logdbs (Storage Manager copy ID:
0 1423130).
.................
.................
.................
2002-02-15 13:12:53 2401 2399 /opt/informix/bin/onbar_d complete, returning 15
2 (0x98)

dsierror.log
The dsierror.log file contains information about the communication between the X/Open
Backup Services Application Programmer's Interface (XBSA interface) and On-Bar. This log
may not exist on your system. The error log is created when a failure message is generated.
Example:

12/03/01 16:05:41 TcpOpen: TCP/IP error connecting to server.

12/03/01 16:05:41 sessOpen: Failure in communications open call. rc: -50
12/03/01 18:38:45 cuSignOnResp: Server rejected session; result code: 53
12/03/01 18:38:45 sessOpen: Error 53 receiving SignOnResp verb from server

dsmerror.log
The dsmerror.log file contains information about IBM Spectrum Protect software processes.
This log provides error codes that can be used to obtain more information about any potential
problems with the software. This log may not exist on your system. The error log is created
when a failure message is generated.
Example:

03/04/02 14:07:21 TcpOpen: TCP/IP error connecting to server.

03/04/02 14:07:21 sessOpen: Failure in communications open call. rc: -50
03/04/02 14:07:21 ANS1017E Session rejected: TCP/IP connection failure

Using Avaya CMS LAN Backup March 2021 61

Chapter 5: Troubleshooting the LAN backup feature

Procedure
1. From the # prompt, enter:
dsmc
The system enters the storage manager command line mode and the prompt changes to
tsm>.
2. Enter
help
The system displays a help menu.
3. Scroll through the help menu to find the range of error codes that the error code would fit
into.
4. Enter the numeric designation for the error code range.
5. Scroll through the error code table to find the entry for the error code.
Example:
If the log displays the error code ANS1115W, enter: help
The system displays the help menu.
Scroll through the list, and find the option for the error message:

167 - ANS1100-ANS1119

Enter: 167
The system displays a table with error codes. Scroll through the table, and locate the error
message.

ANS1115W File 'file-namefile-namefile-name' excluded by Include/

Exclude list

nbuerror.log
The nbuerror.log file contains information about Netbackup software processes. This log
provides error codes that can be used to obtain more information about any potential problems
with the software. This log may not exist on your system. The error log is created when a failure
message is generated.

Using Avaya CMS LAN Backup March 2021 62

 Backup logs

IBM Spectrum Protect additional troubleshooting

Procedure
1. From the # prompt, enter:
dsmc
The system enters the storage manager command line mode and the prompt changes to
<tsm>
2. Enter help
The system displays the help menu.
3. Scroll through the help menu to find the range of error codes that the error code would fit
into.
4. Enter the numeric designation for the error code range.
5. Scroll through the error code table to find the entry for the error code.
For example, If the log displays the error code ANS1115W, enter: help. The system
displays the help menu. Scroll through the list and find the option for the error message:
167 - ANS1100-ANS1119
Enter: 167.
The system displays a table with error codes. Scroll through the table and locate the error
message:
ANS1115W File 'file-namefile-namefile-name' excluded by Include/
Exclude list

restore.log
The restore.log file contains information about the status of a data or system restore. This log
is a CMS log. The other backup logs can be used to provide more detailed information about a
particular backup or restore process.

Using Avaya CMS LAN Backup March 2021 63

 Chapter 5: Troubleshooting the LAN backup feature

Example:

===== LAN SYSTEM RESTORE STARTED Tue Dec 12 17:44:41 EST 2017

Cleanup /storage/r_root, please wait...

Restore root file system, please wait...
dsmc restore / /storage/r_root -subdir=yes -preserv=complete started Tue Dec 12 17:44:46 EST 2017
dsmc command return code = 0
dsmc Server Version is "7".1
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
//./lib/kbd
//./lib
16060023 blocks
FIPS 140-2 mode is not enabled and matches the restored backup FIPS 140-2 mode.

===== LAN SYSTEM RESTORE SUCCESSFULLY FINISHED Tue Dec 12 18:26:32 EST 2017
+++++ ON-Bar RESTORE STARTED Wed Dec 13 15:29:35 EST 2017

IBM Tivoli Storage Manager

Command Line Backup-Archive Client Interface
Client Version 7, Release 1, Level 6.3
Client date/time: 12/13/2017 15:29:35
(c) Copyright by IBM Corporation and other(s) 1990, 2016. All Rights Reserved.

Node Name: GADWALL

Session established with server FRITOS: Linux/x86_64
Server Version 7, Release 1, Level 1.100
Server date/time: 12/13/2017 01:25:15 Last access: 12/12/2017 03:53:06

Restore function invoked.

ANS1247I Waiting for files from the server...

Restoring 4,096 /opt/informix/etc --> /opt/informix/etc [Done]
. . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
Restore processing finished.

Total number of objects restored: 1

Total number of objects failed: 0
Total number of bytes transferred: 125 B
Data transfer time: 0.00 sec
Network data transfer rate: 11,097.30 KB/sec
Aggregate data transfer rate: 0.03 KB/sec
Elapsed processing time: 00:00:03
dsmc command return code = 0
dsmc Server Version is 7.1

onbar -r -w -p started Tue Dec 19 14:04:07 EST 2017

onbar -r -w -p finished Tue Dec 19 14:06:04 EST 2017

Rolling forward the logical logs. Please wait...

onmode -sy started Tue Dec 19 14:06:04 EST 2017

+++++ ON-Bar RESTORE SUCCESSFULLY FINISHED Tue Dec 19 14:06:42 EST 2017

Configuring the network settings on a CMS server

For information about configuring the network settings and to enable DNS on a CMS server, see
Configuring the system network of the Maintaining and Troubleshooting Avaya Call Management
System document.

Using Avaya CMS LAN Backup March 2021 64

 Troubleshooting the IBM Spectrum Protect include and exclude list

Troubleshooting the IBM Spectrum Protect include and

exclude list
! WARNING:
WARNING: These notes are for IBM Spectrum Protect only. The scripts for the Netbackup
Server create their own include list at /cms/LANbkup/incl_excl/
bkup_incl.netbackup. Changes to the included files must be made in the
Netbackup scripts, and should only be made by Avaya.

Procedure
1. Enter:
cd /cms/LANbkup/incl_excl

Using Avaya CMS LAN Backup March 2021 65

Chapter 5: Troubleshooting the LAN backup feature

2. Enter:
cat backup_excl.tivoli
The system displays a file similar to the following example.

exclude.dir /proc
exclude.dir /cdrom
exclude.dir /n
exclude.dir /vol
exclude.dir /floppy
exclude.dir /xfn
exclude.dir /dev
exclude.dir /devices
exclude.dir /tmp/.../*
exclude /tmp/*
exclude.dir /var/tmp/.../*
exclude /var/tmp/*
exclude /.../core
exclude /etc/path_to_inst
exclude /etc/nologin
exclude /etc/mnttab
exclude.dir /var/spool/lp/temp
exclude.dir /var/spool/lp/tmp
exclude.dir /var/spool/lp/requests
exclude.dir /var/spool/mqueue
exclude /var/spool/locks/*
exclude.dir /cms/tmp/.../*
exclude /cms/tmp/*
exclude /.../BI/add_on/data/forwarder/*
exclude.dir /INFORMIXTMP

3. Do the following steps only if a modification is required for the backup_excl.tivoli file:

! CAUTION:
CAUTION: Modifying this file can cause future system restores to fail. Contact Avaya
technical support or your product distributor before modifying this file.
a. Enter:
vi /cms/LANbkup/incl_excl/backup_excl.tivoli
b. Change any required settings in the backup_excl.tivoli file.
1. To exclude a directory from the backup, enter:
exclude.dir directory_path
where directory_path is the full path for the directory.
2. To exclude a file from the backup, enter:
exclude file_path
where file_path is the full path for the file.

Using Avaya CMS LAN Backup March 2021 66

 IBM Spectrum Protect Storage pool variable error messages

c. Press Esc. Then enter:

:wq!

IBM Spectrum Protect Storage pool variable error

messages
The IBM Spectrum Protect server software can be configured to backup data to a disk drive and
then migrate the data to another type of storage media. When a predetermined threshold value
is reached, a set amount of data on the disk drive is migrated to another type of storage media.
This process is controlled by the highmig and lowmig storage pool variables. If the highmig and
lowmig storage pool variables are incorrectly set up, then the backup will generate error
messages in the backup.log file and the bar_act.log file.
The backup.log file contains the following error message:

+++++ ON-Bar BACKUP FAILED Wed Feb 27 12:34:24 MST 2002

The bar_act.log file contains the following error message:

2002-02-27 12:34:17 6549 6547 XBSA Error: (BSAEndTxn) Exceeded

available resources.
2002-02-27 12:34:24 6549 6547 /opt/informix/bin/onbar_d complete,
returning 19 (0x13)

The error messages are generated because the system is attempting to migrate only part of an
ACD dbspace to the storage media. Entire ACD dbspaces must be migrated. ACD dbspaces
can contain more than 2 GB of data.
Contact your IBM Spectrum Protect administrator if these error messages are generated. The
administrator will need to adjust the highmig and lowmig storage pool variables based on the
amount of data to be stored on the disk drive and the amount of data to be migrated to the
storage media.

Verifying the network card settings

! Important:
Important: To determine which parameters are supported by a driver, use the following
command: ndd /dev/e1000g0 \?

Using Avaya CMS LAN Backup March 2021 67

Chapter 5: Troubleshooting the LAN backup feature

Procedure
1. To determine the duplex setting of the network card, enter:
ndd /dev/e1000g0 link_duplex
The system displays a number representing the duplex setting for the network interface.

Number displayed Link mode

1 half
2 full

2. To determine the speed of the network connection, enter:

ndd /dev/e1000g0 link_speed
The system displays a number representing the speed setting for the network interface.

Link speed (Mbps)

10 Mbps
100 Mbps
1000Mbps

3. To determine network connectivity, enter:

ndd /dev/e1000g0 link_status
The system displays a number representing the status of the network interface.

Number displayed Link mode

0 no link
1 link established

Note:
Note: If you need to change any network card settings, contact your Avaya or Avaya
partner representative.

Using Avaya CMS LAN Backup March 2021 68

 Checking shared memory parameters

Checking shared memory parameters

About this task
If a data restore fails, check the shared memory parameters. Shared memory errors may be
created if a data restore fails or is manually stopped before completion. If the shared memory
errors are not removed, future restores will fail. The system may also display the following error
message:

oninit: Fatal error in shared memory creation

Procedure
1. Verify that the CMS software and IDS software are off.
a. Enter:
cmsadm
The system displays the CMSADM menu.
b. Enter the number associated with the run_cms option.
c. Enter the number associated with the Turn off both CMS and IDS option.
2. Determine if there are any shared memory errors by entering:
ipcs
The system displays one of the following messages:
● If there are no memory errors the system displays a message similar to the following:

IPC status from <running system> as of Mon Mar 4 14:55:37 EST 2002
T ID KEY MODE OWNER GROUP
Message Queues:
Shared Memory:
m 0 0x50000b2d --rw-r--r-- root root
m 4 0x50302 --rw-rw-rw- root root
m 5 0x30302 --rw-rw-rw- root root
Semaphores:
s 4 0x540302 --ra-ra-ra- root root

Using Avaya CMS LAN Backup March 2021 69

Chapter 5: Troubleshooting the LAN backup feature

● If there are memory errors the system displays a message similar to the following:

IPC status from <running system> as of Mon Mar 4 14:41:22 EST 2002
T ID KEY MODE OWNER GROUP
Message Queues:
Shared Memory:
m 0 0x50000b2d --rw-r--r-- root root
m 1318 0x52574801 --rw-rw---- root informix
m 1319 0x52574802 --rw-rw---- root informix
m 1320 0x52574803 --rw-rw-rw- root informix
m 4 0x50302 --rw-rw-rw- root root
m 5 0x30302 --rw-rw-rw- root root
Semaphores:
s 4 0x540302 --ra-ra-ra- root root

3. Remove any entries that have a group of Informix by entering:

ipcrm -m ID
where ID is the ID number for the line.
Example:
ipcrm -m 1318
4. It may be necessary to repeat Step 3 several times. Remove all Informix entries under
Message Queues, Shared Memory, and Semaphores.

Restarting a IBM Spectrum Protect restore after it has

stopped
About this task
If a data or system restore is stopped partway through the restore process, you might receive
the following error message when you attempt to restart the restore:

An active restore for the same source file specification exsists.

The system generates this message when the restore command is run. This message is
displayed from the terminal window and in the dsmerror.log file. This error is generated
because the IBM Spectrum Protect server is still attempting to execute the previous restore
session.

Using Avaya CMS LAN Backup March 2021 70

 Restarting a IBM Spectrum Protect restore after it has stopped

Procedure
1. Enter:
dsmc cancel restore
The system displays a list of the restore sessions that are still running.
2. Enter the number of the session you want to cancel. It might be necessary to repeat this
process several times.
3. After removing the previous restore sessions, choose one of the following commands to
start a new restore process:
● Restore the system data by entering:
/cms/LANbkup/bin/restore.tivoli
● Restore the CMS data by entering:
/cms/LANbkup/bin/onbar_restore.tivoli
4. Continue with the remainder of the restore procedure you were doing.

Using Avaya CMS LAN Backup March 2021 71

Chapter 5: Troubleshooting the LAN backup feature

Using Avaya CMS LAN Backup March 2021 72

Chapter 6: Resources

Documentation

CMS and CMS Supervisor Documents

Title Description Audience

Overview
Avaya Call Management Describes tested product characteristics and Sales engineers,
System Overview and product capabilities including feature Administrators
Specification descriptions, interoperability, performance
specifications, security, and licensing
requirements.
Product Privacy Statement for Describes how personal data is stored and Administrators
Avaya Call Management processed by CMS.
System
Design
Avaya Customer Experience Describes the Avaya Customer Experience Sales engineers
Virtualized Environment Virtualized Environment market solution
Solution Description from a holistic perspective that focuses on
the functional view of the solution
architecture.
Installation, upgrades, maintenance, and troubleshooting
Deploying Avaya Call Describes how to plan, deploy, and Avaya support
Management System configure CMS on new VMware-based personnel
installations.
Deploying Avaya Call Describes how to plan, deploy, and Avaya support
Management System on configure CMS on new Amazon Web personnel
Amazon Web Services Services installations.
Port Matrix for Avaya Call Lists the ports and connections used by Avaya support
Management System CMS. personnel

Using Avaya CMS LAN Backup March 2021 73

Chapter 6: Resources

Title Description Audience

Avaya Call Management Describes how to install, maintain, and Avaya support
System Dell® PowerEdge™ troubleshoot Dell® servers used with CMS. personnel
R630 and R730 Hardware
Installation, Maintenance and
Troubleshooting
Avaya Call Management Describes how to install, maintain, and Avaya support
System HPE DL20 G9 and troubleshoot HPE servers used with CMS. personnel
DL380 G9 Hardware
Installation, Maintenance, and
Troubleshooting
Planning for Avaya Call Describes the procedures customers must Administrators
Management System Upgrades plan for before and after upgrading to a new
CMS release.
Upgrading Avaya Call Describes the procedures required to Avaya support
Management System upgrade to a new CMS release. personnel
Avaya Call Management Describes the procedures to upgrade from Avaya support
System Base Load Upgrade one base load (for example, 19.1.0.0) to personnel,
another base load (for example, 19.1.0.1). Administrators
Not all releases support base load upgrades.
Maintaining and Describes how to configure, maintain, and Avaya support
Troubleshooting Avaya Call troubleshoot CMS. personnel,
Management System Administrators
Avaya Call Management Describes how to connect and administer Avaya support
System and Communication the Communication Manager systems used personnel,
Manager Connections, by CMS.
Administration, and Administrators
Troubleshooting
Avaya Call Management Describes how to connect to HA servers and Avaya support
System High Availability upgrade to HA. personnel,
Connectivity, Upgrade and
Administration Administrators

User guides
Using Avaya Call Management Describes how to use and maintain a CMS Avaya support
System High Availability HA system. personnel,
Administrators
Using Avaya Call Management Describes how to back up your CMS data Administrators
System LAN Backup using a LAN connection to a remote server.
Using Avaya Call Management Describes how to install and maintain your Avaya support
System High Availability CMS High Availability (HA) system. personnel,
Administrators

Using Avaya CMS LAN Backup March 2021 74

 Documentation

Title Description Audience

Using ODBC and JDBC with Describes how to use Open Database Administrators
Avaya Call Management Connectivity (ODBC) and Java Database
System Connectivity (JDBC) with CMS.
Administration
Administering Avaya Call Provides instructions on administering a Avaya support
Management System contact center using CMS Supervisor. personnel,
Administrators
Avaya Call Management Describes the format of the Call History data Administrators
System Call History Interface files and how to transfer these files to
another computer.
Avaya Call Management Describes each database item and Administrators,
System Database Items and calculation that CMS tracks and how CMS Report designers
Calculations calculates the values displayed on CMS
reports and CMS Supervisor reports.
Avaya Call Management Describes how to design and create custom Administrators,
System Custom Reports reports in CMS. Operations
personnel, Report
designers
Avaya Call Management Describes how to implement security Avaya support
System Security features in CMS. personnel,
Administrators.
CMS Supervisor
Avaya CMS Supervisor Clients Describes how to install and configure CMS Avaya support
Installation and Getting Started Supervisor. personnel,
Administrators
Avaya CMS Supervisor Reports Describes how to use CMS Supervisor Administrators,
reports. Operations
personnel
Avaya CMS Supervisor Report Describes how to create new reports and to Administrators,
Designer edit existing reports through Report Operations
Designer and Report Wizard. personnel, Report
designers

Using Avaya CMS LAN Backup March 2021 75

Chapter 6: Resources

Avaya Solutions Platform Documents

Title Description Audience

Avaya Solutions Describes the key features of Avaya IT Management, sales and
Platform Overview and Solutions Platform server. deployment engineers, solution
Specification architects, support personnel
Installing the Avaya Describes how to install Avaya Solutions Sales and deployment engineers,
Solutions Platform 130 Platform 130 Series servers. solution architects, support
Appliance personnel
Maintaining and Describes procedures to maintain and Sales and deployment engineers,
Troubleshooting Avaya troubleshoot Avaya Solutions Platform solution architects, support
Solutions Platform 130 130 Series servers. personnel
Appliance
Avaya Solutions Describes procedures to use the Sales and deployment engineers,
Platform 130 Series iDRAC9 tools on the Avaya Solutions solution architects, support
iDRAC9 Best Platform 130 Series servers. personnel
Practices

WebLM Documents

Title Description Audience

Deploying standalone Avaya Deploy the application in virtual appliance Implementation
WebLM in Virtual Appliance environment by using Solution personnel
Deployment Manager.
Deploying standalone Avaya Deploy the application in virtualized Implementation
WebLM in Virtualized Environment environment. personnel
Deploying standalone Avaya Deploy the application on cloud services. Implementation
WebLM in Infrastructure as a personnel
Service Environment
Deploying standalone Avaya Deploy the application in software-only Implementation
WebLM in Software-Only environment. personnel
Environment
Upgrading standalone Avaya Upgrade the application. Implementation
WebLM personnel
Administering standalone Avaya Administer the system. System
WebLM administrators

Using Avaya CMS LAN Backup March 2021 76

 Documentation

VMware Documents

VMware Document description Document URL

component or
operation
vSphere Virtual Provides information on managing virtual https://docs.vmware.com/en/
Machine machines in the VMware vSphere Web Client for VMware-vSphere/6.5/
Administration vSphere 6.0 or later. This document also provides com.vmware.vsphere.vm_a
information of the following: dmin.doc/
GUID-55238059-912E-411F
● Deploying OVF templates -A0E9-A7A536972A91.html
● Configuring virtual machine hardware and
options
● Managing Virtual Machines
vSphere Web Provides information on how through a browser https://docs.vmware.com/en/
Client vSphere Web Client connects to a vCenter server VMware-vSphere/6.5/
or directly to an ESXi host if a vCenter Server is com.vmware.vsphere.vcent
not used. erhost.doc/
GUID-A618EF76-638A-49D
A-991D-B93C5AC0E2B1.ht
ml

Note:
Note: If the document description (link) are no longer active, consult VMware for
documents associated with the component or operation.

Related links
Finding documents on the Avaya Support website on page 77
Accessing the port matrix document on page 78
Avaya Documentation Portal navigation on page 78

Finding documents on the Avaya Support website

Procedure
1. Go to https://support.avaya.com.
2. Log on to the Avaya website with a valid Avaya user ID and password.
3. Click Support by Product > Documents.

Using Avaya CMS LAN Backup March 2021 77

Chapter 6: Resources

4. In Enter your Product Here, type the product name and then select the product from the
list.
5. In Choose Release, select an appropriate release number.
The Choose Release field is not available if there is only one release for the product.
6. In the Content Type filter, click a document type, or click Select All to see a list of all
available documents.
For example, for user guides, click User Guides in the Content Type filter. The list only
displays the documents for the selected category.
7. Click the document to open it in your browser or download the document.

Accessing the port matrix document

Procedure
1. Go to https://support.avaya.com.
2. Log on to the Avaya website with a valid Avaya user ID and password.
3. Click Support by Product > Documents.
4. In Enter your Product Here, type the product name and then select the product from the
list.
5. In Choose Release, select an appropriate release number.
The Choose Release field is not available if there is only one release for the product.
6. In the Content Type filter, select one or more of the following categories:
● Application & Technical Notes
● Design, Development & System Mgt
The system displays the Port Matrix document.
7. Click the document to open it in your browser or download the document.

Avaya Documentation Portal navigation

Customer documentation for some programs is now available on the Avaya Documentation
Center website at https://documentation.avaya.com/.

! Important:
Important: For documents that are not available on the Avaya Documentation Center, click
More Sites > Support on the top menu to open https://support.avaya.com.

Using Avaya CMS LAN Backup March 2021 78

 Viewing Avaya Mentor videos

Using the Avaya Documentation Center, you can:

● Search for content in one of the following ways:
- Type a keyword in Search, and click Filters to search for content by product or
release.
- From Products & Solutions, select a solution and product and then select the
appropriate document from the list.
● Sort documents on the search results page by last updated and relevance.
● Publish a PDF of the current section in a document, the section and its subsections, or the
entire document.
● Add content to your collection by using My Docs.
Navigate to the Manage Content > My Docs menu, and do any of the following:
- Create, rename, and delete a collection.
- Add content from various documents to a collection.
- Save a PDF of selected content in a collection and download it to your computer.
- Share content in a collection with others through email.
- Receive content that others have shared with you.
● Add yourself as a watcher by using the Watch icon.
Navigate to the Manage Content > Watchlist menu, and do the following:
- Enable Include in email notification to receive alerts in email.
- Unwatch selected content, all content in a document, or all content on the Watch list
page.
As a watcher, you are notified when content is updated or deleted from a document, or the
document is removed from the portal.
● Share a section on social media platforms, such as Facebook, LinkedIn, and Twitter.
● Send feedback on a section and rate the content.
Note:
Note: Some functionality is only available when you log in to the portal. The available
functionality depends on the role with which you are logged in.

Viewing Avaya Mentor videos

Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot
Avaya products.

Using Avaya CMS LAN Backup March 2021 79

Chapter 6: Resources

About this task

Videos are available on the Avaya Support website, listed under the video document type, and
on the Avaya-run channel on YouTube.

Procedure
● To find videos on the Avaya Support website, go to https://support.avaya.com and do one
of the following:
- In Search, type Avaya Mentor Videos, click Clear All, and select Video in the
Content Type.
- In Search, type the product name. On the Search Results page, click Clear All, and
select Video in the Content Type.
The Video content type is displayed only when videos are available for that product.
In the right pane, the page displays a list of available videos.
● To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and
do one of the following:
- Enter a key word or key words in the Search Channel to search for a specific product
or topic.
- Scroll down Playlists, and click the name of a topic to see the list of videos available for
the topic. For example, Contact Centers.
Note:
Note: Videos are not available for all products.

Support
Go to the Avaya Support website at https://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you
to a support team if an issue requires additional expertise.

Related links
Using the Avaya InSite Knowledge Base on page 80

Using the Avaya InSite Knowledge Base

The Avaya InSite Knowledge Base is a web-based search engine that provides:

Using Avaya CMS LAN Backup March 2021 80

 Support

● Up-to-date troubleshooting procedures and technical tips

● Information about service packs
● Access to customer and technical documentation
● Information about training and certification programs
● Links to other pertinent information
If you are an authorized Avaya Partner or a current Avaya customer with a support contract, you
can access the Knowledge Base without extra cost. You must have a login account and a valid
Sold-To number.
Use the Avaya InSite Knowledge Base for any potential solutions to problems.
1. Go to https://support.avaya.com.
2. Log on to the Avaya website with a valid Avaya user ID and password.
The system displays the Avaya Support page.
3. Click Support by Product > Product Specific Support.
4. In Enter Product Name, enter the product, and press Enter.
5. Select the product from the list, and select a release.
6. Click the Technical Solutions tab to see articles.
7. Select relevant articles.

Using Avaya CMS LAN Backup March 2021 81

Chapter 6: Resources

Using Avaya CMS LAN Backup March 2021 82

Appendix A: Mirrored system disk pairs

Use the following tables to determine the disk layout for your mirrored system:

Dell R630 mirrored disk pairs

Primary disk Mirrored disk

slot 0 slot 1
slot 2

Dell R730 mirrored disk pairs

Primary disk Mirrored disk

slot 0 slot 1
slot 2 slot 3
slot 4 slot 5
slot 6 slot 7
slot 8 slot 9
slot 10 slot 11

HP DL380P G9 mirrored disk pairs

Primary disk Mirrored disk

slot 1 slot 7
slot 2 slot 8
slot 3 slot 9
slot 4 slot 10
slot 5 slot 11
slot 6 slot 12

Using Avaya CMS LAN Backup March 2021 83

Appendix A: Mirrored system disk pairs

Using Avaya CMS LAN Backup March 2021 84

Appendix B: Example IBM Spectrum
Protect policy domain

A policy domain is a group of clients that have similar requirements for backing up and archiving
data. It is recommended that you create a separate policy domain for your CMS servers.The
settings for your particular policy domain will vary from those given in this procedure. For
guidelines on backing up a CMS server, see Recommendations for backing up data on page 31
and the appropriate IBM Spectrum Protect documentation.

! Important:
Important: Avaya support personnel are not responsible for configuring policy domains or
providing IBM Spectrum Protect support.
Example procedure:
1. Enter:
dsmadmc
The system displays the following message:

Tivoli Storage Manager

Command Line Administrative Interface - Version 4, Release 2, Level 1.0
(C) Copyright IBM Corporation, 1990, 2001, All Rights Reserved.

Enter your user id:

2. Enter your user ID.

The system displays the following message:

Enter your password:

3. Enter your password.

The system displays the tsm: SERVER1> prompt.
4. Do the following procedure to configure a policy domain:
a. Create a copy of the standard policy domain by entering:
copy domain standard cmsdomain
Note:
Note: The dash (-) at the end of the following command, allows you to enter a single
large command as several smaller lines of text. The dash allows the command to
continue across multiple lines.

Using Avaya CMS LAN Backup March 2021 85

Appendix B: Example IBM Spectrum Protect policy domain

b. Update the backup copy group by entering:

update copygroup cmsdomain standard standard standard -
type=backup verexists=4
c. Verify the policy set by entering:
validate policyset cmsdomain standard
d. Activate the policy set for the policy domain by entering:
activate policyset cmsdomain standard
Note:
Note: If the node is not registered, you must register the node by entering the following
command:
register node samplenode samplepassword domain=cmsdomain -
userid=none
e. Add the node to the policy domain by entering:
update node samplenode domain=cmsdomain

Using Avaya CMS LAN Backup March 2021 86

Appendix C: Example CMS scheduler
policy for IBM Spectrum
Protect

The IBM Spectrum Protect scheduler is used to automate your backups. This appendix shows
an example of how to set up a scheduler policy. The settings for your particular scheduler policy
will vary from those given in this procedure. For guidelines on backing up a CMS server, see
Recommendations for backing up data on page 31 and the appropriate IBM Spectrum Protect
documentation.

! Important:
Important: Avaya support personnel are not responsible for configuring scheduler policies or
providing IBM Spectrum Protect support.
Example procedure:
1. On the CMS server, do the following procedure:
a. Enter:
vi /etc/inittab
The system displays the inittab file.
b. Add the following line to the end of the file:
ts::once:/usr/bin/dsmc sched > /dev/null 2>&1
c. To save and close the file press Esc. Then enter:
:wq!
d. Enter:
nohup dsmc sched > /dev/null 2>&1 &
2. Using the IBM Spectrum Protect Administrative interface, do the following procedure:
a. Enter:
dsmadmc
The system displays the tsm SERVER > prompt.
Note:
Note: The dash (-) at the end of the following commands, allows you to enter a single
large command as several smaller lines of text. The dash allows the command to
continue across multiple lines.

Using Avaya CMS LAN Backup March 2021 87

Appendix C: Example CMS scheduler policy for IBM Spectrum Protect

b. Define the backup schedule for the daily CMS incremental data backup by entering the
following commands:
define sched cmsdomain daily_cms_backup type=client -
desc="daily CMS incremental data backup" -
action=command obj="/cms/LANbkup/bin/onbar_backup.tivoli 1" -
startdate=06/01/2002 starttime=01:00:00 dayofweek=weekday
c. Define the backup schedule for the weekly CMS incremental system and full data
backups by entering the following commands:
define sched cmsdomain weekly_cms_backup type=client -
desc="weekly CMS incremental system and full data backups" -
action=command obj="/cms/LANbkup/bin/backup.tivoli 1; " -
"/cms/LANbkup/bin/onbar_backup.tivoli 0" -
startdate=06/01/2002 starttime=01:00:00 -
duration=4 durunits=hours perunits=weeks dayofweek=saturday
d. Define the backup schedule for the monthly CMS full system and incremental data
backups by entering the following commands:
define sched cmsdomain monthly_cms_backup type=client -
desc="monthly CMS full system and incremental data backups" -
action=command obj="/cms/LANbkup/bin/backup.tivoli 0; " -
"/cms/LANbkup/bin/onbar_backup.tivoli 1" -
startdate=06/01/2002 starttime=01:00:00 duration=4 -
durunits=hours perunits=months dayofweek=sunday
3. Enter the following commands:
define association cmsdomain daily_cms_backup samplenode
define association cmsdomain weekly_cms_backup samplenode
define association cmsdomain monthly_cms_backup samplenode
4. On the CMS server do the following procedure:
a. Enter:
dsmc
The system displays the tsm> prompt.

Using Avaya CMS LAN Backup March 2021 88

 b. Verify the schedule by entering:
q sched
The system displays a message similar to the following:

(gadwall)-(root)=# dsmc
IBM Tivoli Storage Manager
Command Line Backup-Archive Client Interface
Client Version 7, Release 1, Level 6.3
Client date/time: 12/19/2017 14:54:00
(c) Copyright by IBM Corporation and other(s) 1990, 2016. All Rights
Reserved.

Node Name: GADWALL

Session established with server FRITOS: Linux/x86_64
Server Version 7, Release 1, Level 1.100
Server date/time: 12/19/2017 00:49:37 Last access: 12/19/2017 00:21:42

tsm> q sched
Schedule Name: CMSADM
Description:
Schedule Style: Classic
Action: Incremental
Options:
Objects:
Priority: 5
Next Execution: 7 Hours and 11 Minutes
Duration: 1 Hour
Period: 1 Day
Day of Week: Any
Expire: Never

Schedule Name: WEEKLY_CMS_BACKUP

Description: Weekly full system backup
Schedule Style: Classic
Action: Archive
Options:
Objects: "/cms/LANbkup/bin/backup.tivoli 0"
Priority: 5
Next Execution: 102 Hours and 41 Minutes
Duration: 15 Minutes
Period: 1 Week
Day of Week: Saturday
Expire: Never

tsm>

Using Avaya CMS LAN Backup March 2021 89

Appendix C: Example CMS scheduler policy for IBM Spectrum Protect

Using Avaya CMS LAN Backup March 2021 90

Appendix D: Example CMS policies for
Netbackup

! Important:
Important: This appendix provides some CMS policy examples. There are other ways to get
the same results for some of the selections. Pay special attention to the policy
type because these are the policy types that are needed. Also, you must always
have the schedule looking like the items below if you are running the backups
from the CMS server as described in this document.

Example policy for data

The following screen shot shows the data policy attributes screen from a Netbackup server.

Using Avaya CMS LAN Backup March 2021 91

Appendix D: Example CMS policies for Netbackup

The next screen shows the policy schedule attributes:

The next screen shot shows the schedule start settings:

Using Avaya CMS LAN Backup March 2021 92

 Example policy for File systems (OS)

Example policy for File systems (OS)

The following screen shot shows the OS policy attributes screen from a Netbackup server:

Using Avaya CMS LAN Backup March 2021 93

Appendix D: Example CMS policies for Netbackup

The next screen shows the policy schedule attributes:

The next screen shot shows the file selections for OS backup policy.

Using Avaya CMS LAN Backup March 2021 94

Appendix E: Changing the root user ID
permissions to install software
using FTP

Procedure
1. Log on to the system as root.

! Important:
Important: You cannot directly log on as root from a remote connection. You must log on
using an administered CMS user ID, then use su - root to log on with root
privileges.
2. Make a copy of the /etc/ssh/ssh_config file using the following commands:
cd /etc/ssh
cp ssh_config ssh_config.OFF
3. On the Netbackup server, follow the Netbackup instructions for using the
install_client_files tool to install the Netbackup client software on the CMS server
using the sftp option and the root login.
4. When you are finished installing the Netbackup client software, reconfigure the root user
ID permissions using the following commands:
cd /etc/ssh
cp ssh_config.OFF ssh_config
systemctl stop sshd
systemctl start sshd

Using Avaya CMS LAN Backup March 2021 95

Appendix E: Changing the root user ID permissions to install software using FTP

Using Avaya CMS LAN Backup March 2021 96

Glossary

ACD See Automatic Call Distribution (ACD) on page 97.

Automatic Call A switch feature. ACD is software that channels high-volume incoming call
Distribution (ACD) traffic to agent groups (splits or skills).
Also an agent state where the extension is engaged in an ACD call (with the
agent either talking to the caller or the call waiting on hold).
Avaya Call A software product used by business customers that have a
Management telecommunications switch and receive a large volume of telephone calls that
System (CMS) are processed through the Automatic Call Distribution (ACD) feature of the
switch.
Avaya CMS See Avaya Call Management System (CMS) on page 97.
Data collection off CMS is not collecting ACD data. If you turn off data collection, CMS will not
collect data on current call activity.
Data backup The backup that uses ON-Bar to backup the CMS Informix data.
Data restore The restore that uses ON-Bar to restore the CMS Informix data.
Database A group of files that store ACD data according to a specific time frame: current
and previous intrahour real-time data and intrahour, daily, weekly, and monthly
historical data.
Database item A name for a specific type of data stored in one of the CMS databases. A
database item may store ACD identifiers (split numbers or names, login IDs,
VDNs, and so on) or statistical data on ACD performance (number of ACD
calls, wait time for calls in queue, current states of individual agents, and so on).
Database tables Tables that CMS uses to collect, store, and retrieve ACD data. Standard CMS
items (database items) are names of columns in the CMS database tables.
Device The term used to refer to the peripheral itself; for example, a hard disk or a tape
drive. A peripheral is sometimes referred to as a subdevice or an Logical Unit
(LU).
Disk A round platter, or set of platters, coated with magnetic medium and organized
into concentric tracks for storing data.
EAD See Expert Agent Distribution (EAD) on page 98.
EAS See Expert Agent Selection (EAS) on page 98.
Error message An error message is a response from a program indicating that a problem has
arisen or something unexpected has happened, requiring your attention.

Using Avaya CMS LAN Backup March 2021 97

Ethernet

Ethernet A type of network hardware that allows communication between systems

connected directly together by transceiver taps, transceiver cables, and a
coaxial cable. Also implemented using twisted-pair telecommunications wire
and cable.
Exception A type of activity on the ACD which falls outside of the limits the customer has
defined. An exceptional condition is defined in the CMS Exceptions subsystem,
and usually indicates abnormal or unacceptable performance on the ACD (by
agents, splits or skills, VDNs, vectors, trunks, or trunk groups).
Expert Agent A call queued for a skill will go to the most idle agent (primary skill agent).
Distribution (EAD) Agents who are idle and have secondary agent skills will receive the call
queued for a skill if there are no primary agents available.
Expert Agent An optional feature that bases call distribution on agent skill (such as language
Selection (EAS) capability). EAS matches the skills required to handle a call to an agent who
has at least one of the skills required.
Forecast reports These reports display expected call traffic and agent or trunk group
requirements for the customer’s call center for a particular day or period in the
future.
Historical database Contains intrahour records for up to 62 days in the past, daily records for up to
5 years in the past, and weekly or monthly records for up to 10 years for each
CMS-measured agent, split or skill, trunk, trunk group, vector, and VDN.
Historical reports Reports that display past ACD data for various agent, split or skill, trunk, trunk
group, vector, or VDN activities.
Host name A name that you (or your system administrator) assign to your system unit.
IDS See Informix Dynamic Server (IDS) on page 98.
Informix Dynamic The relational database management system that is used with CMS Release 3
Server (IDS) Version 9 and later.
Link A transmitter-receiver channel or system that connects two locations.
Log in The process of gaining access to a system by entering a user name and,
optionally, a password.
Log out The process of exiting from a system.
Measured A term that means an ACD element (agent, split or skill, trunk, trunk group,
vector, VDN) has been identified to CMS for collection of data.
Multi-user mode A mode of CMS in which any administered CMS user can log into CMS. Data
continues to be collected if data collection is “on”.
Network address A unique number assigned to each system on a network, consisting of the
network number and the system number. Also known as Internet Address or
Internet Protocol (IP) address.
Node A unique name used to identify a client to the server.

Using Avaya CMS LAN Backup March 2021 98

 TSC

Non-Volatile A random access memory (RAM) system that holds its contents when external
Random Access power is lost.
Memory (NVRAM)
NVRAM See Non-Volatile Random Access Memory (NVRAM) on page 99.
ON-Bar An Informix IDS tool that works with a Storage Manager to backup and restore
the Informix Database.
Operating system The software that controls and allocates the resources, such as memory, disk
(OS) storage, and the screen display for the computer.
Single-user mode A CMS mode in which only one person can log into CMS. Data collection
continues if data collection is “on”. This mode is required to change some CMS
administration.
Skill In relationship to the call center, think of skill as a specific customer need or
requirement, or perhaps a business need of the call center.
SQL See Structured Query Language (SQL) on page 99.
Small Computer A hardware interface that allows the connection of peripheral devices (such as
System Interface hard disks, tape drives and CD-ROM drives) to a computer system.
(SCSI)
Split A group of extensions that receive special-purpose calls in an efficient,
cost-effective manner. Normally, calls to a split arrive over one or a few trunk
groups.
Storage device A hardware device that can receive data and retain it for subsequent retrieval.
Such devices cover a wide range of capacities and speeds of access.
Storage manager A 3rd party software package that manages backups and restores. It gets the
data from CMS and ON-Bar and writes it to the storage devices.
Structured Query A language used to interrogate and process data in a relational database. SQL
Language (SQL) commands can be used to interactively work with a database or can be
embedded within a programming language to interface to a database.
Super-user A user with full access privileges on a system, unlike a regular user whose
access to files and accounts is limited.
Switch A private switch system providing voice-only or voice and data communications
services (including access to public and private networks) for a group of
terminals within a customer’s premises.
System A general term for a computer and its software and data.
System backup The backup that uses a storage manager to backup the UNIX files.
System restore The restore that uses a storage manager to restore the UNIX files.
TCP/IP See Transmission Control Protocol/Internet Protocol (TCP/IP) on page 100.
TSC Technical Service Center. The Avaya organization that provides technical
support for Avaya products.

Using Avaya CMS LAN Backup March 2021 99

Transmission Control Protocol/Internet Protocol (TCP/IP)

Transmission A communications protocol that provides interworking between dissimilar

Control Protocol/ systems. It is the de facto standard for Linux systems.
Internet Protocol
(TCP/IP)
Trunk A telephone line that carries calls between two switches, between a Central
Office (CO) and a switch, or between a CO and a phone.
Trunk group A group of trunks that are assigned the same dialing digits - either a phone
number or a Direct Inward Dialing (DID) prefix.
User ID The login ID for a CMS user.
User name A combination of letters, and possibly numbers, that identifies a user to the
system.
VDN See Vector Directory Number (VDN) on page 100.
Vector A list of steps that process calls in a user-defined manner. The steps in a vector
can send calls to splits, play announcements and/or music, disconnect calls,
give calls a busy signal, or route calls to other destinations. Calls enter vector
processing by way of VDNs, which may have received calls from assigned
trunk groups, from other vectors, or from extensions connected to the switch.
Vector Directory An extension number that is used in ACD software to permit calls to connect to
Number (VDN) a vector for processing. A VDN is not assigned an equipment location; it is
assigned to a vector. A VDN can connect calls to a vector when the calls arrive
over an assigned automatic-in trunk group or when calls arrive over a
dial-repeating (DID) trunk group, and the final digits match the VDN. The VDN
by itself may be dialed to access the vector from any extension connected to
the switch.
XBSA (X/Open An open system interface that allows ON-Bar to communicate to the Storage
Backup Services Manager.
Application
Programmer's
Interface)

Using Avaya CMS LAN Backup March 2021 100

 Index

Index

B G
back.log . . . . . . . . . . . . . . . . . . . . . . 58 Glossary . . . . . . . . . . . . . . . . . . . . . . 97
backup
data . . . . . . . . . . . . . . . . . . . . . . 34
recommendations . . . . . . . . . . . . . . . . 31 H
system . . . . . . . . . . . . . . . . . . . . . 32 hardware
bar_act.log . . . . . . . . . . . . . . . . . . . . 61 required . . . . . . . . . . . . . . . . . . . . 12
basic . . . . . . . . . . . . . . . . . . . . . . . 57 https
//support.avaya.com/Copyright . . . . . . . . . . . 3
C
CMS I
data restore . . . . . . . . . . . . . . . . . . 43 include exclude list . . . . . . . . . . . . . . . 25, 65
system restore . . . . . . . . . . . . . . . . . 46
configuring software
LAN backup, initial . . . . . . . . . . . . . . . 16 L
LAN backup
D initial software configuration . . . . . . . . . . . 16
support . . . . . . . . . . . . . . . . . . . . . 13
data backup
logs . . . . . . . . . . . . . . . . . . . . . . 58
on demand . . . . . . . . . . . . . . . . . . . 35 M
performing . . . . . . . . . . . . . . . . . . . 34
mirrored system disk pairs . . . . . . . . . . . . . 83
disk pairs . . . . . . . . . . . . . . . . . . . . . 83
dsierror.log . . . . . . . . . . . . . . . . . . . . 61
dsm.sys . . . . . . . . . . . . . . . . . . . . . . 22
dsmerror.log . . . . . . . . . . . . . . . . . . . . 61
N
network card . . . . . . . . . . . . . . . . . . . . 67

E
error logs . . . . . . . . . . . . . . . . . . . . . 58
O
error messages ON-Bar
shared memory . . . . . . . . . . . . . . . . . 69 recommended configurations . . . . . . . . . . . 17
storage pool variables . . . . . . . . . . . . . . 67

R
F recommended configurations
failure ON-Bar . . . . . . . . . . . . . . . . . . . . . 17
data restore . . . . . . . . . . . . . . . . . 69, 70 storage manager . . . . . . . . . . . . . . . . 20
system restore . . . . . . . . . . . . . . . . . 70 required
hardware . . . . . . . . . . . . . . . . . . . . 12
software . . . . . . . . . . . . . . . . . . . . 11
responsibilities . . . . . . . . . . . . . . . . . . . 13
restarting a restore . . . . . . . . . . . . . . . . . 70
restore
CMS data . . . . . . . . . . . . . . . . . . . . 43

Using Avaya CMS LAN Backup March 2021 101

Index

CMS system . . . . . . . . . . . . . . . . . . 46
specific files . . . . . . . . . . . . . . . . . . 46
restore.log . . . . . . . . . . . . . . . . . . . . . 63

S
shared memory . . . . . . . . . . . . . . . . . . 69
software
required . . . . . . . . . . . . . . . . . . . . .11
storage manager
recommended configurations . . . . . . . . . . 20
storage pool variables . . . . . . . . . . . . . . . 67
system backup . . . . . . . . . . . . . . . . . . 32
on demand . . . . . . . . . . . . . . . . . . . 33

T
Tivoli
password file . . . . . . . . . . . . . . . . . . 24
troubleshooting . . . . . . . . . . . . . . . . . . 57
data backup log . . . . . . . . . . . . . . . . 58
include exclude list . . . . . . . . . . . . . . . 65
network card . . . . . . . . . . . . . . . . . . 67

V
verifying
dsm.sys . . . . . . . . . . . . . . . . . . . . 22
include exclude list . . . . . . . . . . . . . . . 25
network card settings . . . . . . . . . . . . . . 67

Using Avaya CMS LAN Backup March 2021 102