W-NMS Backup and Restore User Guide

8/11/2019 W-NMS Backup and Restore User Guide

1/160

UMTS, GPRS, GSM

W-NMS Backup and RestoreUser Guide

OAM 4.2 Preliminary 06.10 June 2005

Whats inside...Understanding backup and restorePerforming system backup and restorePerforming configuration data backup and restorePerforming historical data archive and retrievalPerforming centralized backup and restore with an a rchive policyPerforming centralized backup and restore with no archive policyRMAN

used for HFB Oracle databaseAppendix A: Additional processes and informationAppendix B: Data backed upAppendix C: TroubleshootingAppendix D: Technical note - alternative policies

411-8111-521


2/160

test


3/160

UMTS, GPRS, GSM

W-NMS Backup and RestoreUser Guide

Document number: 411-8111-521Product release: OAM 4.2Document version: Preliminary 06.10Date: June 2005

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright 20012005 Nortel, All Rights Reserved

Originated in Canada and the USA

NORTEL CONFIDENTIAL

The information contained herein is the property of Nortel and is strictly confidential. Except as expressly authorized in writing byNortel, 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 toprotect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel,the holder is granted no rights to use the information contained herein.

Information is subject to change without notice. Nortel reserves the right to make changes in design or components as progress inengineering and manufacturing may warrant.

* Nortel Networks, the Nortel Networks 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.VERITASNetBackup is a trademark of VERITAS Software Global CorporationTrademarks are acknowledged with an asterisk (*) at their first appearance in the document.


4/160

ivNortel Confidential Copyright 20012005 Nortel

411-8111-521 Preliminary 06.10 June 2005


5/160

vNortel Confidential Copyright 20012005 Nortel

UMTS, GPRS, GSM W-NMS Backup and Restore OAM 4.2

Publication historyMay 2005

OAM 4.2 Preliminary general re-release, issue 06.10.

This release adds a note about Veritas Netbackup version support.

April 2005OAM 4.2 Preliminary re-release to LiveLink only, issue 06.09.

Answer to Q01108740, NTP timer restriction no longer applies, as thebackup/restore scripts deal with the issue.

March 2005

OAM 4.2 Preliminary release, issue 06.08Added CMS-related directories to the lists in Appendix C.

Corporate rebranding (content only)

March 2005OAM 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, AppendixC: Troubleshooting , Centralized Data Backup .

Added PAM directories to Table B-6 .

February 2005

OAM 4.2 - Draft 6.06 (to test) Update of 4.2 document with post-Standard CR fixes entered in the 4.1

document. Q010600001: Sun Fire E4900 backup and restore procedures. ( Procedure

2-5 and Procedure 2-8 )

Q01038906: various small changes


6/160

vi Publication historyNortel Confidential Copyright 20012005 Nortel


January 2005

OAM 4.2Draft 6.05. Fixed the following CRs: Q01038906 BR: Inconsistency backup data in SRS

Q01045552 BR: NTP issues with ctrl-d messages for 4800 server Q01048288 UMTS:v4.1:B&R: NTP doc 411-8111-521 B&R user guide

Updated documentation roadmap drawing and re-branding tables.

December 2004

OAM 4.2Draft 6.04. Fixed the following CRs: Q01021419 B&R: Appendix B of NTP 411-8111-521 needs to reflect

new location of files

Q01033454 B&R: Appendix B of NTP 411-8111-521 need to update for

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

for MDP comp on perf

Q01033595 B&R: Appendix B of NTP 411-8111-521 needs to add sysmgmt component to table B-8

Q01034380 B&R: Appendix B of NTP 411-8111-521 needs to add 2 filesfor perf server

Q01040622 BR: remove tape during system restore generates infiniteloop

November 2004OAM 4.2Draft 6.03. Fixed the following CRs: Q01022527-01: removed -L option from local data backup and restore,

and local archive and retrieval

Q01021419: Update Appendix B for changed locations of coreDA files

Q01027762: Update Appendix B for changed stability data files and newwiclet user files

Q01029791: Update procedure 5-11 to match changed user interface.

Q01028775: Update Appendix B for changed location of csal.propertiesfile

Additional changes include updating the name of the Solaris agent to matchchanging VERITAS terminology and adding Srm.config to SRS componentin Appendix B.


7/160

Publication history viiNortel Confidential Copyright 20012005 Nortel


November 2004

OAM 4.2Draft 6.02 Removed references to iut_addmachineinroc.sh -xml

Restore lost headings in Performing centralized backup and restore withan archive policy .

Corrected typos

November 2004

OAM 4.2Draft 6.01 Changed Performing centralized backup and restore with an archive

policy and Performing centralized backup and restore with no archivepolicyRMAN used for HFB Oracle database to require manualinstallation of Veritas NetBack Solaris and Oracle agents.

Updated documentation references for NetBackup 5.1. Updated Appendix B: Data backed up as indicated by change bars.

October 2004

OAM 4.1Preliminary 5.17. Fixed Case 040819-61194.

September 2004

OAM 4.1Preliminary 5.16. Fixed CR Q00954549 by changing Procedure 3-3 step 12 and Procedure

5-10 step 17 to make the state of the HFB Oracle database irrelevant.

Fixed CR Q00954058 by changing steps 4 and 5 of procedure 2-1 toremove retrieve staging.

Fixed CR Q00954561 by adding a new step (Step 14) to Procedure 3-3and to Procedure 5-10 (Step 19).

Added support for feature 28129 Backup and Restore Oracle DatabaseUsing RMAN Utility.

Added support for defining a policy to backup multiple servers.

Updated Appendix B: Data backed up as indicated by change bars.

Added Appendix D: Technical note - alternative policies .

Fixed CR Q00976062 by adding the tape type to the requirements forspecific procedures.

Updated branding.

August 2004

OAM 4.1Preliminary 5.10-5.15. Draft for internal review.


8/160

viii Publication historyNortel Confidential Copyright 20012005 Nortel


July 2004

OAM 4.1Preliminary 5.09. Added documentation roadmap to About thisdocument and corrected branding tables.

June 2004OAM 4.1Draft 5.08. Fixed CR Q00919465 by adding a note to procedures3-1 and 4-1 that if a local backup or archive is invoke while the centralizedversions of the operations is running, both will fail. Corrected typo on page 1-6. Fixed CR Q00925527 by changing step 4 in procedure 5-10.

June 2004

OAM 4.1Draft 5.07. Added procedure for configuring automatic local databackup.

April-June 2004

OAM 4.1Draft 5.01 through 5.06 for internal review. Development ofdocument branched off of OAM 4.0a document - issues 4.x continues tosupport 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 currentrelease. Added troubleshooting section (Appendix C). Numerous usabilityimprovements.

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 anindividual application.

February 2004UMTS 4.0, GPRS 6.0Draft, Issue 04.07.

Resolve CR Q00804565. Add prerequisite in chapter 1 that only one NTPserver protocol process can be running. Applies to all servers.


9/160

Publication history ixNortel Confidential Copyright 20012005 Nortel


Resolve CR Q00842704. Add restriction on performing a primary mainserver backup and secondary main server backup at the same time.

Resolve Q00842698-01. Add setenv diag-switch? true command.

February 2004UMTS 4.0, GPRS 6.0Draft, Issue 04.06.

Resolve CRs Q00832688, Q00838703, Q00838709: updates to procedures 3-3, 3-4, 3-5, 3-6.

January 2004

UMTS 4.0, GPRS 6.0Draft, Issue 04.05.

Remove all references to Oracle on the main server (primary and secondary)as Oracle is no longer installed on it.

January 2004

UMTS 4.0, GPRS 6.0Draft, Issue 04.04. Updates from Verification.

December 2003

UMTS 4.0, GPRS 6.0Draft, Issue 04.03. Additional updates from Design.

December 2003

UMTS 4.0, GPRS 6.0Draft, Issue 04.02. Updates based on Design review.

December 2003UMTS 4.0, GPRS 6.0Draft, Issue 04.01. This document includesinformation and procedures for full system backup and restore that used to bein the GPRS/UMTS OAM Full Backup and Restore Procedure , 411-8111-537.

The previous release of this document was named Preside for Wireless Internet OAM Data Backup and Restore User Guide . It has been renamed toPreside for Wireless Internet OAM Backup and Restore User Guide .

November 2003

UMTS 3.0, GPRS 5.0Standard, Issue 03.15 (GGSN 3.2). The followingupdates have been made:

In Appendix A, corrected the HFB directories backed up.

September 2003

UMTS 3.0, GPRS 5.0Standard, Issue 03.14 (GPRS 5.0 ChR).


10/160

x Publication historyNortel Confidential Copyright 20012005 Nortel


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


11/160

Nortel Confidential xi

UMTS, GPRS, GSM W-NMS Backup and Restore User Guide OAM 4.2

Contents 1

About this document xi

About this document xvAudience for this document xvOrganization of this document xvRelated documents xvi

Roadmap to W-NMS documents xviiIndication of hypertext links xviiiNortel branding xix

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

Performing system backup and restore 2-1System backup 2-1

Backing up a system manually 2-3Backing up a system automatically 2-4

System restore 2-5Restoring a system 2-5Booting to single user mode on a Sun Fire 4800 server 2-8Booting to single user mode on a Sun Fire E4900 server 2-10Booting to single user mode 2-12Enabling the disk array (Sun Fire 4800) 2-13Enabling the disk array (Sun Fire E4900) 2-15

Performing configuration data backup and restore 3-1Backing up configuration data 3-2

Backing up configuration data manually 3-2Backing up configuration data automatically 3-5

Restoring configuration data 3-6

Performing historical data archive and retrieval 4-1


12/160

xii Contents Nortel Confidential


Archiving historical data locally 4-2Archiving historical data automatically 4-5Retrieving historical data locally 4-7

Performing centralized backup and restore with an archive policy5-1Configuring NetBackup 5-4Installing the UNIX NetBackup Client 5-5Installing the VERITAS NetBackup Oracle agent 5-6

Requirements 5-6Creating backup path files 5-7Configuring policies 5-9

Configuring policies using VERITAS NetBackup 5-11Upgrading a VERITAS NetBackup server from OAM 3.x to OAM 4.x 5-13Backing up configuration data manually 5-14Archiving historical data manually 5-14Restoring a server using VERITAS NetBackup 5-15

Stopping the server processes 5-15Restoring the brd files 5-17Restoring the data for the server 5-19

Retrieving historical data 5-22

Performing centralized backup and restore with no archivepolicyRMAN used for HFB Oracle database 6-1Configuring NetBackup 6-5Installing the UNIX NetBackup Client 6-6Installing the VERITAS NetBackup Oracle agent 6-7

Requirements 6-7Creating backup path files 6-8Configuring policies 6-11

Configuring policies using VERITAS NetBackup 6-13Backing up configuration data manually 6-15Restoring a server using VERITAS NetBackup 6-15

Stopping the server processes 6-16Restoring the brd files 6-17Restoring the data for the server 6-19

Appendix A: Additional processes and information A-1Finding out the type of data on a tape A-2Finding out the contents of a configuration data backup tape A-3Finding out the contents of an historical data archive tape A-4RNC data backup from the main server A-4

RNC data restore to the main server A-5

Appendix B: Data backed up B-1System data backup B-1Configuration data backup B-4Historical data archive B-16

hfb module B-17


13/160

Nortel Confidential Contents xiii


csal module B-17audittr module B-17ne_sda module B-18oam_sda module B-18mycom module B-18

pdi, gdi, sdi and cdi modules B-19adi module B-20

Appendix C: Troubleshooting C-1General C-1System Backup C-2System Restore C-2Local Data Backup C-3Local Data Restore C-4Local Data Archive C-5Local Data Retrieval C-6Centralized Data Backup C-9Centralized Data Restore C-11Centralized Data Archival C-12Centralized Data Retrieval C-13

Appendix D: Technical note - alternative policies D-1

Index E-1


14/160

xiv Contents Nortel Confidential



15/160

xvNortel Confidential Copyright 20012005 Nortel


About this document 1This document explains the backup and restore functionality provided by theNortel Wireless Network Management System (W-NMS.) Use the backupprocedures to back up the data for the servers contained in one RegionalOperating Center (ROC).

This chapter contains the following sections: Audience for this document on page 1-xv

Organization of this document on page 1-xv

Related documents on page 1-xvi

Indication of hypertext links on page 1-xviii

Nortel branding on page 1-xix

Audience for this document 1

This document is for network administrators who install and administerW-NMS.

Organization of this document 1

Chapter 1, Understanding backup and restore provides a general overviewof W-NMS backup and restore, including restrictions and limitations.

Chapter 2, Performing system backup and restore contains procedures forbacking up and restoring the system data for a server.

Chapter 3, Performing configuration data backup and restore containsprocedures for backing up and restore the configuration data for a server.

Chapter 4, Performing historical data archive and retrieval containsprocedures for archiving and retrieving the historical data for a server.


16/160

xvi About this documentNortel Confidential Copyright 20012005 Nortel


Chapter 5, Performing centralized backup and restore with an archivepolicy explains how to back up and restore the data on the servers from acentral location using the third party application VERITAS NetBackup. Usethese procedures only if an archive profile for archiving historical data hasbeen set.

Chapter 6, Performing centralized backup and restore with no archivepolicyRMAN used for HFB Oracle database is an alternative to Chapter 5.Use this chapter if you do not need to configure a centralized archive policy toarchive historical data, or, if the system has a separate backup policy to backup the historical data or data in all the file systems on the server, use thischapter to back up the HFB Oracle database through RMAN utility as part ofthe data backup.

Appendix A: Additional processes and information contains procedures forchecking the contents of a tape. It also describes the RNC backup and restore

process.

Appendix B: Data backed up lists the files and directories backed up foreach server and application.

Appendix C: Troubleshooting provides troubleshooting procedures forback-up and restore actions.

Appendix D: Technical note - alternative policies describes an alternativeapproach to defining backup policies for VERITAS NetBackup.

Related documents 1

The following Nortel Technical Publications (NTPs) provide more informationabout the products and services described in this document: W-NMS System Management , 411-8111-538

About the Nortel UMTS RNC 1000 , 411-8111-906

W-NMS Engineering Guide , 450-3101-638

Some of the procedures in this document refer to the Sun Management Center(SMC). For information about the SMC, refer to W-NMS System

Management , 411-8111-538.

Some of the procedures in this document refer to a third party product forbackup and restore called VERITAS NetBackup. For information aboutVERITAS NetBackup refer to the VERITAS documents.


17/160


18/160

xviii About this documentNortel Confidential Copyright 20012005 Nortel


Figure 1-2W-NMS documentation roadmap (continued)

Indication of hypertext links 1

Hypertext links in this document are indicated in blue. If viewing a PDFversion of this document, click on the blue text to jump to the associatedsection or page.


19/160

About this document xixNortel Confidential Copyright 20012005 Nortel


Nortel branding 1

Nortel is changing the branding of some of its product lines. Part of this effortincludes changing the names of the products. New product names have beencreated using the following format:

Nortel

where: describes what function the product performs.

is a model series number.

For example, the Baystack 450 product has been renamed as the NortelEthernet Switch 450 . Some of the new product names are quite lengthy. Tomake our documents easier to read, the product names are shortened aftertheir first occurrence. For example, the Nortel Ethernet Switch 450 product

name is referred to as the Ethernet Switch 450 for second and subsequentoccurrences.

To alleviate any confusion the rebranding might cause, Table iii and Table iv are job aids to assist the end user in reconciling inconsistent productterminology across multiple documents. During the transition, both theexisting product names and the new product names may appear in thedocumentation and software.

Table iii details the original product names and their corresponding new andabbreviated product names. Table iv details the new product names to theoriginal names.

Table iiiOriginal product names mapped to new names

Original Name(s) New Name Short Name Function

Alteon ApplicationSwitch xxxx

Nortel Applications Switchxxxx

ApplicationsSwitch xxxx

Alteon Web Switch 184 Nortel Web Switch 184 WebSwitch 184

BayStack 450 Nortel Ethernet Switch 450 EthernetSwitch 450

BPS2000 2-port SFPGBIC MDA

Nortel Ethernet Switch 2-portSFP GBIC MDA

sheet 1 of 3


20/160

xx About this documentNortel Confidential Copyright 20012005 Nortel


CCN CS(DMS MSC) Nortel GSM/UMTS MSC MSC Mobile SwitchingCenter

CCN HLR(DMS HLR)

Nortel GSM/UMTS HLR 100 HLR 100 Home LocationRegister

Combined MSC andHLR(DMS Trinode)

Nortel GSM/UMTS CombinedMSC/HLR

CombinedMSC/HLR

Contivity xxxx Secure IPServices Gateway

Nortel VPN Router xxxx VPN Routerxxxx

DMS Gateway MobileSwitching Center(GMSC)

Nortel GSM/UMTS MSCServer

MSC Server Mobile SwitchingCenter

GPP Nortel GSM/UMTS IWF IWF Interworking Function

HSS Nortel GSM/UMTS HSS HSS Home SubscriberServer

iBTS Nortel BTS xxxx BTS xxxx Base TransceiverStation

IMS Solution Nortel IMS IMS IP MultimediaSubsystem

NIMS-PrOptima forPreside for WirelessInternet

NIMS-PrOptima forW-NMS a

Network InformationManagement System& Wireless NetworkManagement System

Nortel Networks SecureRouter xxxx

Nortel VPN Router xxxx VPN Routerxxxx

Offline Configuration forAccess Networks(OCAN)

Wireless Provisioning Systemfor Access b

WPS forAccess

Wireless ProvisioningSystem

Passport 7400 (7K) Nortel Mult iservice Switch7400

MultiserviceSwitch 7400

Passport 15000 (15K) Nortel Multiservice Switch15000

MultiserviceSwitch 15000

Table iiiOriginal product names mapped to new names (continued)


sheet 2 of 3


21/160

About this document xxiNortel Confidential Copyright 20012005 Nortel


Passport 20000 (20K) Nortel Multiservice Switch20000 MultiserviceSwitch 20000

Preside for WirelessInternet (PWI)

Nortel Wireless NetworkManagement System

W-NMS Network ManagementSystem for WirelessNetworks

RNC Nortel UMTS RNC xxxx RNC xxxx

Shasta 5000 BSN Nortel IP Services EdgeRouter 5500

IP ServicesEdge Router5500

Univity GGSN(Shasta GGSN)

Nortel GGSN GGSN Gateway GPRSSupport Node

Univity HLR c Nortel GSM/UMTS HLR 200 HLR 200 Home LocationRegister

Univity MLC(MLC)

Nortel MLC MLC Mobile LocationCenter

Univity SGSN(SGSN,GPRS SGSN,UMTS SGSN,USGSN or U-SGSN)

Nortel SGSN(Nortel SGSN/GPRSNortel SGSN/UMTS-use where required todifferentiate technology.)

SGSN(SGSN/GPRS,SGSN/UMTS-use whererequired to

differentiatetechnology.)

Serving GPRSSupport Node

Univity SignalingGateway (SIG d ,SS7-IP Gateway)

Nortel GSM/UMTS SIG SIG Signaling InterworkingGateway

UMGW (MGW,Passport Voice Gateway(PVG))

Nortel GSM/UMTS MGW MGW Media Gateway

Wireless Gateway (WG)NOTE: Configuration NOT

supported in PC04 andbeyond, is supported in OAM.

See the following:- Nortel SGSN

- Nortel GSM/UMTS MGW

a. NIMS PrOptima is a sub-component of W-NMSb. WPS for Access is a sub-component of W-NMSc. May have also been referred to as Everest HLR

Table iiiOriginal product names mapped to new names (continued)


sheet 3 of 3


22/160


23/160

About this document xxiiiNortel Confidential Copyright 20012005 Nortel


NIMS-PrOptima for W-NMSc

NIMS-PrOptima forPreside for WirelessInternet

Nortel MLC MLC Univity MLC, MLC

Nor tel Multiservice Switch 7400 Multiservice Switch 7400 Passpor t 7400 (7K)

Nortel Multiservice Switch 15000 Multiservice Switch 15000 Passport 15000 (15K)

Nortel Multiservice Switch 20000 Multiservice Switch 20000 Passport 20000 (20K)

Nortel VPN Router xxxx VPN Router xxxx Contivity xxxx Secure IPServices Gateway,Nortel Networks SecureRouter xxxx

Nortel SGSN:- Nortel SGSN/GPRS- Nortel SGSN/UMTS

SGSNSGSN/GPRSSGSN/UMTS)

Univity SGSN,GPRS SGSN,UMTS SGSN,U-SGSN, or USGSNfunction of a WirelessGateway

Nortel UMTS RNC xxxx RNC xxxx RNC

Nortel Web Switch 184 Web Switch 184 Alteon Web Switch 184

Nortel Wireless NetworkManagement System

W-NMS Preside for WirelessInternet (PWI)

Wireless Provisioning System forAccess d

WPS for Access Offline Configuration forAccess Networks (OCAN)

a. May also have been referred to as Everest HLRb. May also have been referred to as HP SIGc. NIMS PrOptima is a sub-component of W-NMSd. WPS for Access is a sub-component of W-NMS

Table ivNew product names mapped to original name(s) (continued)

New Name Short Name Original Name(s)

sheet 2 of 2


24/160

xxiv About this documentNortel Confidential Copyright 20012005 Nortel



25/160

1-1Nortel Confidential Copyright 20012005 Nortel


Understanding backup and restore 1This document contains procedures for backup and restore of the following W-NMS servers: primary main server

secondary main server(s)

performance server(s) Software Repository Server (SRS)

Server of Client (SOC)

This chapter is divided into the following sections:

Backup and Restore overview on page 1-2

Backing up and restoring a regional operation center on page 1-4

Restrictions and Limitations on page 1-4

Prerequisites on page 1-6

ubvaClient theory of operation on page 1-6

Centralized backup and restore of Oracle database using RMAN utilityon page 1-7


26/160

1-2 Understanding backup and restoreNortel Confidential Copyright 20012005 Nortel


Backup and Restore overview 1The data on an OAM server is backed up using three types of backups. Eachtype of backup backs up different types of data. Depending on the type ofbackup, you can back up each server individually, using a local backup

procedure (local), or you can back up all servers from a central location, usingVERITAS NetBackup (centralized). Backups can be performed manually(manual) or they can be scheduled to run automatically (automatic). Thefollowing table summarizes the characteristics of each type of backup:

Table 1-1Types of backups

Type of backup Local orcentralized

System downtime

Data backed up a Recommendedfrequency

system databackup

local, manual

local, automatic(single tape only)

Approximately20-30 minutes,

while snapshotof data istaken.

Backup ofsnapshot isdone whilesystem isonline.

EEPROM variables

Metadata (Solaris VolumeManager Configurations)

File systems: /, /usr, /var,/ home, /opt, /opt/nortel(excluding /opt/nortel/logs)

Directories: /opt/nortel/ logs/3rd_party

Installation logs: /opt/ nortel/logs/iut_tools/*.log*

afterinstallation,

upgrade, orpatch on theserver

configurationdata backup

local, manual


centralized,automatic

centralized,manual

None.

Backup isperformedwhile systemis online. b

configuration data fornetwork elements and W-NMS, W-NMS systemmanagement data,software repository

weekly (andimmediatelybefore or after asystem databackup)


27/160

Understanding backup and restore 1-3Nortel Confidential Copyright 20012005 Nortel


The equivalent types of restores are also supported.

For detailed information and procedures about each type of backup or restore,refer to the other chapters in this document.

historical dataarchive


local, manual

centralized,automatic

centralized,manual

None.

Archive isperformedwhile systemis online.

HFB alarmsOAM stability dataNE-based stability dataCSALAudit Trail3GPP XML files

daily

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 .

Table 1-2Types of restores

Type of restore Local orcentralized

Online oroffline

Comments

system restore local offline must be followed by a configuration data restore

configurationdata restore

local

centralized

offline

historical dataretrieval

local

centralized

online with centralized data retrieval, you can retrievespecific files or directories

Table 1-1Types of backups

Type of backup Local orcentralized

System downtime

Data backed up a Recommendedfrequency


28/160



Backing up and restoring a regional operation center 1The backup and restore procedures are intended to be used to back up orrestore the data on all the servers in a single Regional Operating Center(ROC).

For a system backup, the Primary Main Server must be backed up first,followed immediately by a system backup of the other servers in the ROC.For a configuration data backup, back up all the servers in the ROC at thesame time.

When a configuration data backup or a system backup is running on theSecondary Main Server, do not run a system backup on the Primary MainServer. For the Secondary Main Server backup to run successfully, allapplications on the Primary Main Server must be up running (during aPrimary Main Server system backup, some of the applications on the PrimaryMain Server are stopped and restarted.)

When you restore one server in the ROC, you must restore all the servers inthe ROC. Restore the Primary Main and Secondary Main Servers first,followed by the other servers.

Performing backup and restore as recommended in this section ensures thatthe data in the ROC remains consistent.

Note: Only the servers listed at the beginning of this chapter aresupported for backup and restore. However, a ROC can contain otherservers in addition to the ones listed.

Restrictions and Limitations 1The following restrictions apply to W-NMS backup and restore. The restrictionsapply for both local backup and restore and centralized backup and restore usingVERITAS NetBackup 5.1. Only the standard W-NMS server configuration is supported for backup

and restore. Any deviation from the standard server configuration is notsupported. For information about the standard W-NMS serverconfiguration, see the W-NMS Engineering Guide , 450-3101-638.

System backup or restore is performed for all the components on a server.You cannot back up or restore an individual component in a system

backup. If any of the following operations are being performed and you attempt to

start a backup, the backup will fail. If a backup is running and you attemptto perform one of the operations, the operation will fail:

3GPP bulk configuration management

execution of wireless internet command language (WICL) scripts


29/160



import of a data request form (DRF) in the Access database

During a backup, the network time protocol (NTP) server is out ofservice. The NTP server is returned to service when the backupcompletes.

The W-NMS configuration data backup and the historical data archive areperformed 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 backupis running.

When a configuration data backup or a system backup is running on theSecondary Main Server, do not run a system backup on the Primary MainServer. For the Secondary Main Server backup to run successfully, allapplications on the Primary Main Server must be up running (During aPrimary Main Server system backup, some of the applications on thePrimary Main Server are stopped and restarted.).

The following information applies to local backup and restore:

the maximum length of the path to the directory or file to be backed up(including the file to be backed up) is 1023 characters

Table 1-3

CEM In the CEM, do not commission new network elements managed by the CEM. Do notset Dialed Digits, Threshold, Mass Export, or Customizable OM.

Network Services PlatformSUMBB

AccessControl

Do not modify network layouts or link edits.

Do not make changes to Access Control.

MDM Do not add, remove or change the connection to Passport or SNMP-based networkelements.

Nortel Wireless Network Management System (W-NMS)

Do not perform software installation, apply software patches, or perform softwareupgrades.

Do not update the software configuration.


30/160



Prerequisites 1Before performing the procedures in this document you must ensure that thebackup and restore package has been installed on each server to be backed upor 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 scriptsare 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 runningon each server to be backed up or restored. The backup and restore scriptscheck for this and ensure the correct process is running ( /etc/rc2.d/ S74xntpd).

ubvaClient theory of operation 1You use the ubvaClient utility to generate lists of backup paths for use increating VERITAS NetBackup backup policies for centralized backup andrestore (see procedure Procedure 5-4 and Procedure 5-5 .) You run it on a serverthat you want to backup, and it collects information about what applicationsare installed on the server, what files they need to have backed up, and generateslists of paths to the files. When you create backup policies, the backup andrestore solution will use these lists to determine what to back up. When yourun 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 andparses 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 policynames 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 addto the UNIX backup policy

b. backup_ORACLE - this file is created only on a Performance serverinstalled with NIMS-PrOptima and contains the path to the Oraclebackup script. You add this path to the Oracle policy.

c. backup_USER - this file is created only on a Performance serverinstalled with NIMS-PrOptima. It is empty, and its presence indicatesthat a User backup policy needs to be configured.


31/160



d. classNames - this file contains the policy names you specified in point5.

e. clientOS - this file contains the Solaris OS version running on theserver.

7. Creates symbolic links to scripts that NetBackup uses to back up theserver 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. to /opt/nortel/shell/backup/veritas/centralarchive.sh

d. /usr/openv/netbackup/bin/bpend_notify. to /opt/nortel/shell/backup/veritas/postcentralarch.sh

Centralized backup and restore of Oracle database using RMANutility 1

Starting in OAM 4.2, users can customize Centralized (VERITAS) Backupand Restore to back up the HFB Oracle database using the Oracle RMANutility. The user must define a corresponding Oracle policy on the VERITASNetBackup server.

In addition, since this new feature is not currently compatible withCentralized Historical Data Archive and Retrieval, the user must disableHistorical Data Archive and Retrieval. The user then must define additionalbackup policies to back up the other historical data that would otherwise havebeen backed up by the Historical Data Archive and Retrieval feature, asappropriate. Historical data archive in Appendix B: Data backed up provides a complete list of the data backed up by Historical Archive Data andRetrieve.

Since this feature applies only to servers supported with Centralized backupand restore, there is no conflict with Historical Data Archive and retrievalprocess on servers that are supported only with Local Backup and Restorefeatures.

Chapter 6, Performing centralized backup and restore with no archivepolicyRMAN used for HFB Oracle database provides a completeoperations reference for use with the RMAN feature.


32/160




33/160



Performing system backup and restore 2This chapter describes the system backup and system restore. It containsprocedures for backing up the system data or restoring the system data underthese headings:

System backup on page 2-1

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

System restore on page 2-5

Restoring a system on page 2-5

Booting to single user mode on a Sun Fire 4800 server on page 2-8

Booting to single user mode on a Sun Fire E4900 server on page 2-10

Booting to single user mode on page 2-12

Enabling the disk array (Sun Fire 4800) on page 2-13

Enabling the disk array (Sun Fire E4900) on page 2-15

System backup 2A system backup backs up the disk layout and file system information for allpartitions, operating systems, application programs, and directory structures.A system restore restores the same data. For a complete list of directories andfiles backed up or restored, see System data backup in Appendix B: Databacked up .

A system backup minimizes the amount of time that a server is out of serviceby taking a snapshot of the data to be backed up while the serverapplications are offline. The applications are restarted and then a backup ofthe snapshot data is performed. The time to complete the backup isapproximately two hours, with the server being out of service for 20 to 30


34/160


35/160

Performing system backup and restore 2-3Nortel Confidential Copyright 20012005 Nortel


Backing up a system manuallyPerform this procedure to back up the system on a server manually.

Requirements

Before performing this procedure, you must: perform a configuration data backup either immediately before orimmediately after the system backup

ensure that the server is online

have DDS-4 tape(s) ready to store the backup data

Note: To reduce tape read/write or input/output errors during backup orrestore, follow the manufacturers maintenance guidelines for your tapesand tape drives. For example, do not use magnetic tapes beyond theirrecommended life expectancy and clean tape drives regularly.

know the password for the nortel user and the root user

read and comply with the prerequisites section in Chapter 1,Understanding backup and restore

Procedure 2-1Backing up a system manually

Step Action

1 Log onto the server you are backing up as nortel (or some other normaluser), start a terminal session and then become the root user by entering

su -

2 Insert a tape into the tape drive of the server.

3 Enter:

localSysDump

4 If the tape is blank, the backup starts.

If the tape is not blank, you are prompted to confirm that the backup willoverwrite any data currently on the tape. The backup will not start untilyou confirm (Y).

5 If the data to be backed up takes up more than one tape, you are

prompted to insert another tape.

6 Review the log file in the /usr/local/nortel/tools/log directory to make surethat the backup completed successfully.

7 End of procedure.


36/160

2-4 Performing system backup and restoreNortel Confidential Copyright 20012005 Nortel


Backing up a system automaticallyThis procedure explains how to modify the crontab file to schedule a systembackup to run automatically at regular intervals.

Restrictions for automatic backupThe following restrictions apply to an automatic backup: The data to be backed up must fit on one DDS-4 tape. If the data does not

fit on one tape, the backup fails and an error message is logged.

Before the backup is scheduled to run, you must ensure that there is a tapein the tape drive of the server to be backed up. If there is no tape in thetape drive at the time the backup runs, the backup fails writes an errormessage to the log file.

RequirementsBefore performing this procedure, you must be familiar with the UNIX crontabutility.

Procedure 2-2Backing up a system automatically

Step Action


su -

2 Copy the crontab file to a temporary file. For example,

crontab -l > /tmp/tempcrontab

3 Add a line to the temporary file that schedules the system backup. Thefollowing example schedules a system backup to run at 3:15 everyMonday:

15 3 * * 1 /usr/bin/localSysDump -s > /dev/null 2>&1

4 Make the temporary file the crontab file. Example:

crontab /tmp/tempcrontab

5 Delete the temporary file.

The backup will run according to the schedule you have defined in thecrontab file. Before the backup runs, ensure that you have complied withthe restrictions described in the section titled Restrictions for automaticbackup .

6 End of procedure.


37/160



System restore 2A system restore restores the operating system and application executables tothe server. A system restore is performed manually and the server is offlinewhile it runs.

The electronically erasable programmable read-only memory (EEPROM)settings are backed up when the system is backed up. When the system isrestored, the settings are written to /usr/local/nortel/tools/cfg/EEPROM. Therestore modifies the BOOT-DEVICE setting in EEPROM as part of therestore process. All other settings in the file are identical to those in theEEPROM, so you can read the file to review the EEPROM settings.

After you perform a system restore, you must perform a configuration datarestore to ensure that the applications are fully functional. See Chapter 3,Performing configuration data backup and restore for more information. Ifyou want to restore historical data, you can also perform an historical dataretrieval. See Chapter 4, Performing historical data archive and retrieval .

Restoring a systemPerform this procedure to restore the system on a server. A system restoreconsists of the following steps: restore the operating system file systems

reboot the server

mirror the disks

reboot the server

restore the application file systems restore application data (configuration data restore)

RequirementsBefore 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

Have Solaris operating system CD-ROM available

know the password for the root user


38/160



Procedure 2-3Restoring a system

Step Action

1 If you are working on a Sun Microsystems Sun Fire 4800 server, performProcedure 2-4 . If you are working on a Sun Microsystems Sun Fire E4900server, perform Procedure 2-5 . If you are working on any other type ofserver, perform Procedure 2-6 .

2 Insert the tape into the tape drive of the server.

3 Enter:

cd /

cpio -idI /dev/rmt/0n

Note: In the previous command, the last character in the text string idIis an upper case i.

4 Enter:

cd /tmp/backup/tools/bin

./localSysRestore.sh [-HVh] [-t ]

where -V displays the version of the tool-h causes the usage to be displayed-H displays detailed usage for the command.-t specifies the tape drive that contains the tape (if

you do not specify the -t option, the command will restore fromtape device /dev/rmt/0n)

5 If you are working on a Sun Microsystems Sun Fire 4800 server:

The script returns to the command line prompt.

a. Enter:

init 0

The OBP prompt appears:

{0} ok

b. Enable the disk array.See Procedure 2-7 for SF4800 or Procedure 2-8 for the SFE4900.

6 If you are working on any other type of ser ver:

The server reboots.


39/160



7 At this point, the meta devices are being configured.8 Wait for the following message to appear:

Type control-d to proceed with normal startup, (orgive the root password for system maintenance)

9 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 isOkay .

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 messageappears:

Mount volume 2

If this message appears:

a. Eject the tapeb. Put the next tape in the tape drive

c. Press the key

The data restore continues. When the restore is complete , the followingmessage appears; do NOT enter control-d :


13 Do NOT enter control-d. Enter the password for the root user.

14 Review the log file in the /usr/local/nortel/tools/log directory to make surethat the restore completed successfully.

15 Perform a configuration data restore starting from step 5 of procedureProcedure 3-3 .

16 End of procedure.

Procedure 2-3Restoring a system

Step Action


40/160



Booting to single user mode on a Sun Fire 4800 serverThis procedure is referenced in Procedure 2-3 . It disables the disk array of theSun Fire 4800 server and then boots the server to single user mode. If you areworking on a server that is not a Sun Fire 4800, see Procedure 2-5 (Sun Fire

E4900) or Procedure 2-6 (other types of servers).RequirementsBefore performing this procedure, you must: know the password for the root user

know the IP address of the Sun Fire 4800 System Controller

Procedure 2-4Booting to single user mode on a Sun Fire 4800 server

Step Action

1 Connect to the System Controller of the Sun Fire 4800 server fromanother host. Enter:

telnet

where is the IP address of the Sun Fire 4800 SystemControlle r

A list of valid values is displayed and the following prompt appears:

Input:

2 Enter:

0

The following prompt appears:

SChostname:SC>

3 Enter:

cons a

4 Enter:

init 0


{0} ok

5 Enter:

setenv auto-boot? false


41/160



6 Press the Ctrl key and then press the ] key. This key sequence returnsyou to the telnet session.

7 Enter the following commands:

send brk

setkeyswitch off

disc

disable /N0/IB6/P0/B0/C3


console a

setkeyswitch on

These commands disable the disk array.

8 Insert the Solaris operating system compact disc into the CD-ROM drive.

9 Enter:

setenv diag-switch? true

boot cdrom -rs


Procedure 2-4Booting to single user mode on a Sun Fire 4800 server

Step Action


42/160



Booting to single user mode on a Sun Fire E4900 serverThis procedure is referenced in Procedure 2-3 . It disables the disk array of theSun Fire E4900 server and then boots the server to single user mode. If you areworking on a server that is not a Sun Fire E4900, see Procedure 2-4 for a Sun

Fire 4800 server and Procedure 2-6 for all other types of servers.RequirementsBefore performing this procedure, you must: know the password for the root user

know the IP address of the Sun Fire E4900 System Controller

have the Solaris 8 02/04 special CDROM for the SFE4900

Procedure 2-5Booting to single user mode on a Sun Fire E4900 server

Step Action

1 Connect to the System Controller of the Sun Fire E4900 server fromanother host. Enter:

telnet

where is the IP address of the System Controlle r


Input:

2 Enter:

0


SChostname:SC>

3 Enter:

cons a

4 Enter:

init 0


{0} ok



43/160



6 Enter the following commands:send brk



These commands disable the disk array.

7 Insert the Solaris 8 02/04 operating system compact disc into the CD-ROM drive.Note: This CD is mandatory to boot on an SFE4900 for this version.

8 Enter the following command:resume


{0} ok

9 Enter the following command:

boot cdrom -rs

Message: Type control-d to proceed with normal startup, (or give theroot password for system maintenance).


Procedure 2-5Booting to single user mode on a Sun Fire E4900 server

Step Action


44/160



Booting to single user modeThis procedure is referenced in Procedure 2-3 . Perform it when you are workingon a server that is not a Sun Fire 4800. If you are working on a Sun Fire 4800or E4900 server, use Procedure 2-4 (4800) or Procedure 2-5 (E4900), for the

appropriate serverRequirementsBefore performing this procedure you must: know the password for the root user

have the Solaris operating system compact disc

Procedure 2-6Booting to single user mode

Step Action

1 Log onto the server using the root user.2 Enter:

init 0


{0} ok

3 If the server you are working on is a Sun E4500, enter:

setenv sbus-probe-default 3120

4 Insert the Solaris operating system compact disc into the CD-ROM drive.

5 Enter:

setenv diag-switch? true

boot cdrom -rs

The following message appears:

INIT:SINGLE USER MODE

6 End of procedure.


45/160



Enabling the disk array (Sun Fire 4800)This procedure is referenced in Procedure 2-3 . This procedure is onlyapplicable for a Sun Fire 4800.

RequirementsBefore performing this procedure, you must: know the password for the root user

know the IP address of the Sun Fire 4800 System Controller

Procedure 2-7Enabling the disk array for the Sun Fire 4800

Step Action

1 Connect to the System Controller of the Sun Fire 4800 server from

another host.2 Enter:

telnet

where is the IP address of the Sun Fire 4800 SystemControlle r


Input:

3 Enter:

0


SChostname:SC>

4 Enter:

cons a

5 Enter:

init 0


{0} ok

6 Enter:

setenv auto-boot? false


46/160




8 Enter the following commands:

send brk

setkeyswitch off

disc

enable /N0/IB6/P0/B0/C3


console a

setkeyswitch on

These commands enable the disk array.

9 Enter:

setenv auto-boot? true

boot -rs


Procedure 2-7Enabling the disk array for the Sun Fire 4800

Step Action


47/160



Enabling the disk array (Sun Fire E4900)This procedure is referenced in Procedure 2-3 . This procedure is onlyapplicable for a Sun Fire E4900.

RequirementsBefore performing this procedure, you must: know the password for the root user

know the IP address of the Sun Fire E4900 System Controller

Procedure 2-8Enabling the disk array for a Sun Fire E4900

Step Action

1 Connect to the System Controller of the Sun Fire E4900 server from

another host.2 Enter:

telnet

where is the IP address of the System Controlle r

A list of vali d values is displayed and the following prompt appears:

Input:

3 Enter:

0


SChostname:SC>

4 Enter:

cons a

5 Enter:

init 0


{0} ok



48/160



7 E nter the following commands:send brk



These commands enable the disk array.


resume


{0} ok


boot -rs

The following message appears:


10 Enter the password for the root user.


Procedure 2-8Enabling the disk array for a Sun Fire E4900

Step Action


49/160



Performing configuration data backupand restore 3

A configuration data backup backs up the configuration data and the softwarerepository. A configuration data restore restores the configuration data and thesoftware repository.

A configuration data backup is performed while the server is online. Aconfiguration data restore is performed while the server is offline.

This chapter contains procedures for the following:

Backing up configuration data on page 3-2

Backing up configuration data manually on page 3-2

Backing up configuration data automatically on page 3-5

Restoring configuration data on page 3-6

For a complete list of directories and files backed up or restored, seeConfiguration data backup in Appendix B: Data backed up .

You can perform a configuration data backup or restore in two ways: on each server, using the procedures in this document (known as local

backup and restore)

from a backup and restore server, using VERITAS NetBackup 5.1 (knownas centralized backup and restore, for more information, see Chapter 5,Performing centralized backup and restore with an archive policy )

RESTRICTIONS AND LIMITATIONSFor information about restrictions and limitations when performingconfiguration data backup or restore, refer to the section titledRestrictions and Limitations in Chapter 1.


50/160

3-2 Performing configuration data backup and restoreNortel Confidential Copyright 20012005 Nortel


Backing up configuration data 3

Backing up configuration data manuallyUse Procedure 3-1 to back up the configuration data on each of the servers inthe regional operation center (ROC). For details about which files, directories,and databases are backed up, see Configuration data backup in AppendixB: Data backed up .

RequirementsWhen backing up the configuration data for a server, you must back up thedata for all servers in the ROC at the same time. You must perform the backupprocedure on each server in the ROC. This maintains the consistency andintegrity of the data throughout the ROC.

Before performing this procedure you must: Have a blank DDS-4 tape ready to store the backup data. You can also use

a tape that has data on it and overwrite it.Note: To reduce tape read/write or input/output errors during backup orrestore, follow the manufacturers maintenance guidelines for your tapesand tape drives. For example, do not use magnetic tapes beyond theirrecommended life expectancy and clean tape drives regularly.

Read and comply with the prerequisites section in Chapter 1,Understanding backup and restore .

Know the password for the nortel and root users on the server.

If you try to run a configuration data backup while acentralized configuration data backup is running (see Chapter5, Performing centralized backup and restore with an archivepolicy ), both backup operations will fail and the data will notbe backed up.


51/160

Performing configuration data backup and restore 3-3Nortel Confidential Copyright 20012005 Nortel


Procedure 3-1Backing up configuration data

Step Action


su -

2 Insert a blank tape into the tape drive of the server.

3 Enter:

localbackup [-d ] [-m ] [-t ]

The square brackets [] indicate options. See Table 3-1 for descriptions ofthe options. You can also enter localbackup [-h] [-H] in the commandline to see the valid options and their definitions.

4 If the tape is blank, the backup starts. Go to step 9 .

5 If the tape is not blank, the following message is displayed:

All data on this tape will be overwritten should you continue with thebackup.

6 The following prompt displays:

Do you wish to continue? [yes]

7 If you want to continue with the backup, press the Enter key. Go to step 9 .

8 If you want to abort the backup, enter:

no

The backup aborts and the script completes.

End of procedure.

9 The system displays the log information as the backup progresses. Afterthe backup is complete, the name of the log file and the label of the tapeare 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



52/160



Table 3-1options definitions for backing up configuration data

parameter value

-d Delay the backup by . is a valuebetween 3 and 60 that indicates the amount of time to wait inminutes before performing the backup.

If this option is not specified, the default delay is three minutes.

-h or -H displays help information about the command. Cannot becombined with other options.

-m

Display the to users. is textstring that is sent out as a message before the backup starts inaddition to the default message Data backup will start in xminutes. The message is sent to NSP clients and currently

logged-in consoles.

Specify the message text inside double quotation marks. Forexample, Please do not use WICL. This will cause themessage Data backup will start in x minutes. Please do notuse WICL. to be sent to logged-in consoles.

-t Write the backup to .

If this option is not specified, the command will use the tapedevice /dev/rmt/0n.

-s Use only with scheduled operations. If the backup requires

more than one tape, the script will write an error message tothe log file and quit immediately. If the tape drive is emptywhen the operation starts, the script will write an errormessage to the log file and quit immediately.


53/160



Backing up configuration data automaticallyThis procedure explains how to modify the crontab file to schedule aconfiguration data backup to run automatically at regular intervals.

Restrictions for automatic backupThe following restrictions apply to an automatic backup: The data to be backed up must fit on one DDS-4 tape. If the data does not

fit on one tape, the backup fails and an error message is logged.

Before the backup is scheduled to run, you must ensure that there is a tapein the tape drive of the server to be backed up. If there is no tape in thetape drive at the time the backup runs, the backup fails and the applicationwrites an error message to the log file.

RequirementsBefore performing this procedure, you must be familiar with the UNIX crontabutility.

Procedure 3-2Backing up configuration data automatically

Step Action


su -

2 Copy the crontab file to a temporary file. For example,crontab -l > /tmp/tempcrontab

3 Add a line to the temporary file that schedules the configuration databackup. The following example schedules a configuration data backup torun at 3:15 every Monday:

15 3 * * 1 /usr/bin/localbackup -s > /dev/null 2>&1

4 Make the temporary file the crontab file. Example:

crontab /tmp/tempcrontab

5 Delete the temporary file.

The backup will run according to the schedule you have defined in thecrontab file. Before the backup runs, ensure that you have complied withthe restrictions described in the section titled Restrictions for automaticbackup .

6 End of procedure.


54/160



Restoring configuration data 3

This procedure restores the configuration data for a server.

RequirementsIf you want to restore the configuration data to a server within the ROC, youmust restore the configuration data to all the servers in the ROC. That is, youmust perform this procedure on each server in the ROC. Restore the PrimaryMain and Secondary Main Servers first, followed by the other servers. Thismaintains the consistency and integrity of the data throughout the ROC.

Before performing this procedure you must: read and comply with the prerequisites section in Chapter 1,


have the tape(s) that contain the data you want to restore

know the password for the nortel user know the password for the root user

Procedure 3-3Restoring configuration data

Step Action

1 Log onto the server as nortel.

Stopping the server processes

2 In a terminal window command line, enter:

/opt/nortel/shell/sysmgt/wam_stopall.sh

All processes on the server are stopped.

Note: You can also use the Sun Management Center (SMC) to stop allprocesses on the server. For more information refer to Preside forWireless Internet System Management , 411-8111-538.

3 Enter:

su - root

sheet 1 of 3


55/160



4 If you are working on the primary main server, enter:/opt/SUNWsymon/sbin/es-stop -A

If you are working on a Sun Fire 4800 or E4900 that is the secondarymain or performance server, enter:

/opt/SUNWsymon/sbin/es-stop -al

For all other server types, enter:

/opt/SUNWsymon/sbin/es-stop -a

The SMC and other processes are stopped.

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

data restore, the sub-mirrors are not yet attached at this point.

5 Insert the backup tape that contains the data you want to restore into thetape drive of the server. If the data is contained on more than one tape,insert the first tape.

6 If you want to verify the label on the tape, in a terminal window commandline enter:

localrestore -l [-t ]

The label of the tape is displayed.

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

7 Enter:

localrestore [-t ]

Note: The square brackets [ ] indicate options. See Table 3-2 fordescriptions of the options. You can also enter localrestore [-h] [-H] inthe command line to see the valid parameters and their definitions.

If the tape does not have a label the script reports an error andterminates. Otherwise, the restore starts.

If a system restore was performed immediately prior to this local datarestore, the mirrored disks will be attached and the root par tition will now

be synchronized. The screen will display the progress of the root partitionsynchronization. Wait for the operation to complete and for the commandprompt to reappear.

Procedure 3-3 (continued)Restoring configuration data

Step Action

sheet 2 of 3


56/160



8 Verify that the restore completed successfully by reviewing the contents ofthe log file. Enter:

more /opt/nortel/logs/backup/restore.log

Starting the server processes

9 Reboot the server. Enter:

init 6

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

10 Log in to the server as the root user.

11 From the command line interface, enter:su - nortel -c /opt/nortel/shell/sysmgt/wam_startall.sh -a

Note: You can also use the SMC to start all processes on the server. Formore information refer to Preside for Wireless Internet SystemManagement , 411-8111-538.

12 Before performing the next step:

a. Make sure that all applications (except possibly the HFB Oracledatabase) are up and running; on servers with an HFB Oracledatabase, the database may be running or stopped for this step.

b. Make sure that you are the root user.

13 Enter:

postDataRestore

If you are working on the main server, this command rebuilds the HFBOracle database and JavaHelp if they are corrupt. If you are working onany other server, this command deletes and cleans up temporary filesused during the restore process. The logs for this process are written to / opt/nortel/logs/backup/postDataRestore.log


Procedure 3-3 (continued)Restoring configuration data

Step Action

sheet 3 of 3


57/160


58/160




59/160



Performing historical data archive andretrieval 4

A historical data archive backs up the Historical Fault Browser (HFB) alarms,3rd Generation Partnership Project (3GPP) extensible markup language(XML) files, Centralized Security Audit Logging (CSAL) data, W-NMS andNE Stability Analysis data, and other data that is not essential to the day today OAM processes. For a complete list of directories and files backed up,see Appendix B: Data backed up . A historical data archive or retrieval isperformed while the server is online.

This chapter contains the following sections:

Archiving historical data locally on page 4-2

Archiving historical data automatically on page 4-5

Retrieving historical data locally on page 4-7

There are two ways to perform an historical data archive or retrieval: on each server, using the procedures in this document (known as local

historical data archive or retrieval)

from a backup and restore server, using VERITAS NetBackup 5.1(Known as centralized historical data archive or retrieval. See Chapter 5,Performing centralized backup and restore with an archive policy )


60/160

4-2 Performing historical data archive and retrievalNortel Confidential Copyright 20012005 Nortel


Archiving historical data locally 4

Use this procedure to archive the historical data on an individual server.

RequirementsBefore performing this procedure you must: Have a blank DDS-4 tape ready to store the backup data. You can also use

a tape that has data on it and overwrite it.

Note: To reduce tape read/write or input/output errors during backup orrestore, follow the manufacturers maintenance guidelines for your tapesand tape drives. For example, do not use magnetic tapes beyond theirrecommended life expectancy and clean tape drives regularly.

Read and comply with the prerequisites section in Chapter 1,Understanding backup and restore .

Know the password for the nortel and root users on the server

If you try to archive data while a centralized data archive isrunning (see Chapter 5, Performing centralized backup andrestore with an archive policy ), both archive operations willfail and the data will not be archived.

Procedure 4-1Archiving historical data locally

Step Action

1 Log onto the server you are backing up as nortel (or some other normaluser), start a console session and then become the root user by entering

su -

2 Insert a tape into the tape drive of the server.

3 Enter:

localarchive [-h|H] [-d ] [-D ] [-t ]See Table 4-1 for definitions of the options and parameters. If you do notspecify any options, all historical data for the previous day is archived.


61/160

Performing historical data archive and retrieval 4-3Nortel Confidential Copyright 20012005 Nortel


4 If the tape is blank, the backup starts. Go to step 8 .5 If the tape is not blank, the following message is displayed:

All the data on this tape will be overwritten should you continue withthe backup.

The following prompt displays:

Do you wish to continue? [yes]

6 If you want to continue with the backup, press the Enter key and go tostep 8 .

7 If you want to abort the backup, enter:

no

The backup aborts and the script completes.

8 If the data to be backed up takes up more than one tape, you areprompted to insert another tape.

9 Review the log file /opt/nortel/logs/backup/ar/archive.log to make sure thatthe archive completed successfully. If you did not specify a log file namein step 3 , the log file is named archive.log.


Table 4-1option and parameter definitions for localarchive command

parameter value

-h or -H Display help information about the command - cannot becombined with other options

-d Archive data for a day or days prior to today (maximum of 4days of data.) Cannot be combined with the -D option.

If n is specified, data from the current day - n is archived. Forexample, to archive data from the day before yesterday,specify n = 2.

If n:m is specified, data between the previous nth day andmth day is archived. m must be greater than or equal to n. Forexample, if the current date is January 10 and you want toarchive data from January 4 - 7 inclusive, specify 3:6.

sheet 1 of 2

Procedure 4-1Archiving historical data locally

Step Action


62/160



-D

Archive data for a specific date or range of dates (maximumof 4 days of data.) Cannot be combined with the -d option.

If YYYYMMDD is specified, all historical data for the dateYYYYMMDD is archived. For example, to archive data onDecember 27, 2003, specify 20031227.

If YYYYMMDDa :YYYYMMDDb is specified, all historical databetween the two dates is archived. YYYYMMDD b must begreater than YYYYMMDD a and the dates must span 4 orfewer days.

-t Write the backup to tape device .

is the name of the tape device.

If the -t option is not specified, the command assumes thetape device is /dev/rmt/0n.

-s Use only with scheduled operations. If the backup requiresmore than one tape, the script will write an error message tothe log file and quit immediately. If the tape drive is emptywhen the operation starts, the script will write an errormessage to the log file and quit immediately.

Table 4-1 (continued)option and parameter definitions for localarchive command

parameter value

sheet 2 of 2


63/160


64/160



5 Delete the temporary file.The archive will run according to the schedule you have defined in thecrontab file. Before the archive runs, ensure that you have complied withthe restrictions described in the section titled Restrictions for automaticarchive .

6 Check the log file /opt/nortel/logs/backup/ar/archive.log following everyscheduled archive operation to ensure that the operation completedwithout errors.

7 End of procedure.

Procedure 4-2Archiving historical data automatically

Step Action


65/160

Performing historical data archive and retrieval 4-7Nortel Confidential Copyright 20012005 Nortel


Retrieving historical data locally 4

Use this procedure to retrieve the historical data for an individual server.

RequirementsBefore performing this procedure you must: read and comply with the prerequisites section in Chapter 1,


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-3Retrieving historical data locally

Step Action

1 Log onto the server you are backing up as nortel (or some other normaluser), start a console session and then become the root user by entering

su -

2 Insert the tape into the tape drive of the server. If there is more than onetape, insert the first one.

3 Enter:

localretrieve [-h|H] [-f] [-l] [-a mod1:mod2:...:modN] [-D ] [-t ]

See Table 4-2 for definitions of the options parameters. If you do notspecify any options, all historical data on the tape is retrieved.

4 If the data to be retrieved spans more than one tape, you are prompted toinsert the next tape.

5 Review the log file /opt/nortel/logs/backup/ar/retrieve.log to make surethat the retrieve completed successfully. If you did not specify a log filename in step 3 , the log file is named retrieve.log.

6 End of procedure.


66/160



Table 4-2parameter definitions for localretrieve command

parameter value

-h or -H Display help information about the command. Cannot becombined any other options.

-f Perform an automatic purge if there is not enough disk space toperform the retrieval.

If this parameter is not specified, and there is not enough diskspace to store the retrieval data, during the execution of theretrieval a message will be displayed, with a choice to eitherpurge the data that currently exists on the disk or to abort theretrieval.

-l Display the tape label. Can be used alone or in combination

with the -t option. l is a lower case L, not an uppercase i.-a mod1:mod2:...modN

retrieve only the data for modules listed. If this option is notspecified, data for all modules on the tape is retrieved.

Example: cdi:gdi:mycom

See Table B-11 for a list of possible values.

-D

Retrieve data for a specific date or range of dates (maximum of4 days of data.) If this option is not specified, all data archivedon the tape is retrieved.

If YYYYMMDD is specified, all historical data for the dateYYYYMMDD is retrieved. For example, to retrieve data onDecember 27, 2003, specify 20031227.

If YYYYMMDDa :YYYYMMDDb is specified, all historical databetween the two dates is retrieved. YYYYMMDD b must begreater than YYYYMMDD a and the dates must span 4 or fewerdays.

-t Use the tape device . is the name ofthe tape drive. If this option is not specified, the commandassumes that the tape device is /dev/rmt/0n.


67/160



Performing centralized backup andrestore with an archive policy 5

This chapter contains information about using VERITAS NetBackup 5.1 toperform backup and restore of the W-NMS servers. The procedures do notprovide instructions about how to install or use VERITAS NetBackup.

This chapter includes the following topics:

Configuring NetBackup on page 5-4

Installing the UNIX NetBackup Client on page 5-5

Installing the VERITAS NetBackup Oracle agent on page 5-6

Creating backup path files on page 5-7

Configuring policies on page 5-9

Upgrading a VERITAS NetBackup server from OAM 3.x to OAM 4.xon page 5-13

Backing up configuration data manually on page 5-14

Archiving historical data manually on page 5-14

Restoring a server using VERITAS NetBackup on page 5-15

Retrieving historical data on page 5-22

Use this section if you plan to configure a centralized Archive

policy to archive historical data.If you have your own backup policy to back up the historicaldata or the file systems, refer to Performing centralizedbackup and restore with no archive policyRMAN used forHFB Oracle database instead.


68/160

5-2 Performing centralized backup and restore with an archive policyNortel Confidential Copyright 20012005 Nortel


Before performing the procedures in this chapter you must ensure that theserver that has the VERITAS NetBackup server software installed cancommunicate with all the servers you want to back up. Refer to the VERITASdocumentation for more information.

For more information about VERITAS NetBackup, refer to the followingVERITAS documents: VERITAS NetBackup 5.0 System Administrators Guide Volume I for

UNIX , N10238B

VERITAS NetBackup 5.0 System Administrators Guide Volume II forUNIX , N10239B

VERITAS NetBackup 5.0 Users Guide for UNIX , N10262B

VERITAS NetBackup 5.1 for Oracle System Administrators Guide forUNIX , N12320B

VERITAS NetBackup 5.1 Installation Guide for UNIX , N12358B

VERITAS NetBackup Performance Tuning for UNIX Platforms

Before performing the procedures in this chapter you must be familiar with andknow how to perform the following tasks using VERITAS NetBackup: create and configure a policy

back up the data on a server

restore the data to a server

monitor NetBackup activity

WARNING:Only VERITAS NetBackup version 5.1 has been tested withthe following procedures. Other versions may interactdifferently with the backup and restore scripts.

RESTRICTIONS AND LIMITATIONSFor information about restrictions and limitations when performingcentralized backup or restore, refer to the section titled Restrictions and

Limitations in Chapter 1.


69/160

Performing centralized backup and restore with an archive policy 5-3Nortel Confidential Copyright 20012005 Nortel


The procedures in this chapter explain: how to create backup path files for the W-NMS servers

how to configure policies for the W-NMS servers

how to configure the UNIX NetBackup Client and Oracle agent how to perform a backup or a restore of a W-NMS server

The following table shows the procedures that are applicable for each server:

Table 5-1Procedures to perform by server

Server

Procedure VeritasNetBackup a

a. This is the server that has the VERITAS NetBackup Data Center software installed.

Main Server Performance SRS SOC

Primary Secondary

Configure NetBackupProcedure 5-1

X

Install UNIX NetBackup Client bProcedure 5-2

b. See the procedure for information about when to perform this procedure.

X X X X X

Install Oracle agent cProcedure 5-3

c. See the procedure for information about when to perform this procedure.

X

Create backup path fileProcedure 5-4

X X X X X

Configure policiesProcedure 5-5 X

Back up a server Performed automatically by NetBackup

Back up a server manually See Backing up configuration data manually in this chapter

restore a server

Stop

W-NMS Backup and Restore User Guide

Documents

Transcript of W-NMS Backup and Restore User Guide