Vous êtes sur la page 1sur 203
Nokia Networks WCDMA RAN, Rel. WCDMA 16, Operating Documentation, Issue 03 Administering OMS DN70339432 Issue 10A

Nokia Networks

WCDMA RAN, Rel. WCDMA 16, Operating Documentation, Issue 03

Administering OMS

DN70339432

Issue 10A Approval Date 2015-10-30

Administering OMS

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2016 Nokia Solutions and Networks. All rights reserved.

f

Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional information.

Administering OMS

Table of Contents

This document has 203 pages

 

Summary of

9

1

Backup and

11

  • 1.1 Backup and restore in

11

  • 1.2 Preparing for the backup of databases in

15

  • 1.3 Making a full software backup in OMS.........................................17

  • 1.4 Making a partial software backup in OMS....................................21

  • 1.5 Making a custom software backup in OMS..................................23

  • 1.6 Transferring the backup archive file from OMS to an external storage

server..............................................................................

26

  • 1.7 Creating a self-contained USB rescue stick.................................27

  • 1.8 Restoring the whole system in OMS with self made full backup

archive and USB rescue

29

  • 1.9 Restoring databases in

34

  • 1.10 Restoring LDAP directory of

36

  • 1.11 Restoring a single file or directory in OMS...................................37

  • 1.12 Backup of OMS fails.....................................................................39

  • 1.13 Restoring of database in OMS fails..............................................41

  • 1.14 Restoring of LDAP directory of OMS

fails....................................

43

  • 1.15 Restoring of system image, single file, or directory in OMS fails.....
    45

 

47

2

Parameter

49

  • 2.1 introduction.........................................................

Parameter Tool

49

  • 2.2 Browsing configuration

50

  • 2.3 Modifying configuration data objects............................................51

  • 2.4 Modifying attributes of configuration data objects........................54

    • 3 User management........................................................................57

  • 3.1 Introduction to user

57

  • 3.2 Management of user accounts.....................................................57

  • 3.3 User account

60

  • 3.4 Internal LDAP user management.................................................61

  • 3.5 Command line interface for internal LDAP user management.....61

  • 3.5.1 Creating user accounts with

61

  • 3.5.2 Modifying user accounts with

64

  • 3.5.3 Deleting user accounts with CLI...................................................67

  • 3.5.4 Creating user groups with CLI......................................................67

  • 3.5.5 Deleting user groups with

68

  • 3.5.6 Administering user-group mappings with

70

  • 3.5.7 Administering group-permission mappings with

71

Administering OMS

  • 3.5.8 Dumping service account data with CLI.......................................75

  • 3.5.9 Generating a random password with CLI.....................................76

  • 3.5.10 Changing passwords for user

77

  • 3.5.11 mapping...............................................................................

MMI

79

3.6

Credential service

79

  • 3.6.1 Checking the password of a

79

  • 3.6.2 Setting the password for a credential...........................................80

  • 3.6.3 Changing the ownership of a credential.......................................82

  • 3.6.4 credential..................................................................

Restoring a

84

  • 3.6.5 credential....................................................................

Deleting a

85

3.7

Centralized User Authentication and Authorization......................86

  • 3.7.1 CUAA...................................................................

Introduction to

86

  • 3.7.2 CUAA replicator command line interface

87

  • 3.7.3 CUAA............................................................................

Enabling

90

  • 3.7.4 CUAA...........................................................................

Disabling

91

  • 3.7.5 Enabling and disabling CUAA automatic

92

  • 3.7.6 CUAA.................................................................

TLS support for

92

  • 3.7.7 CUAA related internal LDAP

93

3.8

Defining group permission restrictions for OMS Element Manager

 

93

  • 3.8.1 Creating users group....................................................................97

  • 3.8.2 Adding group to permission object in LDAP.................................97

  • 3.8.3 Creating new

98

  • 3.8.4 Usage...........................................................................................98

3.9

Changing SSH session inactivity time-out with

99

4

Certificate

100

4.1

Certificate

100

  • 5 License Management.................................................................101

    • 5.1 License management.................................................................101

  • 5.2 file..................................................................

Importing license

103

  • 5.3 file..................................................................

Exporting license

104

  • 5.4 file....................................................................

Deleting license

105

  • 5.5 Activating network element

105

  • 5.6 Deactivating network element feature........................................106

  • 5.7 Querying the status of a network element

107

  • 5.8 licenses......................................................................

Listing all

108

  • 5.9 Querying license information......................................................109

6

Data

111

  • 6.1 MySQL support...........................................................................111

  • 6.2 Collecting MySQL log files in OMS.............................................112

  • 6.3 Monitoring MySQL mount

points................................................

113

  • 6.4 LDAP directory and parameter management.............................117

    • 6.4.1 Parameter management.............................................................117

    • 6.4.2 Management object

model.........................................................

118

Administering OMS

6.4.3

LDAP

121

7

CORBA naming service in

123

CORBA naming

  • 7.1 service.............................................................

123

  • 7.2 Naming service is not functioning

125

8

Log

128

  • 8.1 Logging process in OMS............................................................128

  • 8.2 OMS...........................................................................

Syslog in

132

  • 8.3 Starter logs.................................................................................134

  • 8.4 Viewing syslog contents in OMS................................................134

  • 8.5 Configuring log rotation in

OMS.................................................

135

  • 8.6 Enabling trace logging in OMS...................................................138

  • 8.7 Troubleshooting data collection with OMS.................................140

  • 8.7.1 OMS troubleshooting data

140

  • 8.7.2 OMS troubleshooting data collection for

149

  • 8.7.2 Description.................................................................................

149

  • 8.7.2 Expected

149

  • 8.7.3 Content of troubleshooting data collection

150

  • 8.8 OMS syslog is not working properly...........................................150

9

Time

154

  • 9.1 Time management in

154

  • 9.2 Configuring NTP services in

155

  • 9.3 Testing NTP................................................................................157

  • 9.4 Changing time zone settings in OMS.........................................158

  • 10 Fault

161

  • 11 Security......................................................................................

162

  • 12 Maintenance...............................................................................163

    • 12.1 Maintenance...............................................................................163

    • 12.2 OMS shutdown and startup........................................................165

    • 12.3 Scheduling backups in

OMS......................................................

168

  • 12.4 Monitoring file system usage......................................................169

  • 12.5 Monitoring memory usage..........................................................175

  • 12.6 Configuring SNMP protocol for HP Systems Insight Manager...179

  • 12.7 HP Agentless Management for OMS Gen8

181

  • 12.7.1 Introduction to HP Agentless Management................................181

  • 12.7.2 Configuring HP SIM 7.0 for HP Agentless

185

12.8

HP disk health checking tool for OMS........................................187

  • 12.8.1 Introduction to HP disk health checking

188

  • 12.8.2 Using HP disk health checking tool............................................188

  • 12.8.3 Analyzing HP disk health checking tool report...........................189

    • 12.9 Disabling or enabling USB functions on boot in Gen8 OMS......192

      • 12.10 Upgrading OMS BIOS................................................................194

      • 12.11 Maintenance checklist................................................................198

Administering OMS

13

200

  • 13.1 Logging in to

200

  • 13.2 Emulating terminal with the screen command.........................202

Administering OMS

List of Figures

Figure 1

Parameter Tool main

49

Figure 2

CUAA diagram....................................................................................86

Figure 3

Network element delivered with optional features............................101

Figure 4

Upgrading feature capacity...............................................................102

Figure 5

Taking new features into use............................................................102

Figure 6

Parameter management

118

Figure 7

MOM figure

120

Figure 8

Example of a Parameter Tool MOM

121

Figure 9

Private naming service graph...........................................................124

Figure 10

Naming service

124

Figure 11

Logging process overview................................................................130

Figure 12

Syslog master and syslog proxy.......................................................133

Figure 13

Time management architecture........................................................154

Figure 14

The iLO 4 subsystem........................................................................182

Figure 15

The health summary information tab................................................185

Figure 16

Configure SNMP parameters for HP SIM 7.0 to manage a ProLiant

Gen8 server using HP Agentless

187

Figure 17

Main system boot screen of the HP

193

Figure 18

 

194

Administering OMS

List of Tables

Table 1

Attributes for fsuseradd tool...........................................................63

Table 2

Attributes for fsusermod tool...........................................................65

Table 3

Attributes for fsuserdel tool...........................................................67

Table 4

Attributes for fsgroupadd tool.........................................................68

Table 5

Attributes for fsgroupdel tool.........................................................69

Table 6

Attributes for fsgpasswd tool...........................................................70

Table 7

Attributes for fspermadd tool...........................................................72

Table 8

Attributes for fspermdel tool...........................................................73

Table 9

Attributes for fsgroupperm -a command......................................74

Table 10

Attributes for fsgroupperm -d command......................................74

Table 11

fsdumpgroups tool..........................................................................75

Table 12

fsdumpperm

76

Table 13

fsdumpusers tool............................................................................76

Table 14

Required permissions to launch Web UI

94

Table 15

Required permissions to open Application Launcher

96

Table 16

Common OMS log files.....................................................................130

Table 17

The files created by the rsyslogd daemon

...................................

133

Table 18

List of OMS

174

Table 19

Information supplied by SNMP agents and iLO firmware.................183

Table 20

Routine maintenance

198

Administering OMS

Summary of changes

Summary of changes

Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes between issues 10 (2015-07-06, WCDMA 16) and 10A (2015-10-30, WCDMA 16)

HP disk health checking tool for OMS HPADUCLI tool has been replaced by HPSSACLI tool.

Querying capacity usage

This section has been removed.

Importing License File

A note has been added.

Changes between issues 09B (2015-04-10, RU50 EP1) and 10 (2015-07-06, WCDMA

16)

License Management

This chapter has been added.

Maintenance OMS shutdown and startup has been added.

Dumping service account data with CLI Dump the group related data to the screen step has been updated.

Defining group permission restrictions for OMS Element Manager operations

Required permissions to launch Web UI pages table has been updated.

Required permissions to open Application Launcher applications table has been updated.

Maintenance checklist Routine maintenance tasks table has been updated.

Disabling or enabling USB functions on boot in Gen8 OMS

This section has been updated.

HP BIOS configuration CLI tool in Gen8 OMS

This section has been removed.

Summary of changes

Administering OMS

Changes between issues 09A (2014-11-25, RU50 EP1) and 09B (2015-04-10, RU50

EP1)

Configuring NTP services in OMS Steps has been updated. Testing NTP Steps has been updated.

Administering OMS

Backup and restore

1

Backup and restore

1.1

Backup and restore in OMS

Making regular backup copies of the software and databases of the OMS ensures that a user has a functional copy of the software which can be used if there are problems with the software or hardware, for example, a logical disk crash or a configuration error.

Backup and restore operation can be performed in two different ways:

remote backup and restore

 

The remote backup functionality enables the NetAct operator a remotely triggered backup of OMS system data. Remote operation can be scheduled from NetAct backup scheduler (regular or periodical backup) or can be initiated from NetAct using NWI3 interface request. All operation is planned and executed remotely using NetAct. The remote restore functionality enables downloading of OMS backup file (result file from partial or custom backup operation) remotely from NetAct. The downloaded backup file can be activated immediately in the OMS or activation can be triggered later on (except in cases of full backup). The full restore is not available remotely because the system must be booted using an external USB boot device. Refer to Description of RAN1845: OMS Data Backup and Restore Solution and NetAct documentation for more information.

g

Note: Remote backup and restore is the preferred way of executing backup and restore operations. For more information see Managing OMS Software Using NetAct document.

 

local OMS backup and restore command line interface

 

The OMS provides CLI based tools in order to perform local backup and restore operation of OMS data. This functionality requires manual commands to create the backup file as to upload it from OMS to an external storage. A user may also create the backup directory manually if it is not yet created. The backup directory is located

in /var/mnt/local/backup/SS_Backup.

 

It is recommended that person who deals with backup, restore actions as well with scripts, has basic knowledge of Linux and a good understanding of RPM (see the RPM man pages for detailed information).

w

NOTICE: Before executing any local backup and restore related command or script make sure that there is no remote operation ongoing.

Users can make a full, a partial, or a custom backup of the software. All types of backups are made using the omsbr_backup CLI command. See Making a full software backup in OMS.

Users can restore the whole system or a part of the system with the omsbr_restore CLI command. See Restoring databases in OMS.

When running the backup and restore commands, users must be logged into the OMS

as root.

Backup and restore

Administering OMS

t

Tip: If the backup or restore is executed remotely, consider using screen tool. See section Emulating terminal with the screen command in this document.

Backup types

A backup can be a full, partial, or custom backup. A backup is modular, meaning that the backup procedure consists of executing backup modules. Each module can create the backup archive of a backup item, for example the database backup module creates a backup of the databases. Note that all items are not necessarily used in all deployments. The approximated backup sizes are:

Full backup takes around 3.5-9 GB. Partial backup takes about <100 MB. Custom backup takes about <50 MB.

Note that the backup should be taken when there are no major on-going activities in the network element. For example, the backup may occasionally fail if the LDAP directory is manipulated at the time when the backup is taken.

A full backup includes the following items:

system image, including variable data and configuration files

databases LDAP directory system restoration tools

A partial backup is similar to full backup, except the first item does not include system image; only variable data and configuration files are included on partial backup.

A custom backup allows users to choose the backup items to include in the backup that includes:

system image, including variable data and configuration files databases LDAP directory system restoration tools

The backup modules first create individual backup files of the application file systems, databases, LDAP directory, and system restoration tools. The individual backup files are stored in temporary subdirectories in the directory

/var/mnt/local/backup/SS_Backup/tar

Finally, the system image module makes the system image backup and combines it with the individual backup files into a single compressed tar file that is located in

/var/mnt/local/backup/SS_Backup

The backup scripts and the configuration files are located in the directory

/etc/opt/Nokia_BP/fsbackup

OMS backup file content and file naming

Since OMS backup operations are performed using OMS Platform tools, the content of OMS data set that is preserved in full, partial, and custom backup operations is explicitly defined at OMS Platform level. In this regard, to control the amount of data to be

Administering OMS

Backup and restore

preserved, OMS manages configuration files that specify which part of the directory content is included and excluded during backup operations. These configuration files are

available in /etc/opt/Nokia_BP/fsbackup/backup.c directory.

OMS generates backup filename when the archive filename was not specified by the operator during execution of backup script using CLI. OMS generates backup filename when no filename is explicitly specified during execution of backup script locally.

The OMS backup filename structure is as follows:

<OMS_Id>_<OMSProduct>_<backupType_[backupPart] >_<SWRelease>_<date&time>.<file compression extension>

where:

OMS_Id is a unique OMS identifier of the network,

OMSProduct is a product type (rnc),

backupType is a type of backup (full, partial, custom),

backupPart is a parameter that refers to the specific backup content (which is used in case of the custom type of backup only); the possible values of the backupPart parameter are as follows:

DB_[database name] is the name of included database (for example:

DB_DB_Topology),

LD if LDAP directory is included,

SI if entire system image is included,

VI if configuration files and variable data on the system image are included,

RT if system restoration tools are included, HD if home directory is included,

SWRelease is the active software set name,

date&time is the backup's creation date and time in a yyyymmdd_hhmmss format,

file compression extension - tar.gz.

Examples:

OMS-

1_rnc_full_R_GOMS<oms_build>.release_oms_20130517_092430.tar.g

z

OMS-

23_rnc_partial_R_GOMS<oms_build>.release_oms.corr10_20130516_1

52805.tar.gz

OMS-

4_rnc_custom_DB_DB_Alarm_DB_DB_Topology_LD_VI_R_GOMS<oms_build

>.release_oms.corr44_20130520_094500.tar.gz

Backup logs

A backup operation creates entries into the system log, a cumulative backup log, and a backup-specific log.

The system log (syslog) contains entries of when the backup started and by whom, if it was interrupted and the status of the backup (OK or NOK). It is located in the directory

/var/log.

Backup and restore

Administering OMS

The following are examples of syslog entries. Example:

The backup process started:

Mar 1 13:40:06 info CLA-0 logger: SYSLOG(fsbackup) Starting backup procedure

Example:

The user interrupted the backup process:

Mar 1 13:50:39 info CLA-0 logger: SIGINT(fsbackup:_trapSigInt) User interrupt EXITCODE 2

Example:

The backup process failed:

Mar 1 13:50:39 info CLA-0 logger: SYSLOG(fsbackup:_trapSigExit) Backup failed with ERRORS (OMS- <OMS_ID>_<OMS_product>_<backup_type>_R_GOMS<OMS_build>.release_oms.corr<corr _number>_<time_stamp>.log)

Example:

The backup process succeeded:

Mar 1 13:50:39 info CLA-0 logger: SYSLOG(fsbackup:_trapSigExit) finished OK! (OMS- <OMS_ID>_<OMS_product>_<backup_type>_R_GOMS<OMS_build>.release_oms.corr<corr _number>_<time_stamp>.log)

The cumulative backup log, backup.log, contains log entries for all backups and restore operations. It is located in the directory

/var/mnt/local/backup/SS_Backup/log

In the cumulative backup log, a log entry for a backup consists of several rows. The rows are numbered, and for each backup the numbering starts from 1.

The cumulative backup log entries contain the following information:

the name of the backup log, including the start time of the backup the end time of the backup the status of the backup (OK or NOK) the command used to start the backup including the options the name of the user who started the backup the size of the backup archive file the name of md5 checksum of the backup archive file.

Each backup also has a backup-specific log. It contains information on everything that occurred during the backup. If the backup failed, user can look for errors in the backup- specific log.

The name of the backup-specific log file includes the type of the backup (full, partial, or custom), the name of the delivery, and the backup execution date and time.

The backup-specific log file is stored in the backup directory

/var/mnt/local/backup/SS_Backup/log

Restore operation types

Administering OMS

Backup and restore

A partial restore may be necessary, for example, if the database(s) or LDAP directory is faulty. To enable the partial restoring, the system must be running.

The omsbr_restore command is used for restore operations:

g

restoring all database backups restoring one specified database backup restoring LDAP directory backup restoring a single file or a subdirectory

Note: Note that all items are not necessarily used in all deployments.

A full restore is required when the system cannot be repaired using a partial backup and a user needs to restore the whole system from the backup archive. During a full restore, the user restores all backup items: application file systems, databases, LDAP directory, and the system image.

g

Note: Note that the full restore is possible only if the USB stick is in use.

A broken system image usually causes a boot loop. Reasons for that include a logical disk crash, a corrupted file system or an accidental deletion of files or directories on the system image. The system must be booted using an external USB boot device, for example a USB flash memory drive.

Backup scheduling and storing

It is recommended to always create a full backup before and after a software upgrade. It is recommended to make a partial backup every night. Backups can be scheduled using a cron (a daemon used for executing scheduled commands). For instructions, see Scheduling backups in OMS.

Note that the backup archive, in both full and partial backup, takes up a large amount of disk space.

Full backup takes around 3.5-9 GB. Partial backup takes about <100 MB. Custom backup takes about <50 MB.

If a user creates the backup frequently, the disk soon becomes full. To avoid this, the user needs to delete old backup files to release disk space for the new ones.

It is also recommended that user keeps a backup history for a certain period of time by moving the existing backup file to an external server before executing a new backup. It is recommended to keep at least the full backup and the latest partial backup, but it is also recommended to keep a longer history of partial backups. For example, if a database becomes corrupted and this is not noticed immediately, the latest partial backup may also contain the corrupted data. In such a case, it is necessary to search through older partial (or full) backups to find the latest database backup that is not corrupted.

  • 1.2 Preparing for the backup of databases in OMS Summary

Backup and restore

Administering OMS

Databases DB_AidS and DB_Topology are the only databases which are included to the backup. Databases DB_Alarm, DB_CosNaming, DB_CMPlan, DB_Junak, and DB_PMData are not included to the backup by default. You can include or exclude required databases from the backup by changing the fsdbBackup parameter (Y/N).

Purpose

Follow this procedure, to configure the OMS to prepare the backup of the database other than AidS.

Result

Expected outcome

The database is included to the backups. The backup procedure can be started.

g

Note: Changing the value of fsdbBackup to Y may cause OMS backup partition to become full. Remember to change the value back to N after the necessary backup is done.

Steps

  • 1 Open the Application Launcher.

in the Start menu (Programs > Nokia > Application Launcher Client 2 > Application Launcher Client) in Windows or

in the menu (Applications > Other > Application Launcher Client) in Linux.

  • 2 Launch the Parameter Tool.

  • 3 Enable the backup of a database.

To activate the backup of a certain database edit the parameter.

fsClusterId=ClusterRoot, fsFragmentId=DB, fsdbName=DB_<DB Name>

Change the value of fsdbBackup: N > fsdbBackup: Y

t

t

w

Tip:

Empty value means the same as Y.

Tip: You can add the parameter value manually. For more information on adding parameter value and using Parameter Tool, see chapter Parameter Administration.

NOTICE: For Alarm DB and Topology DB backup the S value (instead of Y) must be used to run domain/subsystem specific scripts. The S value is set by default. Changing (or removing) the S value for Alarm DB and Topology DB may cause unpredicted behavior of a network system and thus is not allowed.

Administering OMS

Backup and restore

When the S value is set, the extent of the databases backup is defined automatically by the respective OMS domain.

w

NOTICE: This is strongly recommended to ensure that the S value is set for the two following databases:

The value of fsdbBackup for Alarm DB: DB_Alarm > fsdbBackup: S The value of fsdbBackup for Topology DB: DB_Topology > fsdbBackup:

S

  • 1.3 Making a full software backup in OMS Summary Use the omsbr_backup command to create a full backup of the system. The syntax of the command is as follows: omsbr_backup -f [-a <filename>] The argument -f means full backup. Backup the entire system image. The argument -a is optional and specifies the output (backup archive) filename. When this option is not indicated, OMS generates backup archive with appropriate filename. First the backup modules create individual tar files of the application file systems, databases, LDAP Directory, and system restoration tools. The individual tar files are stored in temporary subdirectories in the following directory: /var/mnt/local/backup/SS_Backup/tar Finally, the system image module makes the system image backup and combines it with the individual tar files into a single archive <backup archive file> that is located in /var/mnt/local/backup/SS_Backup The name of the backup tar archive file includes the OMS ID, type of the backup (full, partial, or custom), the OMS product, name of the OMS delivery (OMS build), and the backup execution date and time, for example, OMS- <OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr_numb er>_<time_stamp>.tar.gz. Excluding the xmlfilesBU directory from full backup

While taking a full backup, the xmlfilesBU directory is included by default. But, when the size of the xmlfilesBU directory is huge, you have an option to exclude the directory from full backup by adding

/var/mnt/local/sysimg/OMSftproot/xmlfilesBU/* into a file /etc/opt/Nokia_BP/fsbackup/backup.c/bu_systemimg.full.exclude

Backup and restore

Administering OMS

Purpose

Make a full backup of the whole system including the system image, variable data and configuration files, application file systems, databases, LDAP Directory, the system restoration tools.

Before you start

Make sure that the following conditions are met:

The OMS is up and running in its normal working state. For instructions on how to check the state, see Checking and changing the state of a managed object in OMS.

You are logged in as the root user.

You configured the OMS to include or exclude the certain databases in the backup - see Preparing for the backup of databases in OMS.

There is enough free disk space for the backup archive file. You can estimate the amount of disk space needed from the previous backup archive files. The disk space you need during a full backup is at least two times the size of the old backup archive file. You may also verify the occupancy of /var/mnt/local/sysimg partition with the df -h command. If the occupancy (column Use%) is over 90%, the backup fails. If necessary, free disk space by transferring backups to an external server and deleting unnecessary files. For instructions, see Transferring the backup archive file from OMS to an external storage server.

You have no unnecessary operator's files, both permanent or temporary. The following command might be helpful for finding files over 100 MB: find

/var/mnt/local/sysimg -size +100M

Result

Expected outcome

Mon Oct 12 18:39:04 2015 OMS::TRACE INFO <omsbr_backup> CLA-0 Backup operation succeeded!!! Mon Oct 12 18:39:04 2015 OMS::TRACE INFO <omsbr_backup> CLA-0 Lock is released

A compressed backup archive file

OMS-

<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr_numb

er>_<time_stamp>.tar.gz

and md5 checksum file are created in

/var/mnt/local/backup/SS_Backup directory.

t

Tip: If the operation is executed remotely, consider using screen tool. See section Emulating terminal with the screen command in this document.

Unexpected outcome

A backup archive file may be missing or may exist but it is incomplete.

The system raises the alarm 70064 BACKUP ERROR.

In an error situation, information of the error is entered in the syslog and in the backup log.

Administering OMS

Backup and restore

The syslog entries can be seen from the syslog file located in /var/log. To check the error entries from syslog, enter:

tail -n 200 /var/log/syslog | grep -i backup

Also check the backup log for errors and warnings.

Post requisites

To verify that the operation was successful:

Check that there are no backup error messages in the syslog file.

Check the existence of the backup archive file and the md5 checksum file by entering the following command:

ls /var/mnt/local/backup/SS_Backup

Steps

  • 1 Log in to the OMS remotely and then switch to the root account by entering su - command. For more information, see Logging in to the OMS.

  • 2 Check the space availability on backup partition by entering df -h | grep backup command.

w

Example:

# df -h | grep backup

/dev/md5 16G

173M

15G

2% /var/mnt/local/backup

NOTICE: Note that sizes of OMS partitions may differ depending on used disk sizes.

  • 3 Start the full backup procedure. Enter the following command: omsbr_backup -f Expected outcome The backup archive file is created in the /var/mnt/local/backup/SS_Backup/ directory.

t

Tip: The backup or recovery progress reports (or indicators) are not supported for the RAN1845: OMS Data Backup and Restore Solution feature. OMS does not inform about progress of the operation. The operator should check the final status of the operation.

Backup and restore

Administering OMS

  • 4 Generate md5 checksum for the backup archive. Go to the directory where the backup archive file is located /var/mnt/local/backup/SS_Backup/ and execute the following command: # md5sum <backup archive file> > <backup archive file>.md5sum Example

# md5sum OMS-<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr_number>_<time_stamp>.tar.gz > OMS-<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr_number>_<time_stamp>.tar.gz.md5sum

Expected outcome

The md5sum checksum file is created next to the existing backup archive file in the

/var/mnt/local/backup/SS_Backup/

directory.

  • 5 Split the backup archive file (optional). The FAT32 filesystem used on the USB stick does not allow files larger than 4 GB. If the backup archive file size exceeds 4 GB it needs to be split.

t

Tip: The split can be used even if the backup archive file size is less than 4 GB.

Use the zsplitbackup.sh script:

zsplitbackup.sh /var/mnt/local/backup/SS_Backup/<backup archive file>

Example

# zsplitbackup.sh /var/mnt/local/backup/SS_Backup/

OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>.tar.gz

> source file: /var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>.tar.gz

> destination folder: /var/mnt/local/backup/SS_Backup > part size: 1024 MB > file size: 4105 MB (4304455680 B) > parts to create: 5

> parts prefix: OMS-<OMS_ID>_rnc _<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number> _<time_stamp>_

> Splitting in progress ... creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>_aa'

creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>_ab'

creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>_ac'

creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>_ad'

Administering OMS

Backup and restore

creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

g

_<time_stamp>_ae'

> Split complete!

Note: The backupPart refers to the specific custom software backup only. See zsplitbackup.sh in Command Line Interface Tools and Management Scripts in OMS or run zsplitbackup.sh -h for more options.

  • 1.4 Making a partial software backup in OMS Summary Use the omsbr_backup command to create a partial backup of the system. The syntax of the command is as follows: omsbr_backup -p [-a <filename>] The argument -p starts the partial backup. The argument -a is optional and specifies the output (backup archive) filename. When this option is not indicated, OMS generates backup archive with appropriate filename. First the backup modules create individual tar files of the application file systems, databases, LDAP directory, and system restoration tools. The individual tar files are stored in temporary subdirectories in the directory /var/mnt/local/backup/SS_Backup/tar Finally, the system image module makes the system image backup and combines it with the individual tar files into a single <backup archive file> that is located in /var/mnt/local/backup/SS_Backup The name of the backup tar archive file includes the OMS ID, type of the backup (partial), the OMS product, name of the OMS delivery (OMS build), and the backup execution date and time, for example, OMS- <OMS_ID>_rnc_partial_R_GOMS<OMS_build>.release_oms.corr<corr_n umber>_<time_stamp>.tar.gz. Purpose Make a partial backup to create a backup archive of the application file systems, databases, LDAP Directory, the system restoration tools, and a backup of the configuration files and variable data of the system image. Before you start Make sure that the following conditions are met: The OMS is up and running in its normal working states. For instructions on how to check the state, see Checking and changing the state of a managed object in OMS.

Backup and restore

Administering OMS

You have appropriate root privileges.

You configured the OMS to include or exclude the certain databases in the backup - see Preparing for the backup of databases in OMS.

There is enough free disk space for the backup archive file. If necessary, free disk space by transferring old backups to an external server and deleting unnecessary files. For instructions, see Transferring the backup archive file from OMS to an external storage server.

Result

Expected outcome

The backup archive and md5 checksum file are created in the subdirectory

/var/mnt/local/backup/SS_Backup

Unexpected outcome

A backup archive file may exist but it is incomplete.

The system raises the alarm 70064 BACKUP ERROR.

In an error situation, information of the error is entered in the syslog and in the backup log.

The syslog entries can be seen from the syslog file located in /var/log. To check the error entries from syslog, enter:

tail -n 200 /var/log/syslog | grep -i backup

Also check the backup log for errors and warnings.

Post requisites

To verify that the operation was successful:

Check that there are no backup error messages in the syslog file.

Check the existence of the backup archive file and the md5 checksum file by entering the following command:

ls /var/mnt/local/backup/SS_Backup

Steps

  • 1 Log in to the OMS remotely and then switch to the root account by entering su - command. For more information, see Logging in to the OMS.

  • 2 Start the partial backup procedure. Enter the following command: omsbr_backup -p Expected outcome

Administering OMS

Backup and restore

The backup archive file is created in the

/var/mnt/local/backup/SS_Backup/

directory.

  • 3 Generate md5 checksum for the backup archive. Go to the directory where the backup archive file is located /var/mnt/local/backup/SS_Backup/ and execute the following command: # md5sum <backup archive file> > <backup archive file>.md5sum Example

# md5sum OMS-<OMS_ID>_rnc_partial_R_GOMS<OMS_build>.release_oms.corr<corr_number>_<time_stamp>.tar.gz > OMS-<OMS_ID>_rnc_partial_R_GOMS<OMS_build>.release_oms.corr<corr_number>_<time_stamp>.tar.gz.md5sum

Expected outcome

The md5sum checksum file is created next to the existing backup archive file in the

/var/mnt/local/backup/SS_Backup/

directory.

  • 1.5 Making a custom software backup in OMS Summary Use the omsbr_backup command to create a custom backup of the system. The syntax of the command is as follows: omsbr_backup -c [ -d [<DB name>] ] [ -l ] [ -S | -s ] [ -r ] [ -P ] [-a <filename>]

You have the following options:

-c: custom backup

-a: optional argument to specify the output (backup archive) filename; when this option is not indicated, OMS generates backup archive with appropriate filename

-d [<DB name>]: backup the database (irrespective of the fsdbBackup LDAP parameter value); if the database name is specified, only that database is copied; if the database name is not specified, all the databases are copied

-l: backup content of the master LDAP database

-S: backup the entire system image backup; it is not possible to combine this option with -s

-s: backup the configuration files and variable data on the system image; it is not possible to combine this option -S

-r: backup the system restoration tools

-P: backup the content of home directories (in practice plugin

/etc/opt/Nokia_BP/fsbackup/bu_plugin.d/bu_home.sh is executed)

-v <on|off>: shows the processing details of backup; this is ON by default -h: shows the command usage

Backup and restore

Administering OMS

-F|--appfilesystem: make an Application File System backup

The name of the backup tar archive file includes the OMS ID, type of the backup (custom), backup part, the OMS product, name of the OMS delivery (OMS build), and the backup execution date and time, for example, OMS-

<OMS_ID>_rnc_<custom_[backupPart]

>_R_GOMS<OMS_build>.release_oms.corr<corr_number>_<time_stamp>

.tar.gz.

The backupPart refers to specific custom backup content. The possible values are as follows:

DB_<database name> - name of included database (for example

DB_DB_Topology)

LD - if LDAP directory is included

SI - if entire system image is included

VI - if configuration files and variable data on the system image are included

RT - if system restoration tools are included

HD - if home directory is included

Purpose

Make a custom software backup to create a backup archive of the backup items you have selected.

Before you start

Make sure that the following conditions are met:

OMS is up and running in its normal working state.

You have appropriate root privileges.

There is enough free disk space for the backup archive file. If necessary, free disk space by transferring backups to an external server and deleting unnecessary files. For instructions, see Transferring the backup archive file from OMS to an external storage server.

g

Note: The fsdbBackup LDAP parameter has no impact on including or excluding a certain database in the custom software backup.

Result

Expected outcome

The backup archive and the md5 checksum file are created in the subdirectory

/var/mnt/local/backup/SS_Backup

Unexpected outcome

A backup archive file may exist but it is incomplete.

The system raises the alarm 70064 BACKUP ERROR.

In an error situation, information of the error is entered in the syslog and in the backup log.

The syslog entries can be seen from the syslog file located in /var/log. To check the error entries from syslog, enter:

Administering OMS

Backup and restore

tail -n 200 /var/log/syslog | grep -i backup

Also check the backup log for errors and warnings.

Post requisites

To verify that the operation was successful:

Check that there are no backup error messages in the syslog file.

Check the existence of the backup archive file and the md5 checksum file by entering the following command:

ls /var/mnt/local/backup/SS_Backup

Steps

  • 1 Log in to the OMS remotely and then change the root user permission by entering su - command. For more information, see Logging in to the OMS.

  • 2 Start the custom backup procedure. Enter: omsbr_backup -c [ -d [<DB name>] ] [ -l ] [ -S | -s ] [ -r ] [ -P ] [-a <filename>] Expected outcome The backup archive file is created in the /var/mnt/local/backup/SS_Backup/ directory.

  • 3 Generate md5 checksum for the backup archive. Go to the directory where the backup archive file is located /var/mnt/local/backup/SS_Backup/ and execute the following command: # md5sum <backup archive file> > <backup archive file>.md5sum Example

# md5sum OMS-<OMS_ID>_rnc _custom_<backupPart>_R_GOMS<OMS_build>.release_oms.corr<corr_number>_<time_stamp>.tar.gz > OMS-<OMS_ID>_rnc

_custom_<backupPart>_R_GOMS<OMS_build>.release_oms.corr<corr_number>_<time_stamp>.tar.gz.md5sum

Expected outcome

The md5sum checksum file is created next to the existing backup archive file in the

/var/mnt/local/backup/SS_Backup/

directory.

Backup and restore

Administering OMS

  • 4 Split the backup archive file (optional). The FAT32 filesystem used on the USB stick does not allow files larger than 4 GB. If the backup archive file size exceeds 4 GB it needs to be split.

t

Tip: The split can be used even if the backup archive file size is less than 4 GB.

Use the zsplitbackup.sh script:

zsplitbackup.sh /var/mnt/local/backup/SS_Backup/<backup archive file>

Example

# zsplitbackup.sh /var/mnt/local/backup/SS_Backup/

OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>.tar.gz

> source file: /var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>.tar.gz

> destination folder: /var/mnt/local/backup/SS_Backup > part size: 1024 MB > file size: 4105 MB (4304455680 B) > parts to create: 5

> parts prefix: OMS-<OMS_ID>_rnc _<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number> _<time_stamp>_

> Splitting in progress ... creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>_aa'

creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>_ab'

creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>_ac'

creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

_<time_stamp>_ad'

creating file `/var/mnt/local/backup/SS_Backup/OMS-<OMS_ID>_rnc

_<backupType_[backupPart]>_R_GOMS<OMS_build>.release_oms.corr<corr_number>

g

_<time_stamp>_ae'

> Split complete!

Note: The backupPart refers to the specific custom software backup only.

See zsplitbackup.sh in Command Line Interface Tools and Management Scripts in OMS or run zsplitbackup.sh -h for more options.

  • 1.6 Transferring the backup archive file from OMS to an external storage server Summary

Administering OMS

Backup and restore

Because the backup is made locally, the backup archive file can be transferred to an external storage server using, for example, scp.

w

NOTICE: Note that only root user or users belonging to _nokfsuibackupgroup are allowed to perform this operation.

If you want to add any non-root user to the _nokfsuibackupgroup group, use the commands described in chapter Administering user-group mappings with CLI. You can also list members of _nokfsuibackupgroup as described in chapter .

Purpose

Transfer the backup archive file from the local hard disk to an external storage server as an additional safety precaution. In addition to that, transfer the backup archive file to free local hard disk space and keep a history of the different backup versions.

Before you start

Make sure that the following conditions are met:

You are logged in as root or you are a member of _nokfsuibackupgroup group.

Backup tar archive file is available in the backup subdirectory. Connection to the external server can be established.

Expected outcome

The backup archive file is copied to the desired storage server.

Post requisites The success of the file transfer can be verified by, for example md5 program. The checksums can be computed and checked by the md5sum command.

Steps

  • 1 Transfer the backup file to the desired location. Enter the following command: scp /var/mnt/local/backup/SS_Backup/<backup archive file> \ <username>@<Ip address>:/home/<username>

t

Tip: The \ character is used to indicate that a command continues to the next line. Command lines ending with \ must not be entered as separate commands.

  • 1.7 Creating a self-contained USB rescue stick

Backup and restore

Administering OMS

Purpose

Creating a bootable USB stick containing a backup archive. Except for single or split backup archive file(s), the USB stick should contain also the md5 checksum file.

Before you start

This procedure requires a USB stick with at least 8 GB capacity. Only in exceptional cases if the backup size does not exceed 3 GB, a 4 GB USB stick can be used.

Make sure that USB Drive Key Enumeration option is enabled in the BIOS configuration (for Gen8 OMS only). For more information, see and Disabling or enabling USB functions on boot in Gen8 OMS.

Steps

  • 1 Create a bootable USB stick. For instructions, see Creating a bootable USB stick in Installing and Commissioning OMS.

  • 2 Create install folder on the USB stick.

w

NOTICE: The name of the folder must be install.

Example

  • md X:\install where X: is the USB stick drive letter.

  • 3 Copy files to the USB stick. Connect the USB stick to an external computer. Copy the following files to the /install directory on the USB stick:

InstallGOMS_USB.sh (to be downloaded from

/opt/Nokia/SS_OMSINST/usb/ directory in OMS) OMS- <OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr _number>_<time_stamp>.tar.gz.md5sum (the MD5 checksum)

If the backup archive has not been split:

OMS-

<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr

_number>_<time_stamp>.tar.gz

If the backup archive has been split:

OMS-

<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr

_number>_<time_stamp>_aa

Administering OMS

Backup and restore

OMS-

<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr

_number>_<time_stamp>_ab

OMS-

<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr

_number>_<time_stamp>_ac

OMS-

<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr

_number>_<time_stamp>_ad

OMS-

<OMS_ID>_rnc_full_R_GOMS<OMS_build>.release_oms.corr<corr

_number>_<time_stamp>_ae

 

...

g

Note: Total number of archive parts may differ in the real system, depending on the backup archive file size. All of them must be copied to the USB stick.

For instructions on copying files to an external computer, see Transferring files from OMS to client computer in Installing and Commissioning OMS.

g

Note: Make sure that the /install directory does not contain any other files.

Perform this procedure every time you make a backup. If no incremental software deliveries were installed since the last backup you can use the existing

InstallGOMS_USB.sh file.

  • 1.8 Restoring the whole system in OMS with self made full backup archive and USB rescue stick Summary

A full restore is required when the system cannot be manually repaired from a partial backup. The reason may be a logical disk crash, a corrupted file system, or an accidental deletion of files and directories on the system image.

Broken system image usually causes the node to go into a boot loop. If the boot partition is broken, the boot procedure hangs already in the BIOS state. In this instruction it is assumed by default that the whole disk structure is broken, including the application file systems, partition structure, and boot block.

g

g

Note:

Note that the full restore is possible only if the USB stick is in use.

Note: Note that during custom or partial restore operation OMS is not operational in radio network. All the recovery groups (except the crucial ones) are disabled. After restore all recovery groups become operational.

Backup and restore

Administering OMS

Purpose

To restore the whole system with a bootable USB stick containing the self made backup archive. If you are using the backup server, the backup archive file must be copied to the USB before the restore procedure.

Before you start

The prerequisites for the OMS installation are as follows:

Two hard drives are installed to the OMS.

The USB stick has been prepared according to the instructions given in the previous sections (Creating a self-contained USB rescue stick).

The USB stick contains only the USB boot part (syslinux folder) and one self made full backup archive in install folder (when backup server is not in use).

Connect an external monitor and keyboard to OMS.

Notice that on USB installation OMS BIOS must be in UTC/GMT time (United Kingdoms time).

Make sure that USB Drive Key Enumeration option is enabled in the BIOS configuration (for Gen8 OMS only). For more information, see and Disabling or enabling USB functions on boot in Gen8 OMS.

Note that log is written to USB stick /logs/Install--<timestamp>.log

Procedure

  • 1 Boot up the OMS. To boot up the OMS, execute the following in the order they are listed:

    • a) Connect the external USB boot stick into the OMS's USB port.

    • b) Reset the OMS node by pressing the Power On button in the front panel of the blade or rackmount hardware.

    • c) Choose the Setup by pressing F9 on the external keyboard to enter BIOS and to check the system date and time.

    • d) Select Date and Time from the BIOS and adjust clock to UTC/GMT time (the United Kingdom's time). Confirm the settings by pressing Enter.

    • e) Save the setting and exit BIOS (press F10).

    • f) When prompted, press F11 to enter the Boot Menu.

    • g) Choose 3) One Time Boot to USB DriveKey.

    • h) Wait for the OMS to boot from the external USB boot device.

    • i) To choose correct selection from the list, enter the following text: fp4_hprm (for HP ProLiant rack hardware) fp4_hpbs (for HP ProLiant blade hardware)

    • j) Log into the preboot system as the root user (no password needed).

    • k) Verify time with date command after OMS first boot: #date #Wed Jan 30 13:36:31 EST 2014 Time should be correct (UTC/GMT). Ignore the time zone information (here EST) in date printout.

Administering OMS

Backup and restore

  • 2 Check the device name of the USB stick. Check the device name of the USB stick. The device name can be determined from dmesg output. Enter the following command: # dmesg | grep -i 'removable disk' Result The example output of the command: sd 1:0:0:0: [sdc] Attached SCSI removable disk Append the [xxx] to "/dev/" to have the full name for the device (in this case the device name is /dev/sdc).

  • 3 Mount the USB stick, copy the installation script. Substitute xxx with the device name found in step Check the device name of the USB stick. Notice the partition number (“1”) after the device name. For example, if the USB stick device name found in step Check the device name of the USB stick. is /dev/sdc, the complete parameter passed to mount command is /dev/sdc1. # cd /tmp # mkdir -p /media/FPRESCUE # mount /dev/xxx1 /media/FPRESCUE # cp /media/FPRESCUE/install/InstallGOMS_USB.sh /tmp/ # dos2unix InstallGOMS_USB.sh # chmod 744 InstallGOMS_USB.sh # cd /tmp If mount command fails Check the correct device name: # less /var/log/dmesg If the device name is correct, remove usb-storage module: # modprobe -r usb-storage Wait a few seconds and reload the module using the following command: # modprobe usb-storage Mount the USB stick again: mount /dev/xxx1 /media/FPRESCUE Substitute xxx with the correct device name.

  • 4 If you are using the backup server, configure the ethernet interfaces of the OMS and copy the backup archive files to USB stick. To configure the ethernet interfaces of the OMS enter the following commands: ifconfig eth# <ip address> netmask <netmask> route add default gw <gw address> where eth# is the ethernet interface. The interface eth0 must be configured to the same network with the backup server. The interface eth1 must be configured to the node where the full restore is done.

Backup and restore

Administering OMS

Example:

ifconfig eth0 192.168.0.8 netmask 255.255.0.0 ifconfig eth1 10.102.90.151 netmask 255.255.255.0 route add default gw 10.102.90.1

To copy the backup archive files from backup server to the USB stick enter the following command:

scp <backup server>:/<archive file> /media/FPRESCUE/install

After the transfer is completed, you can remove the physical connection to the backup server.

  • 5 Start the installation script. Start the installation script by running the following command: # ./InstallGOMS_USB.sh After you have given the command, the following text appears on the screen: This script will install GOMS. Running this script will take about 1 hour 20 minutes. Merging image chunks is supported. When you ready to continue press [Y/y] This machine's system date and time is: Thu Feb 6 10:19:58 UTC 2014 Is this date and time correct [Y/y] or [N/n]? Time should be correct (UTC/GMT). If you need to set up the system date and time, select N/n. After you have given the N/n answer, the following text appears: Type a year (eg. 2014): Type a month .. (01 Type a day of month (eg. 01):

12):

Type an hour (00 Type a minute (00

..

..

23):

59):

Now the system date and time is:

Fri Feb 21 14:19:01 UTC 2014

press enter to continue

Now wait until the script finishes and asks to remove USB stick and boot OMS. Continue with the next step.

g

Note: The script execution time depends on the hardware in use as well as the restoration archive size. It may vary from 20 minutes to 1 hour 20 minutes.

Administering OMS

Backup and restore

t

Tip: If the partition table configuration changes between installations (current vs. coming), or if the hardware RAID is not initialized, the installation is likely to fail in partition creation and cause the following error message:

No such file /var/mnt/local/backup/SS_Backup ...

If this happens, check the logical drive (RAID) configuration (see step Verify the configuration or Verify the configuration in the Configuring hardware for OMSchapter of the Installing and Commissioning OMS document), then run the InstallGOMS_USB.sh script again.

  • 6 Remove the USB stick. Follow the instructions when the # ./InstallGOMS_USB.sh has been completed: Remove USB stick. After reboot, change BIOS boot order to boot from Hard Drive And save settings. To reboot target when ready press [Y/y] Remove the USB stick first and then press y to reboot the OMS.

t

Tip: If you use iLO console instead of KVM, OMS may reboot automatically depending on HP iLO firmware version.

  • 7 Log in to the OMS as a root. Log in to the OMS locally as a root. The root password has been converted during the backup procedure. It means the root password remains the same as it was before the backup and restore procedure.

  • 8 Change directory and run CompleteGOMS_USBInstallation.sh. To start the commissioning script run the following commands: # cd /opt/Nokia/SS_OMSINST/usb/ # dos2unix CompleteGOMS_USBInstallation.sh # chmod 744 CompleteGOMS_USBInstallation.sh # ./CompleteGOMS_USBInstallation.sh

  • 9 Select the appropriate option of the CompleteGOMS_USBInstallation.sh

script usage.

 

When you are asked:

Do you want to perform custom restore or fresh OMS installation?

choose

1
1

to perform the custom restore:

Do you want to perform custom restore or fresh OMS installation? Custom restore will only unlock cluster, restore databases and application file system

Backup and restore

Administering OMS

Rest of data will be restored from Backup file, system will not be rebooted

Fresh installation (new OMS) will also modify IP addresses, passwords, ssh keys, OMS Id, timezones, etc. In this option OMS will be rebooted

Press '1' for custom restore or '2' for fresh installation. Press 'q' to quit script:

Step result

After executing the CompleteGOMS_USBInstallation.sh script, you get the follwing prompt:

---------------------------

> Operation completed.

---------------------------

Result

Expected outcome

The whole system is restored and is available to be used normally.

Unexpected outcome

For instructions on how to proceed in error situations, refer to the following instructions:

If the error concerns restoring databases, refer to Restoring of database in OMS fails.

If the error concerns restoring LDAP directory, refer to Restoring LDAP directory of OMS fails.

If the error concerns restoring the system image, a file, or a directory, refer to Restoring of system image, single file, or directory in OMS fails.

If the system freezes for more than two minutes, refer to Software management commands cause the OMS operations to hang.

If restoring the system from USB rescue stick fails, see OMS USB installation or USB restore fail because of TAR problem.

  • 1.9 Restoring databases in OMS

w

Summary

NOTICE: Errors may occur if the state of the managed objects, recovery groups, or recovery units are locked or unlocked during restoration. Do not change the state of managed objects during restoration.

Administering OMS

Backup and restore

Use the omsbr_restore command to restore a single database. The syntax of the command is as follows:

omsbr_restore -c -d [<database name>] <backup archive>

The parameter -c means the custom restore. The parameter -d starts the database restore operation. There are the following arguments:

<database name>: the name of the database you want to restore. <backup archive>: the backup archive file (located in

/var/mnt/local/backup/SS_Backup).

As a result the specified database backup is restored.

t

Tip: It is also possible to restore all databases by omitting the name of the database. This is usually needed only during a full restore.

Purpose

Restoring the required databases from the backup archive if the error situation concerns the databases only.

Before you start

Make sure that the following conditions are met:

You have appropriate root privileges. The destination system directory is available. The backup archive file to be restored is available.

Expected outcome

The specified databases are restored correctly to the destination location and are available to be used normally. The database logs of a MySQL database are not deleted when a single MySQL database is restored.

Unexpected outcome

For more instructions on how to proceed in an error situation, see Restoring of database in OMS fails.

Steps

  • 1 Log in to the OMS remotely and then switch to root account by entering su - command. For more information, see Logging in to the OMS.

Backup and restore

Administering OMS

  • 2 Check that no processes in OMS is disabled. Enter the following command: zstatus -d

  • 3 Restore the database from the backup archive file. Enter the following command: omsbr_restore -c -d [<database name>] <backup archive>

t

Tip: If the operation is executed remotely, consider using screen tool. See section Emulating terminal with the screen command in this document.

Example:

To restore the DB_Alarm from the backup archive file run the following command:

omsbr_restore -c -d DB_Alarm

OMS-

<OMS_ID>_rnc_partial_R_GOMS<OMS_build>.release_oms.corr<cor

r_number>_<time_stamp>.tar.gz

  • 1.10 Restoring LDAP directory of OMS

w

Summary

NOTICE: Errors may occur if the state of the managed objects, recovery groups, or recovery units are locked or unlocked during restoration. Do not change the state of the managed objects during restoration.

Use the omsbr_restore wrapper to restore LDAP directory. LDAP database restore can be performed only on the same system for which the backup has been performed. Do not try to restore LDAP database after clean OMS installation. During the base build installation new passwords are generated for the different services which prevents from successful LDAP database restore.

The syntax of the command is as follows:

omsbr_restore -c -l <backup archive>

The parameter -c means the custom restore. The parameter -l starts the LDAP directory restore operation. There is the following argument:

<backup archive>: the backup archive file

(located in /var/mnt/local/backup/SS_Backup)

Administering OMS

Backup and restore

Purpose

Restore only an LDAP directory from the backup archive if the error situation concerns only the LDAP directory.

Before you start

Make sure that the following conditions are met:

You have the appropriate root privileges.

The backup archive file to be restored is available.

The LDAP server is up and running.

Expected outcome

The LDAP directory files are restored correctly to the destination location and are being used by running OpenLDAP server.

Unexpected outcome

For instructions on how to proceed in an error situation, see Restoring of LDAP directory of OMS fails.

Example:Restoring LDAP directory from a custom backup

omsbr_restore -c -l <OMS_ID>_rnc _custom_R_GOMS<OMS_build>.release_oms.corr<corr_number>_<time_stamp>.tar .gz

Steps

  • 1 Log in to the OMS remotely and then switch to the root account by entering su - command. For more information see Logging in to the OMS.

  • 2 Restore the LDAP directory. Enter the following command: omsbr_restore -c -l <backup archive>

  • 1.11 Restoring a single file or directory in OMS

w

Summary

NOTICE: Errors may occur if the state of the managed objects, recovery groups, or recovery units are locked or unlocked during restoration. Do not change the state of the managed objects during restoration.

Backup and restore

Administering OMS

Use the omsbr_restore wrapper to restore a single file or LDAP directory. The syntax of the command is as follows:

omsbr_restore -c -s <file or directory name> <backup archive>

The parameter -c means the custom restore. The parameter -s means making a sysconf restore. There are the following arguments:

<file or directory name>: the name of the file or directory you want to restore.

<backup archive>: the backup archive file

(located in /var/mnt/local/backup/SS_Backup)

As a result the specified directory or file is restored into the destination location.

Purpose

If an error situation concerns a directory or a file only, restore only the required file or directory from the backup archive file.

When restoring a file or directory, check that it is safe to restore the file or directory to the system. It is not recommended to restore files or directories to the runtime environment if you do not know exactly what you are doing.

Note that you cannot restore databases with this procedure.

Before you start

Make sure that the following conditions are met:

You have the appropriate root privileges. The backup archive file to be restored is available.

Expected outcome

The specified directory or file is restored correctly to the destination location.

Unexpected outcome

Alarm is raised.

For instructions on how to proceed in an error situation, see Restoring of system image, single file, or directory in OMS fails .

Steps

  • 1 Log in to the OMS remotely and then switch to root account by entering su - command. For more information, see Logging in to the OMS.

Administering OMS

Backup and restore

  • 2 Check that no processes in OMS is disabled. Enter the following command: zstatus -d

  • 3 Restore the file or directory To restore a directory or a file, enter the following command: omsbr_restore -c -s <file or directory name> <backup archive>

  • 1.12 Backup of OMS fails Description The backup process may fail if, for example: The user does not have the required privileges to execute the backup. The system is not fully functional. There is not enough free disk space available for the backup archive. The database backup process may also fail if, for example: There is an internal database system error. There is a system timeout while making a backup of a database. Symptoms

When the backup process fails:

The system creates the alarm 70064 BACKUP ERROR.

The backup process is either completed or interrupted. Even though the backup of one backup item fails, the system continues making backups of the other backup items and creates a backup archive in the subdirectory

/var/mnt/local/backup/SS_Backup

The system displays an error message on the local output device and creates an entry in the syslog file.

Recovery procedures

Refer to the error message shown on the local output device and check the syslog file in /var/log to determine the cause for the error situation. Check the following points to solve the problem.

Backup and restore

Administering OMS

Recovering from a backup failure

Procedure

  • 1 Check the alarm and the log files.

    • a) Check the alarm with the appropriate alarm management tool. The alarm includes the name of the backup log.

    • b) Search for backup-related entries in the syslog. Enter the following command: grep -i backup /var/log/syslog

    • c) Search the backup log for strings ERROR or WARNING and check the status from the end of the log.

  • 2 In case of permission denied error follow instructions below.

Option

Description

If

the error message on the local output device is permission

denied

Then

check that you have the required root privileges.

  • 3 Check that there is enough free disk space for the backup.

Check the amount of available disk space. Enter:

df -h /var/mnt/local/backup

If necessary, free disk space by Transferring backup archive files from OMS to an external storage server and deleting unnecessary backup files.

  • 4 In case of internal database system error follow the instructions below.

Option

Description

If

there is an internal database system error

Then

Check that the databases are up and running with the fshascli

-s /<database> command.

  • 5 In case of DBBackup: timeout error follow the instructions below.

Option

Description

If

the error message in the syslog is DBBackup: timeout while

making a backup for database: <name of database>

Administering OMS

Backup and restore

Option

Description

Then

contact your local Nokia representative.

  • 6 In case the above mentioned instructions solved the problem, follow the instructions below.

Option

Description

If

the above mentioned instructions solved the problem,

Then

refer to the instructions in Making a full software backup in OMS, Making a partial software backup in OMS or Making a custom software backup in OMS.

Else

contact your local Nokia representative.

  • 1.13 Restoring of database in OMS fails Description Restoring of database may fail if, for example:

The user does not have the required privileges to execute the restore command.

There is not enough free disk space available for the backup files. Note that the restore operation takes more disk space than a backup archive file, because the backup archives are unzipped during the restore operation.

The backup archive to be restored is faulty. There is an internal database error.

Symptoms

When restoring a database fails:

The restore process is interrupted.

The system displays an error message on the output device and creates an entry in the syslog file.

Recovery procedures

Refer to the error message shown on the local output device and check the syslog file in /var/log directory to determine the cause for the error situation. Check the following points to solve the problem.

Backup and restore

Administering OMS

Recovering from a failure to restore database

Procedure

  • 1 Check the log files.

    • a) Search for restore-related entries in the syslog. Enter the following command: grep -i restore /var/log/syslog

    • b) Search the backup log for text strings ERROR or WARNING and check the status from the end of the log.

  • 2 Execute the omsbr_restore -c -d <DB_name> <backup_archive> command again and examine the output.

  • 3 In case of permission denied error follow the instructions below.

Option

Description

If

the error message on the local output device is permission

denied

Then

check that you have the root privileges.

  • 4 In case of DBRestore: No such database error follow the instructions below.

Option

Description

If

the error message in the syslog is DBRestore: No such

database

Then

check that you have entered the restore command correctly.

  • 5 Check that there is enough free disk space available. You can check the amount of available disk space using the following command: df -h /var/mnt/local/backup If necessary, free disk space with the instructions in Transferring backup archive files from OMS to an external storage server and delete unnecessary backup files.

  • 6 In case the above mentioned instructions solved the problem, follow the instructions below.

Option

Description

If

the above mentioned instructions solved the problem,

Administering OMS

Backup and restore

Option

Description

Then

refer to the instructions in Restoring databases in OMS

Else

contact your local Nokia representative.

  • 1.14 Restoring of LDAP directory of OMS fails Description Restoring of LDAP directory may fail if, for example: The user does not have the required privileges to execute the restore command. There is not enough free disk space available for the backup files. Note that the restore operation takes more disk space than a backup archive file, because the backup archives are unzipped during the restore operation. The backup archive to be restored is faulty. The system is unable to write into destination files or replace existing files. Symptoms

When restoring the LDAP directory fails:

The restore process is interrupted.

The system displays an error message on the output device and creates an entry in the syslog file.

Recovery procedures

Refer to the error message shown on the local output device and check the syslog file in /var/log to determine the cause for the error situation. Check the following points to solve the problem.

Recovering from a failure to restore LDAP directory

Procedure

  • 1 Check the log files.

    • a) Search for restore-related entries in syslog. Enter the following command: grep -i restore /var/log/syslog

Backup and restore

Administering OMS

  • b) Search the backup log for text strings ERROR or WARNING and check the status from the end of the log.

  • 2 Execute the omsbr_restore -c -l <backup_archive> command again and examine the output.

  • 3 Check that you have the root privileges.

  • 4 In case of invalid directory error follow the instructions below.

Option

Description

If

the error message is invalid directory given as parameter

Then

check that the source and destination directories exist.

  • 5 Check that there is enough free disk space available. You can check the amount of available disk space using the following command: df -h /var/mnt/local/backup If necessary, free the disk space by Transferring backup archive files from OMS to an external storage server and deleting unnecessary backup files.

  • 6 Check that the LDAP server is up and running. Because OMS LDAP is running under RG /Directory you need to check if this directory is enabled and active. Enter the following command: fshascli -s /Directory An example printout of the fshascli -s /Directory command: Directory: administrative(UNLOCKED) operational(ENABLED) usage(ACTIVE) procedural() availability() unknown(FALSE) alarm() Note that when you are restoring the whole system, you can skip this step as the LDAP server is not up and running. Note that LDAP is a critical process of OMS and if it is not up and running OMS will reboot.

Administering OMS

Backup and restore

  • 7 In case the above mentioned instructions solved the problem follow the procedures below.

Option

Description

If

the above mentioned instructions solved the problem

Then

refer to the instructions in Restoring LDAP directory in OMS.

Else

contact your local Nokia representative.

  • 1.15 Restoring of system image, single file, or directory in OMS fails Description Restoring of the system image, a single file, or a directory may fail if, for example:

The user does not have the required privileges to execute the restore command.

There is not enough free disk space available for restoring the backup. Note that the restore operation takes more disk space than a backup archive file, because the backup archives are unzipped during the restore operation.

The backup archive to be restored is faulty.

Symptoms

When restoring the system image, a single file, or a directory fails:

The restore process is interrupted.

The system displays an error message on the output device and creates an entry in the syslog file.

Recovery procedures

Refer to the error message shown on the local output device and check the syslog file in /var/log to determine the cause for the error situation. Check the following points to solve the problem.

Backup and restore

Administering OMS

Recovering from a failure to restore system image, a file, or a directory

Procedure

  • 1 Check the log files.

    • a) Search for restore-related entries in the syslog. Enter the following command: grep -i restore /var/log/syslog

    • b) Search the backup log for text strings ERROR or WARNING and check the status from the end of the log.

  • 2 Execute the omsbr_restore -c -s [<file_or_directory>] <backup_archive> command again and examine the output.

  • 3 In case of no such file or directory error follow the instructions below.

Option

Description

If