Professional Documents
Culture Documents
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
* 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
06.10
June 2005
v
Copyright 20012005 Nortel
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.
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.
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.
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
November 2004
OAM 4.2Draft 6.03. Fixed the following CRs:
Q01022527-01: removed -L option from local data backup and restore,
and local archive and retrieval
Q01027762: Update Appendix B for changed stability data files and new
wiclet user files
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
Nortel Confidential
November 2004
OAM 4.2Draft 6.02
Removed references to iut_addmachineinroc.sh -xml
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.
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.
Added support for feature 28129 Backup and Restore Oracle Database
Using RMAN Utility.
Updated branding.
August 2004
OAM 4.1Preliminary 5.10-5.15. Draft for internal review.
UMTS, GPRS, GSM
OAM 4.2
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
UMTS 4.0, GPRS 6.0Draft, Issue 04.07.
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
Copyright 20012005 Nortel
Nortel Confidential
September 2003
UMTS 3.0, GPRS 5.0Standard, Issue 03.14 (GPRS 5.0 ChR).
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
xi
xv
xvii
1-1
1-7
2-1
3-1
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
5-13
6-1
A-1
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
Appendix C: Troubleshooting
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
D-1
Index
E-1
OAM 4.2
xiv
Contents
411-8111-521
Nortel Confidential
Preliminary
06.10
June 2005
xv
Copyright 20012005 Nortel
Nortel Confidential
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:
OAM 4.2
Related documents
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
Nortel Confidential
OAM 4.2
Figure 1-2
W-NMS documentation roadmap (continued)
411-8111-521
Preliminary
06.10
June 2005
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.
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
Applications
Switch xxxx
Web
Switch 184
BayStack 450
Ethernet
Switch 450
Function
sheet 1 of 3
OAM 4.2
Table iii
Original product names mapped to new names (continued)
Original Name(s)
New Name
Short Name
Function
CCN CS
(DMS MSC)
MSC
Mobile Switching
Center
CCN HLR
(DMS HLR)
HLR 100
Home Location
Register
Combined
MSC/HLR
VPN Router
xxxx
MSC Server
Mobile Switching
Center
GPP
IWF
Interworking Function
HSS
HSS
Home Subscriber
Server
iBTS
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
VPN Router
xxxx
WPS for
Access
Multiservice
Switch 7400
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
Nortel Confidential
Table iii
Original product names mapped to new names (continued)
Original Name(s)
New Name
Short Name
Multiservice
Switch 20000
W-NMS
RNC
RNC xxxx
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.)
Univity Signaling
Gateway (SIG d,
SS7-IP Gateway)
SIG
Signaling Interworking
Gateway
UMGW (MGW,
Passport Voice Gateway
(PVG))
MGW
Media Gateway
Function
Network Management
System for Wireless
Networks
OAM 4.2
Table iv
New product names mapped to original name(s)
New Name
Short Name
Original Name(s)
BPS2000 2-port SFP
GBIC MDA
BTS xxxx
iBTS
BayStack 450
Nortel GGSN
GGSN
Combined MSC/HLR
HLR 100
HLR 200
Univity HLR a
HSS
HSS
IWF
GPP
MGW
UMGW (function of a
Wireless Gateway), Passport
Voice Gateway (PVG)
MSC
CCN CS,
DMS MSC
MSC Server
SIG
Nortel IMS
IMS
IMS Solution
sheet 1 of 2
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Table iv
New product names mapped to original name(s) (continued)
New Name
Short Name
Original Name(s)
NIMS-PrOptima for
Preside for Wireless
Internet
Nortel MLC
MLC
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
RNC xxxx
RNC
W-NMS
sheet 2 of 2
OAM 4.2
411-8111-521
Preliminary
06.10
June 2005
1-1
Copyright 20012005 Nortel
Nortel Confidential
This document contains procedures for backup and restore of the following WNMS servers:
primary main server
performance server(s)
OAM 4.2
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.
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
weekly (and
immediately
before or after a
system data
backup)
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.
Local or
centralized
Online or
offline
Comments
system restore
local
offline
configuration
data restore
local
offline
centralized
historical data
retrieval
local
online
centralized
For detailed information and procedures about each type of backup or restore,
refer to the other chapters in this document.
OAM 4.2
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.
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
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.
Access
Control
MDM
OAM 4.2
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).
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
OAM 4.2
411-8111-521
Preliminary
06.10
June 2005
2-1
Copyright 20012005 Nortel
Nortel Confidential
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
OAM 4.2
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
know the password for the nortel user and the root user
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 -
Enter:
localSysDump
If the data to be backed up takes up more than one tape, you are
prompted to insert another tape.
End of procedure.
OAM 4.2
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
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 -
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
411-8111-521
Preliminary
End of procedure.
06.10
June 2005
Nortel Confidential
System restore
Requirements
Before performing this procedure, you must:
read and comply with the prerequisites section in Chapter 1,
Understanding backup and restore
have the tape(s) that contain the data you want to restore
OAM 4.2
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.
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)
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Procedure 2-3
Restoring a system
Step
Action
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
c.
The data restore continues. When the restore is complete, the following
message appears; do NOT enter control-d:
Type control-d to proceed with normal startup, (or
give the root password for system maintenance)
13
Do NOT enter control-d. Enter the password for the root user.
14
15
16
End of procedure.
OAM 4.2
Procedure 2-4
Booting to single user mode on a Sun Fire 4800 server
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
Enter:
0
Enter:
cons a
Enter:
init 0
Enter:
setenv auto-boot? false
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Procedure 2-4
Booting to single user mode on a Sun Fire 4800 server
Step
Action
Press the Ctrl key and then press the ] key. This key sequence returns
you to the telnet session.
Insert the Solaris operating system compact disc into the CD-ROM drive.
Enter:
setenv diag-switch? true
boot cdrom -rs
10
End of procedure.
OAM 4.2
Procedure 2-5
Booting to single user mode on a Sun Fire E4900 server
Step
Action
Connect to the System Controller of the Sun Fire E4900 server from
another host. Enter:
telnet <SC IPAddress>
where <SC IPAddress> is the IP address of the System Controller
Enter:
0
Enter:
cons a
Enter:
init 0
411-8111-521
Preliminary
Press the Ctrl key and then press the ] key. This key sequence returns
you to the telnet session.
06.10
June 2005
Nortel Confidential
Procedure 2-5
Booting to single user mode on a Sun Fire E4900 server
Step
Action
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.
10
End of procedure.
OAM 4.2
Procedure 2-6
Booting to single user mode
Step
Action
Enter:
init 0
Insert the Solaris operating system compact disc into the CD-ROM drive.
Enter:
setenv diag-switch? true
boot cdrom -rs
411-8111-521
Preliminary
End of procedure.
06.10
June 2005
Nortel Confidential
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:
telnet <SC IPAddress>
where <SC IPAddress> is the IP address of the Sun Fire 4800 System
Controlle r
Enter:
0
Enter:
cons a
Enter:
init 0
Enter:
setenv auto-boot? false
OAM 4.2
Procedure 2-7
Enabling the disk array for the Sun Fire 4800
Step
Action
Press the Ctrl key and then press the ] key. This key sequence returns
you to the telnet session.
Enter:
setenv auto-boot? true
boot -rs
10
411-8111-521
Preliminary
End of procedure.
06.10
June 2005
Nortel Confidential
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:
telnet <SC IPAddress>
where <SC IPAddress> is the IP address of the System Controller
Enter:
0
Enter:
cons a
Enter:
init 0
Press the Ctrl key and then press the ] key. This key sequence returns
you to the telnet session.
OAM 4.2
Procedure 2-8
Enabling the disk array for a Sun Fire E4900
Step
Action
411-8111-521
10
11
End of procedure.
Preliminary
06.10
June 2005
3-1
Copyright 20012005 Nortel
Nortel Confidential
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)
OAM 4.2
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
Nortel Confidential
Procedure 3-1
Backing up configuration data
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 -
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 you want to continue with the backup, press the Enter key. Go to step 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.
OAM 4.2
Table 3-1
options definitions for backing up configuration data
parameter
value
-d <delay time>
-h or -H
-m <message
text>
-t <tape name>
-s
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
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
Before performing this procedure, you must be familiar with the UNIX crontab
utility.
Procedure 3-2
Backing up configuration data automatically
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 -
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
End of procedure.
OAM 4.2
have the tape(s) that contain the data you want to restore
Procedure 3-3
Restoring configuration data
Step
Action
Enter:
su - root
sheet 1 of 3
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Action
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>]
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
OAM 4.2
Action
11
Note: You can also use the SMC to start all processes on the server. For
more information refer to Preside for Wireless Internet System
Management, 411-8111-538.
12
13
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
-t <tape name>
OAM 4.2
411-8111-521
Preliminary
06.10
June 2005
4-1
Copyright 20012005 Nortel
Nortel Confidential
OAM 4.2
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
Archiving historical data locally
Step
Action
Log onto the server you are backing up as nortel (or some other normal
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
Nortel Confidential
Procedure 4-1
Archiving historical data locally
Step
Action
If you want to continue with the backup, press the Enter key and go to
step 8.
If the data to be backed up takes up more than one tape, you are
prompted to insert another tape.
10
End of procedure.
Table 4-1
option and parameter definitions for localarchive command
parameter
value
-h or -H
-d <n|n:m>
OAM 4.2
value
-D <YYYYMMDD |
YYYYMMDD a:
YYYYMMDD b>
-t <tape name>
-s
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
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
Before performing this procedure, you must be familiar with the UNIX crontab
utility. You can use the man crontab command to get more information about
crontab.
Procedure 4-2
Archiving historical data automatically
Step
Action
Log onto the server you are backing up as nortel (or some other normal
user), start a console session and then become the root user by entering
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
OAM 4.2
Procedure 4-2
Archiving historical data automatically
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
the restrictions described in the section titled Restrictions for automatic
archive.
411-8111-521
End of procedure.
Preliminary
06.10
June 2005
Nortel Confidential
Use this procedure to retrieve the historical data for an individual server.
Requirements
Before performing this procedure you must:
read and comply with the prerequisites section in Chapter 1,
Understanding backup and restore
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
Log onto the server you are backing up as nortel (or some other normal
user), start a console session and then become the root user by entering
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.
End of procedure.
OAM 4.2
Table 4-2
parameter definitions for localretrieve command
parameter
value
-h or -H
-f
-l
-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.
411-8111-521
Preliminary
06.10
June 2005
5-1
Copyright 20012005 Nortel
Nortel Confidential
OAM 4.2
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.
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
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
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
Secondary
Configure policies
Procedure 5-5
Back up a server
restore a server
Stop the server processes
Procedure 5-8
Restore the brd files
Procedure 5-9
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
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
Configuring NetBackup
Step
Action
Log onto the server that has the NetBackup server software installed.
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
End of procedure.
Preliminary
06.10
June 2005
Nortel Confidential
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.
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
End of procedure.
OAM 4.2
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
Install the NetBackup Oracle Agent on the W-NMS server that has been
installed with
Log onto the server as nortel (or some other normal user), start a terminal
session and then become the root user by entering
su -
411-8111-521
End of procedure.
Preliminary
06.10
June 2005
Nortel Confidential
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
/opt/nortel/data/backup/BRTools/
veritas/client/backup_ORACLE
/opt/nortel/data/backup/BRTools/
veritas/client/backup_USER
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
OAM 4.2
Procedure 5-4
Creating backup path files
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 -
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
End of procedure.
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Configuring policies
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
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
Standard
Standard
OAM 4.2
Policy
Historical data
(ARCHICAL)
UNIX files
Oracle database
Client List
<host name>
<host name>
<host name>
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.)
/etc/hostsb
User Backupd, e
Full Backup
User Archivee
Script Path
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>
OAM 4.2
Procedure 5-5
Configuring policies using VERITAS NetBackup
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
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.
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
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.
End of procedure.
OAM 4.2
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.
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
Log onto the server as nortel (or some other normal user), start a terminal
session and then become the root user by entering
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
End of procedure.
Preliminary
06.10
June 2005
Nortel Confidential
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)
Stopping the server processes
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
Stopping the server processes
Step
Action
Log onto the server you are restoring to, using the nortel user ID.
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 2
OAM 4.2
Action
End of procedure.
sheet 2 of 2
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Action
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
Destination client: the OAM server host name of the network interface
dedicated to the backup and restore LAN
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.
OAM 4.2
Action
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:
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 exited from the NetBackup Administration tool, start from step 1
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
UNIX files
Requirements
This procedure must be performed after Procedure 5-9.
Procedure 5-10
Restoring the data for the server
Step
Action
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
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 /).
OAM 4.2
Action
Monitor the status of the restore job from the Activity Monitor window.
10
Enter:
postVeritasRestore ABORT
This will cancel the restore operation and perform the necessary cleanup. Wait for the clean-up to finish.
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:
If you exited from the NetBackup Administration tool, start from step 1
of Procedure 5-9.
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Action
16
Note: You can also use the SMC to start all processes on the server. For
more information refer to Preside for Wireless Internet System
Management, 411-8111-538.
17
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
OAM 4.2
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
Before performing this procedure you must:
read and comply with the prerequisites section in Chapter 1,
Understanding backup and restore.
ensure that there is enough disk space in /opt/nortel/data to store the data
you want to retrieve
Procedure 5-11
Retrieving historical data
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
Action
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
Destination client: the OAM server host name of the network interface
dedicated to the backup and restore LAN
Click the use Backup History to set date range icon. The Date
Range dialog will pop up. Select the ARCHIVAL policy of the desired
backup date and click OK. You may select multiple dates to restore.
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.
In the Restore Files window select the Restore everything to its original
location check box.
10
11
Monitor the status of the restore job from the Activity Monitor window.
12
OAM 4.2
Action
13
14
Do not perform the rest of the steps in this procedure. Investigate the
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
16
17
End of procedure.
sheet 3 of 3
411-8111-521
Preliminary
06.10
June 2005
6-1
Copyright 20012005 Nortel
Nortel Confidential
OAM 4.2
6-2 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
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.
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
411-8111-521
Preliminary
06.10
June 2005
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-3
how to enable the Centralized Backup and Restore of HFB Database with
RMAN Utility feature
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
Secondary
Configure policies
Procedure 6-5
Back up a server
restore a server
Stop the server processes
Procedure 6-6
Restore the brd files
Procedure 6-7
Xd
a. This is the server that has the VERITAS NetBackup Data Center software installed.
OAM 4.2
6-4 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
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
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-5
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 6-1
Configuring NetBackup
Step
Action
Log onto the server that has the NetBackup server software installed.
End of procedure.
OAM 4.2
6-6 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
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
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.
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
End of procedure.
Preliminary
06.10
June 2005
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-7
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
Install the NetBackup Oracle Agent on the W-NMS server that has been
installed with either
Log onto the server as nortel (or some other normal user), start a terminal
session and then become the root user by entering
su -
End of procedure.
OAM 4.2
6-8 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
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
/opt/nortel/data/backup/BRTools/
veritas/client/backup_UNIX
/opt/nortel/data/backup/BRTools/
veritas/client/backup_ORACLE
/opt/nortel/data/backup/BRTools/
veritas/client/backup_USER
411-8111-521
Preliminary
06.10
June 2005
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
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
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 -
OAM 4.2
6-10 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
Procedure 6-4
Creating backup path files
Step
Action
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
End of procedure.
411-8111-521
Preliminary
06.10
June 2005
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-11
Configuring policies
Policy
Default name
Primary Main
UNIX files
Oracle database
Oracle control files
<host name>_NNunix
<host name>_NNoracle
<host name>_NNuser
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
Historical data
(ARCHIVAL)
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.
OAM 4.2
6-12 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
Table 6-4
Policy parameter values
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.)
Script Path
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
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-13
Table 6-5
variable definitions
Variable
Description
<host name>
OAM 4.2
6-14 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
Procedure 6-5
Configuring policies using VERITAS NetBackup
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
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
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.
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)
OAM 4.2
6-16 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
Action
Log onto the server you are restoring to, using the nortel user ID.
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
411-8111-521
Preliminary
End of procedure.
06.10
June 2005
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-17
Action
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
Destination client: the OAM server host name of the network interface
dedicated to the backup and restore LAN
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.
OAM 4.2
6-18 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
Procedure 6-7 (continued)
Restoring the brd files
Step
Action
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:
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 exited from the NetBackup Administration tool, start from step 1
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
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-19
UNIX files
Requirements
This procedure must be performed after Procedure 6-7.
Procedure 6-8
Restoring the data for the server
Step
Action
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
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 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 /).
OAM 4.2
6-20 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
Procedure 6-8 (continued)
Restoring the data for the server
Step
Action
Monitor the status of the restore job from the Activity Monitor window.
10
Enter:
postVeritasRestore ABORT
This will cancel the restore operation and perform the necessary cleanup. Wait for the clean-up to finish.
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:
If you exited from the NetBackup Administration tool, start from step 1
of Procedure 6-7.
411-8111-521
Preliminary
06.10
June 2005
Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database 6-21
Procedure 6-8 (continued)
Restoring the data for the server
Step
Action
16
Note: You can also use the SMC to start all processes on the server. For
more information refer to Preside for Wireless Internet System
Management, 411-8111-538.
17
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
OAM 4.2
6-22 Performing centralized backup and restore with no archive policyRMAN used for HFB Oracle
database
411-8111-521
Preliminary
06.10
June 2005
A-1
Copyright 20012005 Nortel
Nortel Confidential
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
OAM 4.2
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.
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
Nortel Confidential
Action
Log on to the server you are backing up, using the root user.
Insert a tape into the tape drive of the server. Make sure the tape has
been rewound to the beginning.
End of procedure.
OAM 4.2
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
Log on to the server you are backing up, using the root user.
Insert a tape into the tape drive of the server. Make sure the tape has
been rewound to the beginning.
Enter:
localretrieve -i
End of procedure.
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
Preliminary
06.10
June 2005
Nortel Confidential
OAM 4.2
411-8111-521
Preliminary
06.10
June 2005
B-1
Copyright 20012005 Nortel
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.
This chapter contains the following sections:
OAM 4.2
Table B-2
Secondary 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*
Table B-3
Performance 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)
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Table B-4
SRS
file systems and directories backed up
EEPROM variables
Solaris Volume Manager Configurations
File systems
/
/usr
/var
/home
/opt
/opt/nortel (excluding /opt/nortel/logs)
Table B-5
SOC 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)
OAM 4.2
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
OAM 4.2
Table B-6
Primary Main Server
component
data backed up
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
Directories
/opt/nortel/config/backup
/opt/nortel/data/backup/BRTools/br/backup_data/config
OAM 4.2
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
OAM 4.2
Table B-7
Secondary main server
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
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
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
Secondary main server
component
data backed up
Directories
/opt/nortel/config/backup
/opt/nortel/data/backup/BRTools/br/backup_data/config
Common Services
Directories
/opt/nortel/config/fmk
/opt/nortel/config/wicl
System Management
Directories
/opt/nortel/config/sysmgt
/var/opt/SUNWsymon
excluding
/opt/nortel/config/sysmgt/am
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
Audit Trail
Files
/opt/nortel/config/AuditTrail/auditTrailConfigData
/opt/nortel/config/AuditTrail/csal.properties
HFB
Directories
/opt/nortel/config/applications/hfb
OAM 4.2
Table B-8
Performance server
component
Common services
Directories
/opt/nortel/config/fmk
/opt/nortel/config/wicl
System
Management
Directories
/opt/nortel/config/sysmgt
/var/opt/SUNWsymon
excluding
/opt/nortel/config/sysmgt/am
PDI
Files
/opt/nortel/config/packet/pdi/pdi.cfg
GDI
Directories
/opt/nortel/config/packet/gdi
MDP
Files
/etc/opt/Magellan/LIClicenses.cfg
/etc/opt/Magellan/LICcustName.cfg
Directories
/opt/MagellanNMS/cfg
/opt/MagellanNMS/data
/opt/MagellanMDP/cfg/mdp
/opt/MagellanMDP/cfg/mdp/pp/rdf
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
/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
Directories
/etc/hosts
/etc/inet/hosts
/opt/nortel/config/backup
/opt/nortel/data/backup/BRTools/br/backup_data/config
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
/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
CEM
Directories
/opt/nortel/data/coreEMS/nodes
sheet 2 of 2
OAM 4.2
Table B-9
SRS server
component
System
Management
Directories
/opt/nortel/config/sysmgt
/var/opt/SUNWsymon
excluding
/opt/nortel/config/sysmgt/am
Directories
/opt/nortel/config/backup
/opt/nortel/data/backup/BRTools/br/backup_data/config
SRS
Files
/opt/nortel/config/srm/Srm.cfg
Directories
/opt/nortel/data/srs
excluding
/opt/nortel/data/srs/tmp
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
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Table B-10
SOC server
component
System
Management
Directories
/opt/nortel/config/sysmgt
/var/opt/SUNWsymon
excluding
/opt/nortel/config/sysmgt/am
SOC
Files
/opt/nortel/data/iut_tools/network_updater/MetaFrame.dat
/var/CTXSmf/ctxconfdb.HKLM.dir
/var/CTXSmf/ctxconfdb.HKLM.pag
Directories
/opt/nortel/config/backup
/opt/nortel/data/backup/BRTools/br/backup_data/config
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
OAM 4.2
Application Components
primary main
HFB
hfb
CSAL
csal
Audit Trail
audittr
ne_sda, oam_sda
Audit Trail
audittr
ne_sda, oam_sda
MYCOM
mycom
PDI
pdi
GDI
gdi
SDI
sdi
CDI
cdi
ADI
adi
xdi
Audit Trail
audittr
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
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
where <yyyymmdd> is the date.
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
OAM 4.2
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:
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
Copyright 20012005 Nortel
Nortel Confidential
Appendix C: Troubleshooting
This section contains a number of problems that may occur during a backup
or restore. The section is divided into the following categories:
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
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.
OAM 4.2
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
Check whether the clean light on the tape drive is blinking. If it is, clean
the tape drive head several times and try to do the system restore again.
Check the log file. If you find error messages that show the problem
results from restoring certain files that the system restore 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, try to do the system restore one more time. If the problem
persists, contact Nortel support for help.
Preliminary
06.10
June 2005
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.
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.
OAM 4.2
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.
411-8111-521
Check whether the clean light on the tape drive is blinking. If it is, clean
the tape drive head several times and try to do the local data restore again.
Check the log file. If you find error messages that show the problem
results from restoring certain files that the local data restore 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, 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
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 local data archive again.
Check the log file. If you find error messages that show the problem
results from archiving certain files that the data archive 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 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:
Use SMC to check that all applications are up and running and in good
state.
OAM 4.2
Check whether the clean light on the tape drive is blinking. If it is, clean
the tape drive head several times and try to do the local data restore again.
Check the log file. If you find error messages that show the problem
results from retrieving certain files that the local data retrieval 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, 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.
Use SMC to check that all applications are up and running and in good
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
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
OAM 4.2
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
Preliminary
06.10
June 2005
Nortel Confidential
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.
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:
OAM 4.2
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.
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.
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.
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.
OAM 4.2
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.
411-8111-521
Preliminary
06.10
June 2005
Nortel Confidential
Check the archive policy. Make sure there are two schedules configured;
one is type of Full Backup, and the other User Archive.
Use SMC to check that all applications are up and running and in a
trouble-free state.
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.
OAM 4.2
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
Preliminary
06.10
June 2005
D-1
Copyright 20012005 Nortel
Nortel Confidential
OAM 4.2
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>
411-8111-521
Preliminary
06.10
June 2005
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.
OAM 4.2
Table D-1
Policy parameter values
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
If ubvaClient created a
backup_ORACLE file on this
server, add the servers host
name to the client lista
If ubvaClient created a
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
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
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
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
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
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
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