W-NMS Backup and Restore User Guide

411-8111-521
UMTS, GPRS, GSM
W-NMS Backup and Restore

User Guide
OAM 4.2 Preliminary 06.10 June 2005
Whats inside...
Understanding backup and restore
Performing system backup and restore
Performing configuration data backup and restore
Performing historical data archive and retrieval
Performing centralized backup and restore with an archive policy
Performing centralized backup and restore with no archive policyRMAN
used for HFB Oracle database
Appendix A: Additional processes and information
Appendix B: Data backed up
Appendix C: Troubleshooting
Appendix D: Technical note - alternative policies
test
UMTS, GPRS, GSM

User Guide
Document number: 411-8111-521

Product release: OAM 4.2
Document version: Preliminary 06.10
Date: June 2005
Copyright 20012005 Nortel, All Rights Reserved

Copyright Country of printing Confidentiality Legal statements Trademarks
Originated in Canada and the USA

NORTEL CONFIDENTIAL
The information contained herein is the property of Nortel and is strictly confidential. Except as expressly authorized in writing by
Nortel, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know,
and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to
protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel,
the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel reserves the right to make changes in design or components as progress in
engineering and manufacturing may warrant.
* Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks. NIMSPrOptima is a trademark of MyCom International. Sun Fire and Sun StorEdge are trademarks of Sun Microsystems, Inc.VERITAS
NetBackup is a trademark of VERITAS Software Global Corporation
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
iv
Nortel Confidential
411-8111-521
Preliminary
Copyright 20012005 Nortel
06.10
June 2005
v
Nortel Confidential
Publication history
May 2005
OAM 4.2 Preliminary general re-release, issue 06.10.
This release adds a note about Veritas Netbackup version support.
April 2005
OAM 4.2 Preliminary re-release to LiveLink only, issue 06.09.
Answer to Q01108740, NTP timer restriction no longer applies, as the
backup/restore scripts deal with the issue.
March 2005
OAM 4.2 Preliminary release, issue 06.08
Added CMS-related directories to the lists in Appendix C.
Corporate rebranding (content only)
March 2005
OAM 4.2 - Draft release (06.07)
Added recommendations for setting backup times for archiving historical
data. Refer to Procedure 5-1, Procedure 5-5 and Appendix C, Appendix
C: Troubleshooting, Centralized Data Backup.
Added PAM directories to Table B-6.
February 2005
OAM 4.2 - Draft 6.06 (to test)
Update of 4.2 document with post-Standard CR fixes entered in the 4.1
document.
Q010600001: Sun Fire E4900 backup and restore procedures. (Procedure

2-5 and Procedure 2-8)
Q01038906: various small changes
UMTS, GPRS, GSM
OAM 4.2
vi Publication history
Nortel Confidential
January 2005
OAM 4.2Draft 6.05. Fixed the following CRs:
Q01038906 BR: Inconsistency backup data in SRS
Q01045552 BR: NTP issues with ctrl-d messages for 4800 server
Q01048288 UMTS:v4.1:B&R: NTP doc 411-8111-521 B&R user guide
Updated documentation roadmap drawing and re-branding tables.

December 2004
Q01021419 B&R: Appendix B of NTP 411-8111-521 needs to reflect
new location of files
Q01033454 B&R: Appendix B of NTP 411-8111-521 need to update for

new backup file on soc
Q01033574 B&R: Appendix B of NTP 411-8111-521 need to update list

for MDP comp on perf
Q01033595 B&R: Appendix B of NTP 411-8111-521 needs to add sys

mgmt component to table B-8
Q01034380 B&R: Appendix B of NTP 411-8111-521 needs to add 2 files

for perf server
Q01040622 BR: remove tape during system restore generates infinite

loop
November 2004
Q01022527-01: removed -L option from local data backup and restore,
and local archive and retrieval
Q01021419: Update Appendix B for changed locations of coreDA files
Q01027762: Update Appendix B for changed stability data files and new
wiclet user files
Q01029791: Update procedure 5-11 to match changed user interface.
Q01028775: Update Appendix B for changed location of csal.properties

file
Additional changes include updating the name of the Solaris agent to match
changing VERITAS terminology and adding Srm.config to SRS component
in Appendix B.
411-8111-521
Preliminary
06.10
June 2005
Publication history vii

Nortel Confidential
November 2004
OAM 4.2Draft 6.02
Removed references to iut_addmachineinroc.sh -xml
Restore lost headings in Performing centralized backup and restore with

an archive policy.
Corrected typos
November 2004
OAM 4.2Draft 6.01
Changed Performing centralized backup and restore with an archive
policy and Performing centralized backup and restore with no archive
policyRMAN used for HFB Oracle database to require manual
installation of Veritas NetBack Solaris and Oracle agents.
Updated documentation references for NetBackup 5.1.
Updated Appendix B: Data backed up as indicated by change bars.
October 2004
OAM 4.1Preliminary 5.17. Fixed Case 040819-61194.
September 2004
OAM 4.1Preliminary 5.16.
Fixed CR Q00954549 by changing Procedure 3-3 step 12 and Procedure
5-10 step 17 to make the state of the HFB Oracle database irrelevant.
Fixed CR Q00954058 by changing steps 4 and 5 of procedure 2-1 to

remove retrieve staging.
Fixed CR Q00954561 by adding a new step (Step 14) to Procedure 3-3

and to Procedure 5-10 (Step 19).
Added support for feature 28129 Backup and Restore Oracle Database
Using RMAN Utility.
Added support for defining a policy to backup multiple servers.
Updated Appendix B: Data backed up as indicated by change bars.
Added Appendix D: Technical note - alternative policies.
Fixed CR Q00976062 by adding the tape type to the requirements for

specific procedures.
Updated branding.
August 2004
OAM 4.1Preliminary 5.10-5.15. Draft for internal review.
UMTS, GPRS, GSM
OAM 4.2
viii Publication history

Nortel Confidential
July 2004
OAM 4.1Preliminary 5.09. Added documentation roadmap to About this
document and corrected branding tables.
June 2004
OAM 4.1Draft 5.08. Fixed CR Q00919465 by adding a note to procedures
3-1 and 4-1 that if a local backup or archive is invoke while the centralized
versions of the operations is running, both will fail. Corrected typo on page 16. Fixed CR Q00925527 by changing step 4 in procedure 5-10.
June 2004
OAM 4.1Draft 5.07. Added procedure for configuring automatic local data
backup.
April-June 2004
OAM 4.1Draft 5.01 through 5.06 for internal review. Development of
document branched off of OAM 4.0a document - issues 4.x continues to
support OAM 4.0a, issues 5.x support OAM 4.1. Branding updated.
Document now tracks OAM software release rather than network releases.
Fixes for CRs Q00890716 and Q00891546 rolled forward into current
release. Added troubleshooting section (Appendix C). Numerous usability
improvements.
March 2004
UMTS 4.0, GPRS 6.0Preliminary, Issue 04.09. Release for OAM 4.0a.
Resolve CR Q00864772, minor changes to Procedure 2-2.
March 2004
UMTS 4.0, GPRS 6.0Draft, Issue 04.08.
Update Appendix B to show the data backed up by type of backup: system,
data, and historical.
Update procedure 4-10 to explain that you can restore historical data for an
individual application.
February 2004
Resolve CR Q00804565. Add prerequisite in chapter 1 that only one NTP
server protocol process can be running. Applies to all servers.
411-8111-521
Preliminary
06.10
June 2005
Publication history ix
Nortel Confidential
Resolve CR Q00842704. Add restriction on performing a primary main

server backup and secondary main server backup at the same time.
Resolve Q00842698-01. Add setenv diag-switch? true command.
February 2004
Resolve CRs Q00832688, Q00838703, Q00838709: updates to procedures 33, 3-4, 3-5, 3-6.
January 2004
Remove all references to Oracle on the main server (primary and secondary)
as Oracle is no longer installed on it.
January 2004
UMTS 4.0, GPRS 6.0Draft, Issue 04.04. Updates from Verification.
December 2003
UMTS 4.0, GPRS 6.0Draft, Issue 04.03. Additional updates from Design.
December 2003
UMTS 4.0, GPRS 6.0Draft, Issue 04.02. Updates based on Design review.
December 2003
UMTS 4.0, GPRS 6.0Draft, Issue 04.01. This document includes
information and procedures for full system backup and restore that used to be
in the GPRS/UMTS OAM Full Backup and Restore Procedure, 411-8111-537.
The previous release of this document was named Preside for Wireless
Internet OAM Data Backup and Restore User Guide. It has been renamed to
Preside for Wireless Internet OAM Backup and Restore User Guide.
November 2003
UMTS 3.0, GPRS 5.0Standard, Issue 03.15 (GGSN 3.2). The following
updates have been made:
In Appendix A, corrected the HFB directories backed up.
September 2003
UMTS 3.0, GPRS 5.0Standard, Issue 03.14 (GPRS 5.0 ChR).
UMTS, GPRS, GSM
OAM 4.2
x Publication history
Nortel Confidential
August 2003
UMTS 3.0, GPRS 5.0Standard (UMTS 3.0 ChR), Issue 03.13
June 2003
UMTS 3.0, GPRS 5.0Standard, Issue 03.12.
November 2002
GPRS 5.0, UMTS 3.0, Preliminary, Issue 03.05.
September 2002
GPRS 5.0, UMTS 3.0, Draft, Issue 03.01.
June 2002
UMTS 2.1, Draft, Issue 02.09.
April, 2002
Preliminary, Issue 02.08.
February 2002
UMTS 2.0, Draft, Issue 02.01. First draft of the backup and restore user
guide.
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
xi
Contents
About this document
xi
About this document
xv
Audience for this document xv

Organization of this document xv
Related documents xvi
Roadmap to W-NMS documents
Indication of hypertext links xviii
Nortel branding xix
xvii

Backup and Restore overview 1-2
Backing up and restoring a regional operation center 1-4
Restrictions and Limitations 1-4
Prerequisites 1-6
ubvaClient theory of operation 1-6
Centralized backup and restore of Oracle database using RMAN utility
1-1
1-7
Performing system backup and restore
2-1
System backup 2-1

Backing up a system manually 2-3
Backing up a system automatically 2-4
System restore 2-5
Restoring a system 2-5
Booting to single user mode on a Sun Fire 4800 server 2-8
Booting to single user mode on a Sun Fire E4900 server 2-10
Booting to single user mode 2-12
Enabling the disk array (Sun Fire 4800) 2-13
Enabling the disk array (Sun Fire E4900) 2-15
Performing configuration data backup and restore
3-1
Backing up configuration data 3-2

Backing up configuration data manually 3-2
Backing up configuration data automatically 3-5
Restoring configuration data 3-6
Performing historical data archive and retrieval

UMTS, GPRS, GSM
W-NMS Backup and Restore User Guide
4-1
OAM 4.2
xii
Contents
Nortel Confidential
Archiving historical data locally 4-2
Archiving historical data automatically
Retrieving historical data locally 4-7
4-5
Performing centralized backup and restore with an archive policy

5-1
Configuring NetBackup 5-4
Installing the UNIX NetBackup Client 5-5
Installing the VERITAS NetBackup Oracle agent 5-6
Requirements 5-6
Creating backup path files 5-7
Configuring policies 5-9
Configuring policies using VERITAS NetBackup 5-11
Upgrading a VERITAS NetBackup server from OAM 3.x to OAM 4.x
Archiving historical data manually 5-14
Restoring a server using VERITAS NetBackup 5-15
Stopping the server processes 5-15
Restoring the brd files 5-17
Restoring the data for the server 5-19
Retrieving historical data 5-22
5-13
Performing centralized backup and restore with no archive

policyRMAN used for HFB Oracle database
6-1
Configuring NetBackup 6-5

Installing the UNIX NetBackup Client 6-6
Installing the VERITAS NetBackup Oracle agent 6-7
Requirements 6-7
Creating backup path files 6-8
Configuring policies 6-11
Configuring policies using VERITAS NetBackup 6-13
Restoring a server using VERITAS NetBackup 6-15
Stopping the server processes 6-16
Restoring the brd files 6-17
Restoring the data for the server 6-19
Appendix A: Additional processes and information
A-1
Finding out the type of data on a tape A-2

Finding out the contents of a configuration data backup tape A-3
Finding out the contents of an historical data archive tape A-4
RNC data backup from the main server A-4
RNC data restore to the main server A-5

System data backup B-1
Configuration data backup B-4
Historical data archive B-16
hfb module B-17
411-8111-521
Preliminary
06.10
June 2005
B-1
Nortel Confidential
Contents
csal module B-17
audittr module B-17
ne_sda module B-18
oam_sda module B-18
mycom module B-18
pdi, gdi, sdi and cdi modules
adi module B-20
xiii
B-19
C-1
General C-1
System Backup C-2
System Restore C-2
Local Data Backup C-3
Local Data Restore C-4
Local Data Archive C-5
Local Data Retrieval C-6
Centralized Data Backup C-9
Centralized Data Restore C-11
Centralized Data Archival C-12
Centralized Data Retrieval C-13
Appendix D: Technical note - alternative policies
D-1
Index
E-1
UMTS, GPRS, GSM
OAM 4.2
xiv
Contents
411-8111-521
Nortel Confidential
Preliminary
06.10
June 2005
xv
Nortel Confidential
About this document
This document explains the backup and restore functionality provided by the
Nortel Wireless Network Management System (W-NMS.) Use the backup
procedures to back up the data for the servers contained in one Regional
Operating Center (ROC).
This chapter contains the following sections:
Audience for this document on page 1-xv
Organization of this document on page 1-xv
Related documents on page 1-xvi
Indication of hypertext links on page 1-xviii
Nortel branding on page 1-xix
Audience for this document
This document is for network administrators who install and administer

W-NMS.
Organization of this document
Chapter 1, Understanding backup and restore provides a general overview

of W-NMS backup and restore, including restrictions and limitations.
Chapter 2, Performing system backup and restore contains procedures for
backing up and restoring the system data for a server.
Chapter 3, Performing configuration data backup and restore contains
procedures for backing up and restore the configuration data for a server.
Chapter 4, Performing historical data archive and retrieval contains
procedures for archiving and retrieving the historical data for a server.
UMTS, GPRS, GSM
OAM 4.2
xvi About this document

Nortel Confidential
Chapter 5, Performing centralized backup and restore with an archive

policy explains how to back up and restore the data on the servers from a
central location using the third party application VERITAS NetBackup. Use
these procedures only if an archive profile for archiving historical data has
been set.
Chapter 6, Performing centralized backup and restore with no archive
policyRMAN used for HFB Oracle database is an alternative to Chapter 5.
Use this chapter if you do not need to configure a centralized archive policy to
archive historical data, or, if the system has a separate backup policy to back
up the historical data or data in all the file systems on the server, use this
chapter to back up the HFB Oracle database through RMAN utility as part of
the data backup.
Appendix A: Additional processes and information contains procedures for
checking the contents of a tape. It also describes the RNC backup and restore
process.
Appendix B: Data backed up lists the files and directories backed up for
each server and application.
Appendix C: Troubleshooting provides troubleshooting procedures for
back-up and restore actions.
Appendix D: Technical note - alternative policies describes an alternative
approach to defining backup policies for VERITAS NetBackup.
Related documents
The following Nortel Technical Publications (NTPs) provide more information

about the products and services described in this document:
W-NMS System Management, 411-8111-538
About the Nortel UMTS RNC 1000, 411-8111-906
W-NMS Engineering Guide, 450-3101-638
Some of the procedures in this document refer to the Sun Management Center
(SMC). For information about the SMC, refer to W-NMS System
Management, 411-8111-538.
Some of the procedures in this document refer to a third party product for
backup and restore called VERITAS NetBackup. For information about
VERITAS NetBackup refer to the VERITAS documents.
411-8111-521
Preliminary
06.10
June 2005
About this document xvii

Nortel Confidential
Roadmap to W-NMS documents

Figure 1 and show the documents in the W-NMS documentation set.
Figure 1
W-NMS documentation roadmap
UMTS, GPRS, GSM
OAM 4.2
xviii About this document

Nortel Confidential
Figure 1-2
W-NMS documentation roadmap (continued)
Indication of hypertext links

Hypertext links in this document are indicated in blue. If viewing a PDF
version of this document, click on the blue text to jump to the associated
section or page.
411-8111-521
Preliminary
06.10
June 2005
About this document xix

Nortel Confidential
Nortel branding
Nortel is changing the branding of some of its product lines. Part of this effort
includes changing the names of the products. New product names have been
created using the following format:
Nortel <function> <model>
where:
<function> describes what function the product performs.
<model> is a model series number.
For example, the Baystack 450 product has been renamed as the Nortel
Ethernet Switch 450. Some of the new product names are quite lengthy. To
make our documents easier to read, the product names are shortened after
their first occurrence. For example, the Nortel Ethernet Switch 450 product
name is referred to as the Ethernet Switch 450 for second and subsequent
occurrences.
To alleviate any confusion the rebranding might cause, Table iii and Table iv
are job aids to assist the end user in reconciling inconsistent product
terminology across multiple documents. During the transition, both the
existing product names and the new product names may appear in the
documentation and software.
Table iii details the original product names and their corresponding new and
abbreviated product names. Table iv details the new product names to the
original names.
Table iii
Original product names mapped to new names
Original Name(s)
New Name
Short Name
Alteon Application
Switch xxxx
Nortel Applications Switch

xxxx
Applications
Switch xxxx
Alteon Web Switch 184
Nortel Web Switch 184
Web
Switch 184
BayStack 450
Nortel Ethernet Switch 450
Ethernet
Switch 450
BPS2000 2-port SFP

GBIC MDA
Nortel Ethernet Switch 2-port

SFP GBIC MDA
Function
sheet 1 of 3
UMTS, GPRS, GSM
OAM 4.2
xx About this document

Nortel Confidential
Table iii
Original product names mapped to new names (continued)
Original Name(s)
New Name
Short Name
Function
CCN CS
(DMS MSC)
Nortel GSM/UMTS MSC
MSC
Mobile Switching
Center
CCN HLR
(DMS HLR)
Nortel GSM/UMTS HLR 100
HLR 100
Home Location
Register
Combined MSC and

HLR
(DMS Trinode)
Nortel GSM/UMTS Combined

MSC/HLR
Combined
MSC/HLR
Contivity xxxx Secure IP

Services Gateway
Nortel VPN Router xxxx
VPN Router
xxxx
DMS Gateway Mobile

Switching Center
(GMSC)
Nortel GSM/UMTS MSC

Server
MSC Server
Mobile Switching
Center
GPP
Nortel GSM/UMTS IWF
IWF
Interworking Function
HSS
Nortel GSM/UMTS HSS
HSS
Home Subscriber
Server
iBTS
Nortel BTS xxxx
BTS xxxx
Base Transceiver
Station
IMS Solution
Nortel IMS
IMS
IP Multimedia
Subsystem
NIMS-PrOptima for
Preside for Wireless
Internet
NIMS-PrOptima for
W-NMSa
Nortel Networks Secure

Router xxxx
VPN Router
xxxx
Offline Configuration for

Access Networks
(OCAN)
Wireless Provisioning System

for Access b
WPS for
Access
Passport 7400 (7K)
Nortel Multiservice Switch

7400
Multiservice
Switch 7400
Passport 15000 (15K)

15000
Multiservice
Switch 15000
sheet 2 of 3
411-8111-521
Preliminary
06.10
June 2005
Network Information
Management System
& Wireless Network
Management System
Wireless Provisioning
System
About this document xxi

Nortel Confidential
Table iii
Original product names mapped to new names (continued)
Original Name(s)
New Name
Short Name

20000
Multiservice
Switch 20000

Internet (PWI)
Nortel Wireless Network

Management System
W-NMS
RNC
Nortel UMTS RNC xxxx
RNC xxxx
Shasta 5000 BSN
Nortel IP Services Edge

Router 5500
IP Services
Edge Router
5500
Univity GGSN
(Shasta GGSN)
Nortel GGSN
GGSN
Gateway GPRS
Support Node
Univity HLR c
HLR 200
Home Location
Register
Univity MLC
(MLC)
Nortel MLC
MLC
Mobile Location
Center
Univity SGSN
(SGSN,
GPRS SGSN,
UMTS SGSN,
USGSN or U-SGSN)
Nortel SGSN
(Nortel SGSN/GPRS
Nortel SGSN/UMTS
SGSN
(SGSN/GPRS,
SGSN/UMTS
Serving GPRS
Support Node
-use where required to

differentiate technology.)
-use where
required to
differentiate
technology.)
Univity Signaling
Gateway (SIG d,
SS7-IP Gateway)
Nortel GSM/UMTS SIG
SIG
Signaling Interworking
Gateway
UMGW (MGW,
Passport Voice Gateway
(PVG))
Nortel GSM/UMTS MGW
MGW
Media Gateway
Wireless Gateway (WG)
See the following:

- Nortel SGSN
- Nortel GSM/UMTS MGW
NOTE: Configuration NOT

supported in PC04 and
Function
Network Management
System for Wireless
Networks
beyond, is supported in OAM.

sheet 3 of 3
a. NIMS PrOptima is a sub-component of W-NMS

b. WPS for Access is a sub-component of W-NMS
c. May have also been referred to as Everest HLR
UMTS, GPRS, GSM
OAM 4.2
xxii About this document

Nortel Confidential
d. May have also been referred to as HP SIG
Table iv
New product names mapped to original name(s)
New Name
Short Name
Nortel Ethernet Switch 2-port SFP

GBIC MDA
Original Name(s)
BPS2000 2-port SFP
GBIC MDA
Nortel Applications Switch xxxx
Applications Switch xxxx
Alteon Application Switch

xxxx
Nortel BTS xxxx
BTS xxxx
iBTS
Nortel Ethernet Switch 450
Ethernet Switch 450
BayStack 450
Nortel GGSN
GGSN
Univity GGSN, Shasta

GGSN
Nortel GSM/UMTS Combined

MSC/HLR
Combined MSC/HLR
Combined MSC and HLR,

DMS Trinode
HLR 100
CCN HLR, DMS HLR
HLR 200
Univity HLR a
Nortel GSM/UMTS HSS
HSS
HSS
Nortel GSM/UMTS IWF
IWF
GPP
Nortel GSM/UMTS MGW
MGW
UMGW (function of a
Wireless Gateway), Passport
Voice Gateway (PVG)
Nortel GSM/UMTS MSC
MSC
CCN CS,
DMS MSC
Nortel GSM/UMTS MSC Server
MSC Server
DMS Gateway Mobile

Switching Center (GMSC)
Nortel GSM/UMTS SIG
SIG
Univity Signaling Gateway,

SIG b,
SS7-IP Gateway
Nortel IMS
IMS
IMS Solution
Nortel IP Services Edge Router

5500
IP Services Edge Router 5500
Shasta 5000 BSN
sheet 1 of 2
411-8111-521
Preliminary
06.10
June 2005
About this document xxiii

Nortel Confidential
Table iv
New product names mapped to original name(s) (continued)
New Name
Short Name
NIMS-PrOptima for W-NMS c
Original Name(s)
NIMS-PrOptima for
Internet
Nortel MLC
MLC
Univity MLC, MLC
Nortel Multiservice Switch 7400
Multiservice Switch 7400
Passport 7400 (7K)
VPN Router xxxx
Contivity xxxx Secure IP

Services Gateway,
Nortel Networks Secure
Router xxxx
Nortel SGSN:
- Nortel SGSN/GPRS
- Nortel SGSN/UMTS
SGSN
SGSN/GPRS
SGSN/UMTS)
Univity SGSN,
GPRS SGSN,
UMTS SGSN,
U-SGSN, or USGSN
function of a Wireless
Gateway
Nortel UMTS RNC xxxx
RNC xxxx
RNC
Nortel Web Switch 184
Web Switch 184
Alteon Web Switch 184
Nortel Wireless Network

Management System
W-NMS

Internet (PWI)
Wireless Provisioning System for

Access d
WPS for Access
Offline Configuration for

Access Networks (OCAN)
sheet 2 of 2
a. May also have been referred to as Everest HLR

b. May also have been referred to as HP SIG
c. NIMS PrOptima is a sub-component of W-NMS
d. WPS for Access is a sub-component of W-NMS
UMTS, GPRS, GSM
OAM 4.2
xxiv About this document

Nortel Confidential
411-8111-521
Preliminary
06.10
June 2005
1-1
Nortel Confidential
This document contains procedures for backup and restore of the following WNMS servers:
primary main server
secondary main server(s)
performance server(s)
Software Repository Server (SRS)
Server of Client (SOC)
This chapter is divided into the following sections:
Backup and Restore overview on page 1-2
Backing up and restoring a regional operation center on page 1-4
Restrictions and Limitations on page 1-4
Prerequisites on page 1-6
ubvaClient theory of operation on page 1-6
Centralized backup and restore of Oracle database using RMAN utility

on page 1-7
UMTS, GPRS, GSM
OAM 4.2
1-2 Understanding backup and restore

Nortel Confidential
Backup and Restore overview
The data on an OAM server is backed up using three types of backups. Each
type of backup backs up different types of data. Depending on the type of
backup, you can back up each server individually, using a local backup
procedure (local), or you can back up all servers from a central location, using
VERITAS NetBackup (centralized). Backups can be performed manually
(manual) or they can be scheduled to run automatically (automatic). The
following table summarizes the characteristics of each type of backup:
Table 1-1
Types of backups
Type of backup
Local or
centralized
System down
time
Data backed up a
Recommended
frequency
system data
backup
local, manual
Approximately
20-30 minutes,
while snapshot
of data is
taken.
EEPROM variables
after
installation,
upgrade, or
patch on the
server
local, automatic
(single tape only)
Backup of
snapshot is
done while
system is
online.
Metadata (Solaris Volume

Manager Configurations)
File systems: /, /usr, /var,/
home, /opt, /opt/nortel
(excluding /opt/nortel/logs)
Directories: /opt/nortel/
logs/3rd_party
Installation logs: /opt/
nortel/logs/iut_tools/*.log*
configuration
data backup
local, manual
None.
local, automatic
(single tape only)
Backup is
performed
while system
is online.b
centralized,
automatic
centralized,
manual
411-8111-521
Preliminary
06.10
June 2005
configuration data for

network elements and WNMS, W-NMS system
management data,
software repository
weekly (and
immediately
before or after a
system data
backup)
Understanding backup and restore 1-3

Nortel Confidential
Table 1-1
Types of backups
Type of backup
Local or
centralized
System down
time
Data backed up a
Recommended
frequency
historical data
archive
local, automatic
(single tape only)
None.
HFB alarms
OAM stability data
NE-based stability data
CSAL
Audit Trail
3GPP XML files
daily
local, manual
centralized,
automatic
Archive is
performed
while system
is online.
centralized,
manual
a. For a detailed list of the files and directories backed up, see Appendix B: Data backed up.
b. Some operations cannot be performed while the backup is in progress; see Table 1-3.
The equivalent types of restores are also supported.

Table 1-2
Types of restores
Type of restore
Local or
centralized
Online or
offline
Comments
system restore
local
offline
must be followed by a configuration data restore
configuration
data restore
local
offline
centralized
historical data
retrieval
local
online
with centralized data retrieval, you can retrieve

specific files or directories
centralized
For detailed information and procedures about each type of backup or restore,
refer to the other chapters in this document.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Backing up and restoring a regional operation center
The backup and restore procedures are intended to be used to back up or

restore the data on all the servers in a single Regional Operating Center
(ROC).
For a system backup, the Primary Main Server must be backed up first,
followed immediately by a system backup of the other servers in the ROC.
For a configuration data backup, back up all the servers in the ROC at the
same time.
When a configuration data backup or a system backup is running on the
Secondary Main Server, do not run a system backup on the Primary Main
Server. For the Secondary Main Server backup to run successfully, all
applications on the Primary Main Server must be up running (during a
Primary Main Server system backup, some of the applications on the Primary
Main Server are stopped and restarted.)
When you restore one server in the ROC, you must restore all the servers in
the ROC. Restore the Primary Main and Secondary Main Servers first,
followed by the other servers.
Performing backup and restore as recommended in this section ensures that
the data in the ROC remains consistent.
Note: Only the servers listed at the beginning of this chapter are
supported for backup and restore. However, a ROC can contain other
servers in addition to the ones listed.
Restrictions and Limitations
The following restrictions apply to W-NMS backup and restore. The restrictions
apply for both local backup and restore and centralized backup and restore using
VERITAS NetBackup 5.1.
Only the standard W-NMS server configuration is supported for backup
and restore. Any deviation from the standard server configuration is not
supported. For information about the standard W-NMS server
configuration, see the W-NMS Engineering Guide, 450-3101-638.
System backup or restore is performed for all the components on a server.

You cannot back up or restore an individual component in a system
backup.
If any of the following operations are being performed and you attempt to
start a backup, the backup will fail. If a backup is running and you attempt
to perform one of the operations, the operation will fail:
3GPP bulk configuration management
execution of wireless internet command language (WICL) scripts
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
import of a data request form (DRF) in the Access database
During a backup, the network time protocol (NTP) server is out of

service. The NTP server is returned to service when the backup
completes.
The W-NMS configuration data backup and the historical data archive are
performed while the system is online. As activity on the system increases,
the potential for data corruption to occur during the backup also increases.
Do not perform any of the operations shown in Table 1-3 while a backup
is running.
Table 1-3
CEM
In the CEM, do not commission new network elements managed by the CEM. Do not
set Dialed Digits, Threshold, Mass Export, or Customizable OM.
Network Services Platform

SUMBB
Do not modify network layouts or link edits.
Access
Control
Do not make changes to Access Control.
MDM
Do not add, remove or change the connection to Passport or SNMP-based network

elements.
Nortel Wireless Network Management System (W-NMS)

Do not perform software installation, apply software patches, or perform software
upgrades.
Do not update the software configuration.
When a configuration data backup or a system backup is running on the

Secondary Main Server, do not run a system backup on the Primary Main
Server. For the Secondary Main Server backup to run successfully, all
applications on the Primary Main Server must be up running (During a
Primary Main Server system backup, some of the applications on the
Primary Main Server are stopped and restarted.).
The following information applies to local backup and restore:

the maximum length of the path to the directory or file to be backed up
(including the file to be backed up) is 1023 characters
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Prerequisites
Before performing the procedures in this document you must ensure that the
backup and restore package has been installed on each server to be backed up
or restored. The installation of the backup and restore scripts is part of the
installation of W-NMS. To verify that the installation has been completed,
look at the /opt/nortel/shell/backup directory. The backup and restore scripts
are stored in this directory. If the backup scripts are not in the /opt/nortel/
shell/backup directory, contact your Nortel representative.
There must only be one network time protocol (NTP) server process running
on each server to be backed up or restored. The backup and restore scripts
check for this and ensure the correct process is running ( /etc/rc2.d/
S74xntpd).
ubvaClient theory of operation
You use the ubvaClient utility to generate lists of backup paths for use in
creating VERITAS NetBackup backup policies for centralized backup and
restore (see procedure Procedure 5-4 and Procedure 5-5.) You run it on a server
that you want to backup, and it collects information about what applications
are installed on the server, what files they need to have backed up, and generates
lists of paths to the files. When you create backup policies, the backup and
restore solution will use these lists to determine what to back up. When you
run the ubvaClient utility, it does the following:
1. Adds an entry for REQUIRED_INTERFACE to the NetBackup agents
configuration file on the server (/usr/openv/netbackup/bp.conf)
2. Discovers which OAM applications are installed on the server
3. Retrieves BRD (backup and restore data) files from those applications and
parses them to create backup and exclusion paths
4. Creates the exclude list file /usr/openv/netbackup/exclude_list
5. Presents you with default policy names and asks you to enter the policy
names you want to use.
6. Creates the following files in /opt/nortel/data/backup/BRTools/veritas/
client:
a. backup_UNIX - this file contains a list of backup paths for you to add
to the UNIX backup policy
b. backup_ORACLE - this file is created only on a Performance server
installed with NIMS-PrOptima and contains the path to the Oracle
backup script. You add this path to the Oracle policy.
c. backup_USER - this file is created only on a Performance server
installed with NIMS-PrOptima. It is empty, and its presence indicates
that a User backup policy needs to be configured.
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
d. classNames - this file contains the policy names you specified in point
5.
e. clientOS - this file contains the Solaris OS version running on the
server.
7. Creates symbolic links to scripts that NetBackup uses to back up the
server as follows:
a. /usr/openv/netbackup/bin/bpstart_notify to
/opt/nortel/shell/backup/veritas/preVeritasBackup.sh
b. /usr/openv/netbackup/bin/bpend_notify to
/opt/nortel/shell/backup/veritas/postVeritasBackup.sh
c. /usr/openv/netbackup/bin/bpstart_notify.<archive policy name> to
/opt/nortel/shell/backup/veritas/centralarchive.sh
d. /usr/openv/netbackup/bin/bpend_notify.<archive policy name> to
/opt/nortel/shell/backup/veritas/postcentralarch.sh
Centralized backup and restore of Oracle database using RMAN

utility
Starting in OAM 4.2, users can customize Centralized (VERITAS) Backup

and Restore to back up the HFB Oracle database using the Oracle RMAN
utility. The user must define a corresponding Oracle policy on the VERITAS
NetBackup server.
In addition, since this new feature is not currently compatible with
Centralized Historical Data Archive and Retrieval, the user must disable
Historical Data Archive and Retrieval. The user then must define additional
backup policies to back up the other historical data that would otherwise have
been backed up by the Historical Data Archive and Retrieval feature, as
appropriate. Historical data archive in Appendix B: Data backed up
provides a complete list of the data backed up by Historical Archive Data and
Retrieve.
Since this feature applies only to servers supported with Centralized backup
and restore, there is no conflict with Historical Data Archive and retrieval
process on servers that are supported only with Local Backup and Restore
features.
Chapter 6, Performing centralized backup and restore with no archive
policyRMAN used for HFB Oracle database provides a complete
operations reference for use with the RMAN feature.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
411-8111-521
Preliminary
06.10
June 2005
2-1
Nortel Confidential
Performing system backup and restore2

This chapter describes the system backup and system restore. It contains
procedures for backing up the system data or restoring the system data under
these headings:
System backup on page 2-1

Backing up a system manually on page 2-3
Backing up a system automatically on page 2-4
System restore on page 2-5

Restoring a system on page 2-5
Booting to single user mode on a Sun Fire 4800 server on page 2-8
Booting to single user mode on a Sun Fire E4900 server on page 210
Booting to single user mode on page 2-12
Enabling the disk array (Sun Fire 4800) on page 2-13
Enabling the disk array (Sun Fire E4900) on page 2-15
System backup
A system backup backs up the disk layout and file system information for all
partitions, operating systems, application programs, and directory structures.
A system restore restores the same data. For a complete list of directories and
files backed up or restored, see System data backup in Appendix B: Data
backed up.
A system backup minimizes the amount of time that a server is out of service
by taking a snapshot of the data to be backed up while the server
applications are offline. The applications are restarted and then a backup of
the snapshot data is performed. The time to complete the backup is
approximately two hours, with the server being out of service for 20 to 30
UMTS, GPRS, GSM
OAM 4.2
2-2 Performing system backup and restore

Nortel Confidential
minutes of that time. A system restore is performed offline and takes

approximately four hours.
RESTRICTIONS AND LIMITATIONS

For information about restrictions and limitations when performing
system backup or restore, refer to the section titled Restrictions and
Limitations in Chapter 1.
411-8111-521
Preliminary
06.10
June 2005
Performing system backup and restore 2-3

Nortel Confidential
Backing up a system manually

Perform this procedure to back up the system on a server manually.
Requirements
Before performing this procedure, you must:
perform a configuration data backup either immediately before or
immediately after the system backup
ensure that the server is online
have DDS-4 tape(s) ready to store the backup data

Note: To reduce tape read/write or input/output errors during backup or
restore, follow the manufacturers maintenance guidelines for your tapes
and tape drives. For example, do not use magnetic tapes beyond their
recommended life expectancy and clean tape drives regularly.
know the password for the nortel user and the root user
read and comply with the prerequisites section in Chapter 1,

Procedure 2-1
Backing up a system manually
Step
Action
Log onto the server you are backing up as nortel (or some other normal
user), start a terminal session and then become the root user by entering
su -
Insert a tape into the tape drive of the server.
Enter:
localSysDump
If the tape is blank, the backup starts.

If the tape is not blank, you are prompted to confirm that the backup will
overwrite any data currently on the tape. The backup will not start until
you confirm (Y).
If the data to be backed up takes up more than one tape, you are
prompted to insert another tape.
Review the log file in the /usr/local/nortel/tools/log directory to make sure

that the backup completed successfully.
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Backing up a system automatically

This procedure explains how to modify the crontab file to schedule a system
backup to run automatically at regular intervals.
Restrictions for automatic backup
The following restrictions apply to an automatic backup:
The data to be backed up must fit on one DDS-4 tape. If the data does not
fit on one tape, the backup fails and an error message is logged.
Before the backup is scheduled to run, you must ensure that there is a tape
in the tape drive of the server to be backed up. If there is no tape in the
tape drive at the time the backup runs, the backup fails writes an error
message to the log file.
Requirements
Before performing this procedure, you must be familiar with the UNIX crontab
utility.
Procedure 2-2
Backing up a system automatically
Step
Action
su -
Copy the crontab file to a temporary file. For example,

crontab -l > /tmp/tempcrontab
Add a line to the temporary file that schedules the system backup. The
following example schedules a system backup to run at 3:15 every
Monday:
15 3 * * 1 /usr/bin/localSysDump -s > /dev/null 2>&1
Make the temporary file the crontab file. Example:

crontab /tmp/tempcrontab
Delete the temporary file.

The backup will run according to the schedule you have defined in the
crontab file. Before the backup runs, ensure that you have complied with
the restrictions described in the section titled Restrictions for automatic
backup.
411-8111-521
Preliminary
End of procedure.
06.10
June 2005

Nortel Confidential
System restore
A system restore restores the operating system and application executables to

the server. A system restore is performed manually and the server is offline
while it runs.
The electronically erasable programmable read-only memory (EEPROM)
settings are backed up when the system is backed up. When the system is
restored, the settings are written to /usr/local/nortel/tools/cfg/EEPROM. The
restore modifies the BOOT-DEVICE setting in EEPROM as part of the
restore process. All other settings in the file are identical to those in the
EEPROM, so you can read the file to review the EEPROM settings.
After you perform a system restore, you must perform a configuration data
restore to ensure that the applications are fully functional. See Chapter 3,
Performing configuration data backup and restore for more information. If
you want to restore historical data, you can also perform an historical data
retrieval. See Chapter 4, Performing historical data archive and retrieval.
Restoring a system
Perform this procedure to restore the system on a server. A system restore
consists of the following steps:
restore the operating system file systems
reboot the server
mirror the disks
reboot the server
restore the application file systems
restore application data (configuration data restore)
Requirements
have the tape(s) that contain the data you want to restore
Have Solaris operating system CD-ROM available
know the password for the root user
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Procedure 2-3
Restoring a system
Step
Action
If you are working on a Sun Microsystems Sun Fire 4800 server, perform
Procedure 2-4. If you are working on a Sun Microsystems Sun Fire E4900
server, perform Procedure 2-5. If you are working on any other type of
server, perform Procedure 2-6.
Insert the tape into the tape drive of the server.
Enter:
cd /
cpio -idI /dev/rmt/0n
Note: In the previous command, the last character in the text string idI
is an upper case i.
4
Enter:
cd /tmp/backup/tools/bin
./localSysRestore.sh [-HVh] [-t <tape drive>]
where -V displays the version of the tool
-h causes the usage to be displayed
-H displays detailed usage for the command.
-t <tape drive> specifies the tape drive that contains the tape (if
you do not specify the -t option, the command will restore from
tape device /dev/rmt/0n)
If you are working on a Sun Microsystems Sun Fire 4800 server:
The script returns to the command line prompt.

a. Enter:
init 0
The OBP prompt appears:

{0} ok
b.
6
Enable the disk array.

See Procedure 2-7 for SF4800 or Procedure 2-8 for the SFE4900.
If you are working on any other type of server:
The server reboots.
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Procedure 2-3
Restoring a system
Step
Action
At this point, the meta devices are being configured.
Wait for the following message to appear:

Type control-d to proceed with normal startup, (or
give the root password for system maintenance)
Do NOT enter control-d. Enter the password for the root user.
10
Enter:
metastat | more
11
In the message that displays, verify that the State of meta device is
Okay.
12
Enter:
init 6
The system reboots and then the application files are restored.
If the data to be restored spans multiple tapes, the following message
appears:
Mount volume 2
If this message appears:

a. Eject the tape
b.
Put the next tape in the tape drive
c.
Press the <Enter> key
The data restore continues. When the restore is complete, the following
message appears; do NOT enter control-d:
13
Do NOT enter control-d. Enter the password for the root user.
14
Review the log file in the /usr/local/nortel/tools/log directory to make sure

that the restore completed successfully.
15
Perform a configuration data restore starting from step 5 of procedure

Procedure 3-3.
16
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Booting to single user mode on a Sun Fire 4800 server

This procedure is referenced in Procedure 2-3. It disables the disk array of the
Sun Fire 4800 server and then boots the server to single user mode. If you are
working on a server that is not a Sun Fire 4800, see Procedure 2-5 (Sun Fire
E4900) or Procedure 2-6 (other types of servers).
Requirements
know the IP address of the Sun Fire 4800 System Controller
Procedure 2-4
Step
Action
Connect to the System Controller of the Sun Fire 4800 server from
another host. Enter:
telnet <SC IPAddress>
where <SC IPAddress> is the IP address of the Sun Fire 4800 System
Controlle r
A list of valid values is displayed and the following prompt appears:

Input:
2
Enter:
0
The following prompt appears:

SChostname:SC>
3
Enter:
cons a
Enter:
init 0

{0} ok
5
Enter:
setenv auto-boot? false
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Procedure 2-4
Step
Action
Press the Ctrl key and then press the ] key. This key sequence returns
you to the telnet session.
Enter the following commands:

send brk
setkeyswitch off
disc
disable /N0/IB6/P0/B0/C3
console a
setkeyswitch on
These commands disable the disk array.
Insert the Solaris operating system compact disc into the CD-ROM drive.
Enter:
setenv diag-switch? true
boot cdrom -rs
10
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Booting to single user mode on a Sun Fire E4900 server

This procedure is referenced in Procedure 2-3. It disables the disk array of the
Sun Fire E4900 server and then boots the server to single user mode. If you are
working on a server that is not a Sun Fire E4900, see Procedure 2-4 for a Sun
Fire 4800 server and Procedure 2-6 for all other types of servers.
Requirements
know the IP address of the Sun Fire E4900 System Controller
have the Solaris 8 02/04 special CDROM for the SFE4900
Procedure 2-5
Step
Action
Connect to the System Controller of the Sun Fire E4900 server from
another host. Enter:
where <SC IPAddress> is the IP address of the System Controller

Input:
2
Enter:
0

SChostname:SC>
3
Enter:
cons a
Enter:
init 0

{0} ok
5
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Procedure 2-5
Step
Action

send brk
These commands disable the disk array.
Insert the Solaris 8 02/04 operating system compact disc into the CDROM drive.
Note: This CD is mandatory to boot on an SFE4900 for this version.
Enter the following command:

resume
{0} ok

boot cdrom -rs
Message: Type control-d to proceed with normal startup, (or give the
root password for system maintenance).
10
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Booting to single user mode

This procedure is referenced in Procedure 2-3. Perform it when you are working
on a server that is not a Sun Fire 4800. If you are working on a Sun Fire 4800
or E4900 server, use Procedure 2-4 (4800) or Procedure 2-5 (E4900), for the
appropriate server
Requirements
Before performing this procedure you must:
have the Solaris operating system compact disc
Procedure 2-6
Booting to single user mode
Step
Action
Log onto the server using the root user.
Enter:
init 0

{0} ok
3
If the server you are working on is a Sun E4500, enter:

setenv sbus-probe-default 3120
Insert the Solaris operating system compact disc into the CD-ROM drive.
Enter:
setenv diag-switch? true
boot cdrom -rs
The following message appears:

INIT:SINGLE USER MODE
6
411-8111-521
Preliminary
End of procedure.
06.10
June 2005

Nortel Confidential
Enabling the disk array (Sun Fire 4800)

This procedure is referenced in Procedure 2-3. This procedure is only
applicable for a Sun Fire 4800.
Requirements
know the IP address of the Sun Fire 4800 System Controller
Procedure 2-7
Enabling the disk array for the Sun Fire 4800
Step
Action
Connect to the System Controller of the Sun Fire 4800 server from
another host.
Enter:
where <SC IPAddress> is the IP address of the Sun Fire 4800 System
Controlle r

Input:
3
Enter:
0

SChostname:SC>
4
Enter:
cons a
Enter:
init 0

{0} ok
6
Enter:
setenv auto-boot? false
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Procedure 2-7
Enabling the disk array for the Sun Fire 4800
Step
Action

send brk
setkeyswitch off
disc
enable /N0/IB6/P0/B0/C3
console a
setkeyswitch on
These commands enable the disk array.
Enter:
setenv auto-boot? true
boot -rs
10
411-8111-521
Preliminary
End of procedure.
06.10
June 2005

Nortel Confidential
Enabling the disk array (Sun Fire E4900)

This procedure is referenced in Procedure 2-3. This procedure is only
applicable for a Sun Fire E4900.
Requirements
know the IP address of the Sun Fire E4900 System Controller
Procedure 2-8
Enabling the disk array for a Sun Fire E4900
Step
Action
Connect to the System Controller of the Sun Fire E4900 server from
another host.
Enter:
where <SC IPAddress> is the IP address of the System Controller

Input:
3
Enter:
0

SChostname:SC>
4
Enter:
cons a
Enter:
init 0

{0} ok
6
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Procedure 2-8
Enabling the disk array for a Sun Fire E4900
Step
Action

send brk
These commands enable the disk array.

resume
{0} ok

boot -rs
The following message appears:

411-8111-521
10
Enter the password for the root user.
11
End of procedure.
Preliminary
06.10
June 2005
3-1
Nortel Confidential
Performing configuration data backup

and restore
3
A configuration data backup backs up the configuration data and the software
repository. A configuration data restore restores the configuration data and the
software repository.
A configuration data backup is performed while the server is online. A
configuration data restore is performed while the server is offline.
This chapter contains procedures for the following:
Backing up configuration data on page 3-2

Backing up configuration data manually on page 3-2
Backing up configuration data automatically on page 3-5
Restoring configuration data on page 3-6
For a complete list of directories and files backed up or restored, see

Configuration data backup in Appendix B: Data backed up.
You can perform a configuration data backup or restore in two ways:
on each server, using the procedures in this document (known as local
backup and restore)
from a backup and restore server, using VERITAS NetBackup 5.1 (known
as centralized backup and restore, for more information, see Chapter 5,
Performing centralized backup and restore with an archive policy)

configuration data backup or restore, refer to the section titled
Restrictions and Limitations in Chapter 1.
UMTS, GPRS, GSM
OAM 4.2
3-2 Performing configuration data backup and restore

Nortel Confidential
Backing up configuration data
Backing up configuration data manually

Use Procedure 3-1 to back up the configuration data on each of the servers in
the regional operation center (ROC). For details about which files, directories,
and databases are backed up, see Configuration data backup in Appendix
B: Data backed up.
Requirements
When backing up the configuration data for a server, you must back up the
data for all servers in the ROC at the same time. You must perform the backup
procedure on each server in the ROC. This maintains the consistency and
integrity of the data throughout the ROC.
Have a blank DDS-4 tape ready to store the backup data. You can also use
a tape that has data on it and overwrite it.
Read and comply with the prerequisites section in Chapter 1,

Understanding backup and restore.
Know the password for the nortel and root users on the server.
If you try to run a configuration data backup while a
centralized configuration data backup is running (see Chapter
5, Performing centralized backup and restore with an archive
policy), both backup operations will fail and the data will not
be backed up.
411-8111-521
Preliminary
06.10
June 2005
Performing configuration data backup and restore 3-3

Nortel Confidential
Procedure 3-1
Backing up configuration data
Step
Action
su -
Insert a blank tape into the tape drive of the server.
Enter:
localbackup [-d <delay time>] [-m <message text>] [-t <tape
name>]
The square brackets [] indicate options. See Table 3-1 for descriptions of
the options. You can also enter localbackup [-h] [-H] in the command
line to see the valid options and their definitions.
If the tape is blank, the backup starts. Go to step 9.
If the tape is not blank, the following message is displayed:

All data on this tape will be overwritten should you continue with the
backup.
The following prompt displays:

Do you wish to continue? [yes]
If you want to continue with the backup, press the Enter key. Go to step 9.
If you want to abort the backup, enter:

no
The backup aborts and the script completes.

End of procedure.
9
The system displays the log information as the backup progresses. After
the backup is complete, the name of the log file and the label of the tape
are displayed
10
Look at the contents of the log file to confirm that the backup completed
successfully. Enter:
more /opt/nortel/logs/backup/backup.log
11
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table 3-1
options definitions for backing up configuration data
parameter
value
-d <delay time>
Delay the backup by <delay time>. <delay time> is a value

between 3 and 60 that indicates the amount of time to wait in
minutes before performing the backup.
If this option is not specified, the default delay is three minutes.
-h or -H
displays help information about the command. Cannot be

combined with other options.
-m <message
text>
Display the <message text> to users. <message text> is text

string that is sent out as a message before the backup starts in
addition to the default message Data backup will start in x
minutes. The message is sent to NSP clients and currently
logged-in consoles.
Specify the message text inside double quotation marks. For
example, Please do not use WICL. This will cause the
message Data backup will start in x minutes. Please do not
use WICL. to be sent to logged-in consoles.
-t <tape name>
Write the backup to <tape name>.

If this option is not specified, the command will use the tape
device /dev/rmt/0n.
-s
411-8111-521
Preliminary
Use only with scheduled operations. If the backup requires

more than one tape, the script will write an error message to
the log file and quit immediately. If the tape drive is empty
when the operation starts, the script will write an error
message to the log file and quit immediately.
06.10
June 2005

Nortel Confidential
Backing up configuration data automatically

This procedure explains how to modify the crontab file to schedule a
configuration data backup to run automatically at regular intervals.
Restrictions for automatic backup
The following restrictions apply to an automatic backup:
The data to be backed up must fit on one DDS-4 tape. If the data does not
fit on one tape, the backup fails and an error message is logged.
Before the backup is scheduled to run, you must ensure that there is a tape
in the tape drive of the server to be backed up. If there is no tape in the
tape drive at the time the backup runs, the backup fails and the application
writes an error message to the log file.
Requirements
utility.
Procedure 3-2
Backing up configuration data automatically
Step
Action
su -

Add a line to the temporary file that schedules the configuration data
backup. The following example schedules a configuration data backup to
run at 3:15 every Monday:
15 3 * * 1 /usr/bin/localbackup -s > /dev/null 2>&1


The backup will run according to the schedule you have defined in the
crontab file. Before the backup runs, ensure that you have complied with
backup.
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Restoring configuration data
This procedure restores the configuration data for a server.

Requirements
If you want to restore the configuration data to a server within the ROC, you
must restore the configuration data to all the servers in the ROC. That is, you
must perform this procedure on each server in the ROC. Restore the Primary
Main and Secondary Main Servers first, followed by the other servers. This
maintains the consistency and integrity of the data throughout the ROC.
have the tape(s) that contain the data you want to restore
know the password for the nortel user
Procedure 3-3
Step
Action
Log onto the server as nortel.
Stopping the server processes

2
In a terminal window command line, enter:

/opt/nortel/shell/sysmgt/wam_stopall.sh
All processes on the server are stopped.

Note: You can also use the Sun Management Center (SMC) to stop all
processes on the server. For more information refer to Preside for
Wireless Internet System Management, 411-8111-538.
3
Enter:
su - root
sheet 1 of 3
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Procedure 3-3 (continued)

Step
Action
If you are working on the primary main server, enter:

/opt/SUNWsymon/sbin/es-stop -A
If you are working on a Sun Fire 4800 or E4900 that is the secondary
main or performance server, enter:
/opt/SUNWsymon/sbin/es-stop -al
For all other server types, enter:
/opt/SUNWsymon/sbin/es-stop -a
The SMC and other processes are stopped.

Note: If a system restore was performed immediately prior to this local
data restore, the sub-mirrors are not yet attached at this point.
5
Insert the backup tape that contains the data you want to restore into the
tape drive of the server. If the data is contained on more than one tape,
insert the first tape.
If you want to verify the label on the tape, in a terminal window command
line enter:
localrestore -l [-t <tape name>]
The label of the tape is displayed.

Note: l is a lower-case L, not an upper-case i.
7
Enter:
localrestore [-t <tape name>]
Note: The square brackets [ ] indicate options. See Table 3-2 for
descriptions of the options. You can also enter localrestore [-h] [-H] in
the command line to see the valid parameters and their definitions.
If the tape does not have a label the script reports an error and
terminates. Otherwise, the restore starts.
If a system restore was performed immediately prior to this local data
restore, the mirrored disks will be attached and the root partition will now
be synchronized. The screen will display the progress of the root partition
synchronization. Wait for the operation to complete and for the command
prompt to reappear.
sheet 2 of 3
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential

Step
Action
Verify that the restore completed successfully by reviewing the contents of

the log file. Enter:
more /opt/nortel/logs/backup/restore.log
Starting the server processes

9
Reboot the server. Enter:

init 6
After about ten minutes, the server will be up and running.

10
Log in to the server as the root user.
11
From the command line interface, enter:

su - nortel -c /opt/nortel/shell/sysmgt/wam_startall.sh -a
Note: You can also use the SMC to start all processes on the server. For
more information refer to Preside for Wireless Internet System
12
Before performing the next step:

a. Make sure that all applications (except possibly the HFB Oracle
database) are up and running; on servers with an HFB Oracle
database, the database may be running or stopped for this step.
b.
13
Make sure that you are the root user.
Enter:
postDataRestore
If you are working on the main server, this command rebuilds the HFB
Oracle database and JavaHelp if they are corrupt. If you are working on
any other server, this command deletes and cleans up temporary files
used during the restore process. The logs for this process are written to /
opt/nortel/logs/backup/postDataRestore.log
14
End of procedure.
sheet 3 of 3
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Table 3-2
option definitions for restoring a server
parameter
value
-h or -H
displays help information about the command
-t <tape name>
Restore from tape device <tape name>.

If this option is not specified, the restore will use the tape
device /dev/rmt/0n.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
411-8111-521
Preliminary
06.10
June 2005
4-1
Nortel Confidential
Performing historical data archive and

retrieval
4
A historical data archive backs up the Historical Fault Browser (HFB) alarms,
3rd Generation Partnership Project (3GPP) extensible markup language
(XML) files, Centralized Security Audit Logging (CSAL) data, W-NMS and
NE Stability Analysis data, and other data that is not essential to the day to
day OAM processes. For a complete list of directories and files backed up,
see Appendix B: Data backed up. A historical data archive or retrieval is
performed while the server is online.
Archiving historical data locally on page 4-2
Archiving historical data automatically on page 4-5
Retrieving historical data locally on page 4-7
There are two ways to perform an historical data archive or retrieval:

on each server, using the procedures in this document (known as local
historical data archive or retrieval)
from a backup and restore server, using VERITAS NetBackup 5.1

(Known as centralized historical data archive or retrieval. See Chapter 5,
Performing centralized backup and restore with an archive policy)
UMTS, GPRS, GSM
OAM 4.2
4-2 Performing historical data archive and retrieval

Nortel Confidential
Archiving historical data locally
Use this procedure to archive the historical data on an individual server.

Requirements
Have a blank DDS-4 tape ready to store the backup data. You can also use
a tape that has data on it and overwrite it.
Read and comply with the prerequisites section in Chapter 1,

Know the password for the nortel and root users on the server
If you try to archive data while a centralized data archive is
running (see Chapter 5, Performing centralized backup and
restore with an archive policy), both archive operations will
fail and the data will not be archived.
Procedure 4-1
Step
Action
user), start a console session and then become the root user by entering
su -
Enter:
localarchive [-h|H] [-d <n|n:m>] [-D <YYYYMMDD |
YYYYMMDD a:YYYYMMDD b>] [-t <tape name>]
See Table 4-1 for definitions of the options and parameters. If you do not
specify any options, all historical data for the previous day is archived.
411-8111-521
Preliminary
06.10
June 2005
Performing historical data archive and retrieval 4-3

Nortel Confidential
Procedure 4-1
Step
Action
If the tape is blank, the backup starts. Go to step 8.
If the tape is not blank, the following message is displayed:

All the data on this tape will be overwritten should you continue with
the backup.
The following prompt displays:
Do you wish to continue? [yes]
If you want to continue with the backup, press the Enter key and go to
step 8.
If you want to abort the backup, enter:

no
The backup aborts and the script completes.

8
If the data to be backed up takes up more than one tape, you are
prompted to insert another tape.
Review the log file /opt/nortel/logs/backup/ar/archive.log to make sure that

the archive completed successfully. If you did not specify a log file name
in step 3, the log file is named archive.log.
10
End of procedure.
Table 4-1
option and parameter definitions for localarchive command
parameter
value
-h or -H
Display help information about the command - cannot be

combined with other options
-d <n|n:m>
Archive data for a day or days prior to today (maximum of 4

days of data.) Cannot be combined with the -D option.
If n is specified, data from the current day - n is archived. For
example, to archive data from the day before yesterday,
specify n = 2.
If n:m is specified, data between the previous nth day and
mth day is archived. m must be greater than or equal to n. For
example, if the current date is January 10 and you want to
archive data from January 4 - 7 inclusive, specify 3:6.
sheet 1 of 2
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table 4-1 (continued)

option and parameter definitions for localarchive command
parameter
value
-D <YYYYMMDD |
YYYYMMDD a:
YYYYMMDD b>
Archive data for a specific date or range of dates (maximum

of 4 days of data.) Cannot be combined with the -d option.
If YYYYMMDD is specified, all historical data for the date
YYYYMMDD is archived. For example, to archive data on
December 27, 2003, specify 20031227.
If YYYYMMDDa:YYYYMMDD b is specified, all historical data
between the two dates is archived. YYYYMMDDb must be
greater than YYYYMMDDa and the dates must span 4 or
fewer days.
-t <tape name>
Write the backup to tape device <tape name>. <tape name>

is the name of the tape device.
If the -t option is not specified, the command assumes the
tape device is /dev/rmt/0n.
-s
Use only with scheduled operations. If the backup requires

more than one tape, the script will write an error message to
the log file and quit immediately. If the tape drive is empty
when the operation starts, the script will write an error
message to the log file and quit immediately.
sheet 2 of 2
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
This procedure explains how to modify the crontab file to schedule an

historical data archive to run automatically at regular intervals.
Restrictions for automatic archive
The following restrictions apply to an automatic archive:
The data to be archived must fit on one DDS-4 tape. If the data does not fit
on one tape, the archive fails and an error message is logged.
Before the archive is scheduled to run, you must ensure that there is a tape
in the tape drive of the server to be archived. If there is no tape in the tape
drive at the time the archive runs, the archive fails and an error message is
logged.
Requirements
utility. You can use the man crontab command to get more information about
crontab.
Procedure 4-2
Step
Action
su -

Add a line to the temporary file that schedules the historical data archive.
The following example schedules an archive to run at 3:15 every day and
it archives the previous days data:
15 3* * */usr/bin/localarchive -s > /dev/null 2>&1
Note: The -s option is necessary for a scheduled operation.

4

UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Procedure 4-2
Step
Action
The archive will run according to the schedule you have defined in the
crontab file. Before the archive runs, ensure that you have complied with
archive.
411-8111-521
Check the log file /opt/nortel/logs/backup/ar/archive.log following every

scheduled archive operation to ensure that the operation completed
without errors.
End of procedure.
Preliminary
06.10
June 2005

Nortel Confidential
Retrieving historical data locally
Use this procedure to retrieve the historical data for an individual server.
Requirements
have the tape(s) that contain the data you want to retrieve
know the password for the nortel and root users on the server
Procedure 4-3
Retrieving historical data locally
Step
Action
su -
Insert the tape into the tape drive of the server. If there is more than one
tape, insert the first one.
Enter:
localretrieve [-h|H] [-f] [-l] [-a mod1:mod2:...:modN] [-D <YYYYMMDD
| YYYYMMDDa:YYYYMMDDb>] [-t <tapedrive>]
See Table 4-2 for definitions of the options parameters. If you do not
specify any options, all historical data on the tape is retrieved.
If the data to be retrieved spans more than one tape, you are prompted to
insert the next tape.
Review the log file /opt/nortel/logs/backup/ar/retrieve.log to make sure

that the retrieve completed successfully. If you did not specify a log file
name in step 3, the log file is named retrieve.log.
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table 4-2
parameter definitions for localretrieve command
parameter
value
-h or -H
Display help information about the command. Cannot be

combined any other options.
-f
Perform an automatic purge if there is not enough disk space to

perform the retrieval.
If this parameter is not specified, and there is not enough disk
space to store the retrieval data, during the execution of the
retrieval a message will be displayed, with a choice to either
purge the data that currently exists on the disk or to abort the
retrieval.
-l
Display the tape label. Can be used alone or in combination

with the -t option. l is a lower case L, not an uppercase i.
-a mod1:mod2:...
modN
retrieve only the data for modules listed. If this option is not
specified, data for all modules on the tape is retrieved.
Example: cdi:gdi:mycom
See Table B-11 for a list of possible values.
-D <YYYYMMDD | Retrieve data for a specific date or range of dates (maximum of

YYYYMMDDa:
4 days of data.) If this option is not specified, all data archived
YYYYMMDDb>
on the tape is retrieved.
If YYYYMMDD is specified, all historical data for the date
YYYYMMDD is retrieved. For example, to retrieve data on
December 27, 2003, specify 20031227.
If YYYYMMDD a:YYYYMMDDb is specified, all historical data
between the two dates is retrieved. YYYYMMDD b must be
greater than YYYYMMDDa and the dates must span 4 or fewer
days.
-t <tapedrive>
411-8111-521
Preliminary
06.10
Use the tape device <tapedrive>. <tapedrive> is the name of

the tape drive. If this option is not specified, the command
assumes that the tape device is /dev/rmt/0n.
June 2005
5-1
Nortel Confidential
Performing centralized backup and

restore with an archive policy
Use this section if you plan to configure a centralized Archive

policy to archive historical data.
If you have your own backup policy to back up the historical
data or the file systems, refer to Performing centralized
backup and restore with no archive policyRMAN used for
HFB Oracle database instead.
This chapter contains information about using VERITAS NetBackup 5.1 to
perform backup and restore of the W-NMS servers. The procedures do not
provide instructions about how to install or use VERITAS NetBackup.
This chapter includes the following topics:
Configuring NetBackup on page 5-4
Installing the UNIX NetBackup Client on page 5-5
Installing the VERITAS NetBackup Oracle agent on page 5-6
Creating backup path files on page 5-7
Configuring policies on page 5-9
Upgrading a VERITAS NetBackup server from OAM 3.x to OAM 4.x

on page 5-13
Archiving historical data manually on page 5-14
Restoring a server using VERITAS NetBackup on page 5-15
Retrieving historical data on page 5-22
UMTS, GPRS, GSM
OAM 4.2
5-2 Performing centralized backup and restore with an archive policy

Nortel Confidential
Before performing the procedures in this chapter you must ensure that the
server that has the VERITAS NetBackup server software installed can
communicate with all the servers you want to back up. Refer to the VERITAS
documentation for more information.
WARNING:
Only VERITAS NetBackup version 5.1 has been tested with
the following procedures. Other versions may interact
differently with the backup and restore scripts.
For more information about VERITAS NetBackup, refer to the following

VERITAS documents:
VERITAS NetBackup 5.0 System Administrators Guide Volume I for
UNIX, N10238B
VERITAS NetBackup 5.0 System Administrators Guide Volume II for

UNIX, N10239B
VERITAS NetBackup 5.0 Users Guide for UNIX, N10262B
VERITAS NetBackup 5.1 for Oracle System Administrators Guide for

UNIX, N12320B
VERITAS NetBackup 5.1 Installation Guide for UNIX, N12358B
VERITAS NetBackup Performance Tuning for UNIX Platforms
Before performing the procedures in this chapter you must be familiar with and
know how to perform the following tasks using VERITAS NetBackup:
create and configure a policy
back up the data on a server
restore the data to a server
monitor NetBackup activity

centralized backup or restore, refer to the section titled Restrictions and
411-8111-521
Preliminary
06.10
June 2005
Performing centralized backup and restore with an archive policy 5-3

Nortel Confidential
The procedures in this chapter explain:

how to create backup path files for the W-NMS servers
how to configure policies for the W-NMS servers
how to configure the UNIX NetBackup Client and Oracle agent
how to perform a backup or a restore of a W-NMS server
The following table shows the procedures that are applicable for each server:
Table 5-1
Procedures to perform by server
Server
Procedure
Veritas
NetBackupa
Main Server
Primary
Configure NetBackup
Procedure 5-1
Performance SRS SOC
Secondary
Install UNIX NetBackup Clientb

Procedure 5-2
Install Oracle agent c

Procedure 5-3
Create backup path file

Procedure 5-4
Configure policies
Procedure 5-5
Back up a server
Performed automatically by NetBackup
Back up a server manually
See Backing up configuration data manually in this chapter
restore a server
Stop the server processes
Procedure 5-8
Restore the brd files
Procedure 5-9
Restore the configuration data

Procedure 5-10
Xd
a. This is the server that has the VERITAS NetBackup Data Center software installed.
b. See the procedure for information about when to perform this procedure.
c. See the procedure for information about when to perform this procedure.
d. This procedure requires the VERITAS NetBackup server to transfer backup data to the OAM server.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Configuring NetBackup
This procedure modifies the bp.conf file to allow time for backup activities
that must occur before a backup starts.
Requirements
Perform this procedure before performing any of the other procedures in this
chapter.
Procedure 5-1
Step
Action
Log onto the server that has the NetBackup server software installed.
Open the following file for editing:

/opt/openv/netbackup/bp.conf
Add the following lines to the file:

BPSTART_TIMEOUT = <seconds>
CLIENT_READ_TIMEOUT = <seconds>
where <seconds> is an integer value greater than or equal to 3600
Note: If you use the archive and retrieval feature and configure an
Archive policy to archive historical data, set the time to 14400 (4 hours) to
avoid time-out situations when the system is archiving historical data.
Monitor the next archive operation to ensure the time is adequate. If
necessary, increase the time if your system has a large amount of
historical data.
411-8111-521
Save the bp.conf file.
End of procedure.
Preliminary
06.10
June 2005

Nortel Confidential
Installing the UNIX NetBackup Client
Install the UNIX NetBackup Client after initial installation and after each
upgrade of the server. Refer to VERITAS NetBackup 5.1 Installation Guide
for UNIX (N12358B) for the details of Client installation. Use Procedure 5-2
to install the UNIX NetBackup Client.
Procedure 5-2
Installing and configuring the UNIX NetBackup Client
Step
Action
Log onto the server as nortel (or some other normal user), start a terminal
session and then become the root user by entering
su -
Verify that the file /etc/hosts contains an entry for the VERITAS
NetBackup server. If the file does not contain such an entry, edit the file
and add one.
Install the UNIX NetBackup Client on the W-NMS server. Refer to

VERITAS NetBackup 5.1 Installation Guide for UNIX (N12358B)
for details.
Edit the file /usr/openv/netbackup/bp.conf
Look for the following lines and add them if they do not already exist:
SERVER = <NetBackup server host name>
CLIENT_NAME = <client host name>
REQUIRED_INTERFACE = <client host name>
where <NetBackup server host name> is the host name of the
VERITAS NetBackup server
where <client host name> is the host name of the backup and restore
network interface on the server
Save and close the bp.conf file.
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Installing the VERITAS NetBackup Oracle agent
This procedure installs and configures the Oracle agent for VERITAS
Netbackup. Perform this procedure only if you want to back up the Oracle
database.
Requirements
Perform this procedure on Performance Servers that have MyCom PrOptima
installed immediately after initial server installation and after each
upgrade. Perform this procedure before performing the first backup on the
server.
Procedure 5-3
Installing and configuring the VERITAS NetBackup Oracle agent
Step
Action
Verify that the Oracle database is up and running.
Open the SMC GUI
Browse to the Oracle Supervision icon for the server:
<host name>->Local Applications->Oracle Supervision
Verify that there are no alarms on the Oracle application group.
Install the NetBackup Oracle Agent on the W-NMS server that has been
installed with
MyCom PrOptima Oracle database (Performance Server)
Refer to VERITAS NetBackup 5.1 for Oracle System

Administrators Guide for UNIX (N12320B) for details.
3
su -
Note: Running configAgent will temporarily interrupt access to the Oracle

database.
4
In a terminal window, enter the following command:

configAgent
411-8111-521
Verify that configAgent completes without errors. Errors are displayed to

the screen and logged to /opt/nortel/logs/backup/configAgent.sh.log.
End of procedure.
Preliminary
06.10
June 2005

Nortel Confidential
Creating backup path files
Use this procedure to create the backup path files. A backup path file is used
to determine which files and directories to back up. You can use the file as a
reference when configuring policies for a server. For more information about
policies, refer to the VERITAS documentation.
The following table describes the backup path files created by this procedure.
Table 5-2
backup path file
purpose
/opt/nortel/data/backup/BRTools/
veritas/client/backup_UNIX
specifies the UNIX files on the server which will be backed

up
veritas/client/backup_ORACLE
specifies the path to the script which performs the Oracle

backup (created only on a Performance Server on which
both NIMS-PrOptima and an Oracle database have been
installed.)
veritas/client/backup_USER
indicates that a user policy must be configured to back up

Oracle control files (created only on a Performance Server
on which both NIMS-PrOptima and an Oracle database
have been installed.)
Requirements
Before performing this procedure you must have previously installed and
configured the UNIX NetBackup Client and if required, the VERITAS
NetBackup Oracle agent. See Procedure 5-2 and Procedure 5-3. For
information about what the ubvaClient utility actually does, see ubvaClient
theory of operation in Chapter 1.
You must perform this procedure:
after installation of any new software
after upgrade of previously installed software
Perform Procedure 5-4 on each server to be backed up.

The UNIX NetBackup Clients and (optionally) Oracle agents
must be properly installed on the servers before performing
Procedure 5-4.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Procedure 5-4
Step
Action
su -
Verify that /usr/openv/netbackup/bp.conf contains an entry for the clients

hostname. The syntax is CLIENT_NAME = <host name>, where <host
name> is the clients host name that is associated with the backup and
restore sub-net.
In the terminal window, enter:

ubvaClient
Do you plan to configure an Archive Policy to archive
historical data?
NOTE: For customers who use Nortel standard backup/
restore & archive/retrieval solution,
please enter "y".
For others who customized a File System policy to
backup data of file systems, please enter "n".
[y,n,q to quit]: y
You will be asked to enter the name for each policy you need to configure
on the VERITAS NetBackup server. Note that for ubvaClient policy and
class mean the same thing. The default name for each policy is shown in
Table 5-3. You may follow your organizations naming conventions and
use different names. Be sure to record and use the same names when
you configure the policies on the VERITAS NetBackup server.
4
Verify that the backup path files exist in the /opt/nortel/data/backup/

BRTools/veritas/client directory. Look at the log file in /opt/nortel/logs/
backup/ubvaClient.log to make sure that the script ran successfully.
End of procedure.
Note: Nortel recommends that you now perform a System Backup to

back up the client software and the configuration parameters you set.
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Configuring policies
Procedure 5-5, Configuring policies using VERITAS NetBackup, explains

how to use VERITAS NetBackup to configure the policies. When you
perform this procedure, define the policies using the values shown in Table 54. Configure policies for each server as shown in Table 5-3; if you changed
the policy names when you ran ubvaClient, use the names you defined instead
of the default names.
Table 5-3
Default policy names
Server
Policy
Default name
Primary Main
UNIX files
<host name>_NNunix
Secondary Main
UNIX files
<host name>_NNunix
Performance
UNIX files
Oracle database
Oracle control files
<host name>_NNunix
<host name>_NNoracle
<host name>_NNuser
SRS
UNIX files
<host name>_NNunix
Server of Client
UNIX files
<host name>_NNunix
Per server, ROC

or NOCa
Historical data
(ARCHIVAL)
NNoam_archive
a. This policy may be defined per server, per ROC or per NOC. Define the policy and add as many Clients
(servers) to the policy as is appropriate.
The values that must be used when configuring the policies are shown in
Table 5-4. The variables used in Table 5-3 and Table 5-4 are explained in
Table 5-5.
Table 5-4
Policy parameter values
Parameter
Policy
UNIX files
Oracle database
Historical data
(ARCHICAL)
Default
<host name>_NNunix <host name>_NNoracle <host name>_NNuser NNoam_archive
Policy Name
Policy type
Standard
Oracle
UMTS, GPRS, GSM
Standard
Standard
OAM 4.2

Nortel Confidential
Table 5-4 (continued)
Parameter
Policy
Historical data
(ARCHICAL)
UNIX files
Oracle database
Client List
<host name>
<host name>
<host name>
<host name> for each

of primary main,
secondary main,
performance, SRS, and
SOC servers in a ROC
or NOC a
Hardware
and
operating
system
Solaris, Solaris8
Solaris, Solaris8
Solaris, Solaris8
Solaris, Solaris8
Path Name
not applicable
all entries in /opt/
nortel/data/backup/
BRTools/veritas/client/
backup_UNIX (Use
the UNIX more
command to find all
the entries.)
null (Do not enter a

value.)
/etc/hostsb
User Backupd, e
Full Backup
User Archivee
Backup Type Full backupc

(Schedule)
Automatic Full Backup

Application Backupe
Script Path
/opt/nortel/shell/backup/ not applicable

veritas/
veritasBpOracle.sh
not applicable
compression no
not applicable
no
no
Allow
no
multiple data
streams
not applicable
yes
no
not applicable
a. For historical data archive, you can define policies per server, per ROC or per NOC.
b. The historical data policy has two schedules. The first one, the Full Backup schedule, is used to trigger the prearchive script on the host. The second, the actual User Archive, is invoked by the pre-archive script on the host.
The Full Backup will not run unless a backup path is specified; /etc/hosts is recommended as it will always exist
on the host, but you could instead configure any small file that is guaranteed to exist on the host.
c. For the UNIX files and the Oracle database, you can define additional backup schedules for other types of backups.
d. For the Oracle control files, define only the User Backup Backup Type.
e. For User Backup, Application Backup and User Archive Backup Type, a duration of 24 hours is recommended
to ensure that these two backups can be run at any time.
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Table 5-5
variable definitions
Variable
Description
<host name>
The OAM server host name of the network interface dedicated

to the backup and restore local area network (LAN). For a Sun
Fire 4500 or a Sun Fire 880, use the host name associated
with the qfe1 port. For a Sun Fire 4800 or E4900, use the host
name associated with the qfe0 port.
Configuring policies using VERITAS NetBackup

Use this procedure to configure policies for the W-NMS servers. In this
procedure you can set variables like the backup type, rotation, and start
window period. Use Table 5-4 to define the policies for the W-NMS servers.
If you do not define the parameters as specified in Table 5-4, the backup will
fail. Set any parameters not shown in Table 5-4 according to your corporate
standards. Perform this procedure for each server to be backed up.
As per the restrictions on backup and restore listed in
Chapter 1, Understanding backup and restore, configure the
policy for the data backup on the Secondary Main Server to
run at a different time from the System Backup on the Primary
Main Server.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Procedure 5-5
Step
Action
Log onto the NetBackup Administration window. Enter:

/usr/openv/netbackup/bin/jnbSA &
Create a new policy using the Backup Policy Configuration Wizard for each of the following
items, if they exist on the server:
UNIX files
Oracle database
historical data (can be per server, per ROC or per NOC according to customer
requirements)
Note: Create a policy for the Oracle database only if the file /opt/nortel/data/backup/
BRTools/veritas/client/backup_ORACLE file exists. Create a policy for the Oracle control files
only if the /opt/nortel/data/backup/BRTools/veritas/client/backup_USER file exists.
3
For historical data, you must create two schedules, one with Type of backup = Full Backup
and one with Type of backup = User Archive. Nortel recommends that you configure the User
Archive schedule with a start time of 00:00:00 and a duration of 24:00:00 for each day of the
week. This will allow the User Archive to be invoked any time of the day as recommended in
Table 1-1.
Changing the NetBackup system configuration

4
From the Configure menu of the Global Data Manager window, select NetBackup System
Configuration.
Change the Maximum jobs per client to 99 as per VERITAS' recommendations - see
VERITAS NetBackup 5.1 for Oracle System Administrator's Guide for Unix (N12320B).
Note: Instead of changing the value of Maximum jobs per client globally, you may set this value on a
per-client basis with the bpclient command. The syntax is as follows:
/usr/openv/netbackup/bin/admincmd/bpclient -client <client hostname> -add -max_jobs 99
where <client hostname> is the host name of the server that you are backing up.
6
If an Archive policy has been configured to archive historical data, ensure that the time-out
value is set appropriately. Refer to Procedure 5-1, step 3.
WARNING: Failure to set time-out value appropriately may cause the archive process to
time-out.
End of procedure.
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Upgrading a VERITAS NetBackup server from OAM 3.x to OAM 4.x 5

This procedure explains the steps you must perform on the VERITAS
NetBackup server if you are upgrading from OAM 3.0b or OAM 3.1 to OAM
4.0a, OAM 4.1, or OAM 4.2 and you are using centralized backup and
restore.
Requirements
Perform this procedure if:
you are upgrading from OAM 3.0b or OAM 3.1 to OAM 4.0a, OAM 4.1
or OAM 4.2
you used centralized backup and restore in with OAM 3.0a or OAM 3.1
and you intend to use centralized backup and restore in OAM 4.0a, OAM
4.1 or OAM 4.2
Procedure 5-6
Upgrading from UMTS 3.0, GPRS 5.0 to UMTS 4.0, GPRS 6.0
Step
Action
Make sure that you have performed Procedure 5-4 and Procedure 5-5.
On the VERITAS NetBackup server, delete the Oracle backup policy

(default name: <hostname>_NNoracle) for the Primary Main Server.
On the VERITAS NetBackup server, delete the user backup up policy

(default: <hostname>_NNuser) for the Primary Main Server.
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
If you want to run a configuration data backup other than the automatic backups
performed by VERITAS NetBackup, you must run the following policies:
UNIX files policy (<host name>_NNunix)
Oracle database policy (on the servers that have the Oracle database;
default name is <host name>_NNoracle)
Do not run the Oracle control files policy (<host name>_NNuser) manually.
See Table 5-3 for a list of the policies that apply to each server.
For more information about backing up a server manually, see the VERITAS
NetBackup 5.1 System Administrators Guide, 100-001459.
Archiving historical data manually
If you want to run an historical data archive other than the automatic archive
performed by VERITAS NetBackup, perform this procedure. This procedure
archives the historical data for one server.
Procedure 5-7
Archiving historical data manually
Step
Action
su -
Enter:
centralarchive -D yyyymmdd
where yyyymmdd is the year, month, and day that you want to archive
You can archive multiple days of data by repeating the command,
separating each command by a semi-colon. Example:
centralarchive -D 20031223; centralarchive -D 20031225;
centralarchive -D 20031231
The data is archived to the disk of the server and then VERITAS
NetBackup backs up the data to tape (performed by NNoam_archive).
When the archive is complete, a message stating the process is complete
is displayed.
411-8111-521
Check the log files stored at /opt/nortel/logs/backup/ar/centralarchive.log

to ensure that the archive completed successfully.
End of procedure.
Preliminary
06.10
June 2005

Nortel Confidential
Restoring a server using VERITAS NetBackup
When you restore one server in a ROC, you must restore all the other servers
in the ROC to maintain the consistency and integrity of the data throughout the
ROC. Restore the Primary and Secondary Main Servers first, followed by the
other servers.
Perform the following procedures to restore the data for a server. You must
perform the procedures in the order listed:
1. Procedure 5-8, Stopping the server processes (performed on the server
being restoredMain, Performance, and Server of Clients only)
2. Procedure 5-9, Restoring the brd files (performed on the VERITAS
NetBackup Master Server and the server being restored)
3. Procedure 5-10, Restoring the data for the server (performed on the
VERITAS NetBackup Master Server and the server being restored)
This procedure stops the server processes. This is the first of three procedures
you must perform when you restore a server using VERITAS NetBackup.
Procedure 5-8
Step
Action
Log onto the server you are restoring to, using the nortel user ID.

3
Enter:
su - root
sheet 1 of 2
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Step
Action
If you are working on the primary main server enter:

Note: l is a lower case L, not an upper case i.


5
End of procedure.
sheet 2 of 2
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Restoring the brd files

This procedure restores the /opt/nortel/data/backup/parsed_brd directory.
There are configuration files in the /opt/nortel/data/backup/parsed_brd
directory which control how a restore is performed. This procedure is the
second of three procedures you must perform when you restore a server using
VERITAS NetBackup.
Requirements
You must perform this procedure after you perform Procedure 5-8.
Procedure 5-9
Step
Action
Log on to the NetBackup Administration window on the VERITAS

NetBackup Master Server. If you are not logged in locally, set the
DISPLAY environment variable to point to the workstation X display server
and then enter:
Start the Backup, Archive, and Restore utility.
Use the following values in the Backup, Archive, and Restore window:
NetBackup server: host name of the server that has the NetBackup
server software installed
Source client: the OAM server host name of the network interface
dedicated to the backup and restore LAN
Policy type: Standard (this is the default value)
Destination client: the OAM server host name of the network interface
Use the following values in the Restore Files tab:
Restore type: Normal backups (this is the default value)
Click the use Backup History to set date range icon. (Its the icon
on the far right; hover the cursor over the icon to show its name.) The
Date Range dialog will pop up. Select the Unix policy of the desired
backup date and click OK.
In the Browse directory: field, type /opt/nortel/data/backup/

BRTools/br/parsed_brd and press the Enter key.
Select the check box for the parsed_brd directory
Click on the Restore button

sheet 1 of 2
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Step
Action
Use the following values in the Restore Files window:
Select the Restore everything to its original location check box
Select the Overwrite existing files check box
Click on the Start Restore button.
Launch the Activity Monitor from the Global Data Manager window and
monitor the status of the restore job.
10
Successful completion of the restore job is indicated by a Status of zero. If

you receive a Status of zero, go to step 14.
Non-zero Status
11
If you receive a Status that is not zero, open a terminal window on the
server that is being restored. If you are not already the root user, on that
server, become the root user (enter su - ).
12
Enter:
postVeritasRestore ABORT
This will cancel the restore operation and perform the necessary cleanup. Wait for the clean-up to finish.
13
Investigate the problem that caused the non-zero Status for the restore
job. After you have resolved the problem, attempt the restore again:
If you re-started SMC or the server processes, start from the

beginning of Procedure 5-8;
If you exited from the NetBackup Administration tool, start from step 1
of this procedure
Otherwise, start from step 2 of this procedure.
14
Keep the NetBackup Administration window open because you will use it
in Procedure 5-10.
15
End of procedure.
sheet 2 of 2
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Restoring the data for the server

This procedure restores the data from a selected backup created in VERITAS
NetBackup. This procedure is the third of three procedures you must perform
when you restore a server using VERITAS NetBackup.
This procedure restores the:
backup and restore data files
UNIX files
Oracle database (if applicable for the server)
Requirements
This procedure must be performed after Procedure 5-9.
Procedure 5-10
Step
Action
Restoring the data

1
In a terminal window that is logged in as root on the server being restored

(if necessary, become the root user by entering su -), enter:
preVeritasRestore
Note: If you want to cancel the restore operation after you have executed
the preVeritasRestore command, you must enter the command
postVeritasRestore ABORT to cancel the restore and then start from step
3 in Procedure 5-9 again.
2
Go to the NetBackup Administration session you started in Procedure 59.
Restore the data, using the values as shown in the following steps.
Click the use Backup History to set date range icon. The Date
Range dialog will pop up. Select the UNIX policy (and USER policy if
any) that you specified in Procedure 5-9 step 4. You have to select the
USER policy to restore the MyCom Oracle database on a
Performance server.
In the Directory Structure column, select the check box for /. This
will select all paths (they all start with /).

sheet 1 of 3
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Step
Action
Select the Restore everything to its original location check box.
Select the Overwrite existing files check box.
Monitor the status of the restore job from the Activity Monitor window.

If you receive a Status of 1, refer to Centralized Data Restore in

Appendix C: Troubleshooting. If you received the Status of 1 because of
the ACL settings in /opt/nortel/data/srs, go to step 12. Otherwise (that is,
for any non-zero Status), open a terminal window on the server that is
being restored. If you are not already the root user, on that server,
become the root user (enter su - ).
10
Enter:
11
12
Do not perform the rest of the steps in this procedure. Investigate the
problem that caused the non-zero Status for the restore job. After you
have resolved the problem, attempt the restore again:

of Procedure 5-9.
Otherwise, start from step 2 of Procedure 5-9.

postVeritasRestore
Note: If a system restore was performed immediately prior to this

centralized data restore, the mirror disks will be attached and the root
partition will be synchronized at this point. Wait for the operation to
complete and for the command prompt to reappear.
13
Look at the log file in /opt/nortel/logs/backup/centralBackupRestore.log to

make sure the restore ran successfully.
sheet 2 of 3
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential

Step
Action

14

init 6

15
16

17

a. Make sure that all applications (except possibly the HFB Oracle
database) are up and running; on servers with an HFB Oracle
database, the database may be running or stopped for this step.
b.
18
Enter:
postDataRestore
If you are working on the Main Server, this command rebuilds the HFB
Oracle database and JavaHelp if they are corrupt. If you are working on
any other server, this command deletes and cleans up temporary files
used during the restore process.
19
End of procedure.
sheet 3 of 3
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Retrieving historical data
Use this procedure to retrieve the historical data for a server using VERITAS
NetBackup. This procedure retrieves the data from a selected historical data
archive created by VERITAS NetBackup. You can retrieve historical data for
an individual application.
Requirements
ensure that there is enough disk space in /opt/nortel/data to store the data
you want to retrieve
Procedure 5-11
Step
Action
Log onto the server you are retrieving data for as root.
Enter:
prepCentralRetrieve
Wait for the script to finish before proceeding.

Use the Backup, Archive, and Restore utility to retrieve the data, using the
values shown in the following steps.
sheet 1 of 3
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential

Step
Action
Restore type: Archived Backups
Range dialog will pop up. Select the ARCHIVAL policy of the desired
backup date and click OK. You may select multiple dates to restore.
Browse directory: /opt/nortel/data/backup/BRTools/ar/archive_data
Press the Enter key.
A list of directories displays under Directory Structure.

The directory names have the format <yyyymmdd>_OAMAR
where yyyymmdd is the date (year, month, and day) that the data was
archived
7
Select the directories or files you want to restore. To restore the data for
individual applications:
a. Expand the <yyyymmdd>_OAMAR directory.
A list of individual files with the following file name format appears:
<application>.gnutar
b.
Select the files you want to restore.
Click on the Restore button.
In the Restore Files window select the Restore everything to its original
location check box.
10
11
12

sheet 2 of 3
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Step
Action
13
If you receive a Status that is not zero, perform step 2.
14
problem that caused the non-zero Status for the retrieval job. After you
have resolved the problem, perform this procedure starting from step 1.
15
In a terminal window on the server being restored, enter:

centralretrieve <-f>
where <-f> is optional. If you specify -f, if there is not enough room on
the disk to perform the retrieval, an automatic purge is
performed to free up disk space. For information about the
purge mechanism, refer to W-MNSSystem Management, 4118111-538.
16
Look at the log file in /opt/nortel/logs/backup/ar/centralretrieve.log to

make sure that the retrieval was successful.
17
End of procedure.
sheet 3 of 3
411-8111-521
Preliminary
06.10
June 2005
6-1
Nortel Confidential
Performing centralized backup and

restore with no archive policyRMAN
used for HFB Oracle database
6
Use this chapter if you do not need to configure a centralized
archive policy to archive historical data.
If your system has a separate backup policy to back up the
historical data or data in all the file systems on the server, use
this chapter to back up the HFB Oracle database through
RMAN utility as part of the data backup.
Nortel strongly recommends that this feature be deployed
uniformly across the OAM network - no server should use
centralized archive and retrieve for historical data.
If you plan to use a centralized Archive policy, refer to
Performing centralized backup and restore with an
archive policy
This chapter contains information about using VERITAS NetBackup 5.1 to
perform backup and restore of the W-NMS servers. The procedures do not
provide instructions about how to install or use VERITAS NetBackup.
This chapter includes the following topics:
Configuring NetBackup on page 6-5
Installing the UNIX NetBackup Client on page 6-6
Installing the VERITAS NetBackup Oracle agent on page 6-7
Creating backup path files on page 6-8
Configuring policies on page 6-11

UMTS, GPRS, GSM
OAM 4.2
6-2 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
Restoring a server using VERITAS NetBackup on page 6-15
Before performing the procedures in this chapter you must ensure that the
server that has the VERITAS NetBackup server software installed can
communicate with all the servers you want to back up. Refer to the VERITAS
documentation for more information.
WARNING:
Only VERITAS NetBackup version 5.1 has been tested with
the following procedures. Other versions may interact
differently with the backup and restore scripts.
For more information about VERITAS NetBackup, refer to the following

VERITAS documents:
VERITAS NetBackup 5.0 System Administrators Guide Volume I for
UNIX, N10238B
VERITAS NetBackup 5.0 System Administrators Guide Volume II for

UNIX, N10239B
VERITAS NetBackup 5.0 Users Guide for UNIX, N10262B
VERITAS NetBackup 5.1 for Oracle System Administrators Guide for

UNIX, N12320B
VERITAS NetBackup 5.1 Installation Guide for UNIX, N12358B
VERITAS NetBackup Performance Tuning for UNIX Platforms
Before performing the procedures in this chapter you must be familiar with and
know how to perform the following tasks using VERITAS NetBackup:
create and configure a policy
back up the data on a server
restore the data to a server
monitor NetBackup activity

centralized backup or restore, refer to the section titled Restrictions and
411-8111-521
Preliminary
06.10
June 2005
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-3
The procedures in this chapter explain:

how to create backup path files for the W-NMS servers
how to configure policies for the W-NMS servers
how to enable the Centralized Backup and Restore of HFB Database with
RMAN Utility feature
how to configure the UNIX NetBackup Client and Oracle agent
how to perform a backup or a restore of a W-NMS server
The following table shows the procedures that are applicable for each server:
Table 6-1
Procedures to perform by server
Server
Procedure
Veritas
NetBackupa
Main Server
Primary
Configure NetBackup
Procedure 6-1
Performance SRS SOC
Secondary
Install UNIX NetBackup Clientb

Procedure 6-2
Install Oracle agent c

Procedure 6-3
Create backup path file

Procedure 6-4
Configure policies
Procedure 6-5
Back up a server
Performed automatically by NetBackup
Back up a server manually
See Backing up configuration data manually in this chapter
restore a server
Stop the server processes
Procedure 6-6
Restore the brd files
Procedure 6-7
Restore the configuration data

Procedure 6-8
Xd
a. This is the server that has the VERITAS NetBackup Data Center software installed.
UMTS, GPRS, GSM
OAM 4.2
database
b. See the procedure for information about when to perform this procedure.
c. See the procedure for information about when to perform this procedure.
d. This procedure requires the VERITAS NetBackup server to transfer backup data to the OAM server.
411-8111-521
Preliminary
06.10
June 2005
database 6-5
This procedure modifies the bp.conf file to allow time for backup activities
that must occur before a backup starts.
Requirements
Perform this procedure before performing any of the other procedures in this
chapter.
Procedure 6-1
Step
Action
Log onto the server that has the NetBackup server software installed.
Open the following file for editing:

/opt/openv/netbackup/bp.conf
Add the following lines to the file:

BPSTART_TIMEOUT = <seconds>
CLIENT_READ_TIMEOUT = <seconds>
Note: <seconds> is an integer value greater than or equal to 3600

4
Save the bp.conf file.
End of procedure.
UMTS, GPRS, GSM
OAM 4.2
database
Installing the UNIX NetBackup Client
Install the UNIX NetBackup Client after initial installation and after each
upgrade of the server. Refer to VERITAS NetBackup 5.1 Installation Guide
for UNIX (N12358B) for the details of Client installation. Use Procedure 6-2
to install the UNIX NetBackup Client.
Procedure 6-2
Installing and configuring the UNIX NetBackup Client
Step
Action
su -
Verify that the file /etc/hosts contains an entry for the VERITAS
NetBackup server. If the file does not contain such an entry, edit the file
and add one.
Install the UNIX NetBackup Client on the W-NMS server. Refer to

VERITAS NetBackup 5.1 Installation Guide for UNIX (N12358B)
for details.
Edit the file /usr/openv/netbackup/bp.conf
Look for the following lines and add them if they do not already exist:
SERVER = <NetBackup server host name>
CLIENT_NAME = <client host name>
REQUIRED_INTERFACE = <client host name>
where <NetBackup server host name> is the host name of the
VERITAS NetBackup server
where <client host name> is the host name of the backup and restore
network interface on the server
411-8111-521
Save and close the bp.conf file.
End of procedure.
Preliminary
06.10
June 2005
database 6-7
Installing the VERITAS NetBackup Oracle agent
This procedure installs and configures the Oracle agent for VERITAS
Netbackup. Perform this procedure only if you want to back up the Oracle
database.
Requirements
Perform this procedure on Performance Servers that have MyCom PrOptima
installed and on Primary Main Servers that have a Historical Fault Browser
Oracle database installed immediately after initial server installation and
after each upgrade. Perform this procedure before performing the first
backup on the server.
Procedure 6-3
Installing and configuring the VERITAS NetBackup Oracle agent
Step
Action
Verify that the Oracle database is up and running.
Open the SMC GUI
Browse to the Oracle Supervision icon for the server:
<host name>->Local Applications->Oracle Supervision
Verify that there are no alarms on the Oracle application group.
Install the NetBackup Oracle Agent on the W-NMS server that has been
installed with either
MyCom PrOptima Oracle database (Performance Server)
Historical Fault Browser Oracle database (Primary Main Server)
Refer to VERITAS NetBackup 5.1 for Oracle System

Administrators Guide for UNIX (N12320B) for details.
3
su -
Note: Running configAgent will temporarily interrupt access to the Oracle

database.
4
In a terminal window, enter the following command:

configAgent
Verify that configAgent completes without errors. Errors are displayed to

the screen and logged to /opt/nortel/logs/backup/configAgent.sh.log.
End of procedure.
UMTS, GPRS, GSM
OAM 4.2
database
NOTE
VERITAS NetBackup supports a variety of approaches to defining
policies; for an example of one of these alternative approaches, see
Appendix D: Technical note - alternative policies. Procedures
Procedure 6-4 and Procedure 6-5 are compatible only with the standard
Nortel approach to defining policies; if you use Procedure 6-4 and
Procedure 6-5 with one of the alternative approaches, your backup and
restore configurations could be over-written.
Use this procedure to create the backup path files. A backup path file is used
to determine which files and directories to back up. You can use the file as a
reference when configuring policies for a server. For more information about
policies, refer to the VERITAS documentation.
The following table describes the backup path files created by this procedure.
Table 6-2
backup path file
purpose
veritas/client/backup_UNIX
specifies the UNIX files on the server which will be backed

up
veritas/client/backup_ORACLE
specifies the path to the script which performs the Oracle

backup (created only on a Performance Server on which
both NIMS-PrOptima and an Oracle database have been
installed, or on a Primary Main Server on which both HFB
and an Oracle database have been installed)
veritas/client/backup_USER
indicates that a user policy must be configured to back up

Oracle control files (created only on a Performance Server
on which both NIMS-PrOptima and an Oracle database
have been installed, or on a Primary Main Server on which
both HFB and an Oracle database have been installed)
411-8111-521
Preliminary
06.10
June 2005
database 6-9
Requirements
Before performing this procedure you must have previously installed and
configured the UNIX NetBackup Client and if required, the VERITAS
NetBackup Oracle agent. See Procedure 6-2 and Procedure 6-3. For
information about what the ubvaClient utility actually does, see ubvaClient
theory of operation in Chapter 1.
You must perform this procedure:
after installation of any new software
after upgrade of previously installed software
Perform Procedure 6-4 on each server to be backed up.

The UNIX NetBackup Clients and (optionally) Oracle agents
must be properly installed on the servers before performing
Procedure 6-4.
Procedure 6-4
Step
Action
su -
Verify that /usr/openv/netbackup/bp.conf contains an entry for the clients

hostname. The syntax is CLIENT_NAME = <host name>, where <host
name> is the clients host name that is associated with the backup and
restore sub-net.
UMTS, GPRS, GSM
OAM 4.2
database
Procedure 6-4
Step
Action
In the terminal window, enter:

ubvaClient
Do you plan to configure an Archive Policy to archive
historical data?
NOTE: For customers who use Nortel standard backup/
restore & archive/retrieval solution,
please enter "y".
For others who customized a File System policy to
backup data of file systems, please enter "n".
[y,n,q to quit]: n
You will be asked to enter the name for each policy you need to configure
on the VERITAS NetBackup server. Note that for ubvaClient policy and
class mean the same thing. The default name for each policy is shown in
Table 6-3. You may follow your organizations naming conventions and
use different names. Be sure to record and use the same names when
you configure the policies on the VERITAS NetBackup server.
4
Verify that the backup path files exist in the /opt/nortel/data/backup/

BRTools/veritas/client directory. Look at the log file in /opt/nortel/logs/
backup/ubvaClient.log to make sure that the script ran successfully.
End of procedure.
Note: Nortel recommends that you now perform a System Backup to

back up the client software and the configuration parameters you set.
411-8111-521
Preliminary
06.10
June 2005
database 6-11
Configuring policies
Procedure 6-5, Configuring policies using VERITAS NetBackup, explains

how to use VERITAS NetBackup to configure the policies. When you
perform this procedure, define the policies using the values shown in Table 64. Configure policies for each server as shown in Table 6-3; if you changed
the policy names when you ran ubvaClient, use the names you defined instead
of the default names.
Table 6-3
Default policy names
Server
Policy
Default name
Primary Main
UNIX files
Oracle database
<host name>_NNunix
<host name>_NNuser
Secondary Main
UNIX files
<host name>_NNunix
Performance
UNIX files
Oracle database
<host name>_NNunix
<host name>_NNuser
SRS
UNIX files
<host name>_NNunix
Server of Client
UNIX files
<host name>_NNunix
Historical data
(ARCHIVAL)
Note: This policy is not required because Archive and

Retrieval has been disabled.
The values that must be used when configuring the policies are shown in
Table 6-4. The variables used in Table 6-3 and Table 6-4 are explained in
Table 6-5.
UMTS, GPRS, GSM
OAM 4.2
database
Table 6-4
Parameter
Policy
UNIX files
Oracle database
Historical data
(ARCHICAL)
Default
<host name>_NNunix <host name>_NNoracle <host name>_NNuser This policy is not
Policy Name
required because
Archive and Retrieval
Policy type Standard
Oracle
Standard
has been disabled.
Client List
<host name>
<host name>
<host name>
Hardware
and
operating
system
Solaris, Solaris8
Solaris, Solaris8
Solaris, Solaris8
Path Name
not applicable
all entries in /opt/
nortel/data/backup/
BRTools/veritas/client/
backup_UNIX (Use
the UNIX more
command to find all
the entries.)
null (Do not enter a

value.)
Backup Type Full backupa

(Schedule)

Application Backupb
Script Path
/opt/nortel/shell/backup/ not applicable

veritas/
veritasBpOracle.sh
not applicable
User Backupb,c
compression no
not applicable
no
Allow
no
multiple data
streams
not applicable
yes
a. For the UNIX files and the Oracle database, you can define additional backup schedules for other types of backups.
b. For Application Backup and User Backup Backup Type, a duration of 24 hours is recommended to ensure that
these two backups can be run at any time.
c. For the Oracle control files, define only the User Backup Backup Type.
411-8111-521
Preliminary
06.10
June 2005
database 6-13
Table 6-5
variable definitions
Variable
Description
<host name>
The OAM server host name of the network interface dedicated

to the backup and restore local area network (LAN). For a Sun
Fire 4500 or a Sun Fire 880, use the host name associated
with the qfe1 port. For a Sun Fire 4800 or E4900, use the host
name associated with the qfe0 port.

Use this procedure to configure policies for the W-NMS servers. In this
procedure you can set variables like the backup type, rotation, and start
window period. Use Table 6-4 to define the policies for the W-NMS servers.
If you do not define the parameters as specified in Table 6-4, the backup will
fail. Set any parameters not shown in Table 6-4 according to your corporate
standards. Perform this procedure for each server to be backed up.
As per the restrictions on backup and restore listed in
Chapter 1, Understanding backup and restore, configure the
policy for the data backup on the Secondary Main Server to
run at a different time from the System Backup on the Primary
Main Server.
UMTS, GPRS, GSM
OAM 4.2
database
Procedure 6-5
Step
Action

Create a new policy using the Backup Policy Configuration Wizard for each of the following
items, if they exist on the server:
UNIX files
Oracle database
Note: Create a policy for the Oracle database only if the file /opt/nortel/data/backup/
BRTools/veritas/client/backup_ORACLE file exists. Create a policy for the Oracle control files
only if the /opt/nortel/data/backup/BRTools/veritas/client/backup_USER file exists.
Changing the NetBackup system configuration
3
From the Configure menu of the Global Data Manager window, select NetBackup System
Configuration.
Change the Maximum jobs per client to 99 as per VERITAS' recommendations - see
VERITAS NetBackup 5.1 for Oracle System Administrator's Guide for Unix (N12320B).
Note: Instead of changing the value of Maximum jobs per client globally, you may set this value on a
per-client basis with the bpclient command. The syntax is as follows:
/usr/openv/netbackup/bin/admincmd/bpclient -client <client hostname> -add -max_jobs 99
where <client hostname> is the host name of the server that you are backing up.
5
End of procedure.
411-8111-521
Preliminary
06.10
June 2005
database 6-15
If you want to run a configuration data backup other than the automatic backups
performed by VERITAS NetBackup, you must run the following policies:
UNIX files policy (<host name>_NNunix)
Oracle database policy (on the servers that have the Oracle database;
default name is <host name>_NNoracle)
Do not run the Oracle control files policy (<host name>_NNuser) manually.
See Table 6-3 for a list of the policies that apply to each server.
For more information about backing up a server manually, see the VERITAS
NetBackup 5.1 System Administrators Guide, 100-001459.
Restoring a server using VERITAS NetBackup
When you restore one server in a ROC, you must restore all the other servers
in the ROC to maintain the consistency and integrity of the data throughout the
ROC. Restore the Primary and Secondary Main Servers first, followed by the
other servers.
Perform the following procedures to restore the data for a server. You must
perform the procedures in the order listed:
1. Procedure 6-6, Stopping the server processes (performed on the server
being restoredMain, Performance, and Server of Clients only)
2. Procedure 6-7, Restoring the brd files (performed on the VERITAS
NetBackup Master Server and the server being restored)
3. Procedure 6-8, Restoring the data for the server (performed on the
VERITAS NetBackup Master Server and the server being restored)
UMTS, GPRS, GSM
OAM 4.2
database

This procedure stops the server processes. This is the first of three procedures
you must perform when you restore a server using VERITAS NetBackup.
Procedure 6-6
Step
Action
Log onto the server you are restoring to, using the nortel user ID.

3
Enter:
su - root
If you are working on the primary main server enter:

Note: l is a lower case L, not an upper case i.


5
411-8111-521
Preliminary
End of procedure.
06.10
June 2005
database 6-17

This procedure restores the /opt/nortel/data/backup/parsed_brd directory.
There are configuration files in the /opt/nortel/data/backup/parsed_brd
directory which control how a restore is performed. This procedure is the
second of three procedures you must perform when you restore a server using
VERITAS NetBackup.
Requirements
You must perform this procedure after you perform Procedure 6-6.
Procedure 6-7
Step
Action
Log on to the NetBackup Administration window on the VERITAS

NetBackup Master Server. If you are not logged in locally, set the
DISPLAY environment variable to point to the workstation X display server
and then enter:
Start the Backup, Archive, and Restore utility.
Use the following values in the Backup, Archive, and Restore window:
Policy type: Standard (this is the default value)
Click the use Backup History to set date range icon. (Its the icon
on the far right; hover the cursor over the icon to show its name.) The
Date Range dialog will pop up. Select the Unix policy of the desired
backup date and click OK.
In the Browse directory: field, type /opt/nortel/data/backup/

BRTools/br/parsed_brd and press the Enter key.
Select the check box for the parsed_brd directory

sheet 1 of 2
UMTS, GPRS, GSM
OAM 4.2
database
Step
Action
Select the Restore everything to its original location check box
Select the Overwrite existing files check box
Launch the Activity Monitor from the Global Data Manager window and
monitor the status of the restore job.
10

Non-zero Status
11
If you receive a Status that is not zero, open a terminal window on the
server that is being restored. If you are not already the root user, on that
server, become the root user (enter su - ).
12
Enter:
13
Investigate the problem that caused the non-zero Status for the restore
job. After you have resolved the problem, attempt the restore again:

of this procedure
Otherwise, start from step 2 of this procedure.
14
Keep the NetBackup Administration window open because you will use it
in Procedure 6-8.
15
End of procedure.
sheet 2 of 2
411-8111-521
Preliminary
06.10
June 2005
database 6-19

This procedure restores the data from a selected backup created in VERITAS
NetBackup. This procedure is the third of three procedures you must perform
when you restore a server using VERITAS NetBackup.
This procedure restores the:
backup and restore data files
UNIX files
Oracle database (if applicable for the server)
Requirements
This procedure must be performed after Procedure 6-7.
Procedure 6-8
Step
Action
Restoring the data

1

preVeritasRestore
Note: If you want to cancel the restore operation after you have executed
the preVeritasRestore command, you must enter the command
postVeritasRestore_noArcPolicy ABORT to cancel the restore and then
start from step 3 in Procedure 6-7 again.
2
Go to the NetBackup Administration session you started in Procedure 67.
Restore the data, using the values as shown in the following steps.
Range dialog will pop up. Select the UNIX policy (and USER policy if
any) that you specified in Procedure 6-7 step 4. You have to select the
USER policy to restore the MyCom Oracle database on a
Performance server or the HFB Oracle Database on a Primary Main
Server.
In the Directory Structure column, select the check box for /. This
will select all paths (they all start with /).

sheet 1 of 3
UMTS, GPRS, GSM
OAM 4.2
database
Step
Action
Select the Restore everything to its original location check box.
Select the Overwrite existing files check box.

If you receive a Status of 1, refer to Centralized Data Restore in

Appendix C: Troubleshooting. If you received the Status of 1 because of
the ACL settings in /opt/nortel/data/srs, go to step 12. Otherwise (that is,
for any non-zero Status), open a terminal window on the server that is
being restored. If you are not already the root user, on that server,
become the root user (enter su - ).
10
Enter:
11
12
problem that caused the non-zero Status for the restore job. After you
have resolved the problem, attempt the restore again:

of Procedure 6-7.
Otherwise, start from step 2 of Procedure 6-7.

postVeritasRestore
Note: If a system restore was performed immediately prior to this

centralized data restore, the mirror disks will be attached and the root
partition will be synchronized at this point. Wait for the operation to
complete and for the command prompt to reappear.
13
Look at the log file in /opt/nortel/logs/backup/centralBackupRestore.log to

make sure the restore ran successfully.
sheet 2 of 3
411-8111-521
Preliminary
06.10
June 2005
database 6-21
Step
Action

14

init 6

15
16

17

a. Make sure that all applications are up and running.
b.
18
Enter:
postDataRestore
If you are working on the Main Server, this command rebuilds the
JavaHelp if it is corrupt. If you are working on any other server, this
command deletes and cleans up temporary files used during the restore
process.
19
End of procedure.
sheet 3 of 3
UMTS, GPRS, GSM
OAM 4.2
database
411-8111-521
Preliminary
06.10
June 2005
A-1
Nortel Confidential
Appendix A: Additional processes and

information
A
This appendix contains:
general procedures that you can use at any time with any type of backup
or restore
Finding out the type of data on a tape on page A-2
Finding out the contents of a configuration data backup tape on
page A-3
Finding out the contents of an historical data archive tape on page
A-4
information about backup and restore of the RNC directory on the Main
Server
RNC data backup from the main server on page A-4
RNC data restore to the main server on page A-5
UMTS, GPRS, GSM
OAM 4.2
A-2 Appendix A: Additional processes and information

Nortel Confidential
Finding out the type of data on a tape
Perform this procedure to find what kind of data is on a backup tape. The
command recognizes only the three types of backup tapes that are supported
in the PWI backup system: system, configuration data, and data archival.
Procedure A-1
Finding out the type of data on a tape
Step
Action
Log on to the server you are backing up, using the root user.
Enter:
brtapeinfo [-t <tape name>]
where <tape name> is the name of the tape device. If the -t option is
not specified, the command assumes that the tape drive is /dev/
rmt/0n.
A message with the following information appears:

Type of Backup
Creation Date
PWI OAM Version
Server Name
Server IP
Server Role
Date Range (for an archive tape only)
Application list (for archive tape only)
If the system does not recognize the data on the tape, the following
message appears:
un-known type of tape
4
411-8111-521
Preliminary
End of procedure.
06.10
June 2005
Appendix A: Additional processes and information A-3

Nortel Confidential
Finding out the contents of a configuration data backup tape
Perform this procedure to find the contents of a tape that contains

configuration data. Do not use this procedure on a tape that contains historical
data or system data.
Requirements
Before performing this procedure, you must have a tape that contains a
configuration data backup.
Procedure A-2
Finding out the contents of a configuration data tape
Step
Action
Insert a tape into the tape drive of the server. Make sure the tape has
been rewound to the beginning.
Enter either of the following commands:

a. localrestore -i [-t <tape name>]
where -t <tape name> specifies the tape device to read from. If the -t
option is not used, the command will read from tape device /
dev/rmt/0n.
The names of the files on the tape display.

b. localrestore -l [-t <tape name>]
The label of the tape is displayed. l is a lower-case L, not an upper-case i.

4
End of procedure.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Finding out the contents of an historical data archive tape
Perform this procedure to find the contents of a tape that contains historical
data. Do not use this procedure on a tape that contains configuration data or
system data.
Requirements
Before performing this procedure, you must have a tape that contains an
historical data archive.
Procedure A-3
Finding out the contents of an archive tape
Step
Action
Insert a tape into the tape drive of the server. Make sure the tape has
been rewound to the beginning.
Enter:
localretrieve -i
The names of the files on the tape are displayed.

4
End of procedure.
RNC data backup from the main server
The Interface Node (I-Node) and the Access Node (A-Node) components of
the Univity Radio Network Controller (RNC) are included in the OAM data
backup. The backup data is stored in the /opt/nortel/data/backup/passport/
auto/RNC directory on the Main Server. Subpaths for individual nodes and
views may exist within this directory; the final directory in each path is
named according to the following convention:
<timestamp>.<dataset>.<datafiles>
where the fields are as follows:
<timestamp> this is the time in yyyymmddhhmmss format
411-8111-521
<dataset> this is Passport view file name
<datafiles> this is the name or names of files that are backed up
Preliminary
06.10
June 2005
Nortel Confidential
Appendix A: Additional processes and information A-5

RNC data restore to the main server
Performing a restore of the primary main server restores the previously

mentioned data to the main server. You must then manually restore the
Passport views to the appropriate network elements. For more information
about restoring Passport network elements, see the Preside MDM Network
Backup and Restore User Guide, 241-6001-807.
For more information about the RNC, see About the Nortel UMTS RNC 1000,
411-8111-906.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
411-8111-521
Preliminary
06.10
June 2005
B-1
Nortel Confidential
This appendix lists the directories and files that are backed up for a system
data backup, configuration data backup, and historical data archive.
System data backup on page B-1
Configuration data backup on page B-4
Historical data archive on page B-16
System data backup

The following tables show the files, directories, and databases that are backed
up for each server for a system data backup.
Table B-1
Primary Main Server
file systems and directories backed up
EEPROM variables
Solaris Volume Manager Configurations
File systems
/
/usr
/var
/home
/opt
/opt/nortel (excluding /opt/nortel/logs)
Directories
/opt/nortel/logs/3rd_party
/opt/nortel/logs/iut_tools/*.log*
UMTS, GPRS, GSM
OAM 4.2
B-2 Appendix B: Data backed up

Nortel Confidential
Table B-2
Secondary Main Server
EEPROM variables
File systems
/
/usr
/var
/home
/opt
Directories
/opt/nortel/logs/3rd_party
/opt/nortel/logs/iut_tools/*.log*
Table B-3
Performance Server
EEPROM variables
File systems
/
/usr
/var
/home
/opt
411-8111-521
Preliminary
06.10
June 2005
Appendix B: Data backed up B-3

Nortel Confidential
Table B-4
SRS
EEPROM variables
File systems
/
/usr
/var
/home
/opt
Table B-5
SOC server
EEPROM variables
File systems
/
/usr
/var
/home
/opt
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Configuration data backup

The following tables show the files, directories, and databases that are backed
up for each server for a configuration data backup.
Table B-6
Primary Main Server
component
data backed up
NSP
Files
/etc/inittab
/etc/passwd
/etc/vfstab
/etc/nsswitch.conf
/etc/shadow
/etc/group
/etc/hosts
/etc/hosts.equiv
/etc/inet/hosts
/etc/inet/inetd.conf
/etc/.osc060005
Directories
/var/spool/cron/crontabs
/etc/mail
/opt/nortel/config/3rd_party
/opt/nortel/data/PresideNSP/apache
/opt/nortel/config/PresideNSP
/opt/nortel/data/PresideNSP/CustomCommands
/opt/nortel/config/applications/csal
/opt/nortel/data/3rd_party
excluding
/opt/nortel/data/3rd_party/java/jboss/db/jbossmq
/opt/nortel/data/3rd_party/netscape
Versant database
/opt/nortel/data/PresideNSP/topology/tums*
/opt/nortel/data/PresideNSP/summary/SUMBB*
/opt/nortel/data/PresideNSP/applicationlaunch/ALBB*
/opt/nortel/data/PresideNSP/fmbb/FMBB*
NDS database
nds
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Table B-6
Primary Main Server
component
data backed up
TTBB
Files
/etc/mail/sendmail.cf
/etc/mail/aliases
Directories
/opt/nortel/data/applications/tti/outMail
/opt/nortel/data/applications/tti/email
/opt/nortel/config/applications/tti
Versant database
/opt/nortel/data/applications/tti/TTBB
CEM
Directories
/opt/nortel/data/coreEMS/configBackup
Core DA
Files
/opt/MagellanMOA/cfg/Mdr/deviceTypes
/opt/nortel/data/users/nortel/coreDA/GEM18.0/coreDANodes.cfg
/opt/nortel/data/users/nortel/coreDA/GEM18.0/neStore.txt
/opt/nortel/data/users/nortel/coreDA/GEM18.0/mdmlogfilters.txt
HFB
Files
/opt/u01/app/oracle/products/9.2.0/network/admin/tnsnames.ora
/opt/u01/app/oracle/products/9.2.0/network/admin/listener.ora
/opt/u01/app/oracle/products/9.2.0/dbs/inithfb.ora
/opt/u01/app/oracle/products/9.2.0/dbs/confighfb.ora
/opt/u[0-9]*
/var/opt/oracle/oratab
/opt/nortel/data/applications/hfb_archive/Criteria.dmp
Directories
/opt/nortel/config/applications/hfb
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table B-6
Primary Main Server
component
data backed up
MDM and IDI
Files
/etc/opt/Magellan/LIClicenses.cfg
/etc/opt/Magellan/LICcustName.cfg
Directories
/opt/MagellanNMS/cfg
/opt/MagellanNMS/cfg/ANP/EM/Service
/opt/MagellanNMS/data
/opt/MagellanNMS/ext/lib/cfg/opt/Nortel/EPIC/cfg
/opt/netRx2/commands
/opt/netRx2/customer
/opt/netRx2/nodes
excluding
/opt/MagellanNMS/cfg/PassportSchema
/opt/MagellanNMS/cfg/ANP/comp
/opt/MagellanNMS/cfg/ANP/EM
/opt/MagellanNMS/data/nrs/rdf/dpn
/opt/MagellanNMS/data/rtac/data
3GPP
Directories
/opt/nortel/config/3gpp
/opt/nortel/data/3gpp
excluding
/opt/nortel/data/3gpp/3g_MOI_Mapping.dat.bak
/opt/nortel/data/3gpp/.br_flag
/opt/nortel/data/3gpp/bulk_temp_data
/opt/nortel/data/3gpp/upload
/opt/nortel/data/3gpp/download
/opt/nortel/data/3gpp/pm_data
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Table B-6
Primary Main Server
component
data backed up
Access EMS
Files
/opt/nortel/data/wicl/poc.cfg
Directories
/opt/nortel/config/access
/opt/nortel/data/access/rmd_conf
see also RNC data backup from the main server in Appendix A: Additional
processes and information
Versant database
/opt/nortel/data/versant/access/umtsdb
System Management
Directories
/opt/nortel/config/sysmgt
/var/opt/SUNWsymon/bin
/var/opt/SUNWsymon/cfg
excluding
/opt/nortel/config/sysmgt/am
SRS
Files
/opt/nortel/config/srm/Srm.cfg
Directories
/opt/nortel/data/srs
excluding
/opt/nortel/data/srs/tmp
Backup and Restore
Directories
/opt/nortel/config/backup
/opt/nortel/data/backup/BRTools/br/backup_data/config
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table B-6
Primary Main Server
component
data backed up
Common Services
Files
/opt/nortel/data/wicl/cli_jobScheduler.dat
Directories
/opt/nortel/config/fmk
/opt/nortel/config/wicl
/opt/nortel/3rd_party/apache/current_tomcat/webapps/wicl/wiclets/user
/opt/nortel/config/stability
/opt/nortel/data/wicl/user
Audit Trail
Files
/opt/nortel/config/AuditTrail/auditTrailConfigData
/opt/nortel/config/AuditTrail/csal.properties
WINSUP Tools
Files
/opt/nortel/config/common/.product_list.cfg
/opt/nortel/config/common/product_list.xml
/opt/nortel/config/iut_tools/roc/iut_rocconfig.cfg
/opt/nortel/config/iut_tools/module/required_version.cfg
/opt/nortel/config/iut_tools/roc/iut_rocconfig.xml
Device Inventory
Files
/opt/nortel/config/deviceinv/.key
/opt/nortel/config/deviceinv/.login
PAM
Directories
/opt/nortel/config/pam/user
/opt/nortel/config/pam/schedule
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Table B-7
Secondary main server
component
data backed up
NSP
Files
/etc/inittab
/etc/passwd
/etc/vfstab
/etc/nsswitch.conf
/etc/shadow
/etc/group
/etc/hosts
/etc/hosts.equiv
/etc/inet/hosts
/etc/inet/inetd.conf
Directories
/var/spool/cron/crontabs
/etc/mail
opt/nortel/config/3rd_party
/opt/nortel/data/PresideNSP/apache
opt/nortel/config/PresideNSP
/opt/nortel/data/3rd_party
excluding:
/opt/nortel/data/3rd_party/java/jboss/db/jbossmq
/opt/nortel/data/3rd_party/netscape
Versant database
/opt/nortel/data/PresideNSP/topology/tums*
/opt/nortel/data/PresideNSP/fmbb/FMBB*
TTBB
Files
/etc/mail/sendmail.cf
/etc/mail/aliases
Directories
/opt/nortel/data/applications/tti/outMail
/opt/nortel/data/applications/tti/email
/opt/nortel/config/applications/tti
Versant database
/opt/nortel/data/applications/tti/TTBB
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table B-7
component
data backed up
CEM
Directories
/opt/nortel/data/coreEMS/configBackup
Core DA
Files
/opt/MagellanMOA/cfg/Mdr/deviceTypes
/opt/nortel/data/users/nortel/coreDA/GEM18.0/coreDANodes.cfg
/opt/nortel/data/users/nortel/coreDA/GEM18.0/neStore.txt
/opt/nortel/data/users/nortel/coreDA/GEM18.0/mdmlogfilters.txt
MDM and IDI
Files
Directories
/opt/MagellanNMS/cfg/ANP/EM/Service
/opt/MagellanNMS/ext/lib/cfg
/opt/Nortel/EPIC/cfg
/opt/netRx2/commands
/opt/netRx2/customer
/opt/netRx2/nodes
excluding
Access EMS
Files
/opt/nortel/data/wicl/poc.cfg
Directories
/opt/nortel/data/access/rmd_conf
see also RNC data backup from the main server in Appendix B: Data
backed up
Versant database
/opt/nortel/data/versant/access/umtsdb
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Table B-7
component
data backed up
Backup and Restore
Directories
Common Services
Directories
System Management
Directories
/var/opt/SUNWsymon
excluding
WINSUP Tools
Files
Audit Trail
Files
HFB
Directories
/opt/nortel/config/applications/hfb
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table B-8
Performance server
component
files and directories backed up
Common services
Directories
System
Management
Directories
/var/opt/SUNWsymon
excluding
PDI
Files
/opt/nortel/config/packet/pdi/pdi.cfg
GDI
Directories
/opt/nortel/config/packet/gdi
MDP
Files
Directories
/opt/MagellanMDP/cfg/mdp
/opt/MagellanMDP/cfg/mdp/pp/rdf
excluding
/opt/MagellanMDP/cfg/mdp/pp
CDI
Files
/opt/nortel/config/circuit/cdi.cfg
sheet 1 of 2
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Table B-8 (continued)
Performance server
component
ADC
Directories
/opt/nortel/config/packet/adc/
SDI
Files
/opt/nortel/config/packet/sdi/sdi.cfg
Backup and Restore
Directories
/etc/hosts
/etc/inet/hosts
MYCOM
Files
/opt/nortel/exe/proptima/lic.cry
Directories
/opt/nortel/data/proptima/users
/opt/nortel/data/proptima/alarm_autogen_report
/opt/nortel/config/proptima
Oracle Database
NIMS
Audit Trail
Files
WINSUP Tools
Files
CEM
Directories
/opt/nortel/data/coreEMS/nodes
sheet 2 of 2
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table B-9
SRS server
component
System
Management
Directories
/var/opt/SUNWsymon
excluding
Backup and Restore
Directories
SRS
Files
/opt/nortel/config/srm/Srm.cfg
Directories
/opt/nortel/data/srs
excluding
/opt/nortel/data/srs/tmp
Audit Trail
Files
WINSUP Tools
Files
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
Table B-10
SOC server
component
System
Management
Directories
/var/opt/SUNWsymon
excluding
SOC
Files
/opt/nortel/data/iut_tools/network_updater/MetaFrame.dat
/var/CTXSmf/ctxconfdb.HKLM.dir
/var/CTXSmf/ctxconfdb.HKLM.pag
Backup and Restore
Directories
Audit Trail
Files
WINSUP Tools
Files
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Historical data archive

When you perform an historical data archive or retrieval, the archive data
associated with a particular application component is identified by a module
name. Table B-11 shows the module names for the components on the OAM
servers. This information applies only to historical data archive and retrieval.
See Chapter 5, Performing centralized backup and restore with an archive
policy for more information.
Table B-11
Module Names
Server
Application Components
Module Name for archive

and retrieval
primary main
HFB
hfb
CSAL
csal
Audit Trail
audittr
Stability Data Analyzer
ne_sda, oam_sda
Audit Trail
audittr
Stability Data Analyzer
ne_sda, oam_sda
MYCOM
mycom
PDI
pdi
GDI
gdi
SDI
sdi
CDI
cdi
ADI
adi
all DIs (PDI, GDI, SDI, CDI

and ADI)
xdi
Audit Trail
audittr
3GPP XML Writer
3gwriter
SRS
Audit Trail
audittr
SOC
Audit Trail
audittr
secondary main
performance
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
The specific files backed up for each module are listed in the following
sections.
hfb module
HFB Oracle tables are partitioned by days; users can specify specific day(s)
they want to archive and the appropriate data is exported into the following
directory:
/opt/nortel/data/applications/hfb_archive
The exported file takes the form of:
PT<yyyymmdd>.dmp
where <yyyymmdd> is the date. For example, PT20040801 represents the
partition on the date August 1/2004. The format of the "dmp" files are Oracle
specific and can be used to restore the data at that date partition. The "dmp"
files come from the Oracle data tables/indices found under directories
/opt/u[0-11]
csal module
CSAL (Centralized Secure Audit Logs) is responsible for logging system
activity in order to identify occurrences of hacking or improper activity on a
system. CSAL writes its log data to the following file:
/opt/nortel/data/applications/csal/CSAL_LOG-<yyyymmdd>.log
where <yyyymmdd> is the date. For example, CSAL_LOG-20040827.log
contains the logs for Aug 27/2004. The file is flat meaning it contains
readable text. After each day the CSAL application compresses the log file
into:
/opt/nortel/data/applications/csal/CSAL_LOG-<yyyymmdd>.log.gz
audittr module
The Audit Trail archival directory contains the security-related logs for the
local server. The data is produced and written by Sun Basic Security Module
(BSM). BSM is responsible for the monitoring of the server and captures the
activities monitored in the security logs. The Audit Trail archival data is
located in the following directories:
/opt/nortel/data/audit/archive/dated<yyyymmdd>
where <yyyymmdd> is the date.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
ne_sda module
The ne_sda data contains information about network element stability data:
notification, initial state (snapshot), state change, alarms, and configuration
information for some core networks elements that can be used to compute
stability reports.
The notifications, the initial state and state changes are extracted from a
database in the Access Network element manager without processing. The
alarms are retrieved from the HFB databases without processing. The
configuration information is retrieved from the daily cmXML export of the
core network; the processing of this file just extracts the required information.
The NE_SDA archival data is located in the following files:
/opt/nortel/data/stability/access/ntf_<yyyymmdd>.*.dat
/opt/nortel/data/stability/access/stc_<yyyymmdd>.*.dat
/opt/nortel/data/stability/access/snap_<yyyymmdd>.dat
/opt/nortel/data/stability/access/hfb_<yyyymmdd>.*.dat
/opt/nortel/data/stability/core/hfb_<yyyymmdd>.*.dat
/opt/nortel/data/stability/core/cfg_%Y%M%D.dat
oam_sda module
The oam_sda contains the user commands: which user has logged into the
system, which command was run by which user. This information is extracted
from OAM Access log files. It also contains information related to the OAM
SUN servers that is retrieved through SMC.
The OAM_SDA archival data is located in the following files:
/opt/nortel/data/stability/access/usc_<yyyymmdd>.*.dat
mycom module
The MYCOM archival data contains the flat files (counters and attributes
values). It contains the processed data from the raw data (observation files
(xml files) and configuration files (drf, xDRF) that is imported into NIMSPrOptima for the specified date. The flat files are taken from /opt/nortel/data/
proptima/flatfiles directory and can be split when a flat file contains several
days of processed data.
In the /opt/nortel/data/proptima/flatfiles directory we have a list of directory
which correspond to the set <NeType-Vendor-Granularity> (for example:
RNC-Nortel-Hour). In those directories we have some files which correspond
to a period imported. (one or two days).
411-8111-521
Preliminary
06.10
June 2005

Nortel Confidential
The MYCOM archival data is located in the following directories:

/opt/nortel/data/proptima/ArchiverRepository/<yyyymmdd>
pdi, gdi, sdi and cdi modules
The PDI, GDI, SDI and CDI archival data contain the XML files that are
processed data from raw data received from the U-SGSN, G-SGSN, Wireless
Gateway (WG), Aggregation Node (AN), Passport backbone, MSC, HLR,
Trinode, HLR200, SLR, HP-SIG, and Shasta. The raw data received from USGSN, G-SGSN, Wireless Gateway (WG), Aggregation Node (AN), and
Passport backbone is in BDF format. The raw data for MSC, HLR, Trinode,
HLR200, SLR is in tab-delimiter format. The raw data for Shasta is in CSV
format. The raw data for SIG is in ASCCII format. The raw data is then
processed by PDI, CDI, GDI, and SDI, respectively to convert it into XML
files.
PDI supports Collected OMs from the U-SGSN, G-SGSN, Wireless Gateway
(WG), Aggregation Node (AN), and Passport backbone. GDI supports gauge
and counter OMs. CDI and SDI support just regular OMs.
The XML files can be compressed or uncompressed depend on the
configuration set by the user in the pm_admin.
The XML files are located in the following archival directories.
/opt/nortel/data/packet/observation/3g-sgsn/<yyyymmdd>
/opt/nortel/data/packet/observation/transmission/<yyyymmdd>
/opt/nortel/data/packet/observation/transmission/<yyyymmdd>
/opt/nortel/data/packet/observation/sig/<yyyymmdd>
/opt/nortel/data/packet/observation/shasta-ggsn/<yyyymmdd>
/opt/nortel/data/circuit/observation/msc/<yyyymmdd>
/opt/nortel/data/circuit/observation/hlr/<yyyymmdd>
/opt/nortel/data/circuit/observation/msc_hlr/<yyyymmdd>
/opt/nortel/data/circuit/observation/slr/<yyyymmdd>
/opt/nortel/data/circuit/observation/mgw/<yyyymmdd>
/opt/nortel/data/packet/sdi/pp/late
/opt/nortel/data/packet/pdi/pp/late
/opt/nortel/data/packet/gdi/shasta-ggsn/pp/late
/opt/nortel/data/circuit/observations/sgw/<yyyymmdd>
/opt/nortel/data/circuit/observations/iwf/<yyyymmdd>
/opt/nortel/data/circuit/observations/unpm/<yyyymmdd>
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
adi module
The archived data includes the performance data generated by the access
network: observation counters and access call trace. The observation counters
handled by the ADI application for OAM04 are:
C-Node application counters
I-Node application counters
I-Node platform counters
NodeB equipment counters
A-Node platform counters (identical list with I-node platform counters)
The archived directories for observation counters are arranged by day per
network element: one directory per day, one sub-directory per network
element, containing all observation counter files for that day.
The Trace data available at the ADI level are originated from the UMTS
Radio network and are aimed to trace the events and measurements occurring
during mobile communications.The archived directories for call trace are
arranged by daily directories for each active trace session.
The ADI archival data are located in the following directories:
/opt/nortel/data/access/observation/<yyyymmdd>/<Network Element>
/opt/nortel/data/access/callTrace/onOAMdemand/<sessionID>/<yyyymmdd>
/opt/nortel/data/access/callTrace/onCoreNetworkdemand/
<sessionID><yyyymmdd>
/opt/nortel/data/access/callTrace/originatedFromGeographicalArea/
<sessionID>/<yyyymmdd>
/opt/nortel/data/access/objectTrace/<Trace Object>/
<sessionID><yyyymmdd>
411-8111-521
Preliminary
06.10
June 2005
C-1
Nortel Confidential
This section contains a number of problems that may occur during a backup
or restore. The section is divided into the following categories:
General on page C-1
System Backup on page C-2
System Restore on page C-2
Local Data Backup on page C-3
Local Data Restore on page C-4
Local Data Archive on page C-5
Local Data Retrieval on page C-6
Centralized Data Backup on page C-9
Centralized Data Restore on page C-11
Centralized Data Archival on page C-12
Centralized Data Retrieval on page C-13
General
Problem: The backup or restore is not able to complete and an error message
is displayed repeatedly on the screen. For example, during a system restore, the
following error message is displayed on the screen:
INFO |Read error while trying to resynchronize
Explanation: The tape was accidentally ejected while a backup or restore

was running. This causes the command to be unable to complete.
Recommended Action:
Enter Ctrl-C (hold down the Ctrl or Control key and press c) to
abort the command. Start over again from the beginning of the procedure.
UMTS, GPRS, GSM
OAM 4.2
C-2 Appendix C: Troubleshooting

Nortel Confidential
System Backup
Problem: The system backup failed with error message containing tape I/O
error.
Explanation: The system backup is not able to write to the tape.
Recommended Action:
Check whether the clean light on the tape drive is blinking. If it is, clean
the tape drive head several times, insert a new tape in the drive and try to
do the system backup again.
Check the log file. If you find error messages that show the problem
results from backing up certain files that the system backup is not able to
handle, contact Nortel support for help.
If the clean light is not blinking and the log file does not report any files
with problems, insert a new tape and try to do the system backup again. If
the problem persists, contact Nortel support for help.
System Restore
Problem: The system restore failed with an error message containing cant
restore <file system> from /dev/rmt...backup failed with error message
containing tape I/O error.
Explanation: The system restore is not able to read from the tape.
Recommended Action:
411-8111-521
the tape drive head several times and try to do the system restore again.
results from restoring certain files that the system restore is not able to
with problems, try to do the system restore one more time. If the problem
persists, contact Nortel support for help.
Preliminary
06.10
June 2005
Appendix C: Troubleshooting C-3

Nortel Confidential
Problem: The new disk does not have the same geometry as the old one.
Explanation: The size of the disk is different from the old one.
Recommended Action:
If the OAM server platform is SF4800, SF4900 or E4500, make sure the
disk arrays are disconnected before the restore. Please type command
format to see a list of disks on the server. You should not see any disk
arrays at this point.
If you have replaced a new disk, make sure the new disk has the same size
as the old one.
Problem: The restore hangs and the message INFO |Read error while
trying to resynchronize appears repeatedly on the terminal.
Explanation: The tape was accidentally removed before completion of the
procedure.
Recommended Action:
Enter Ctrl-C (hold down the Ctrl or Control key and press c) to
abort the restore. Start over again from the beginning of the procedure.
Local Data Backup

Problem: The local backup failed with an error message containing Tape
media error.
Explanation: The local data backup failed to write to tape.
Recommended Action:
do the system backup again.
results from backing up certain files that the system backup is not able to
with problems, insert a new tape and try to do the system backup again. If
the problem persists, contact Nortel support for help.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Problem: The local data backup failed due to an error in the execution of
pre_backup.sh
Explanation: One or more applications pre-backup scripts failed.
Recommended Action:
Use SMC to check that all applications are up and running and in good
state.
Run the local data backup again. If the problem persists, Contact Nortel
support for help.
Local Data Restore

Problem: Local data restore failed with an error message containing Tape
media error.
Explanation: The local data restore failed to read from tape.
Recommended Action:
411-8111-521
the tape drive head several times and try to do the local data restore again.
results from restoring certain files that the local data restore is not able to
with problems, try to do the local data restore one more time. If the
problem persists, contact Nortel support for help.
Preliminary
06.10
June 2005

Nortel Confidential
Local Data Archive

Problem: The local data archive failed with an error message containing
Tape media error.
Explanation: The local data archive failed to write to tape.
Recommended Action:
do the local data archive again.
results from archiving certain files that the data archive is not able to
with problems, insert a new tape and try to do the local data archive again.
If the problem persists, contact Nortel support for help.
Problem: The local data archival failed due to an error in the execution of
ar_pre_archive.sh
Explanation: One or more applications pre-archive scripts failed.
Recommended Action:
state.
Run the localarchive again. If the problem persists, Contact Nortel

support for help.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Local Data Retrieval

Problem: Local data retrieval failed with an error message containing Tape
media error.
Explanation: The local data retrieval failed to read from tape.
Recommended Action:
the tape drive head several times and try to do the local data restore again.
results from retrieving certain files that the local data retrieval is not able
to handle, contact Nortel support for help.
with problems, try to do the local data retrieval one more time. If the
problem persists, contact Nortel support for help.
Problem: The local data retrieval failed due to the error in the execution
ar_pre_retrieve.sh or ar_post_retrieve.sh
Explanation: One or more applications pre-retrieve or post-retrieve scripts
failed.
state.
Run the local retrieve again. If the problem persists, Contact Nortel
support for help.
Problem: The local data retrieval failed with the error message return from
/opt/nortel/shell/sysmgt/wam_enough_space.sh is 1.
Explanation: The existing data plus the data to be retrieved exceeds the
limit of the disk space allowed for the application(s).
Recommended Action:
411-8111-521
Use option -D together with option -a to retrieve only one day and one
applications data at a time.
Create more space. If, when you retrieve one applications data for one
day, you still get the same error message, you may manually remove
historical data from the server to create more space. Table C-1 lists
application data files which can be manually removed
Preliminary
06.10
June 2005

Nortel Confidential
.
CAUTION
Permanent data loss
Do not remove the current data files that the applications are
writing to. Check the time stamps of the files before removing
the files and avoid files with time stamps of the current or
previous day. If possible, remove the oldest files first.
Table C-1
Application data files
Modules
Files
Notes
ne_sda or
oam_sda
/opt/nortel/data/stability/access/usr_%Y%M%D.*.dat
/opt/nortel/data/stability/access/ntf_%Y%M%D.*.dat
/opt/nortel/data/stability/access/stc_%Y%M%D.*.dat
/opt/nortel/data/stability/access/hfb_%Y%M%D.*.dat
/opt/nortel/data/stability/core/hfb_%Y%M%D.*.dat
/opt/nortel/data/stability/sysmgt/oamStabData*.tar
Files older than 7

days can be
removed.
audittr
/opt/nortel/data/archive/dated*/*.*
/opt/nortel/data/archive/dated*
/opt/nortel/data/archive/secondary/*.*
/var/audit/primary/*.*
csal
/opt/nortel/data/applications/csal/*.log.gz
mycom
/opt/nortel/data/proptima/dataimport/read_files/*
/opt/nortel/data/proptima/dataimport/processed_ne/*
cdi or xdi
/opt/nortel/logs/circuit/traces/*
/opt/nortel/data/circuit/collection/successful/*
/opt/nortel/data/circuit/collection/failedfiles/*
/opt/nortel/data/circuit/pp/late/*
/opt/nortel/data/circuit/observation/msc/*
/opt/nortel/data/circuit/observation/hlr/*
/opt/nortel/data/circuit/observation/msc_hlr/*
/opt/nortel/data/circuit/observation/slr/*
/opt/nortel/data/circuit/observation/mgw/*
sheet 1 of 2
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Table C-1
Application data files
Modules
Files
Notes
pdi, sdi,
gdi or xdi
/opt/nortel/logs/packet/pdi/trace/*
/opt/nortel/data/packet/pdi/collection/successful/*
/opt/nortel/data/packet/pdi/collection/failedfiles/*
/opt/nortel/data/packet/pdi/pp/late/*
/opt/nortel/data/packet/observation/2g-sgsn/*
/opt/nortel/data/packet/observation/3g-sgsn/*
/opt/nortel/data/packet/observation/transmission/*
/opt/nortel/data/packet/observation/*g-sgsn
/opt/nortel/logs/packet/sdi/traces/*
/opt/nortel/data/packet/sdi/collection/successful/*
/opt/nortel/data/packet/sdi/collection/failedfiles/*
/opt/nortel/data/packet/sdi/pp/late/*
/opt/nortel/data/packet/observation/sig/*
/opt/nortel/logs/packet/gdi/traces/*
/opt/nortel/data/packet/gdi/shasta-ggsn/conversion/successful/*
/opt/nortel/data/packet/gdi/shasta-ggsn/conversion/failedfiles/*
/opt/nortel/data/packet/gdi/shasta-ggsn/pp/late/*
/opt/nortel/data/packet/observation/shasta-ggsn/*
adi
/opt/nortel/data/inventory/*
/opt/nortel/data/access/tmp/*
/opt/nortel/data/access/stability/*
/opt/nortel/data/intmdm/cas/*
/opt/nortel/data/intmdm/error/*
/opt/nortel/data/intmdm/tmp/*
/opt/nortel/data/intxdrf/tmp/*
/opt/nortel/data/cmXml/scheduledExport/*
/opt/nortel/data/access/observation/*/*
/opt/nortel/data/access/callTrace/*/*
/opt/nortel/data/access/objectTrace/*/*
/opt/nortel/data/*/dfstmp/*
sheet 2 of 2
411-8111-521
If, after attempting to create more space by manually removing historical

data files and retrieving data for only one day for one application at a
time, you still cannot retrieve the data, contact Nortel for assistance.
Preliminary
06.10
June 2005

Nortel Confidential
Centralized Data Backup

Problem: The VERITAS NetBackup server timed out connecting to client
Explanation: The VERITAS NetBackup server cannot make connection to
the OAM servers due to missing host information
Recommended Action:
On the VERITAS NetBackup server, check that /etc/hosts contains an

entry for the OAM servers hostname. If it does not, add a new entry for
the OAM servers host name.
On the OAM server, check that /etc/hosts contains an entry for the
VERITAS NetBackup servers hostname. If it does not, add a new entry
for the VERITAS NetBackup servers hostname.
On the OAM server, check that /usr/openv/netbackup/bp.conf has correct

entries for SERVER, CLIENT_NAME and REQUIRED_INTERFACE.
Problem: client timed out waiting for bpstart_notify to complete

Explanation: The VERITAS NetBackup server does not allow client
enough time to finish its bpstart_notify script.
Recommended Action:
On the VERITAS NetBackup server, add two entries,

BPSTART_TIMEOUT and CLIENT_READ_TIMEOUT, in /usr/openv/
netbackup/bp.conf and set their values to 3600.
If you have already set the same values to above two entries, contact
Nortel support for help.
Problem: The UNIX class backup succeeded but the Oracle class backup
failed.
Explanation: The NetBackup Oracle agent is not installed or the Oracle
class may not be configured correctly.
Recommended Action:
On the OAM server, check that /opt/nortel/3rd_party/oracle/app/oracle/

products/9.2.0/lib/libobk.so has a symbolic link to /usr/openv/netbackup/
bin/libobk.so.1. If this symbolic link does not exist, the NetBackup Oracle
agent is not installed and configured. Manually run /opt/nortel/shell/
backup/veritas/configAgent.sh and select 3 to install and configure the
NetBackup Oracle agent.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
On the VERITAS NetBackup server, check the following items for the
Oracle class configuration.
the policy type is Oracle.
there are two schedules configured --- one of type Application
Backup and the other of type Automatic Full Backup. Make sure
these two schedules have the same retention value. For the schedule of
Automatic Full Backup, Nortel recommends that you set the
frequency and retention to the same values as those in the schedule for
UNIX class.
Under the files attribute, the script to execute the Oracle backup is /
opt/nortel/shell/backup/veritas/veritasBpOracle.sh.
Problem: no storage unit or media available

Explanation: The VERITAS NetBackup server cannot allocate a new tape
to store the backup data.
Recommended Action:
On the Veritas NetBackup server, check that the frequency and retention
of the backup class are the same as the others in the same volume pool.
On the Veritas NetBackup server, either add more new tapes to this
volume pool or re-set the tape drive from the Device Monitor GUI to
overwrite existing tapes.
Problem: UNIX backup class failed due to a previous UNIX class running.
Explanation: The previous UNIX class backup operation was not properly
terminated, causing the next backup operation fails to start.
Recommended Action:
On the Veritas NetBackup server, if there are still any running backup
operations associated with the UNIX class, cancel them.
On the OAM server, do the following command to remove the temporary

files.
# rm
411-8111-521
Preliminary
-f
06.10
/opt/nortel/data/backup/BRTools/br/temp/*
June 2005

Nortel Confidential
Problem: The centralized data backup failed due to an error in the execution
of pre_backup.sh
Explanation: One or more applications pre-backup scripts failed.
Recommended Action:
Use SMC to check that all applications are up and running and in a
trouble-free state.
Attempt the centralized data backup again. If the problem persists,

Contact Nortel support for help.
Centralized Data Restore

Problem: When I restored the data from VERITAS NetBackup server to the
OAM server, I got a return code 1.
Explanation: Some files are partially restored.
Recommended Action:
A known issue is that the VERITAS NetBackup cannot restore the ACL
attributes to files in /opt/nortel/data/srs. If the partially restored files are in
this directory, the postVeritasRestore script will take care of this issue and
restore the ACL attributes to their original.
If partially restored files are not in /opt/nortel/data/srs, please refer to

VERITAS NetBackup Troubleshooting Guide for UNIX and check the
recommended actions for Status Code: 1.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
Centralized Data Archival

Problem: When the centralized data archival is complete, the job of the
archive schedule (Archive type) was not created on the Activity Monitor GUI.
Explanation: The archive schedule of Archive type for archival policy is not
configured.
Recommended Action:
Please check the archival policy. Make sure there are two schedules
configured; one is type of Full Backup, and the other User Archive.
Problem: The centralized data archive failed due to an error in the execution
of ar_pre_archive.sh
Explanation: One or more applications pre-archive scripts failed.
Recommended Action:
Check via SMC that all applications are up running and in good state.
Attempt the centralized data archive again. If the problem persists,

Problem: client timed out waiting for bpstart_notify to complete

Explanation: The VERITAS NetBackup server does not allow client
enough time to finish its bpstart_notify script.
Recommended Action:
411-8111-521
On the VERITAS NetBackup server, add two entries,

BPSTART_TIMEOUT and CLIENT_READ_TIMEOUT, in /usr/openv/
netbackup/bp.conf and set their values to 14400. Monitor the next archive
operation to ensure the time is adequate. It is possible, in rare cases, that
the time will need to be increased further to accommodate large amounts
of historical data.
Preliminary
06.10
June 2005

Nortel Confidential
Centralized Data Retrieval

Problem: When I perform a centralized data retrieval, I do not find any
image with restore type of Archived Backups.
Explanation: The archive schedule of Archive type for archival policy is not
configured. Therefore, there has not been data archived by the VERITAS
NetBackup server.
Recommended Action:
Check the archive policy. Make sure there are two schedules configured;
one is type of Full Backup, and the other User Archive.
Problem: The centralized data retrieval failed due to an error in the

execution of ar_pre_retrieve.sh or ar_post_retrieve.sh
Explanation: One or more applications pre-retrieve or post-retrieve scripts
failed.
Recommended Action:
Use SMC to check that all applications are up and running and in a
trouble-free state.
Attempt the centralized data retrieval again. If the problem persists,

Problem: The centralized data retrieval fails with the error message return
from /opt/nortel/shell/sysmgt/wam_enough_space.sh is 1.
Explanation: The existing data plus the data to be retrieved exceed the limit
of the disk space allowed for the application(s).
Recommended Action:
Transfer only one applications for one data from the VERITAS
NetBackup server to the OAM server at a time. Run the command
centralretrieve after each transfer to retrieve one applications data for
one day.
Create more space. If, when you transfer and retrieve one applications
data for one day, you still get the same error message, you may manually
remove historical data from the server to create more space. Table C-1
lists application data files which can be manually removed.
UMTS, GPRS, GSM
OAM 4.2

Nortel Confidential
CAUTION
Permanent data loss
Do not remove the current data files that the applications are
writing to. Check the time stamps of the files before removing
the files and avoid files with time stamps of the current or
previous day. If possible, remove the oldest files first.
411-8111-521
If, after attempting to create more space by manually removing historical

data files and transferring and retrieving data for only one day for one
application at a time, you still cannot retrieve the data, contact Nortel for
assistance.
Preliminary
06.10
June 2005
D-1
Nortel Confidential
Appendix D: Technical note - alternative

policies
D
Chapter 5, Performing centralized backup and restore with an archive
policy and Chapter 6, Performing centralized backup and restore with no
archive policyRMAN used for HFB Oracle database describe the creation
of two very similar sets of backup policies for Centralized Backup and
Restore. However, VERITAS NetBackup can be configured to provide
centralized backup and restore in a number of different ways.
NOTICE
Because of the very large number of ways in which VERITAS
NetBackup can be used, Nortel has chosen to support only the approach
used in Chapter 5 and Chapter 6; though alternative approaches are
technically feasible given the capabilities of VERITAS NetBackup,
Nortel Global Product Support will be familiar with only the approach
described in Chapter 5 and Chapter 6 and cannot support any alternative
approach the customer may choose to implement unless previously
agreed to by Nortel.
UMTS, GPRS, GSM
OAM 4.2
D-2 Appendix D: Technical note - alternative policies

Nortel Confidential
The procedures in Chapter 5 and Chapter 6 both keep the detailed list of files
to back up on the VERITAS NetBackup server. However, an alternative set of
policies can keep the files list on the OAM servers themselves. You would do
this by creating VERITAS NetBackup exclude and include lists for the
UNIX files on the server and then configuring the matching policies
VERITAS NetBackup server.
For example, suppose you have a ROC with Centralized Backup and Restore
of HFB Oracle Database using RMAN activated on it. To configure exclude
and include lists, you would do the following:
1. Look in /opt/nortel/data/backup/BRTools/veritas/client for the following
files:
backup_UNIX
backup_ORACLE
backup_USER
and note which ones exist on the server.
2. Create a UNIX policy-specific exclude list that excludes everything on
the server by creating a file named exclude_list.<UNIX_policy_name> in
the directory /usr/openv/netbackup/ that contains only one character: *:
echo * > /usr/openv/netbackup/exclude_list.<UNIX_policy_name>
where <UNIX_policy_name> is the policy name that either exists or will

be created to backup the UNIX files.)
3. Create a UNIX policy-specific include list by copying the path list file
(backup_UNIX) generated by ubvaClient to a file named
include_list.<UNIX_policy_name> in the directory /usr/openv/
netbackup/:
cp /opt/nortel/data/backup/BRTools/veritas/client/backup_UNIX \
/usr/openv/netbackup/include_list.<UNIX_policy_name>
Note: Nortel recommends that you now perform a system backup to

backup the configuration parameters you set and any client software you
may have installed.
411-8111-521
Preliminary
06.10
June 2005
Appendix D: Technical note - alternative policies D-3

Nortel Confidential
See Table D-1 for additional information. On the NetBackup server you would
then:
1. Create or edit a policy named <UNIX_policy_name>, where
<UNIX_policy_name> is the name of the policy to backup the UNIX files
on all servers.
2. Delete all backup paths from the Files list of policy
<UNIX_policy_name>.
3. Add the entry ALL_LOCAL_DRIVES to the Files list of policy
<UNIX_policy_name>
4. Add the host name of each server for which ubvaClient created a
backup_UNIX file to the Client list in the policy.
5. Create or edit a policy to backup the HFB and NIMS-PrOptima Oracle
databases on all relevant servers and add the host name of each server for
which ubvaClient created a backup_ORACLE file to the Client list in the
policy.
6. Create or edit a policy to backup the Oracle control files on all relevant
servers and add the host name of each server for which ubvaClient created
a backup_USER file to the Client list in the policy.
7. If you are reducing the number of policies for a system that already had
Centralized Backup and Restore policies configured, you can now delete
the superfluous policies.
8. From the Configure menu of the Global Data Manager window, select
NetBackup System Configuration and change the Maximum jobs per
client to 99 as per VERITAS recommendations - see VERITAS
NetBackup 5.1 for Oracle System Administrators Guide for Unix, p/n
N12320B. Note that you may set this value on a per-client basis using the
bpclient command. The syntax is
/usr/open/netbackup/bin/admincmd/bpclient -client <client_hostname> \
-add -max_jobs 99
where <client_hostname> is the host name of the server that you are
backing up.
9. Configuration of centralized backup and restore is complete. You may now
perform regular backup operations.
UMTS, GPRS, GSM
OAM 4.2
D-4 Appendix D: Technical note - alternative policies

Nortel Confidential
Table D-1
Parameter
Policy
UNIX files
Oracle database
Policy type
Standard
Oracle
Standard
Client List
If ubvaClient created a
backup_UNIX file on this
server, add the servers host
namea to the client list
backup_ORACLE file on this
server, add the servers host
name to the client lista
backup_USER file on this
server, add the servers
host name to the client lista
Hardware
and
operating
system
Solaris, Solaris8
Solaris, Solaris8
Solaris, Solaris8
Path Name
ALL_LOCAL_DRIVES
not applicable
null (Do not enter a value.)
Backup Type Full backupb

(Schedule)

Application Backupc
User Backupc,d
Script Path
/opt/nortel/shell/backup/
veritas/veritasBpOracle.sh
not applicable
compression no
not applicable
no
Allow
no
multiple data
streams
not applicable
yes
not applicable
a. The host name is the name of the network interface dedicated to the backup and restore local area network
(LAN). For a Sun Fire 4500 or a Sun Fire 880, use the host name associated with the qfe1 port. For a Sun
Fire 4800 or E4900, use the host name associated with the qfe0 port.
b. For the UNIX files and the Oracle database, you can define additional backup schedules for other types
of backups.
c. For Application Backup and User Backup Backup Type, a duration of 24 hours is recommended to ensure that these two backups can be run at any time.
d. For the Oracle control files, define only the User Backup Type.
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
E-1
Index
disk array 2-13, 2-15
Access Control 1-5

Access Node. See A-Node
A-Node A-4
B
backup
automatic 2-4
centralized 5-1, 6-1
configuration data 1-2, 3-2, B-4
historical data 1-3, 4-1, B-16
manual 2-3
manual using VERITAS NetBackup 5-14,
6-15
overview 1-1
requirements 3-2
restrictions 1-4
RNC A-4
See also VERITAS NetBackup
system 1-2, B-1
backup and restore data files 5-19, 6-19
backup path, VERITAS NetBackup 5-7, 6-8
backup scripts
installing 1-6
historical data A-4

backup, automatic 4-5
backup, local 4-2
hypertext links xviii
I
I-Node A-4
install
backup scripts 1-6
restore scripts 1-6
Interface Node. See I-Node
L
limitations 1-4
M
main server 1-1, 3-6
MDM 1-5
Multiservice Data Manager. See MDM
N
NetBackup. See VERITAS NetBackup
Network Services Platform 1-5
C
configuration data A-3
crontab 2-4, 3-5
O
online backup 1-5
Oracle 5-19, 6-1, 6-19
D
data consistency 3-2, 3-6
database
Oracle 5-19, 6-19
Versant 5-19, 6-19
P
Performance Server B-2
Performance server B-12
UMTS, GPRS, GSM
OAM 4.2
E-2
Index
Nortel Confidential
performance server 1-1

policies, VERITAS NetBackup
configuring 5-11, 6-13
Primary Main Server B-1, B-4
primary main server 1-1
R
Radio Network Controller. See RNC
Read error C-3
regional operation center. See ROC
restore
backup and restore data files 5-19, 6-19
centralized 5-1, 6-1
configuration data 1-3, 3-6
historical data 1-3, 4-1
historical data, local 4-7
Oracle 5-19, 6-19
overview 1-1
preparing for 5-15, 6-16
requirements 3-6
restrictions 1-4
RNC A-4
system 1-3, 2-5
UNIX files 5-19, 6-19
Versant 5-19, 6-19
restore scripts
installing 1-6
restrictions 1-4
RMAN 6-1
RNC A-4
ROC 1-4
S
Secondary Main Server B-2
Secondary main server B-9
secondary main server 1-1
server
performance 1-1
primary main 1-1
secondary main 1-1
SOC 1-1
SRS 1-1
Server of Client. See SOC
single user mode 2-12
SMC 5-15, 6-16
SOC 1-1, B-3
411-8111-521
Preliminary
06.10
June 2005
SOC server B-15

Software Repository Server. See SRS
SRS 1-1, B-3
SRS server B-14
SUMBB 1-5
Summary Building Block. See SUMBB
Sun Fire 4800 2-8, 2-10
Sun Fire 4900 2-10
Sun Management Center. See SMC
system backup 2-1
system management. See SMC
T
tape 2-3, 2-6, 3-3, 3-7, A-2, A-3, A-4
contents of A-3, A-4
type of data A-2
U
UNIX files 5-19, 6-19
V
VERITAS NetBackup 5-1, 6-1
performing a manual backup with 5-14, 6-15
policies 5-11, 6-13
Versant 5-19, 6-19
W
wam_startall 3-8, 5-21, 6-21
wam_stopall 3-6, 5-15, 6-16
WICL 1-4
wireless internet command language. See
WICL
test
Fam ily Pro duct Manual Contacts Copyrig ht Con fidentiality Legal
UMTS, GPRS, GSM

User Guide
To order documentation from Nortel Global Wireless Knowledge Services, call
(1) (877) 662-5669
To report a problem in this document, call
(1) (877) 662-5669
or send e-mail from the Nortel Customer Training & Documentation World Wide Web site at
http://www.nortel.com/td
Copyright 20012005 Networks, All Rights Reserved
NORTEL CONFIDENTIAL
The information contained herein is the property of Nortel and is strictly confidential. Except as expressly authorized in writing by
Nortel, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to
know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it
uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel reserves the right to make changes in design or components as progress in
engineering and manufacturing may warrant.
* Nortel, the Nortel logo, the Globemark, and Unified Networks are trademarks of Nortel Networks. NIMS-PrOptima is a trademark
of MyCom International. Sun Fire and Sun StorEdge are trademarks of Sun Microsystems, Inc.VERITAS NetBackup is a
trademark of VERITAS Software Global Corporation
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Document number: 411-8111-521
Product release: OAM 4.2
Document version: Preliminary 06.10
Date: June 2005
Originated in Canada and the USA

W-NMS Backup and Restore User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

W-NMS Backup and Restore User Guide

Uploaded by

Copyright:

Available Formats

411-8111-521

UMTS, GPRS, GSM