Spots 10.0 Backup Restore

SIEMENS S.A.

SPOTS-BAR V1.0M

Installation and User Manual

August/2003

E200204-01-614-V10.0I

SIEMENS S.A.Siemens S.A.

R. Irmãos Siemens, nº 12720-093 AmadoraPortugal

All rights reserved. No part of this document may be reproduced or transmitted in any form or byany means, electronic or mechanical, including photocopying and recording, for any purposeother than the purchaser’s personal use without the written permission of SIEMENS S.A.This document consists of a total of 47 pages ( Annex A included).The information contained in this document is subject to change.

INSTALLATION AND USER MANUAL OG IC R&D ON TMN BD BSW3

E200204-01-614-V10.0I-02 3

Table Of Contents

1 GENERAL INFORMATION .........................................................................................................................61.1 ISSUE CONTROL.........................................................................................................................................61.2 HISTORY ....................................................................................................................................................61.3 REFERENCES .............................................................................................................................................61.4 GLOSSARY AND ABBREVIATIONS .................................................................................................................6

2 INTRODUCTION..........................................................................................................................................82.1 PURPOSE...................................................................................................................................................82.2 SCOPE.......................................................................................................................................................82.3 STARTING POINT ........................................................................................................................................82.4 HARDWARE REQUIREMENTS .......................................................................................................................82.5 THIRD-PARTY SOFTWARE REQUIREMENTS ..................................................................................................9

3 INSTALLATION.........................................................................................................................................103.1 INSTALLATION TASK FLOW ........................................................................................................................103.2 PRE-INSTALLATION TASKS.........................................................................................................................11

3.2.1 TCP-IP Configuration ...................................................................................................................113.2.2 System Hard Disk(s) layout..........................................................................................................113.2.3 Stop SPOTS and Oracle database Services ...............................................................................11

3.3 NETWORKER SERVER EDITION SOFTWARE ................................................................................................113.4 NETWORKER MODULE FOR ORACLE ..........................................................................................................13

3.4.1 Link the Module Library File .........................................................................................................143.5 CONFIGURING JUKEBOX DEVICE ...............................................................................................................143.6 INSTALLING SPOTS-BAR SOFTWARE.......................................................................................................16

3.6.1 Installation of Backup Server........................................................................................................163.7 COMPLEMENTARY INSTALLATION TASKS ....................................................................................................17

3.7.1 Managing Volumes.......................................................................................................................183.7.2 Cartridge Identification .................................................................................................................213.7.3 Add Printer to SPOTS-BAR Groups.............................................................................................223.7.4 Enter Company Information .........................................................................................................243.7.5 Legato Networker License Registration .......................................................................................25

3.7.5.1 Enter Enabler Codes.............................................................................................................................. 253.7.5.2 Enter Permanent Codes ........................................................................................................................ 26

3.8 POST-INSTALLATION TASKS ......................................................................................................................263.8.1 Reboot SPOTS-BAR Computer ...................................................................................................26

4 UNINSTALL...............................................................................................................................................274.1 UNINSTALL TASK FLOW ............................................................................................................................274.2 SPOTS-BAR SOFTWARE.........................................................................................................................27

4.2.1 Remove SPOTS-BAR software....................................................................................................284.3 LEGATO NETWORKER SOFTWARE..............................................................................................................28

4.3.1 Reboot SPOTS-BAR Computer ...................................................................................................29

5 BACKUP PROCEDURES .........................................................................................................................305.1 BACKUP RESOURCES ...............................................................................................................................305.2 FIRST MANUAL BACKUP............................................................................................................................31

5.2.1 Reconfiguring SPOTS_OS schedule ...........................................................................................325.2.2 Enable SPOTS_OS Group...........................................................................................................335.2.3 Start SPOTS_OS Backup Group .................................................................................................345.2.4 Post Manual SPOTS_OS Backup – Reset Schedule ..................................................................35

5.3 ENABLE AUTOMATIC STARTUP OF BACKUPS ..............................................................................................365.4 BOOTSTRAP BACKUP................................................................................................................................37

6 RECOVERY PROCEDURES.....................................................................................................................386.1 OS FILES RECOVERY ...............................................................................................................................386.2 SPOTS DATABASE(S) RECOVERY............................................................................................................39

6.2.1 Restore and Recovery Database with Backup Control files ........................................................396.2.2 Restore and Recovery Database .................................................................................................40


E200204-01-614-V10.0I-02 4

6.2.3 Post Restore Procedures .............................................................................................................416.3 CATALOGUE DATABASE RECOVERY...........................................................................................................436.4 DISASTER RECOVERY...............................................................................................................................43

6.4.1 Preparing for a Disaster ...............................................................................................................436.4.2 Recovery Procedures...................................................................................................................44

ANNEX A – HOW TO INSTALL A LTO TAPE DRIVE ON A SOLARIS SYSTEM ..........................................47


E200204-01-614-V10.0I-02 5

List of Figures and Tables

FIGURE 1 – SPOTS-BAR INSTALLATION TASK FLOW DIAGRAM...................................................10FIGURE 2 – STARTING AUTOCHANGER INVENTORY ..................................................................18FIGURE 3 – FINISH AUTOCHANGER INVENTORY.......................................................................18FIGURE 4 – STARTING OSSPOTS LABEL..............................................................................19FIGURE 5 – OSSPOTS LABELING .......................................................................................19FIGURE 6 – CONFIRM OSSPOTS LABEL...............................................................................20FIGURE 7 – STARTING DBSPOTS LABEL..............................................................................20FIGURE 8 – FINISH DBSPOTS LABEL ..................................................................................20FIGURE 9 – RECYCLE VOLUME ............................................................................................21FIGURE 10 – SELECT MANAGE GROUPS................................................................................22FIGURE 11 – GROUPS .......................................................................................................23FIGURE 12 – SERVER........................................................................................................24FIGURE 13 – LAUNCHING SCHEDULES WINDOW......................................................................31FIGURE 14 –SCHEDULES WINDOW .......................................................................................32FIGURE 15 – EDIT SCHEDULE OS_SPOTS............................................................................32FIGURE 16 – LAUNCHING GROUPS .......................................................................................33FIGURE 17 – GROUPS WINDOW ..........................................................................................33FIGURE 18 – LAUNCHING GROUP CONTROL WINDOW ..............................................................34FIGURE 19 – GROUP CONTROL WINDOW ..............................................................................34FIGURE 20 – START SPOTS_OS GROUP..............................................................................34FIGURE 21 – RESET SPOTS_OS SCHEDULE.........................................................................35FIGURE 22 – LAUNCHING GROUPS .......................................................................................36FIGURE 23 – GROUPS WINDOW......................................................................................36FIGURE 24 – NETWORKER RECOVER WINDOW .......................................................................38FIGURE 25 – CONFLICT RESOLUTION WINDOW .......................................................................39FIGURE 26 – BOOTSTRAP REPORT SAMPLE ...........................................................................44FIGURE 27 – RECOVER OS FILES........................................................................................46

TABLE 1 – NETWORKER DAEMONS.......................................................................................13TABLE 2 – NETWORKER RESOURCES....................................................................................30


E200204-01-614-V10.0I-02 6

1 GENERAL INFORMATION

1.1 Issue Control

This document comprises 47 pages, all pages have issue 01.

1.2 History

Issue Date Changes2003-04-14 Creation

1 2003-05-07 First Edition2 2002-08-22 IUS

1.3 References

/SIG/ SPOTS Installation GuideE200204-01-115-V10.0I-*SPOTS 10.0

/NAG/ Legato NetworkerAdministrator’s Guide for Microsoft Windows Version

/NMO/ Legato NetworkerModule for Oracle for Administrator’s Guide

1.4 Glossary and Abbreviations

AutochangerSee-> Jukebox.

Backup ServerThe equipment where the Networker Server is installed. The backup server is responsible for thebackups co-ordination on the network. It keeps tracking of the backup information, writes/readsbackup data into/from tape devices.

Backup ClientThe equipment where the Networker Client is installed. The backup Client is responsible for thebackup/restore executions triggered by the Backup Server.

CartridgeIt refers to the magnetic storage media used in the Jukebox.

Catalogue DatabaseThe catalogue database is an Oracle instance dedicated exclusively to the Oracle RecoveryManager tool. This database supports the information regarding to the target database backupsand also stores all common scripts used in the backup and recovery tasks.

Index and Resource FilesThe Networker index and resource files are repositories where Networker registers theinformation referent to the backup save set locations and Networker configuration parameters.

JukeboxA jukebox is a storage device, which has the ability to load more than one cartridge. It has one ormore built in tape drives.


E200204-01-614-V10.0I-02 7

LabellingLabelling is the process of giving a cartridge a predefined name and making it usable for backup.

Networker GroupClient or group of clients that start backing up files at designated time.

Networker PoolA Pool enables sorting backup data to a selected set of cartridges (volumes). Each group isassociated to one pool of tapes.

Networker ScheduleThe Networker Schedule permits to define the days a backup should take place and the type ofbackup (Full, Incremental).

NMOStands for (Legato) Networker Module for Oracle and represents the interface between OracleServer and the Legato Networker Client, which allows backup and recovery of the database intothe storage media devices.

PM dataPerformance Management Data collected from the network elements and processed by SPOTS.

PM-ServerA network node where SPOTS Performance Management Services are installed.

RMANOracle Recover Manager tools which allow backup of Oracle databases.

SIDSystem Identifier is a unique keyword used to identify an ORACLE database instance(ORACLE_SID). Each Oracle database included in SPOTS solution has its own SID.

Storage NodeNetworker Storage Node is a special kind of Backup Client that allows storing backup data into alocal Autochanger device.


E200204-01-614-V10.0I-02 8

2 INTRODUCTION

2.1 Purpose

SPOTS Backup and Recovery tool provides a set of procedures to configure the third-partyproducts (Legato Networker and/or Oracle Recover Manager) in order to grant protection againstthe loss of SPOTS data.

This manual has three main chapters:

1. Installation – describes how to install and configure all products involved in the backupsolution.

2. Backup – describes the several types of backup configured by SPOTS-BAR and available toprotect SPOTS data.

3. Recovery – describes how to recover SPOTS data from the backup tapes, recovery ofregular OS files, SPOTS database(s) and disaster recovery.

2.2 Scope

SPOTS-BAR V1.0M solution involves two types of data protection:

1. File-system backup

And/or

2. Database(s) backup.

With PM data volume growing and the increasing data collection frequency, SPOTS database(s)cannot be closed to backup.

SPOTS-BAR V1.0M solves this problem by reconfiguring SPOTS database(s), putting them inarchive log mode of operation and customizing Legato Networker to create Incremental andArchivelog backups.

This way it is possible to perform SPOTS database(s) backups in on-line mode, thus notinterrupting the normal SPOTS application operation.

2.3 Starting Point

SPOTS-BAR V1.0M is certified to operate with SPOTS V10.0 software installed on the SingleServer configuration.

There is only one configuration available in SPOTS-BAR V1.0M the Backup Server.

2.4 Hardware Requirements

For installing Legato Networker and SPOTS-BAR software 100 Mbytes of disk space arerequired.

For installing Recovery Catalogue Database 300 Mbytes of disk space are required in/spots_rman partition SPOTS-BAR Backup Server configuration. It is highly recommended forsecurity reasons to use a physical disk not used by the SPOTS database.

An Autochanger tape device load with a minimum of 2 cartridges is also required for eachconfigured SPOTS-BAR Backup Server.

Note: If you intent to use a LTO tape drive or Library in your the system, see Annex A – How toinstall a LTO tape drive on a Solaris System.


E200204-01-614-V10.0I-02 9

2.5 Third-Party Software Requirements

The product Oracle8i Enterprise Server, release 8.1.7 for Solaris Operating System, must bealready installed as part of the SPOTS Server (with SDS component).

The following software products must be available for installation:

• Legato Networker Server Edition 6.1.3 – Solaris Version.

• Legato Networker Module for Oracle version 3.5, Solaris Version.

In addition, the software licenses for the products Networker Server Network Edition, NetworkerModule for Oracle and Networker Autochanger must be also available depending on thefollowing table:

License Types BS

Networker Server ��

Networker Module Oracle (Whenever SpotsDatabase is installed).

��

Autochanger ��BS – Backup Server


E200204-01-614-V10.0I-02 10

3 INSTALLATION

3.1 Installation Task Flow

The installation task flow displayed below summarizes the installation process for SPOTS-BARBackup Server.

BEGIN INSTALLATION

PRE-INSTALLTASKS (Chapter 3.3)

Networker ServerEdition

(Chapter 3.4)

SPOTS-BARSoftware (Chapter 3.6)

Networker Moduke forOracle

(Chapter 3.6.1)

Managing Volumes(Chapter 3.7.1 and

3.7.2)

Add Printer(Chapter 3.7.3)

Add AdministratorUsers (Chapter 3.7.5)

Company Information(Chapter 3.7.6)

Networker LicenceRegistration (Chapter

3.7.7)

POST-INSTALLTASKS (Chapter 3.8)

Configure JukeboxDevice (Chapter 3.5

and 3.5.1)

Figure 1 – SPOTS-BAR installation task flow diagram


E200204-01-614-V10.0I-02 11

3.2 Pre-installation tasks

3.2.1 TCP-IP Configuration

This task consists in the preservation of the TCP-IP configuration for the computer included inthe SPOTS-BAR solution.

Don’t forget to fill-in Annex 5 – Global data – Operating System Data configuration included on/SIG/ SPOTS Installation Guide.

Note: Store the printed layouts on a Backup Folder and save it in a secure place.Whenever you reconfigure each system’s TCP-IP addresses, you must update thisinformation.

The TCP-IP configuration layout information is used when we want to recover after a systemcrash (See 6.4 - Disaster Recovery).

3.2.2 System Hard Disk(s) layout

This task consists in the preservation of the hard disks configuration (printed layout) for thecomputer included in the SPOTS-BAR solution.

Don’t forget to fill-in Annex 5 – Global Data - Disk Partition Configuration included on /SIG/SPOTS Installation Guide.

Note: Store the printed layouts on a Backup Folder and save it in a secure place.Whenever you reconfigure each system’s hard disks, you must update this information.

The hard disk configuration layout information is used when we want to recover after a systemcrash (See 6.4 - Disaster Recovery).

3.2.3 Stop SPOTS and Oracle database Services

It is necessary to stop all existing SPOTS Services, Oracle database processes Net8-Listenerincluded before starting to install Legato NetWorker software and SPOTS-BAR software.

• Log in as root.

• Stop all SPOTS services by running the following commands:

# /etc/init.d/initSpotsPMS stop

Execute the following commands if SPOTS REAL-TIME module have been installed.

# /etc/init.d/init.saawd stop# /etc/init.d/initServer stop

# /etc/init.d/initAgency stop

• Stop Oracle database processes and Net8 listener executing the next command.

# /etc/init.d/dbora stop

3.3 Networker Server Edition software

This chapter explain how to install Networker Server Edition software.

• Log in as root to the system where you are installing the Networker software.


E200204-01-614-V10.0I-02 12

• Insert the CD-ROM “NetWorker Servers, Clients & Storage Nodes Vol. 1” which containsthe Solaris Operating System version into the system drive.

• Locate the appropriate directory for Solaris on the CD-ROM. (usually is/cdrom/cdrom0/solaris)

• Set the PATH environment variable for root user with the /usr/sbin and /usr/bindirectories.

# PATH=/usr/sbin:/usr/bin:$PATH; export PATH

• The Networker software installation scripts modifies the /etc/rpc and /etc/syslog.conf filesduring the installation process, to preserve the original files making a copy of them.

# cp /etc/rpc /etc/rpc.orig#cp /etc/syslog.conf /etc/syslog.conf.orig

• Enter the pkgadd command to start the Networker software package installation.

# pkgadd –d /cdrom/cdrom0/solaris

As a result, the pkgadd menu is displayed, prompting for the Networker package to install inthis host:

The following packages are available: 1 LGTOclnt NetWorker for Solaris (Backup/Recover) Client (sparc) 6.1.3.Build.428 2 LGTOdrvr NetWorker for Solaris (Backup/Recover) Device Drivers (sparc) 6.1.3.Build.428 3 LGTOlicm NetWorker for Solaris (Backup/Recover) Licensing Manager (sparc) 6.1.3.Build.428 4 LGTOman NetWorker for Solaris (Backup/Recover) Man (sparc) 6.1.3.Build.428 5 LGTOnode NetWorker for Solaris (Backup/Recover) Storage Node (sparc) 6.1.3.Build.428 6 LGTOserv NetWorker for Solaris (Backup/Recover) Server (sparc) 6.1.3.Build.428

Select package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]:

• At the prompt, press [Enter] to install all of the packages on the server at the same time.

• Accept the default values proposed by Networker for all installation questions during thepackages installation, with the following two exceptions:

• When you are prompted for the directory that hold the client and licensing serverinformation, answering with ‘/nsr’.

Directory to use for client, licensing and server information [/spots_db4/nsr]? /nsr

• When you are prompted for the Networker server name, entering thecurrent host name (’pms100’in this example).

Enter the first NetWorker server's name [no more]: pms100

• After installing all the packages just quit the pkgadd tool, entering the option ‘q’.

The following packages are available: 1 LGTOclnt NetWorker for Solaris (Backup/Recover) Client (sparc) 6.1.3.Build.428


E200204-01-614-V10.0I-02 13

2 LGTOdrvr NetWorker for Solaris (Backup/Recover) Device Drivers (sparc) 6.1.3.Build.428 3 LGTOlicm NetWorker for Solaris (Backup/Recover) Licensing Manager (sparc) 6.1.3.Build.428 4 LGTOman NetWorker for Solaris (Backup/Recover) Man (sparc) 6.1.3.Build.428 5 LGTOnode NetWorker for Solaris (Backup/Recover) Storage Node (sparc) 6.1.3.Build.428 6 LGTOserv NetWorker for Solaris (Backup/Recover) Server (sparc) 6.1.3.Build.428

Select package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]: q

• Complete the Networker installation, verifying that the Networker daemons shown in thenext table are running. Enter the following command at the system prompt:

# ps –ef | grep nsr

Networker Installation Packages Networker Daemons

Networker Server nsrd, nsrexecd, nsrindexd,nsrmmdbd, nsrmmd

Networker Client nsrexecd

Networker Storage Node nsrexecd, nsrmmd

Table 1 – Networker Daemons

• If the output does not list nsrd and nsrexecd as current processes, run the followingcommand to start the Networker daemons on the server:

# /etc/init.d/networker start

• Eject the CD-ROM “NetWorker Servers, Clients & Storage Nodes Vol. 1” from thesystem drive.

3.4 Networker Module for Oracle

This chapter explain how to install Networker Module for Oracle software.

• Ensure that you are logged in as root on the system.

• Insert the CD-ROM “NetWorker Modules”, which contains the Oracle Module for UNIXOperating System into the system drive.

• Locate the appropriate directory for Oracle on the CD-ROM. (is/cdrom/cdrom0/oracle/solaris_32 for Oracle8i 32-bits version)

• Enter the pkgadd command to start the Networker Module for Oracle software packageinstallation.

# pkgadd –d /cdrom/cdrom0/oracle/solaris_32

As a result, the pkgadd menu is displayed, prompting for the Networker package to install inthis host:

The following packages are available: 1 LGTOnmo Legato NetWorker Module for Oracle 3.5 (sparc) rt_2002_1Q.Build.43



E200204-01-614-V10.0I-02 14

• At the prompt, press [Enter] to install the LGTOnmo package on the server.

• After installing the LGTOnmo package just quit the pkgadd tool, entering the option ‘q’.

The following packages are available: 1 LGTOnmo Legato NetWorker Module for Oracle 3.5 (sparc) rt_2002_1Q.Build.43


• Eject the CD-ROM “NetWorker Modules” from the system drive.

3.4.1 Link the Module Library File

• Verify that all Oracle instances are shut down, enter the following command at thesystem prompt:

# ps –ef | grep oracle

• Shut down the Oracle instances if they are running, executing the next command:


• Log in as the ORACLE_HOME owner.

# su oracle

• Change symbolic link by executing the commands below:

$ . /etc/spotsenv$ cd $ORACLE_HOME/lib$ rm libobk.so

$ ln –s /usr/lib/libnwora.so libobk.so

• Become root user and reboot the computer, enter command at the system prompt:

# /etc/shutdown –y –g0 –i6

3.5 Configuring Jukebox Device

• Log in as root.

• Stop all SPOTS services by running the following commands:

# /etc/init.d/initSpotsPMS stop

Execute the following commands if SPOTS REAL-TIME module have been installed.

# /etc/init.d/init.saawd stop# /etc/init.d/initServer stop# /etc/init.d/initAgency stop

The Jukebox device configuration is part of Backup Server installation, which allow LegatoNetworker to manage this kind of drives.

Begin the jukebox configuration by execution the jbconfig command.

# jbconfig


E200204-01-614-V10.0I-02 15

You will be prompted with several questions which you must answer according either to theboldface values presented below or keep the proposed value.

1) Install a SmartMedia Jukebox. 2) Install an Autodetected SCSI Jukebox. 3) Install an Autodetected NDMP SCSI Jukebox. 4) Install an SJI Jukebox. 5) Install an STL Silo.

What kind of Jukebox are you installing? [1] 2These are the SCSI Jukeboxes currently attached to your system: 1) [email protected]: Exabyte JukeboxWhich one do you want to install? 1Installing an 'Exabyte Jukebox' jukebox.Name you would like to assign to the jukebox device? jbA brief description of the jukebox device? [[email protected]: Exabyte Jukebox] [PressEnter]Pathname of the control port for the jukebox device? [[email protected]] [Press Enter]Do you want automated device cleaning support enabled? (yes/no) yes

Will media drive 1 be shared by multiple device paths? (yes/no) no

Enter hostname that owns media drive 1: ? [pms100] [Press Enter]Enter pathname of media drive 1: ? [/dev/rmt/0cbn] [Press Enter]using '/dev/rmt/0cbn' as device nameShould the drive be configured as a NDMP device? (yes/no) noThis media device has not been configured yet. Pleaseselect a media device type for /dev/rmt/0cbn. 1) 3480 17) 9490 33) optical 2) 3570 18) 9840 34) qic 3) 3590 19) 9940 35) SD3 4) 4890 20) dlt 36) sdlt 5) 4mm 21) dlt1 37) sdlt320 6) 4mm 12GB 22) dlt7000 38) SLR 7) 4mm 20GB 23) dlt8000 39) tkz90 8) 4mm 4GB 24) dst 40) travan10 9) 4mm 8GB 25) dst (NT) 41) tz85 10) 8mm 26) dtf 42) tz86 11) 8mm 20GB 27) dtf2 43) tz87 12) 8mm 5GB 28) file 44) tz88 13) 8mm AIT 29) himt 45) tz89 14) 8mm AIT-2 30) logical 46) tz90 15) 8mm AIT-3 31) LTO Ultrium 47) tzs20 16) 8mm Mammoth-2 32) LTO Ultrium-2 48) VXAChoice? 31Your jukebox does not report that it has a bar code reader, but it doesreport that it can handle volume tags. Some jukeboxes that have barcodereaders report this way. If your jukebox has a barcode reader,do you want bar code reader support enabled? (yes/no) no

Following are attributes that define cleaning cartridge supportfor the jukebox `jb':

auto clean: Yes default cleanings: 5 cleaning slots: 1 Cleaning cartridge volumes Slot number ------------------------------------ ---------------- Cleaning Tape (5 uses left) 1

Make sure that the slots set aside for cleaning cartridgescontain cleaning cartridges. Networker must know the number


E200204-01-614-V10.0I-02 16

of times it can use each cleaning cartridge. You cancontrol how many times Networker will use each cleaningcartridge by using the command –nsrjb -U (number of uses) -S (slot number)For more details please refer to nsrjb man pages.

Following are attributes that define the cleaningschedule for each device in the jukebox.

name: /dev/rmt/0cbn date last cleaned: cleaning interval: 2 weeks cleaning required: No

Verify that the values for these attributes are appropriatefor your installation. If not check documentation on how toset up automated cleaning cartridge support.

Jukebox has been added successfully

Would you like to configure another jukebox? (yes/no) no

3.6 Installing SPOTS-BAR Software

• Insert SPOTS-BAR media on the system’s CD ROM.

• Enter the pkgadd command to start the SPOTS-BAR software package installation.

# pkgadd –d /cdrom/cdrom0/spots_bar

As a result, the pkgadd menu is displayed, prompting for the Spots-BAR package to install inthis host:

The following packages are available: 1 SpotsBAR SPOTS Backup and Restore (sparc) Dev Release 04/23/2003


• At the prompt, press [Enter] to install the SpotsBAR package on the server.

• After installing the SpotsBAR package just quit the pkgadd tool, entering the option ‘q’.

Installation of <SpotsBAR> was successful.

The following packages are available: 1 SpotsBAR SPOTS Backup and Restore (sparc) Dev Release 04/23/2003


3.6.1 Installation of Backup Server

This chapter explains how to use SPOTS-BAR installer (installBackup) to configure a BackupServer.

• After the SpotsBAR package have been installed, go to /opt/spots/Backup/bin directoryand executing the installBackup program.


E200204-01-614-V10.0I-02 17

# cd /opt/spots/Backup/bin# ./installBackup

As a result, the installBackup program displays several installation messages and prompting forthe ORACLE_SID of the target database, Networker home path and Server Name, which youmust answer according either to the boldface values presented below or keep the proposedvalue.

###################################################################### !!! SPOTS-BAR - BACKUP & RECOVERY INSTALLER !!!#####################################################################

Enter the ORACLE SID of target database (default:spot) [?,q] [Press Enter]

Enter the NSR_HOME directory (Legato Networker home path) [?,q] /nsr

Enter the Server name [?,q] pms100

Displays several installation messages ………………………………………………….

SPOTS-BAR software installation terminated successfully without warnings.#

The ‘SPOTS-BAR software installation terminated successfully without warnings.’ message isdisplayed at the end of installBackup execution.

Note: If SAS access to the RC Symbolic Names information was previously configured(as a step of the SPOTS Long-Term Installation - see /SIG/ SPOTS Installation Guide,Section 7.5.6 "RC Access Specifics"), the SPOTS-BAR software installation shallremove the RC Oracle Service definitions from the “tnsnames.ora” file located in thesubdirectory “network/spots_ora_admin” of the “ORACLE_HOME” directory. However,these definitions are saved in a “tnsnames.ora.SAVE” file created in the same directory.

Perform the following actions (as root user) to recover the RC Oracle Service definitions:

Open both the "tnsnames.ora" and “tnsnames.ora.SAVE” files. In the latter file, locate theentries defining the RC Oracle service names (see /SIG/ SPOTS Installation Guide,Section 7.5.6 "RC Access Specifics", step "As root user, edit the file tnsnames.ora...”).Copy the entries to the end of the “tnsnames.ora” file and save the modifications.

3.7 Complementary Installation Tasks

The next administration tasks must be done before SPOTS-BAR can operate properly.

Launch Networker Administrator window.

• At the system prompt run the following command:

# nwadmin -s pms100


E200204-01-614-V10.0I-02 18

3.7.1 Managing Volumes

Fill the jukebox device with the tape cartridges before starting to manage the media volumes.

Figure 2 – Starting Autochanger Inventory

• Click on Media->Inventory menu button to provide Networker with knowledge about ofhow many cartridges are loaded and where they are placed in the jukebox.

Figure 3 – Finish Autochanger Inventory

• On the Jukebox Inventory window, fill-in the Slot Range to inventory and click on OKbutton.

• Click on Cancel button to close the Jukebox Inventory window when the inventoryoperation is finished.

• Having returned to the nwadmin window, click on Media->Label… menu button to enableNetworker to catalog the distribution of tape cartridges per volume Pools.


E200204-01-614-V10.0I-02 19

Figure 4 – Starting OSSPOTS Label

The Jukebox Labeling window will be displayed.

Figure 5 – OSSPOTS Labeling

• Enter Slot Range – Accept the default value of First (2) and set Last to 4 to reserve thefirst three tapes of the autochanger. (In the present case the Slot 1 will be used by thecleaning tape).

• Select OSSPOTS pool from Pool option list field.


E200204-01-614-V10.0I-02 20

• Click OK to start the labeling process.

Figure 6 – Confirm OSSPOTS Label

• Click on OK button to continue

The ‘Finished labeling volumes.’ message is presented upon completion on the bottom of theJukebox Labeling window.

Figure 7 – Starting DBSPOTS Label

• Enter another Slot Range – Set First to 5 and Last to 6 to reserve the last two tapes ofthe autochanger.

• Select DBSPOTS pool from Pool option list field

• Click OK to start the labeling process.

Figure 8 – Finish DBSPOTS Label

• Click on OK button to continue

The ‘Finished labeling volumes.’ message is presented upon completion on the bottom of the


E200204-01-614-V10.0I-02 21

Jukebox Labeling window.

• Click on the Cancel button to terminate cataloging the distribution of tape cartridges pervolume Pools.

Note: Sometimes a window is presented during the labeling process, corresponding toa situation where used tapes are loaded in the Autochanger magazine.

Figure 9 – Recycle Volume

Click on OK button to recycle the volume and continue the labeling process.

3.7.2 Cartridge Identification

It is very important to physically identify the cartridges stored in your jukebox, allowing an easierand quicker cartridge identification, specially when the recovery procedure requests for the tapevolumes that aren’t present in jukebox and that must be loaded prior to continue the process.

• Eject the jukebox magazine.

• For each cartridge in the magazine slot:

• Remove the cartridge from the magazine slot.

• Write the volume name corresponding to that cartridge in its label. (E.g.OSSPOTS.0001).

• Put the cartridge back into the same slot from where you removed it.

• Insert the magazine in jukebox.


E200204-01-614-V10.0I-02 22

3.7.3 Add Printer to SPOTS-BAR Groups

A printer must be configured on the SPOTS-BAR groups to allow the Backup Server to print theBootstrap report information.

Figure 10 – Select Manage Groups

• Click in Customize->Groups… menu button.


E200204-01-614-V10.0I-02 23

Figure 11 – Groups

• Click over SPOTS_DB_0 group to select it.

• Enter the printer name into the Printer field. (The printer must have been previouslyconfigured within Solaris Operating System).

• Click on the Apply button to accept the configuration.

• Repeat the previous steps for SPOTS_DB_1, SPOTS_DB_2, SPOTS_DB_A andSPOTS_OS groups.

• Click on the File->Exit menu button to return into nwadmin window.


E200204-01-614-V10.0I-02 24

3.7.4 Enter Company Information

The first task in the registration process is to fill-in the customer company identificationinformation.

• Click on Server->Server SetUp… menu button to open the Server window.

Figure 12 – Server

• The Server window will be displayed, fill-in all available fields with the appropriatecustomer identification.


E200204-01-614-V10.0I-02 25

• Click on Apply button to save.

• Click on File->Exit menu button to finish this task.

3.7.5 Legato Networker License Registration

The Legato Networker license registration involves the next two tasks described below.

3.7.5.1 Enter Enabler Codes

The first task in the registration process involves entering the Networker Enabler codes that allowthe customer to activate the Networker product-enabling period (45 days since the installationdate).

The enabler codes are provided in the Purchase Certificate document supplied with theNetworker software media kit.

During the enabling period the customer will receive the authorization codes, which allow thepermanent use of Networker software.

• From Networker Administrator program nwadmin select Server->Registration menu baroption.

• In the Enable code attribute, click on Create button and enter the license enabler code.


E200204-01-614-V10.0I-02 26

• Click on Apply button to save the supplied information.

• Repeat the last steps for Networker Module for Oracle and Networker AutochangerModule products.

After you completely entered the enabler codes, you must generate the registration reportinformation and send it to Legato Networker Company.

• From main menu, select Server->Registration option.

• Select View->Tabular menu bar option from Registration window.

• Select File->Print.

• Send the generated report to Legato Networker Company.

3.7.5.2 Enter Permanent Codes

The last registration task occurs when you receive the authorization codes from LegatoNetworker Company.

• From Networker Administrator program nwadmin select Server->Registration menu baroption.

• Fill-in the Auth code field with the received permanent authorization code.

• Click on Apply button to save the supplied information.

• Repeat the last steps for Networker Module for Oracle and Networker AutochangerModule products.

3.8 Post-Installation Tasks

3.8.1 Reboot SPOTS-BAR Computer

To Finish SPOTS-BAR installation, reboot the computer.

• Become root user and enter command at the system prompt:



E200204-01-614-V10.0I-02 27

4 UNINSTALL

4.1 Uninstall Task Flow

The task flow presented below summarizes all process steps for uninstalling SPOTS-BAR.

BEGIN UNINSTALL

Legato NetworkerSoftware (Chapter 4.3)

SPOTS-BARSoftware (Chapter 4.2)

Backup Server(Chapter 4.2.1)

END

Remove SPOTS-BARSoftware (Chapter 4.2.4)

4.2 SPOTS-BAR software

The uninstall process removes the SPOTS-BAR configuration settings and the SPOTS-BARsoftware.

• Login as root user

• Stop only the SPOTS services - (See 3.2.3 - Stop SPOTS ).

• Go to /opt/spots/Backup/bin directory and executing the uninstallBackup program.

# cd /opt/spots/Backup/bin# ./uninstallBackup

During the execution of the uninstallBackup program you need to confirm the SPOTS-BAR de-installation.

###################################################################### !!! SPOTS-BAR - BACKUP & RECOVERY UNINSTALLER !!!#


E200204-01-614-V10.0I-02 28

####################################################################

Do you want to Uninstall SPOTS - Backup software? (Y/N): y.......................

SPOTS-BAR software uninstaller terminated successfully without warnings.#

4.2.1 Remove SPOTS-BAR software

After de-installing SPOTS-BAR configuration, you must remove the software via the PackageRemove program.

# pkgrm SpotsBAR

As a result, the pkgrm menu is displayed, prompting for the Spots-BAR package to uninstallin this host:

The following package is currently installed: SpotsBAR SPOTS Backup and Restore (sparc) Dev Release 05/05/2003

Do you want to remove this package? y

Removal of <SpotsBAR> was successful.#

• At the prompt, press [y] to uninstall the SpotsBAR package on the server.

4.3 Legato Networker software

To de-install Legato Networker software we must execute the following procedures.

• Shut down the Oracle instances, executing the next command:


• Log in as the ORACLE_HOME owner.

# su oracle

• Change symbolic link by executing the commands below:

$ . /etc/spotsenv$ cd $ORACLE_HOME/lib$ rm libobk.so

$ ln –s libdsbtsh8.so libobk.so

• Become root user and remove the Networker Module for Oracle software package,enter command at the system prompt:

# pkgrm LGTOnmo

• At the prompt, press [y] to uninstall the LGTOnmo package on the server.

• Remove the Networker Server Edition software packages, enter the command at thesystem prompt:


E200204-01-614-V10.0I-02 29

# nsr_shutdown# pkgrm LGTOserv LGTOnode LGTOlicm LGTOman LGTOdrvr LGTOclnt

Because there are dependences between Networker packages, you must respect the packageorder present in the previous pkgrm command.

4.3.1 Reboot SPOTS-BAR Computer

To Finish SPOTS-BAR de-installation, reboot the computer.



E200204-01-614-V10.0I-02 30

5 BACKUP PROCEDURES

5.1 Backup Resources

This chapter describes the main Networker backup resources configured by SPOTS-BARsolution.

Group Schedule Pool Backup

Name StartTime

Periodicity Week Day Name Type Targets

SPOTS_OS 13:00 24 hours Sunday OSSPOTS Full Solaris OS files,

SPOTS Application software

and Recovery Cataloguedatabase.

SPOTS_DB_0 20:00 24 hours Saturday DBSPOTS Incremental

Level 0

SPOTS database(s)

SPOTS_DB_1 20:00 24 hours Tuesday DBSPOTS Incremental

Level 1

SPOTS database(s)

SPOTS_DB_2 20:00 24 hours Thursday DBSPOTS Incremental

Level 2

SPOTS database(s)

SPOTS_DB_A 02:00 8 hours Every day DBSPOTS Archive log

Files

SPOTS database(s)

Table 2 – Networker Resources

The Networker resources were designed to cover the majority of SPOTS customer installations.However in some circumstances these resources can be changed using the NetworkerAdministrator tool.

For instance, the SPOTS_OS backup group is configured to start every Sunday at 13:00, as inmost countries Sunday is typically a day of low work. However this rule is no longer valid whenwe install SPOTS in an Arabic customer where the weekend is on Friday.

So the Networker schedule must be redefined according to this reality.

NOTE: The redefinition of previous resources must accomplish the following rules:

- Backups triggered by SPOTS_OS group will backup also the recovery cataloguedatabase, which means that the recovery catalogue database remains closed duringthe backup time frame execution. Any SPOTS database backup started meanwhilewill fail.

- Try to not overlap the backup group executions.


E200204-01-614-V10.0I-02 31

5.2 First Manual Backup

It’s highly recommendable to make a first manual SPOTS_OS backup after SPOTS-BARinstallation and before enabling all groups to start backup automatically.

Launch Networker Administrator window.

• Login as root user and enter on system prompt the following command:

# nwadmin -s pms100

Figure 13 – Launching Schedules Window

• Select from main menu the Customize->Schedules option.


E200204-01-614-V10.0I-02 32

5.2.1 Reconfiguring SPOTS_OS schedule

Figure 14 –Schedules Window

• Click on OS_SPOTS schedule option to select the schedule for SPOTS_OS group.

Figure 15 – Edit schedule OS_SPOTS

Observe the displayed calendar:

• If the current day of week matches with the day of week previously configured(Sunday/Full), click on File->Exit menu button to leave schedule configuration.

• if the day of week previously configured to execute the SPOTS_OS backup (Sunday/Full)does not match the current day (e.g. Friday), click in any Friday column button to select it.

• Click on Full option of Level list field to select it.

• Click on apply button to accept the configuration.

• Select File->Exit menu button to exit from Schedules window.


E200204-01-614-V10.0I-02 33

5.2.2 Enable SPOTS_OS Group

Figure 16 – Launching Groups

• Select from main menu the Customize->Groups option.

Figure 17 – Groups Window

• Select SPOTS_OS group from Groups field list.


E200204-01-614-V10.0I-02 34

• Select Enabled option in the Autostart field.

• Click on Apply to save the group configuration.

• Select File->Exit menu button to exit from Groups window.

5.2.3 Start SPOTS_OS Backup Group

Figure 18 – Launching Group Control Window

• Select from main menu the Server->Group Control... option.

Figure 19 – Group Control Window

• Select SPOTS_OS group and click on Start button.

Figure 20 – Start SPOTS_OS group


E200204-01-614-V10.0I-02 35

• Click on OK button to confirm the SPOTS_OS group starting.

The SPOTS_OS group starts immediately and all clients assigned to it will be backed-up.

5.2.4 Post Manual SPOTS_OS Backup – Reset Schedule

This task is only relevant when changes are made on default schedule behavior for SPOTS_OSgroup. (See 5.2.1 - Reconfiguring SPOTS_OS schedule).

You should execute the steps specified in 5.2.1 - Reconfiguring SPOTS_OS schedule until theLevel list step of OS_SPOTS schedule.

Figure 21 – Reset SPOTS_OS schedule

• Click on Skip option of Level list field to select it.

• Click on apply button to accept the configuration.

• Select File->Exit menu button to exit from Schedules window.


E200204-01-614-V10.0I-02 36

5.3 Enable Automatic Startup of Backups

SPOTS-BAR groups enabling of autostart feature is the action that allows correspondingbackups to perform SPOTS automatically.

Each backup group starts automatically according to its start time, periodicity and scheduled dayof week, resources that were previously configured and assigned.

Figure 22 – Launching Groups

• Select from main menu the Customize->Groups option.

Figure 23 – Groups Window


E200204-01-614-V10.0I-02 37

• Click over SPOTS_DB_0 group to select it.

• Set Autostart feature to Enabled.

• Click on Apply button to accept the configuration.

• Repeat the previous steps for SPOTS_DB_1, SPOTS_DB_2 and SPOTS_DB_A groups.

The SPOTS_OS group was already enabled when we performed the first manual backup.

The Default group is not used in SPOTS-BAR solution - do not enable it.

5.4 Bootstrap Backup

Bootstrap backup it is a special kind of Networker backup that occurs automatically at the end ofSPOTS-BAR backup execution.

It consists in a backup set that includes the client index, media index and resource database ofNetworker Server.

The bootstrap information printed at the end of every bootstrap backup is essential for recoveringthe PM-Servers after a system crash. (See 6.4 - Disaster Recovery).

Once more, store this information on Backup Folder and save it in a secure place.


E200204-01-614-V10.0I-02 38

6 RECOVERY PROCEDURES

The main goal of this section is to explain how to recover SPOTS data from the backups madeby SPOTS-BAR groups when corruption of data or a PM-Server system crash occurs.

The following recovery procedures are available.

6.1 OS files Recovery

The OS files recovery occurs in a scenario where the SPOTS application software, SPOTS-BARsoftware and any other relevant files are corrupted or simply have disappeared from Solaris file-system.

In such cases the following steps shall be performed:

• Login as root on the system where the missing or damaged files were/are.

Launch the Networker Recover program nwrecover.

# nwrecover -s pms100

Figure 24 – Networker Recover Window

• Navigate on the browser tree, selecting the files and directories that you want to restore.

• Click on Mark/Unmark icon to select/de-select files and directories (E.g. /opt/spots).

• To begin the recover process, you can either click on the Start icon or select Start Recoverfrom the menu bar File option.


E200204-01-614-V10.0I-02 39

Figure 25 – Conflict Resolution Window

• Answer No for the first question ‘Do you want to be prompted…’.

• Select ‘Overwrite the existing file’ option, to answer for ‘When conflict occurs, the programshould ?’ question.

• Click on OK button to accept the conflict resolution options and to start the recover process.

6.2 SPOTS Database(s) Recovery

The SPOTS Database recovery scenario occurs when the SPOTS database(s) installed in PM-Server(s) became damaged due to a file-system block corruption, software bugs that internallydamaged the database or by an accidental removal of part or the whole database data files.

It is very important to evaluate the cause of the database crash. This investigation must beperformed using the Oracle Alert log file for the damaged database instance.

The Alert log file is located in the $ORACLE_HOME/trace_<SID>/bg path with the filenameformat alert_<SID>.log, where <SID> is the System Identifier for the database (E.g./opt/oracle/product/trace_spot/bg/alert_spot.log).

Execute the following steps to recover a damaged SPOTS database.

• Login as root on the PM-Server where the damaged SPOTS database was installed.

• Stop all SPOTS services - (See 3.2.3- Stop SPOTS ).

• Disable all backup groups (SPOTS_DB_[0-2,A] and SPOTS_OS) to prevent them fromautomatically starting during the recovery execution.

• Stop/Disable all batch-jobs. If you have configured batch-jobs for DBloader and/or filetransfer jobs for traffic-files, stop them.

• Go to $SPOTS_DIR/Backup/bin directory and execute the restoreBackup command.

# ./restoreBackup

6.2.1 Restore and Recovery Database with Backup Control files

The method of restoring SPOTS database by applying the backup control files is required whenall database control files are corrupted or were erased as a consequence of the crash.


E200204-01-614-V10.0I-02 40

####################################################################

## !!! SPOTS-BAR RESTORE & RECOVERY DATABASE TOOL !!!#####################################################################

Enter the ORACLE SID of target database (default:spot) [?,q]

Selection List1 Stop Database2 Start Database in NOMOUNT state (to restore control file)3 Start Database in MOUNT state (to restore database)4 Open Database5 Open Database (reset logs)6 Restore Database7 Restore Database (with control file)8 Quit

Enter selection [?,??]:

• Press enter to accept the default ORACLE_SID.

• Stop the SPOTS database – Enter 1 at the selection prompt.

• Start the database in NOMOUNT state, Enter 2.

• To Restore and Recovery the SPOTS database with control files - Enter 7.

• Open SPOTS Database, resetting the online redo log files and resynchronize theRecovery Catalog Database – Enter 5.

• Enter 8 at the selection prompt to quit from SPOTS-BAR Database Recovery program.

6.2.2 Restore and Recovery Database

The SPOTS database restoring method is required when one or more database areas aredamaged or erased as a consequence of the crash, but the database control files were notaffected.

####################################################################

## !!! SPOTS-BAR RESTORE & RECOVERY DATABASE TOOL !!!#####################################################################

Enter the ORACLE SID of target database (default:spot) [?,q]

Selection List1 Stop Database2 Start Database in NOMOUNT state (to restore control file)3 Start Database in MOUNT state (to restore database)4 Open Database5 Open Database (reset logs)6 Restore Database7 Restore Database (with control file)8 Quit

Enter selection [?,??]:


E200204-01-614-V10.0I-02 41

• Press enter to accept the default ORACLE_SID.

• Stop the SPOTS database – Enter 1 at the selection prompt.

• Start the database in MOUNT state - Enter 3.

• To Restore and Recovery the SPOTS database, Enter 6.

• Open SPOTS Database – Enter 4.

• Enter 8 at the selection prompt to quit from SPOTS-BAR Database Recovery program.

6.2.3 Post Restore Procedures

• Make a manual database backup level 0 (zero) after a successful SPOTS database restore& recovery, with or without control files.

The procedures to execute this backup are similar with those described in 5.2 -


E200204-01-614-V10.0I-02 42

First Manual Backup, with the following exceptions:

1. The backup group used to manually backup the SPOTS database must beSPOTS_DB_0 instead of SPOTS_OS described in 5.2 -


E200204-01-614-V10.0I-02 43

First Manual Backup.

2. Before starting the database backup level 0(zero) you must enable the SPOTS_DB_0group.

3. After finishing the SPOTS_DB_0 backup group, you must enable SPOTS_DB_1,SPOTS_DB_2, SPOTS_DB_A and SPOTS_OS backup groups.

• Start/Enable all batch-jobs. If you have configured batch-jobs for DBloader and/or filetransfer jobs for traffic-files, start them.

• Reboot the Computer (See 3.8.1 - Reboot SPOTS-BAR Computer).

6.3 Catalogue Database Recovery

A Catalogue Database recovery scenario occurs when the Catalogue database installed in aPM-Server, acting as a Backup Server, becomes damaged due to a file-system block corruption,software bugs that internally damaged the database or by an accidental removal of the databasedata files.

A Catalogue Database holds all information related with all SPOTS database(s) backups - onceit becomes damaged no more SPOTS database(s) backups or recoveries can be made until ithas been recovered.

To recover the Catalogue database execute the following tasks:

• Login as root on the Backup Server.

• Stop all SPOTS and Oracle database services (See 3.2.3- Stop SPOTS ).

• Execute an OS files recovery procedure (See 6.1 - OS files Recovery) for all files containedinside the directory that holds the Recovery Catalogue database (/spots_rman ).

• Reboot the computer to start all services stopped before the recovery execution.


6.4 Disaster Recovery

The Disaster recovery scenario is applicable when several system failures caused by systemhard-disk(s) crashes or by data disruption have put the PM-Server(s) out of service.

The next procedures describe how to recover from a crash of an entire PM-Server acting as aBackup Server.

Due to the complexity of this theme, we suggest you to read the Legato Networker DisasterRecovery Guide available in Networker CD-ROM Documentation Suite.

6.4.1 Preparing for a Disaster

You need to keep saved and up-to-date the following information that will be necessary torecover the system after a crash.

• Solaris 8 CD-ROM and Solaris patches (same version/level as was previously installed).

• Jukebox software drives.

• Legato Networker Software and authorization codes.

• Operation system configuration information.

• Hard-Disk(s) layout configuration.

• TCP-IP configuration information.


E200204-01-614-V10.0I-02 44

6.4.2 Recovery Procedures

This chapter summarizes the disaster recovery procedures for SPOTS-BAR Backup Server.

1. Replace the damaged hardware.

2. Re-install the Solaris 8 Operating System if necessary.

3. Re-install the Solaris 8 patches.

4. Re-install Networker into its original location

5. Login as root user.

6. Run the jbconfig command to install the autochanger (See - 3.5 Configuring JukeboxDevice).

7. Reset the autochanger.

nsrjb -HE8. Make an inventory of all tapes:

nsrjb -Iv –S 1-109. The information contained in the bootstrap report is necessary now to determine the volume

where the most recent bootstrap was stored. The bootstrap report contains also the save setID information required later in this recovery process. If you loose the bootstrap report youmust scan the most recent volumes until you find it by using the commands nsrjb –lnv -S<slot-number> –f /dev/rmt/0cbn and then scanner –B /dev/rmt/0cbn.

February 20 11:06 2002 pms100's bootstrap information Page 1

date time level ssid file record volume01/29/02 18:18:25 full 1458008321 23 0 DBSPOTS.000101/29/02 19:00:02 full 1458673665 2 0 OSSPOTS.00101/29/02 20:00:02 full 1459601153 24 0 DBSPOTS.000101/29/02 20:00:04 full 1459601154 24 1 DBSPOTS.000101/29/02 20:24:22 full 1459942913 58 0 DBSPOTS.000101/30/02 02:02:58 full 1465143809 64 0 DBSPOTS.000101/30/02 09:15:19 full 1471784705 43 0 OSSPOTS.00101/30/02 10:05:03 full 1472548609 70 0 DBSPOTS.000101/30/02 18:03:48 full 1479902209 76 0 DBSPOTS.000101/30/02 19:33:02 full 1481272833 84 0 OSSPOTS.00101/30/02 20:00:02 full 1481724929 77 0 DBSPOTS.000101/30/02 20:00:04 full 1481724930 77 2 DBSPOTS.000101/30/02 20:00:05 full 1481724931 77 1 DBSPOTS.000101/31/02 02:03:23 full 1487268609 83 0 DBSPOTS.0001

Figure 26 – Bootstrap Report Sample

We need to determine the autochanger slot where the volume DBSPOTS.0001 was placed.

10. Once you have determined the slot number where the volume was placed, execute thefollowing command to load the DBSPOTS.0001 volume placed in autochanger slot 4 into thetape device.

nsrjb –lnv -S 4 –f /dev/rmt/0cbnRun the mmrecov command to recover the media database and resources configuration files,once again the bootstrap report information plays a crucial role in this process.

• The following output is presented:

mmrecov: Using pms100 as server

• When the following message appears, enter the save set ID for the latest bootstrap.

Enter the latest bootstrap save set ID [ ]: 1487268609

• When the following message appears, enter the file number to begin the recovery. Ifunknown, press [Enter]. set ID

Enter starting file number (if Known) [0]: 83


E200204-01-614-V10.0I-02 45

• When the following message appears, enter the first record number to begin the recovery. Ifunknown, press [Enter]. set ID

Enter starting record number (if Known) [0]: 0

• From now on press [Enter] to reply with the default answer to all mmrecov questions.

11. As the configuration files cannot be reliably overwritten while Networker is running,mmrecov recovered the res directory as res.R by default. To rename the configuration filesexecute the following steps:

• Shut down the Networker daemons by entering the nsr_shutdown command at the Solariscommsnd prompt. Rename the existing res directory to res.orig.

• Rename the recovered res.R directory to res.

• Restart the Networker daemons previously stopped by first entering the nsrexecdcommand; then enter the nsrd command to complete the Networker startup.

• After verifying that the Networker configurations are correct, remove the /nsr/res.origdirectory.

12. Once you have successfully recovered the server media database and resourcesconfiguration files, you need to recover all indexes for all clients on the Networker Server.

Enter the following command:

nsrck -L713. Now you can recover the Networker Server client data for PM-Server. This task involves the

following steps:

• Recover the additional data stored under Networker home directory.

Launch the Networker User program nwrecover from the Solaris system prompt..

- Select and mark the Networker directory (e.g. ‘/nsr’) for recovery.

- Unmark the following directories.

1. Networker indexes - located in the /nsr/index directory.

2. Networker media database - /nsr/mm directory.

3. Networker configuration files - /nsr/res directory.

- Only for SPOTS-BAR Backup Server configuration, select and mark theSPOTS_OS.res file located under /nsr/res directory.

- To begin the recover process, you can either click on Start icon or select Start Recoverfrom the File menu bar.

• Recover the remainder OS files (See 6.1 - OS files Recovery).


E200204-01-614-V10.0I-02 46

- Important: Do not recover the home directory and sub-directories whereNetworker software was installed.

- To Skip this information unmark the Network Home (by default /nsr) in NetworkerUser recover window.

Figure 27 – Recover OS Files

• Recover Catalogue Database (See 6.3 - Catalogue Database Recovery).

• Recover SPOTS Database with backup control files variant (See 6.2.1 - Restore andRecovery Database with Backup Control files).


E200204-01-614-V10.0I-02 47

ANNEX A – HOW TO INSTALL A LTO TAPE DRIVE ON A SOLARIS SYSTEM

To install a LTO tape drive on a Solaris 8 operating system, you need to things.

First select an unused SCSI ID for the tape drive. Then modify the st.conf file and rebuild thekernel.

To find the available SCSI ID’s you need to halt the system.

From the command prompt enter:

ok probe-scsi-all

As a result, all detected SCSI devices and SCSI ID’s are displayed.

Choose an unused SCSI ID for the LTO tape drive, refer to your LTO or library instructions onsetting the drive’s SCSI ID.

Power off the system and attach the LTO tape drive to the SCSI bus, apply power to the LTOdrive and bring the system back up.

Before the LTO tape drive can be used by Solaris operating system the following commandsmust be executed:

• Login as root user.

• Change into /kernel/drv directory.

• Make a copy of the st.conf file in order to preserve the original content.

• Edit the st.conf file and enter the lines below

tape-config-list="IBM Ultrium-TD1", "IBM Ultrium", "Class-3580";Class-3580 = 1,0x24,0,0x45863D,2,0x00,0x01,0;

• There are five spaces between the words IBM and Ultrium-TD1 for Solaris 8 st.confentries.

• Save the st.conf changes and remove the tape device files located under /dev/rmtdirectory.

• Reboot the Solaris system, using the command boot –r to enable a kernel compile tocreate the tape devices.

• Load a tape into the LTO drive using the library command panel.• Testing the LTO tape status using the mt command.

# mt -f /dev/rmt/0 status

• If the first line of output from the mt command looks like this..

IBM Ultrium LTO tape drive:

… then the st.conf file was edited properly, and the device files are built with thespecified options.

• If the first line of output from the mt command looks like this..

Vendor ‘IBM ‘ Product ‘Ultrium LTO’ tape drive:

… then the st.conf file was not edited properly, and the device files are not built with thespecified options. In this case, remove the device files under /dev/rmt directory, check thest.conf file for proper LTO entry and rebuild the kernal.

Spots 10.0 Backup Restore

Education

Transcript of Spots 10.0 Backup Restore