[i]

Install and configure legato networker 7.1 on Redhat Linux

This procedure explains how to install and configure Legato Networker 7.1 on Redhat Linux 9. To know if your Redhat version is certified with Legato Networker 7.1, check the Legato web site for more

updated information Legato web site.  

Topics

·        Introduction

·        Download Legato Networker 7.1 from Legato Web site

·        Installation requirements

·        Server Installation

·        ·Client installation

·        Verifying the installation

·        Perform a test backup using a directory device

·        Uninstalling the networker software

·        Concepts and definitions

·        Install Legato Networker Module for oracle 4.1 on RedHat

·        Uninstall Legato Networker Module for oracle 4.1 on RedHat

·        Configure scheduled Oracle backups (8i, 9i, 10g)

·        Restore and recover an Oracle backup (8i,9i.10g)

 

Introduction 

The Legato NetWorker product is a suite of storage management software that provides backup, recovery, and other services to computers with a wide variety of

Operating systems and data types. 

The NetWorker product has four major components: 

§        NetWorker client: You install the NetWorker client software on all computers that you want to back up to the NetWorker server.

§        NetWorker storage node: A storage node controls storage devices such as tape drives, autochangers, and silos.

§        NetWorker server: provides control and scheduling for NetWorker operations.

§        Legato License Manager: The Legato License® Manager provides a central place for managing the licenses of all your NetWorker clients and servers. 

Top of the document 

Download Legato Networker 7.1 from Legato Web site  

§        Download the Legato networker file nw71_linux_x86.tar.gzfrom Legato web site

§        Uncompress the downloaded software using the following command: # gunzip nw71_linux_x86.tar.gz

§        Extract the uncompressed, tarred file using the following command: # tar -xvpf nw71_linux_x86.tar 

Top of the document 

Installation requirements 

The following are general NetWorker installation requirements: 

§        All NetWorker servers, clients, and storage nodes must have TCP/IP installed, configured, and networked.

§        The designated server name that the NetWorker software requests must be the hostname of the backup server.

§        The TCP/IP hostname must be identical to the computer name. Do not include an underscore character (_) in the computer name. 

Each storage node requires a client connection license: A NetWorker storage node must have both the NetWorker client software and the storage node software installed. 

Legato Networker 7.1 can be installed on the following Linux versions (Red Hat): 

§        Red Hat 7.1 with Kernel 2.4.2-2

§        Red Hat Advanced Server edition 2.1 with kernel 2.4.9-e.3

§        Red Hat 7.2 with Kernel 2.4.7-10

§        Red Hat 7.3 with Kernel 2.4.18-3

§        Red Hat 8 with Kernel 2.4.18-1 

Hardware requirements for Networker server: 

§        Memory RAM: 128 MB

§        Disk storage for software: 120 MB

§        Online indexes: 5% of total backup data. 

The following pathnames and directories are required for installation: 

Software and Documentation Files

NetWorker Server Default Location

Space Needed

NetWorker Administrator program and NetWorker Client program files

/usr/bin

17 MB

NetWorker daemon and utility command files

/usr/sbin

72 MB

Device drivers

/usr/lib/nsr

6 MB

Online client file and server indexes; media database

/nsr

4 MB

License Manager files

/usr/sbin

/usr/nsr/lic/res

/nsr/lic/res

2 MB

22 KB

21 KB

NetWorker man pages

/usr/share/man

2 MB

 Top of the document

Server Installation 

On the computer designated as the NetWorker server, install all the NetWorker software packages in the following order: client, device driver, storage node, and server.

The License Manager software can be installed at any point in this sequence after the client package is installed 

To install the software: 

§        Enter the following commands to install the client, device driver, storage node, server, and License Manager software:

# rpm -ivh lgtoclnt-7.1-1.i686.rpm lgtodrvr-7.1-1.i686.rpm lgtonode-7.1-1.i686.rpm lgtoserv-7.1-1.i686.rpm lgtolicm-7.1-1.i686.rpm 

§        (Optional) To install the man pages, enter the following command:

# rpm -ivh lgtoman-7.1-1.i686.rpm 

The NetWorker software installation modifies the following system files during  installation. To keep a copy of the current configuration, save the following original files:

The following files are added during the installation process: 

Top of the document

Client Installation 

On the computer designated as the NetWorker client, install only the client NetWorker software package. 

To install the software: 

§        Enter the following commands to install the client, device driver, storage node, server, and License Manager software: 

# rpm -ivh lgtoclnt-7.1-1.i686.rpm  

§        (Optional) To install the man pages, enter the following command:

# rpm -ivh lgtoman-7.1-1.i686.rpm 

Top of the document

Verifying the Installation 

To start the NetWorker Administrator program, enter the following command: # nwadmin -s server_name & 

If the NetWorker Administrator program does not open, check for the following: 

§        The DISPLAY environment variable is set correctly. 

§        The PATH environment variable contains the correct path to the NetWorker programs: 

/usr/bin

/usr/sbin 

If the NetWorker Administrator program cannot connect to the specified server: 

§        Enter the ps command to check that the required NetWorker daemons are present on the NetWorker server: 

# ps -ef | grep nsr 

§        If the output does not list nsrd and nsrexecd as current processes, run the following command to start the NetWorker daemons on the NetWorker server: 

# /etc/init.d/networker start 

Top of the document 

Perform a test backup using a directory device 

To perform a test backup using a directory as device: 

§        Configure a device of type file. 

a.From NetWorker Administrator program menu, choose devices

b.Enter a name for the device, for example /backup

c.In the media type, specify ‘file’ 

§        Label the volume in the Default label pool: 

a.Select a device.

b.Select Label from the main window. The NetWorker Administrator program displays the preconfigured label templates.

c.Select the Default pool and click OK. 

§        Mount the volume in the drive by selecting Mount from the main window. 

§        Configure the NetWorker client: 

a.From the Clients menu, select Client Setup. The Clients dialog box appears.

b.For the Clients attribute, select the NetWorker server host.

c.For the Save Set attribute, specify the path of a single file that requires backing up and click Change. For example, /etc/hosts.

d.Click Apply. 

§        Test the group backup: 

a. Select Group Control from the main window. The Group Control window appears with the Default group highlighted.

b. Select Start. 

§        To view the progress of the test backup, select Details from the Group Control window. Messages appear in the panels of the main window as the backup progresses. 

§        To view the client file index entries, select Indexes from the main window. These entries were created during the test backup. Entries under Save Sets indicate what data was backed up. 

Top of the document 

Uninstalling the networker software 

To uninstall the NetWorker software packages: 

§        Log in as root on the computer where the software is being uninstalled.

§        Run a query to see which packages are installed: # rpm -qa | grep lgto

The packages are displayed in the following format, 7.1 is the release number and -1 is appended by the RPM utility:

lgtonode-7.1-1

lgtoclnt-7.1-1

lgtodrvr-7.1-1

lgtoserv-7.1-1

lgtoman-7.1-1

lgtolicm-7.1-1 

§        Enter the rpm -e package_name command to uninstall the software.

§        To uninstall all the packages, enter:

# rpm -e lgtolicm-7.1-1 lgtoserv-7.1-1 lgtonod lgtonode-7.1-1 lgtodrvr-7.1-1 lgtoclnt-7.1-1 lgtoman-7.1-1

Top of the document 

Concepts and defintions  

The following are some concepts you should know before starting to work with Legato Networker: 

Volume labeling: The NetWorker software labels (initializes) each storage volume with a unique internal label that corresponds to a pool. During backup and other operations,NetWorker software identifies the pool to which a volume belongs by its label. NetWorker software applies a label template to create a unique internal label for each volume. During recovery process, the server prompts you for the required volume by the name given to it when it was labeled. When creating a label template, the name should be consistent with the pool name; for example, you can create a label template ‘AcctFull’ for volumes that belong to a pool called ‘Accounting Full’. 

Devices: A device is a drive that reads and writes data to storage volumes or a disk file during backup, recovery, and other operations. 

Pools: A pool is a specific collection of media to which the NetWorker server writes data. The NetWorker server uses pools to sort and store data. The configuration settings for each pool act, as filters that tell the server which volumes should receive specific data. Pools are used in conjunction with label templates to keep track of which data is on which specific volume. When a scheduled backup occurs, the NetWorker server tries to match the save set to a pool configuration. If the save set matches the criteria of a pool configuration, it is directed to a labeled volume from that pool. The server then checks if a correctly labeled volume for that pool is mounted on a storage device. 

Backup groups: specifies a time of day when a backup occurs. Clients assigned to a backup group will have their specified save sets backed up during their group’s scheduled time. NetWorker backup groups allow you to designate a starting time for a client’s scheduled backup. You can:

§        Schedule the backups to take place in the middle of the night, or some other time when network traffic is low.

§        Balance the backup loads by taking the client’s backup schedule into account when you decide which clients to include in a specific group.

§        Start backup groups at different times of the day to avoid excessive strain on the network or the NetWorker server. 

Schedule: the Schedule resource provides the ability to specify the day of the week and date during the month when the backup occurs. The type and nature of the backup are also specified in this resource. For example, the Client mars runs a full backup of all its save sets every Monday and incremental backups of its save sets on the other days 

The following procedure backup an Oracle database to a specific directory (we don’t have a tape drive): 

1.First step is to create a device, for example /backup, the type of the device is ‘file’

2.Define a label template as Full_Oracle_Database

3.Define a pool as Full Oracle Database Pool

4.Label the volume using the label template and the pool defined above.

5.Define a custom schedule for Oracle database, full backup every Monday (Sched_Full_Oracle_Backup)

6.Define a custom group for Oracle database, Grp_Full_Oracle_Backup

7.Setup the client that contains the Oracle database, assign the schedule and the backup group defined above. 

To start the backup now, from the customize option in the menu, select Groups, and click on ‘start now’:

§        The networker server checks all clients assigned to the group ‘Grp_Full_Oracle_Backup’.

§        It checks their schedules to know what type of backup (full or incremental).  

The group is associated with a specific pool, the networker will direct the clients save sets to ‘Full Oracle Database Pool‘ pool, which is associated with the volume labeled as ‘Full_Oracle_Database’. 

Top of the document 

Install Legato Networker Module for oracle 4.1 on RedHat 

On Linux with Oracle 8.1.6.1, the Oracle patch bug995765 must be installed. For details on the specific operating system versions that the NetWorker Module for Oracle supports, refer to the LEGATO Software Compatibility Guide on the Legato web site. 

The software requires 6MB of disk space; the documentation requires 2 MB of disk space.

To install and enable the NetWorker Module for Oracle software on a single Oracle Server host running Linux, perform the following tasks: 

§        Download the Legato networker file nmo41_linux_x86.tar.gzfrom Legato web site

§        Log in as root on the Oracle server host.

§        Create a temporary installation directory. For example /usr/nsr_extract_nmo

§        Uncompress the downloaded software using the following command:

# gunzip nmo41_linux_x86.tar.gz

§        Extract the uncompressed, tarred file using the following command:

# tar -xvpf nmo41_linux_x86.tar

§        The oracle database doesn’t need to be shutdown during installation.

§        Ensure that the MANPATH environment variable include /usr/man

§        The software must be installed in the same base directory as the NetWorker client software.

§        Run the following command

# rpm -i lgtonmo-4.1-1.i686.rpm

§        To verify the installation succeeded, run the following command:

# rpm -aq | grep -i lgto

§        After installing the software files, you need to link the module library file with the Oracle Server for each Oracle installation that will use the module software for its backups. If installing on Oracle9i or Oracle 10g, you are not required to shut down and restart Oracle instances that use the ORACLE_HOME when linking the library file.

§        Log in as Oracle user.

§        If Oracle version is less than 9i then shutdown the database.

§        Oracle 8.1.6.1 with Oracle patch bug995765 on Linux

% cd $ORACLE_HOME/rdbms/lib

% make -f ins_rdbms.mk ioracle LLIBOBK=/usr/lib/libnwora.so

§        Oracle 8.1.7

% cd $ORACLE_HOME/lib

% rm libobk.so

% ln -s /usr/lib/libnwora.so libobk.so

§        Oracle 9.x and 10.x

% cd $ORACLE_HOME/lib

% ln -s /usr/lib/libnwora.so libobk.so

§        Restart all the instances that use ORACLE_HOME

Top of the document 

Uninstall Legato Networker Module for oracle 4.1 on RedHat 

To uninstall the software:

1.      Ensure that no Oracle database backups are running.

2.      Follow these steps for each Oracle installation that uses the NetWorker Module for Oracle software for its backups:

a.Log in as the ORACLE_HOME owner:

su ORACLE_HOME_owner 

b.      Shut down all Oracle instances that use this ORACLE_HOME.

 

3.      Oracle 8.1.6.1 with Oracle patch bug995765 on Linux

% cd $ORACLE_HOME/lib

% rm libobk.so

% ln -s libdsbtsh8.so libobk.so

% cd $ORACLE_HOME/rdbms/lib

% make -f ins_rdbms.mk   ioracle

4.      Oracle 8.1.7

% cd $ORACLE_HOME/lib

% rm libobk.so

% ln -s libdsbtsh8.so libobk.so

5.      Oracle 9.x and 10.x

% cd $ORACLE_HOME/lib

% rm  libobk.so

6.      Log in as root on the Oracle server host.

7.      Run the following command : # rpm -e lgtonmo-4.1-1 

Top of the document 

Configure scheduled Oracle backups (8i, 9i, 10g) 

Legato Networker uses RMAN to backup/restore Oracle databases; you have to set up RMAN: 

1.      Create a recovery catalog as a schema in an Oracle database:

# create user rman in recovery catalog database as catalog owner

% sqlplus ’SYS/manager@rcat AS SYSDBA’

SQL> CREATE USER rman IDENTIFIED BY rman DEFAULT TABLESPACE cattbs QUOTA UNLIMITED ON cattbs;

SQL> GRANT recovery_catalog_owner TO rman;

SQL> EXIT

# connect to database as catalog owner and create catalog

% rman CATALOG rman/rman@rcat

RMAN> CREATE CATALOG;

RMAN> connect target sys/manager@itsysdb ;

RMAN> register database;

2.      Create an appropriate RMAN script to perform the preferred type of scheduled Oracle backup on an Oracle Server host:

Itsysdb: the tns names for the target database. The parameter REMOTE_LOGIN_PASSWORDFILE should be set to true, so the user SYS can connect as sysdba

Set command id to ‘Fulldb’: Used to identify the rman connection to the target database(Client_info column in v$session)

Send ‘NSR_DATA_VOLUME’: Force Networker to use a specific pool instead of the one defined in the group.

Format string FULL_%d_%u specifies the name of each backup piece. This name can be anything, provided that each backup piece has a unique name on the NetWorker server. Substitution variables, such as %d and %u, can be used to guarantee unique names.

%d specifies the name of the database.

%u specifies an eight-character name consisting of compressed representations of the backup set number and time the backup set was created

connect target sys/manager@itsysdb;

connect CATALOG rman/rman@rcat;

run {

set command id to ‘Fulldb’;

allocate channel t1 type ‘SBT_TAPE’;

allocate channel t2 type ‘SBT_TAPE’;

send ‘NSR_ENV=(NSR_DATA_VOLUME_POOL=MondayFulls)’;

backup full filesperset 4

format ‘/FULL_%d_%u/’

(database);

# backup the current control file for 8.1.7, for 9i and 10g, you don’t have to backup the controlfile, use enable controlfile autobackup.

backup

tag curr_ctlfile

format '/CTL_%d_%u/'

current controlfile;

sql 'alter system archive log current';

# backup all archive logs

backup

filesperset 4

format '/ARCH_%d_%u/'

(archivelog all

delete input);

release channel t1;

release channel t2;}  

To test the RMAN script in Oracle8i, Oracle9i or Oracle10g run the following command:

% rman cmdfile ‘script_name’ send ’”NSR_ENV=(NSR_SERVER=NetWorker_server_name, NSR_GROUP=group_name)”’ 

3.      Customize the nsrnmo script(/usr/sbin), create a new version of the script using the following steps: 

1.Copy the script file nsrnmo to a another file (for example nsrnmoITSYSDB)

2.Customize the environment variables in the new file, only the setting of ORACLE_HOME and PATH is mandatory

3.Configure a networker backup schedule (Sched_Full_Oracle_Backup, see example in concepts and definitions. The oracle backup levels are specified in RMAN scripts.

4.Configure a networker group (Grp_Full_Oracle_backup), see example in concepts and definitions.

5.Configure the client for a scheduled Oracle backup (you have to configure a client for each different ORACLE_HOME):

- For the Save Set attribute, specify the complete pathname of each RMAN script to be used for a scheduled backup (For example, /rman_scripts/fullbck). More than one rman script can be specified.

- Specify a networker schedule backup (Sched_full_oracle_backup).

- Specify a networker group (Grp_Full_Oracle_Backup)

- For the Backup Command attribute, specify the name of a single customized nsrnmo script (nsrnmoITSYSDB)

- Save the client resource 

4.      Testing a schedule Oracle backup: To test a scheduled Oracle backup using the NetWorker Administrator program: 

1. In the Group Control window, highlight the correct Group name for the scheduled Oracle backup.

2. Click Start in the Group Control window.

 

The scheduled backup is complete when the Status of the selected group changes to Finished. If the scheduled backup fails, an error message is produced. 

Top of the document 

Restore and recover an Oracle backup (8i, 9i, 10g) 

Use the following procedure to recover an Oracle backup: 

i.          Create an appropriate RMAN script to perform the type of restore. You can restore the whole database, one tablespace or only one datafile.

The following script ‘tbsresore’ restore the tablespace ‘users’, the networker server is ‘localhost’ and the host oracle database server is ‘ITSYS’.  

run {

allocate channel t1 type ‘SBT_TAPE’;

allocate channel t2 type ‘SBT_TAPE’;

send ‘NSR_ENV=(NSR_SERVER=localhost,

NSR_CLIENT=itsys)’;

sql ‘alter tablespace users offline immediate’;

restore (tablespace users);

sql ‘alter tablespace users online’;

release channel t1;

release channel t2;} 

The following script  ‘fullrestore’ restore Whole database’, the networker server is ‘localhost’ and the host oracle database server is ‘ITSYS’.  

run {

allocate channel t1 type ‘SBT_TAPE’;

allocate channel t2 type ‘SBT_TAPE’;

send ‘NSR_ENV=(NSR_SERVER=localhost,

NSR_CLIENT=itsys)’;

sql ‘alter tablespace users online’;

Restore (database);

recover (database);

sql ‘alter database open’;

release channel t1;

release channel t2;

} 

ii.          To restore the tablespace ‘users”, run the following command: 

% rman target sys/manager@itsysdb rman/rman@rcat cmdfile ‘tbsrestore

 

iii.          To restore whole database”, run the following commands: 

sqlplus /nolog (svrmgrl pour la version 8.1.7)

SQL>connect /as sysdba

SQL>startup mount

SQL>exit

% rman target sys/manager@itsysdb rman/rman@rcat cmdfile ‘fullrestore

 

To restore an Oracle database to different system, use the following procedure: 

1. On the NetWorker server that contains the backup to be restored, specify the hostname of the different system for the Remote Access attribute in the Client resource of the original system.

2. Install and configure NetWorker Module for Oracle on the different system where the Oracle data is to be restored.

3. Install and configure RMAN on the different system.

4. Create an appropriate RMAN restore script.

5. In the RMAN script, set the NSR_SERVER environment variable to the name of the NetWorker server that contains the backup.

6. In the RMAN script, set the NSR_CLIENT environment variable to either the name of the NetWorker client (Oracle Server host) that was backed up or the value of NSR_CLIENT used during the backup.

7. Use the appropriate RMAN command to run the script to restore the Oracle database files. 

Top of the document

References
Oracle Application server 10g Administration Handbook (Oracle Press by John Garmany and Donald K.Burleson)
Oracle Database 10g Installation Guide for UNIX Systems
Oracle Database 10g Release 1 (10.1) Documentation

[i] Copyright Notice
This article may not be published, sold, reproduced or copied in whole or in part without obtaining permission from Itsys Consulting. But you are welcome to put links from your site to the article.
The information provided in this article shows how to install, configure and administer Oracle products and Legato Networker. Every effort has been made to provide the information as accurate as possible, but no warranty or fitness is implied. The use of this information described herein is your responsibility, and to use it in your own environments do so at your own risk.
Comments?