Authentication error (0:5:111) error during Online Oracle DB backup using NMO 5.0

Hi,

If the problem only happens on larger backups, then you should implement a tcp keepalive.  For details of this, you can look at the Configuring TCP Networks and Network Firewalls for EMC NetWorker technical note page 29 which explains how to implement this for each OS.

If this doesn't fix it, increase the debug level on the backup and check the debug log for more detail around the error message.  You do this by adding NSR_DEBUG_LEVEL and NSR_DEBUG_FILE to the parms.

-Bobby

I disabled nsrauth in client and storage node. I will start backup...lets see

No Backup failed again. I am using current username:sys and password. Kindly suggest...........:)

Sabarna Deb,

Do you have any ORA-xxxx messages? Has this backup ever worked or is it new installation?

Does the backup work when running the RMAN script manually?

Regards,

Bill Mason

Previously backup was working fine from networker . No Authentication error. From oracle end, backup is completing. larger database backup is failing, not for small database like "user" tablespace with control file. At the end, backup is failing...............

Change the tcp keepalive to 10,000 in the networker startup script on the backup server and restart networker.

This should solve it.

TCP_keepalive was already set. Now issue has been resolved.

Steps: 1. Delete NSR_Peer information from another oracle physical server paired of effected server (Oracle database in RAC enviroment) because i believe somewhere else second server was interrupting the backup from first oracle client.

           2. Again configure oracle client using legacy method.

Could you please explain,, what do u mean by legacy method.

Did you re-configure it in NMC or Oracle DBA re-confiure it via RMAN script ?

makapil wrote: Could you please explain,, what do u mean by legacy method. Did you re-configure it in NMC or Oracle DBA re-confiure it via RMAN script ?

It means disable nsrauth, Check KB to details.

Longtime back i configured legacy method . Below i am pasting the procedure for taking online oracle database backup using Networker NMO. This may help you. In Legacy, backup RMAN script need to be kept in Oracle server (Vi file). Mention backup Path to RMAN script in Networker oracle client and few parameters we need to enter in Client's property. I forget. I need to recheck.

Procedure

I divided these procedures into three sections:

A.      Installation procedure for taking Oracle Online tape backup and restoration.

B.      Procedure for taking online oracle tape backup.

C.      Restoration.

Section A. Installation procedure for taking Oracle Online tape backup and restoration.

1.       Install legato client software 7.6.2 and NMO 5.0 on destination oracle client one by one as per below steps.

1. 1.rpm –ivh lgtoclnt-7.6.2.6-1.x86_64.rpm
2. 2.Start networker services - /etc/init.d/networker start
3. 3.rpm –ivh lgtonmo-5.0-1.x86_64.rpm

1. Create link for Oracle library.

% cd $ORACLE_HOME/lib

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

1. 4.Make an entry of FQDN of backup server in “servers” file inside /nsr/res/ and and make entries of respective  storage node(if there), backup server, client name with respective ip address in /etc/hosts file.
2. 5. Take small local file system test backup and troubleshoot if any error.

Section B. Procedure for taking online oracle tape backups using EMC networker 7.6.3 and NMO 5.0.

1. 1. Before taking backups, it is always recommended to make below changes in RMAN configuration parameter file of database.

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE ‘SBT_TAPE’ TO 'NMO_%F';

Note:  If we didn’t specify ‘AUTOBACKUP ON’ even though Networker will take control file backup but that would be unrecognizable by user.

1. 2. Create below script through Client configuration NMO Wizard.

RMAN_SCRIPT:

"RUN {

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

ALLOCATE CHANNEL CH2 TYPE 'SBT_TAPE';

ALLOCATE CHANNEL CH3 TYPE 'SBT_TAPE';

ALLOCATE CHANNEL CH4 TYPE 'SBT_TAPE';

ALLOCATE CHANNEL CH5 TYPE 'SBT_TAPE';

SEND 'NSR_ENV=(NSR_SERVER=backup_server_name,NSR_CLIENT= )';

BACKUP

FULL

FORMAT '%d_%U'

DATABASE

INCLUDE CURRENT CONTROLFILE

PLUS ARCHIVELOG;

RELEASE CHANNEL CH1;

RELEASE CHANNEL CH2;

RELEASE CHANNEL CH3;

RELEASE CHANNEL CH4;

RELEASE CHANNEL CH5;

}";

Adjust the number of channels based on oracle server’s CPU utilization.

NOTE (Very Important): Whenever oracle tape backup failed whether manual or scheduled backup. Do contact DBA Team immediately to check whether any background RMAN session is running or not on effected database. If yes, we need to kill bad RMAN session on database and also always make sure that keep “client retries” value 0(zero) in group’s advanced properties. Below is one of the convenient ways we can check from database level.

Command:

SQL> l

  1  SELECT s.sid,s.serial#,p.spid,s.client_info FROM v$process p, v$session s

  2   WHERE p.addr = s.paddr

  3*  AND client_info LIKE '%rman%'

SQL> /

Output (For example)

SID    SERIAL# SPID                     CLIENT_INFO

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

1038      15007 25507                    rman channel=CH6

We need to kill these bad RMAN session with the below command at database level.

SQL> alter system kill session '1038,15007';

System altered.

Section C:Restoring oracle database to same host.

1. 1. Request and check with DBA team to create empty database with the same name or different name with the necessary correct parameter file.
2. 2. Restore control file of last successful full database backup of oracle client with below script. Put database in ‘nomount’ mode prior to control file restoration.

RUN {

SET DBID

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

SEND 'NSR_ENV=(NSR_SERVER=backup_server_name,NSR_CLIENT= )';

RESTORECONTROLFILEFROM“Controlfile_name”;

RELEASE CHANNEL CH1;

}

It is also recommended for to insure successful database restoration do crosscheck of restored (above) control file with networker database not to point by control file to unnecessary datafiles. Database should be in mount mode.

RUN {

ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

SEND 'NSR_ENV=(NSR_SERVER=backup_server_name,NSR_CLIENT= )';

Crosscheck backup;

RELEASE CHANNEL CH1; }

Once cross check backup completed , execute below command in RMAN script.

RMAN>delete noprompt expired backup;

It will delete the expired images from restored control file.

Once control file restored successfully put database in ‘mount’ mode and execute below RMAN script.

RUN {

     ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';

     ALLOCATE CHANNEL CH2 TYPE 'SBT_TAPE';

     ALLOCATE CHANNEL CH3 TYPE 'SBT_TAPE';

     ALLOCATE CHANNEL CH4 TYPE 'SBT_TAPE';

     ALLOCATE CHANNEL CH5 TYPE 'SBT_TAPE';

SEND 'NSR_ENV=(NSR_SERVER=backup_server_name,NSR_CLIENT= )';

     RESTORE DATABASE;

    RECOVER DATABASE;

     RELEASE CHANNEL CH1;

     RELEASE CHANNEL CH2;

     RELEASE CHANNEL CH3;

     RELEASE CHANNEL CH4;

     RELEASE CHANNEL CH5;

}

Moniter and check the log file for successful database restoration.