Archive directory full. RMAN backup failed.

My archive directory went out of space due to rman issue. /tmp was 100%. I had no choice late last night but to move archive logs to another directory (/backups/arch) I changed log_archive_dest also to this location. However RMAN keeps looking at the previous archive directory. Any ideas how I acn make RMAN pick up the archives from this new location?
Oracle version : 10.2.0.4
HP-UX OS
Thank you.

Solved it. Had to use :
catalog start with '<new_directory_of_archivelogs>';
Edited by: 860412 on Aug 3, 2011 9:52 AM

Similar Messages

RMAN Backup Failed.

Hi Gurus,
My RMAN backup failed with below error.Please suggest.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 01/26/2013 22:48:56
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
RMAN>
Recovery Manager complete.
Thanks,

The message indicates that your database is in NOARCHIVELOG mode. You cannot make an RMAN Backup of a database that is OPEN if it is in NOARCHIVELOG mode.
You have two options
1. Make consistent RMAN Backups with the database only in MOUNT mode (SHUTDOWN ; STARTUP MOUNT)
OR
2. Configure for ArchiveLogs (create a target filesystem or FRA), set the database to ARCHIVELOG mode, monitor the volume of ArchiveLog generation, configure both Database and ArchiveLog backups.
Hemant K Chitale

FULL HOT Backup failing with a 6 on media management layer....

Hi all,
My thanks in advance for reading and any posts. Appologies for the long post, but wanted to make sure I got all information required into the post
*******************The background*************************
We are currently doing full hot backups of all production databases to tape. The database we use is RAC install (9.2.0.6.0) on Linux Redhat Enterprise 4 (database on OCFS). We use a seperate Solaris 8 box with 2 HP Ultium tape drives over a standard Cat5 line (100mb), we use Veritas Netbackup 5.1 as our media manager and we use an RMAN repositry on another box. Currently the backup is taking on average 17 hours to complete (something that I have been through with Oracle).
We use the below rman script to do the full database backup.
DATE=`date +%m%d%Y-%H%M%S`; export DATE
USER=`id | cut -f2 -d"(" | cut -f1 -d")"`
ORACLE_SID=ausl5; export ORACLE_SID
ORACLE_USER=oracle; export ORACLE_USER
ORACLE_HOME=/u01/oracle/product/9.2.0 export ORACLE_HOME
#delete log files older than 35 days
find /var/adm/netbackup -name "auslive*" -mtime +35 -type f -exec rm {} \;
#if [ "${USER}" = "root" ]
#then
# su - ${ORACLE_USER} "cd /rac/DBA/scripts/BACKUP/" #-c "${CMD_STRING}"
# SUCCESS=$?
#else
# eval "/rac/DBA/scripts/BACKUP"
# SUCCESS=$?
#fi
<<EOF su - oracle
<<EOF1 /u01/oracle/product/9.2.0/bin/rman msglog /var/adm/netbackup/AUSLIVE_b
ackup.${DATE} append
connect target sys/fowler@rman_ausl5
connect catalog rman/rman@rman
#change archivelog all validate;
run {
allocate channel ch1 type sbt_tape PARMS="BLKSIZE=1048576";
#allocate channel ch2 type sbt_tape PARMS="BLKSIZE=1048576";
#allocate channel ch3 type sbt_tape;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
CONNECT = 'SYS/fowler@rman_ausl5';
#CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
CONNECT = 'SYS/fowler@rman_ausl3';
#CONFIGURE CHANNEL 3 DEVICE TYPE 'SBT_TAPE' CONNECT = 'SYS/fowle
r@rman_ausl4';
change archivelog all validate;
###=============== Veritas Calls =========================
send "NB_ORA_CLASS=ORAhot_AUSLIVE";
#send "NB_ORA_CLIENT=sunatlsunx008";
send "NB_ORA_CLIENT=sunatlsunx008";
send "NB_ORA_SCHED=full";
###=====================main backup sections =============
backup
incremental level=0
filesperset 15
format "bk_%s_%p_%t"
tag "hot_${ORACLE_SID}_${DATE}"
database;
sql "alter system archive log current";
change archivelog all validate;
backup
filesperset 10
format "ct_%s_%p_%t"
current controlfile;
sql "alter system archive log current";
backup
filesperset 150
format "al_%s_%p_%t"
archivelog all not backed up 2 times;
change archivelog all validate;
backup
filesperset 50
format "al_%s_%p_%t"
archivelog until time 'SYSDATE-4' delete input;
change archivelog all validate;
release channel ch1;
#release channel ch2;
#release channel ch3;
exit
EOF1
EOF
Now due to the backup taking so long, we often have archive log backups that kick off. We generally get Restore Validates of this backup once a week.
*********************************Problem*******************************
Getting to the problem, the media manager generally completes the job with a 6, which in Veritas means that the backup failed to back up the requested files. I guess that this could be something to do with the media manager layer. But myself and my colleagues are of the opinion that this is something to do with the archive log backups running inbetween (hence the change archivelog all validate; appearing so many times in the script).
Has anyone got any ideas?
Thanks again for any posts / ideas,
Mark.

No I mean, it really tries to backup everything; control file, archive logs etc...
Yeah I will admit its a bit strange, didn't code it myself. The idea was to do a bit a of house keeping at the same time with the archived redo logs (hence the file system stuff with the archived redo logs).
You see we thought that this might be causing the issue.
any ideas are welcomed,
thanks again,
Mark.

RMAN backup fails using OEM with no output error

I am trying to do a weekly automatic full backup of a database in noarchivelog mode using RMAN in Enterprise Manager. Every time I submit the backup job (even if I try to do an immediate backup) the job fails almost immediately. When I Iook at the job output for the failed attempt, it says that there is no output for the job. I believe I have all of the preferred credentials and priveleges correct. Does anyone have any ideas as to what the problem could be or maybe where I can find an error log for rman to get a better explanation of the error?
Thanks

please check in metalink.....
you find useful informations here:
RMAN backup using Oracle Secure Backup fails with ORA-19511 (sbt__rpc_connect)
Doc ID: Note:396046.1
Best Regards,
Shishir Tekade.
My Blog: http://shishirtekade.blogspot.com

Regarding Full online Backup failed

Dear All,
I have faceing one issue related to SAP system backup, i have shedule sap backup by DB13(full online backup) but frequently it will failed and showing same return code 005. Bellow mentioned is log details pls. check:-
datafile copy filename=/oracle/P01/sapbackup/behgluac.spa/p01.data26 recid=40001 stamp=767722216
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 11/20/2011 16:10:16
ORA-19665: size 517120 in file header does not match actual file size of 514560
ORA-19664: file type: datafile copy, file name: /oracle/P01/sapbackup/behgluac.spa/p01.data27RMAN>
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
*BR0279E Return code from 'SHELL=/bin/sh /oracle/P01/102_64/bin/rman nocatalog': 1*
BR0536E RMAN call for database instance P01 failedBR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
BR0532E Cataloging backups of all database files failedBR0056I End of database backup: behgluac.fnt 2011-11-20 16.10.17
BR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
BR0054I BRBACKUP terminated with errors
Pls. guide me and help me to reslove this issue.
Our server OS is solaries 10 and DB is Oracle 10g.
Regards,
Sweetdiya.

Hii,
Can you tell me option to take backup again on same day if 1st bakup will failure? Bcoz we have try to take backup on same day on same tape when 1st backup had terminated due to error sytem is not take backup. e.g if today tuesday i have take(sunday S01B01,mon S01B02 likethis) tape name S01B03 our backup is failed due to error RC:- 005. we can re-execute bakup or shedule bckup in DB13 again it is agin failed.
so can any body can guide us on this issue plz..
Thanks in advance.
Regards,
Sweetdiya
Edited by: sweetdiya on Nov 22, 2011 10:11 AM

Rman backup fails

hi
we have schedule rman backup using veritas a third party mml , we have policy for daily,weely , monthly full database backup.
daily and weekly backup are working fine only monthly backup is getting failed with the following messages.
released channel: ch00
allocated channel: ch00
channel ch00: sid=172 devtype=SBT_TAPE
channel ch00: VERITAS NetBackup for Oracle - Release 6.0 (2005090703)
Starting backup at 26-JUN-08
channel ch00: starting full datafile backupset
channel ch00: specifying datafile(s) in backupset
including current controlfile in backupset
channel ch00: starting piece 1 at 26-JUN-08
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 06/26/2008 22:32:32
ORA-19506: failed to create sequential file, name="cntrl_1893_1_658449136", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSACreateObject: Failed with error:
Server Status: the specified client does not exist in an active policy within the configuration database
RMAN>
Recovery Manager complete.
Script /prod_ora/proddb/9.2.0/rman/hot_database_backup.sh
==== ended in error on Thu Jun 26 22:32:33 AST 2008 ====
Regards

This is a NetBackup configuration issue. The client doesn't have a policy for your monthly job/schedule. I would recommend comparing the setup of the daily/weekly vs. the monthly job.
Thanks,
Brian

Archive files and rman backup

Hi Experts,
For testing, I creates a testing DB. after that, I delete some archive file from physical side.
testing DB works well.
However, I tyr to back up thsi testing DB. I got below error message
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\Oraclebackup\CLS\exports\RMAN\%U
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
Starting backup at 15-JAN-09
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 01/15/2009 15:18:13
RMAN-06059: expected archived log not found, lost of archived log compromises re
coverability
ORA-19625: error identifying file D:\test\ARC00001_0675529905.001
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
So How to fix this issue?
That means we can not delete any archive log files that we do not need it.
Otherwise there are a problemwhen we try to backup later
JIm

Hi Jim,
change archivelog all crosscheck ;
will do the trick.
You can purge archive files but do it within rman.
Add a line in your rman backup script which makes backup your database and archive files like this.
delete noprompt copy of archivelog all completed before 'SYSDATE-3';
Regards,
Tycho

RMAN backup failes with ORA-19624 occurred during call to DBMS_BACKUP_RESTO

RMAN backup up failes with following errors. It works some times and then failes. When it failes then if i un install and reinstall Oralec agent and Backup cliet then it start working OK for few days and then again start getting error. See the messages below...
Recovery Manager: Release 8.1.7.0.0 - Production
RMAN-06005: connected to target database: MIMSDEVH (DBID=3525230908)
RMAN-06008: connected to recovery catalog database
RMAN> RUN { 2> execute script tapelevel0; 3> }
RMAN-03021: executing script: tapelevel0
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script tapelevel0
RMAN-03007: retryable error occurred during execution of command: allocate
RMAN-07004: unhandled exception during command execution on channel ch00
RMAN-10035: exception raised in RPC: ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-19557: device error, device type: SBT_TAPE, device name:
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
ORA-19511: SBT error = 4110, errno = 0, BACKUP_DIR environment variable is not set
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.DEVICEALLOCATE
Send me some solution...

hi,
what is your backup script
can you post back the result of the command
show all;
from the rman command prompt
regards
Alan

RMAN backup fails atlast during resync catalog with ORA-00001

Hi Everyone,
Database version:10.2.0.2.0
single instance database
My Rman backups were running fine but today i got the error , almost at the end of backup
Finished Control File and SPFILE Autobackup
released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00001: unique constraint (RMAN.CKP_P) violated
Recovery Manager complete.
This problem occured 2 days before.I connected to catalog and ran a resync catalog and the backup worked fine for next day.
Now again today iam experiencing the same problem.
Any help would be great

Thanks for the reply
SQL> select * from rman.rcver;
VERSION
10.02.00.00
10.02.00.02
when i do the resync catalog manually it works fine.only during the end of backup it throws me the error;
was wondering whether can i disable the primary key constraint on CKP table so that i can avoid the error.
since its a live system im thinking lot before i do anything
Thanks
Edited by: centerB on 14-Apr-2011 06:40
Edited by: centerB on 14-Apr-2011 06:57
Edited by: centerB on 14-Apr-2011 07:03

Rman Backups Failing

Hi All,
we have hot backups of DB scheduled(DB Full backup) thru RMAN for all prod DBs.. but since some days all the backups are failing with similar error.. the sample output of one of the backup job run is given below:
set command id to 'BACKUP_PRSAL41_FUL_091007040002';
echo set on
executing command: SET COMMAND ID
connected to recovery catalog database
connected to target database: PRSAL41 (DBID=3043389771)
input datafile fno=00002 name=/prddb02/u12/oradata/prsal41/undotbs01.dbf
input datafile fno=00007 name=/prddb02/u12/oradata/prsal41/autodba8601dat0101.dbf
input datafile fno=00008 name=/prddb02/u12/oradata/prsal41/autodba8601idx0101.dbf
input datafile fno=00004 name=/prddb02/u12/oradata/prsal41/users01.dbf
channel ORA_DISK_1: starting piece 1 at 10-SEP-07
input datafile fno=00006 name=/prddb02/u12/oradata/prsal41/IIS_INDEX_01.dbf
input datafile fno=00005 name=/prddb02/u12/oradata/prsal41/IIS_DATA_01.dbf
input datafile fno=00003 name=/prddb02/u12/oradata/prsal41/sysaux01.dbf
input datafile fno=00001 name=/prddb02/u12/oradata/prsal41/system01.dbf
channel ORA_DISK_1: specifying datafile(s) in backupset
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: sid=147 devtype=DISK
allocated channel: ORA_DISK_1
Starting backup at 10-SEP-07
backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' da
Starting Control File and SPFILE Autobackup at 10-SEP-07
Finished backup at 10-SEP-07
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:25
piece handle=/back01/prsal41/5oiricui_1_1 tag=BACKUP_PRSAL41_FUL_091007040002 comment=NONE
channel ORA_DISK_1: finished piece 1 at 10-SEP-07
Finished Control File and SPFILE Autobackup at 10-SEP-07
piece handle=/back01/prsal41/c-3043389771-20070910-00 comment=NONE
backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' ar
Starting backup at 10-SEP-07
current log archived
released channel: ORA_DISK_1
allocated channel: ORA_MAINT_DISK_1
channel ORA_MAINT_DISK_1: sid=147 devtype=DISK
delete noprompt obsolete device type disk;
allocate channel for maintenance type disk;
Additional information: 3
Linux-x86_64 Error: 2: No such file or directory
ORA-27037: unable to obtain file status
ORA-19625: error identifying file /hubudorap1/arch01/prsal41/1_132_626515083.arc
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
RMAN-03002: failure of backup command at 09/10/2007 04:02:55
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 2 days
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Archive Log 275349 18-JUL-07 /hubudorap1/arch01/prsal41/1_132_626515083.arc
Archive Log 275350 18-JUL-07 /hubudorap1/arch01/prsal41/1_133_626515083.arc
Backup Set 383337 15-AUG-07
Backup Piece 383340 15-AUG-07 /back01/prsal41/44ipdr6h_1_1
Backup Set 383353 15-AUG-07
Backup Piece 383362 15-AUG-07 /back01/prsal41/c-3043389771-20070815-00
Backup Set 500971 07-SEP-07
Backup Piece 500974 07-SEP-07 /back01/prsal41/5iirafql_1_1
Archive Log 501025 07-SEP-07 /hubudorap1/arch01/prsal41/1_404_626515083.arc
Backup Set 500987 07-SEP-07
Backup Piece 500996 07-SEP-07 /back01/prsal41/c-3043389771-20070907-00
Archive Log 505768 07-SEP-07 /hubudorap1/arch01/prsal41/1_405_626515083.arc
Archive Log 505769 07-SEP-07 /hubudorap1/arch01/prsal41/1_406_626515083.arc
Archive Log 505770 07-SEP-07 /hubudorap1/arch01/prsal41/1_407_626515083.arc
Archive Log 505771 08-SEP-07 /hubudorap1/arch01/prsal41/1_408_626515083.arc
deleted backup piece
backup piece handle=/back01/prsal41/5iirafql_1_1 recid=178 stamp=632635222
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_404_626515083.arc recid=373 stamp=632635334
archive log filename=/hubudorap1/arch01/prsal41/1_405_626515083.arc recid=374 stamp=632661717
deleted archive log
backup piece handle=/back01/prsal41/c-3043389771-20070907-00 recid=179 stamp=632635329
deleted backup piece
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_408_626515083.arc recid=377 stamp=632718235
Deleted 7 objects
RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
archive log filename=/hubudorap1/arch01/prsal41/1_407_626515083.arc recid=376 stamp=632705451
deleted archive log
archive log filename=/hubudorap1/arch01/prsal41/1_406_626515083.arc recid=375 stamp=632685605
deleted archive log
RMAN-06212: Object Type Filename/Handle
RMAN-06214: Backup Piece /back01/prsal41/c-3043389771-20070815-00
RMAN-06214: Backup Piece /back01/prsal41/44ipdr6h_1_1
RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_133_626515083.arc
RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_132_626515083.arc
RMAN-06213: --------------- ---------------------------------------------------
release channel;
exit;
released channel: ORA_MAINT_DISK_1
I am not able to detect why the archive log is missing... can anyone help me on this please..?
btw, DBs are oracle 10g R2 non-rac
Backup type : DB Full via RMAN.
Thanks

Hi,
Have you used the CROSSCHECK command?
I am not able to detect why the archive log is missing... can anyone help me on this please..?Could someone removed them through O/S commands (manually) ?
Adith

Archives missing in rman backup

Hi all,
I am able to backup few archives using rman. But its taking some archivelogs in the same directory. Can anybody tell me the reason.
After registering the archivelog using catalog command am able to take the backup of all the files.
Can anybody tell me the exact reason behind this.
many thanx in advance. . .

BALAKRIS005 wrote:
Hi all,
I am able to backup few archives using rman. But its taking some archivelogs in the same directory. Can anybody tell me the reason.
After registering the archivelog using catalog command am able to take the backup of all the files.
Can anybody tell me the exact reason behind this.Hi, there are no problems.Consider you have two archive destinations,then you want bakup archivelogs,in during backup operation rman read information from repository(controlfile or catalog) and backup each log(get only one copy).Rman see one destination and continue backup if there something fails(some logs missing or corrupted) then read other locations and will backup all archivelogs.This is normal situation.

RMAN Backup fail

Hi,
On last saturday in our production envirment L1 Backup was failed. due to these error. What could be the reason.
sql statement: ALTER SYSTEM ARCHIVE LOG CURRENT
released channel: ch1
released channel: ch2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 03/04/2011 08:05:18
RMAN-11003: failure during parse/execution of SQL statement: ALTER SYSTEM ARCHIVE LOG CURRENT
ORA-16038: log 11 sequence# 4199 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 11 thread 1: '/oracle/IPQ/origlogA/log_g11m1.dbf'
ORA-00312: online log 11 thread 1: '/oracle/IPQ/mirrlogA/log_g11m2.dbf'
RMAN>
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters are successfully stored
RMAN>
RMAN>

Hi Kalyani,
This forum category is to discuss E-Biz related issues.
Please post such question in an appropriate category to get better response.
Forum Home » Database » Recovery Manager (RMAN)
Recovery Manager (RMAN)
thanks,
X A H E E R

Last fULL Rman Backup

Hi,
on 10 gR2, any query on RMAN tables that shows the date of the last FULL backup ?
Thank you.

try this, this works in all versions of oracle.
SQL> select ctime "Date"
2       , decode(backup_type, 'L', 'Archive Log', 'D', 'Full', 'Incremental') backup_type
3       , bsize "Size MB"
4 from (select trunc(bp.completion_time) ctime
5          , backup_type
6          , round(sum(bp.bytes/1024/1024),2) bsize
7     from v$backup_set bs, v$backup_piece bp
8     where bs.set_stamp = bp.set_stamp
9     and bs.set_count = bp.set_count
10     and bp.status = 'A'
11     group by trunc(bp.completion_time), backup_type)
12 order by 1, 2;
Date      BACKUP_TYPE    Size MB
03-JUL-10 Archive Log       7.31
03-JUL-10 Full             29.81
03-JUL-10 Incremental    2853.85
04-JUL-10 Archive Log       3.59
04-JUL-10 Full              7.45
04-JUL-10 Incremental       3.05regards,
Rajesh

Bare metal restore of full server backup fails with RPC error 0x800706BA (server 2012)

With Windows Server 2012, after creating a successful windows server backup (full server), I am unable to do a bare metal restore of the system.
EFI System Partition, C:, D: are the volumes on a single array (Raid 5).
Loading WinRE and launching re-image, the full server restore stops after completing the C: restore just after beginning the D: drive restore (data volume) with the error with the message about RPC error 0x800706BA, unavailable.
The system will not boot as a result of the failure.
What may be causing this?
[edit]
I think I have two things working against me here... one, Volume Shadow Copy service wasn't running in WinPE and two.. the D: volume contains data deduplication.
I think this is causing some of my problems.
Is there an additional service that I need to start in WinPE to get a volume that was deduplicated restored perhaps using wbadmin?

Hi,
Thanks for the reply Shaon.
The hardware system is identical; however, I am increasing storage capacity from 12TB to 16TB. Basically, the system is the same, just new hard drives (4x4TB versus 4x3TB). Drives are all identical enterprise class drives and I am actually using
the same system (backup, swap drives then restore).
I tried both using the WinRE restore (re-image) with the backup set, and tried using wbadmin. Both produce same RPC unavailable messages (although using the GUI based tool via WinRE provides the additional error code #).
I do not have any idea what to look at to try to figure this one out.
[edit]
I was just informed of this posting:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/147efccc-e0e9-4458-852e-c3a44ae5cb64/the-system-image-restore-failed-error-details-he-rpc-server-is-unavailable-0x800706ba?forum=windowsbackup
and in my case, this lab server does in fact act also as a DC as well as a file server... do I need to spin up a secondary controller (perhaps in a VM on another machine) to do this restore?

Full RMAN backup in day time

Hi,
if we launche Full RMANBACKUP in day work time, is it bad for performance nad users activities ?
Usually we launche it during the night.
Thank you.
PS : DB 8i RMAN 8i on Win 2003.

Depends on your situation.
If we miss a backup during the evening (backup destination fills up whatever). We often just run the backup during the day. No one (in user land) even notices.
I'm not saying that a full backup will have no impact under any situation, but unless you are running a system pretty close to capacity in terms of CPU, disk bandwidth etc. you should be safe.
In the old days - when we were on 8i.... seem to recall that running a full backup would slow things down and users would gripe, so we had to weight keeping users happy and where we were in terms of recoverability. But I suspect that was more a function of hardware a few years back than Oracle.

Archive directory full. RMAN backup failed.

Similar Messages

Maybe you are looking for