Solved!
Go to SolutionC
Castromotorbox
2 Intern
•
217 Posts
0
10830
December 20th, 2012 05:00
RMAN Backup
Hello,
We have any client configured to make RMAN BAckup. For some of those, backup doesn't work, nothing in NEtworker console and we have the following log on client:
BR0280I BRARCHIVE time stamp: 2012-12-20 14.04.02
BR0202I Saving /oracle/BAL/oraarch/BALarch1_388_800107785.dbf ...
BR0278E Command output of 'SHELL=/bin/sh /oracle/BAL/112_64/bin/rman nocatalog':
Recovery Manager: Release 11.2.0.3.0 - Production on Thu Dec 20 14:04:00 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN>
RMAN> connect target *
connected to target database: BAL (DBID=4135584923)
using target database control file instead of recovery catalog
RMAN> **end-of-file**
RMAN>
host command complete
RMAN> 2> 3> 4> 5> 6> 7> 8>
allocated channel: sbt_1
channel sbt_1: SID=355 device type=SBT_TAPE
channel sbt_1: NMDA Oracle v1.2.0
allocated channel: sbt_2
channel sbt_2: SID=27 device type=SBT_TAPE
channel sbt_2: NMDA Oracle v1.2.0
Starting backup at 20-DEC-12
channel sbt_1: starting archived log backup set
channel sbt_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=385 RECID=6 STAMP=802473216
input archived log thread=1 sequence=386 RECID=7 STAMP=802473450
channel sbt_1: starting piece 1 at 20-DEC-12
channel sbt_2: starting archived log backup set
channel sbt_2: specifying archived log(s) in backup set
input archived log thread=1 sequence=387 RECID=8 STAMP=802474710
input archived log thread=1 sequence=388 RECID=9 STAMP=802476613
channel sbt_2: starting piece 1 at 20-DEC-12
RMAN-03009: failure of backup command on sbt_1 channel at 12/20/2012 14:09:07
ORA-19506: failed to create sequential file, name="BAL_aekdjdyi.8_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
lnm_index_cfx_connect retry failed. See previous error messages. (3:3:11)
channel sbt_1 disabled, job failed on it will be run on another channel
released channel: sbt_1
released channel: sbt_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on sbt_2 channel at 12/20/2012 14:09:07
ORA-19506: failed to create sequential file, name="BAL_aekdjdyi.9_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
lnm_index_cfx_connect retry failed. See previous error messages. (3:3:11)
RMAN>
specification does not match any backup in the repository
RMAN>
Recovery Manager complete.
BR0280I BRARCHIVE time stamp: 2012-12-20 14.09.08
BR0279E Return code from 'SHELL=/bin/sh /oracle/BAL/112_64/bin/rman nocatalog': 1
BR0522E 4 of 13 files / save sets processed by RMAN
BR0536E RMAN call for database instance BAL failed
BR0200I BR_TRACE: location BrRmanCall-56, commands for RMAN in: /oracle/BAL/saparch/.aekdjdyi.cmd
@/oracle/BAL/saparch/..aekdjdyi..cmd
host '/usr/sap/BAL/SYS/exe/run/brtools -f delete /oracle/BAL/saparch/..aekdjdyi..cmd';
run { allocate channel sbt_1 device type 'SBT_TAPE'
parms 'ENV=(NSR_SERVER=bcktrusted.mscs-begia-0004,NSR_CLIENT=puppis,NSR_GROUP=SAP_Online_chu)';
allocate channel sbt_2 device type 'SBT_TAPE'
parms 'ENV=(NSR_SERVER=bcktrusted.mscs-begia-0004,NSR_CLIENT=puppis,NSR_GROUP=SAP_Online_chu)';
backup tag aekdjdyi format 'BAL_aekdjdyi.%s_%p' filesperset 2 check logical
archivelog from sequence 385 until sequence 397 thread 1;
release channel sbt_1;
release channel sbt_2; }
list backup of archivelog from sequence 385 until sequence 397 thread 1 tag aekdjdyi;
exit;
BR0280I BRARCHIVE time stamp: 2012-12-20 14.09.08
BR0543E Offline redolog backup using RMAN failed
For some other client with no significant difference, RMAN works perfectly.
Backint backup is already ok for both kind of client.
Networker version 7.6.4.1 build 1049, NMSAP 4.2 build281.
Client are RHEL5 or RHEL 6.
Thanks for your help
Greg
What is the advantage of using RMAN instead of pure BR* backup instead? Anyway, error suggests that either:
a) client specified in NSR_CLIENT is not what and how it is defined on client
b) user doing backup is not listed at admin list which is required for index management
Gregoire,
I am not sure what the difference is between the two versions of Linux you quote here and why this would produce different behavior from NMDA?
Can you ensure the servers file on the client has all names for the NetWorker server within it and see if this changes behavior?
Also try initiating the backup from the client itself (i.e. cron) rather than NetWorker group and see if this makes a difference. This will have slightly different action on NetWorker server as client file index will not be backed up due to client initiated backup. This may highlight some kind of issue in this area if client initiated backup works.
Regards,
Bill Mason
Castromotorbox
2 Intern
•
217 Posts
5654
0
Posted January 11th, 2013 00:00
Hi Hrvoje,
thanks for your answer. So a) the NSR_client it the same, b) yes it is. But we see that on client RHEL6 with ext3, RMAN works, but with REHL6 ext4, not.
The advantage with RMAN for us is to doing incremental backup, during the backup the block are checked (otherwise you have to do that separetly) and finally, during a RMAN Backup, the Database is not in Backup mode. PErformance of theDB during Backup are better.
Thanks a lot for your help.
Cheers.
JayJay9882
2 Intern
•
161 Posts
5654
0
Posted June 11th, 2013 00:00
Hi,
I have the same problem.
I recently cleaned my administrators list which results in failing RMAN jobs but only in RAC cluster environments.
When I put *@* in the remote access field of the NSR client, backup runs just fine. But *@* is surely not what I want.
If I put user=root,host=server.domain.com in the remote access field the backup fails again. If I put user=root,host=server1.domain.com (first RAC node), user=root,host=server2.domain.com (second RAC node) the same happens.
Can you tell me what exactly you wrote in the administrator list? I appreciate it.
Regards
Jan
Castromotorbox
2 Intern
•
217 Posts
5654
1
Posted June 11th, 2013 01:00
Hi Jan,
We wrote in the Admin list ora[SID]@server.domain.com. ora[SID] is in our case the user we use to do the RMAN backup.
Hope it will help
Greg
JayJay9882
2 Intern
•
161 Posts
5654
0
Posted June 11th, 2013 02:00
Hi Greg,
it works, thx.
But I am doing user=ora[SID],host=server.domain.com which is almost the same.
Cheers
Castromotorbox
2 Intern
•
217 Posts
5654
0
Posted June 10th, 2013 06:00
Hi,
Well we found the solution. It was a problem of right. We need to add the user who sen dthe RMAN command as administrator of Networker. Maybe it will work also with less right, but anyway...
Thanks for your help
Greg