RMAN Failed Backup.

Hello Folks,
DB 10.2.0.4
OS AIX 5.3
How RMAN handles failed backup. If I have failed backups in between two successful backups, and under my retention policy window. When RMAN is going to obsolete failed backups? After my retention window ?
Thanks for your time.

+5) you issue 'delete obsolete' - again nothing is deleted,the backup from Friday is still needed (although meanwhile 8 days old) ,because the second backup from Tuesday is incomplete.+
I'm definitely not sure of this and already tested it: (oracle 10.2.0.4 - rman - AIX)
If you have a recovery windows of 3 days. If your backups are good or failed, after 3 days they'll be all deleted after these kind of commands:
crosscheck backup of database;
delete expired backup;
If the date is older then the 3 days, even if it will delete all the backup of the database from the catalog, then all will be deleted. Then your job is to not have this kind of things happening. (Rman will not say "Oh there's only one backup avalaible I'll keep it to be safe".)
The difference here is that a failed backup will immediately be marked as "obsolete" even before the 3 days and the normal backups will have the rentention policy of 3 days but not more.
Add to this that the retention is sometime shared with other party like tape manager that can automatically delete the backup on tape after 3 days to clean tapes and free space. (So if Rman was able to "think" and change the rule alone it'll not be good anyway)
If you have a recovery window in term of number of backups then it'll be quite different.
In this case all the failer backup will be immediately marked as "obsolete" and will not be counted in the database backup.
Means that if you have the number of backup to 2, it'll take 2 good backup

Similar Messages

RMAN Automatic backup/recovery with oracle fail safe, windows cluster

Hello,
I have question,
1) Whether it is possible to do "RMAN Automatic Backup and recovery" in environment as ?
Environment: -
a. Windows clustering with windows server 2003 Enterprise Edition R2 (Two Node Clustering)
b. Shared disk ( RAID )
c. Oracle 10g standard edition one
d. Oracle fail safe v3.3.3 (for redundancy)
Here we have single oracle instance operating on single database whose files are located on shared disk.
2) If answer to above question is yes please specify if there is some good documentation to it.
Any help regarding this will be greatly appreciated.
Thanks in advance,
Rahul

You just need to make sure that the RMAN scripts are always able to connect to the target database instance whether instance runs on cluster node 1 or cluster node 2
here, If oracle services(resources) will shift from Node1 to Node2 (due to media or any failure) during RMAN Backup then there will be break in connection, will it destroy my backup or will it get started automatically without any harm?
and also I want to know,
Do we need to setup another server which will have RMAN backup script running?

FRA changed but incremental RMAN disk backup failed

This is a 11.1 test database.
There was a daily FRA RMAN backup scheduled from database control. Because of the filesystem space pressure we changed FRA destination to a new filesystem and removed old FRA directories.
But this time RMAN failed because it is trying to access the old files as base. How can I force RMAN to make a new base for daily incremental backup and not loose the already scheduled backup.
Thank you.
Connected to Oracle Database 11g Enterprise Edition Release 11.1.0.6.0
Connected as ODS
SQL> SELECT output FROM v$rman_output ORDER BY recid;
OUTPUT
connected to target database: OWB11 (DBID=373788874, not open)
using target database control file instead of recovery catalog
echo set on
run {
allocate channel oem_disk_backup device type disk;
recover
allocated channel: oem_disk_backup
channel oem_disk_backup: SID=688 device type=DISK
Starting recover at 12-JUL-08 02:01:13
no copy of datafile 5 found to recover
no copy of datafile 7 found to recover
no copy of datafile 8 found to recover
channel oem_disk_backup: starting incremental datafile backup set restore
channel oem_disk_backup: specifying datafile copies to recover
recovering datafile copy file number=00003 name=/dwh0/app/oracle/product/flash_r
channel oem_disk_backup: reading from backup piece /ods01/owb11/flash_recovery_a
OUTPUT
released channel: oem_disk_backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/12/2008 02:01:14
ORA-19870: error while restoring backup piece /ods01/owb11/flash_recovery_area/O
ORA-19625: error identifying file /dwh0/app/oracle/product/flash_recovery_area/O
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
exit;
36 rows selected
SQL>

assuming you are using the Oracle provided backup procedure (you are pretty scarce on details) you need to make sure you don't have any backups (crosscheck backup and delete expired backup comes to mind), and run the procedure again. It will make a new level 0 backup and incrementals on the following days.
Please note if you don't use RMAN to clean up your O/S you will always ruin the RMAN catalog!!!
Sybrand Bakker
Senior Oracle DBA

Got error when creating a standby DB from rman: no backup or copy... Why?

We try to create standby database from a production DB on another server (10.2.0.4). The RMAN backup is in the nfs file system which is also mounted to the target server (the DR box). So, the access path for the rman backup is the same look from primary DB server and DR DB server. I started the RMAN run:
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
5> DUPLICATE TARGET DATABASE for standby
6> nofilenamecheck
7> dorecover;
8> }
9>
10> exit
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=582 devtype=DISK
allocated channel: aux2
channel aux2: sid=584 devtype=DISK
Starting Duplicate Db at 21-JUN-12
contents of Memory Script:
set until scn 12198261770353;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 21-JUN-12
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/21/2012 16:33:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
===========================================================================
The backups should have controlfile. There is rman show all display:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/inbound/online/controlfile_auto%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/inbound/online/%d_%T_%t_%s';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/inbound/online/snapcf_inbound.f';
Why and how to fix? Thanks for help!

Here is the list of command:
RMAN> list backup of controlfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
5518 Full 4.57M DISK 00:00:07 17-JUN-12
BP Key: 5518 Status: AVAILABLE Compressed: NO Tag: TAG20120617T035926
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120617-00
Control File Included: Ckp SCN: 12197994840698 Ckp time: 17-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5522 Full 4.57M DISK 00:00:00 18-JUN-12
BP Key: 5522 Status: AVAILABLE Compressed: NO Tag: TAG20120618T010158
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120618-00
Control File Included: Ckp SCN: 12198041382572 Ckp time: 18-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5526 Full 4.57M DISK 00:00:01 19-JUN-12
BP Key: 5526 Status: AVAILABLE Compressed: NO Tag: TAG20120619T010352
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120619-00
Control File Included: Ckp SCN: 12198090424606 Ckp time: 19-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5530 Full 4.57M DISK 00:00:02 20-JUN-12
BP Key: 5530 Status: AVAILABLE Compressed: NO Tag: TAG20120620T010304
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120620-00
Control File Included: Ckp SCN: 12198146424201 Ckp time: 20-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5534 Full 4.57M DISK 00:00:02 21-JUN-12
BP Key: 5534 Status: AVAILABLE Compressed: NO Tag: TAG20120621T010357
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
Control File Included: Ckp SCN: 12198210334547 Ckp time: 21-JUN-12
==================================================================
I tried to catalog the controlfile:
RMAN> catalog controlfilecopy '/backup/inbound/online/controlfile_autoc-2080040856-20120621-00';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 06/21/2012 17:24:32
ORA-19563: control file header validation failed for file /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
====================================================================
We have level 1 backup everyday, except Sunday. I have level 0 backup on Sunday. I alos tried the metalink note RMAN Duplicate For Standby Fails with Rman-06024: No Backup Or Copy Of The Control File Found To Restore [ID 466321.1]. It does not work.
Thanks for help!

Clonning using RMAN Cold Backup?

Hi,
I have a COLD RMAN backup in prod server and now i want to clone test db using this backup through RMAN. I have 2 question regarding this
1) Where do i need to place the prod RMAN COLD backup files in test server?
2) If i ran below command how RMAN will know where did i placed the backup in test server?
In Test Server
RMAN> duplicate target database to test;DB Version is : 10.2.0.4
Thanks in advance

thanks. Now it is unable to restore the datafiles from rman backup.Below steps i tried.
[oracle@Test test1]$ rman target /
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Feb 21 08:58:46 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/initprod2.ora';
Oracle instance started
Total System Global Area     603979776 bytes
Fixed Size                     1268896 bytes
Variable Size                163578720 bytes
Database Buffers             436207616 bytes
Redo Buffers                   2924544 bytes
RMAN> restore controlfile from '/u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak';
Starting restore at 21-FEB-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control01.ctl
output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control02.ctl
output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control03.ctl
Finished restore at 21-FEB-12
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> catalog start with '/u01/app/oracle/product/10.2.0/backup/test1';
Starting implicit crosscheck backup at 21-FEB-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 3 objects
Finished implicit crosscheck backup at 21-FEB-12
Starting implicit crosscheck copy at 21-FEB-12
using channel ORA_DISK_1
Finished implicit crosscheck copy at 21-FEB-12
searching for all files in the recovery area
cataloging files...
no files cataloged
searching for all files that match the pattern /u01/app/oracle/product/10.2.0/backup/test1
List of Files Unknown to the Database
=====================================
File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak
RMAN>
RMAN> restore database;
Starting restore at 21-FEB-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/app/oracle/oradata/prod2/system.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/prod2/usr04.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/prod2/undo.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/prod2/sysaux.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/prod2/p1_01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/prod2/p2_01.dbf
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
ORA-19870: error reading backup piece /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
ORA-19504: failed to create file "/u01/app/oracle/oradata/prod2/system.dbf"
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
failover to previous backup
creating datafile fno=1 name=/u01/app/oracle/oradata/prod2/system.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/21/2012 09:01:09
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '/u01/app/oracle/oradata/prod2/system.dbf'

User hot and Rman hot backup

During user mode hot backup lots of redo gets generated as the entire block is written when any changes are made to a block which is in hot backup mode.But during Rman hot backup less redo are generated why is this so and whatz the logic invloved? and how oracle recovers the file that has been backed up through Rman.
Could you please explain me regarding this in detail it will be really helpful.
kumaresh

From Article Note:76736.1 RMAN FAQ: Recovery Manager -- Frequently Asked
To understand why RMAN does not require extra logging or backup mode,
you must first understand why those features are required for non-RMAN
online backups.
A non-RMAN online backup consists of a non-Oracle tool, such as cp or
dd, backing up a datafile at the same time that DBWR is updating the
file. We can't prevent the tool from reading a particular block at the
exact same time that DBWR is updating that block. When that happens,
the non-Oracle tool might read a block in a half-updated state, so that
the block which is copied to the backup media might only have been
updated in its first half, while the second half contains older data.
This is called a "fractured block". If this backup needs to be restored
later, and that block needs to be recovered, recovery will fail because
that block is not usable.
The 'alter tablespace begin backup' command is our solution for the
fractured block problem. When a tablespace is in backup mode, and a
change is made to a data block, instead of logging just the changed
bytes to the redo log, we also log a copy of the entire block image
before the change, so that we can reconstruct this block if media
recovery finds that this block was fractured. That block image logging
is what causes extra redo to be generated while files are in backup
mode.
The reason that RMAN does not require extra logging is that it
guarantees that it will never back up a fractured block. We can make
that guarantee because we know the format of Oracle data blocks, and we
verify that each block that we read is complete before we copy it to the
backup. If we read a fractured block, we read the block again to obtain
a complete block before backing it up. non-Oracle tools are not able to
do the same thing because they do not know how to verify the contents of
an Oracle data block.
Backup mode has another effect, which is to 'freeze' the checkpoint in
the header of the file until the file is removed from backup mode.
We do this because we cannot guarantee that the third-party backup
tool will copy the file header prior to copying the data blocks.
RMAN does not need to freeze the file header checkpoint because we
know the order in which we will read the blocks, which enables us to
capture a known good checkpoint for the file.

Using rman to backup a remote database

I am after a good guide or advice on how (what) to install and (how to) run Oracle RMAN
to backup a remote Oracle database.
RMAN must be installed and run on a Solaris (SunOS 5.8) box remote from the Solaris
box (also SunOS 5.8) running the Oracle database but connected to it via a TCP/IP
network.
The Oracle Recovery Manager and Database version is 9.2.0.1.0.
RMAN must perform the backup of the remote database over the network and store
the backup on a disk local to the RMAN box.
The backups may be full or incremental and may be "hot" backups taken while the
Oracle database is open.
The disk files are to be then backed up to tape using Veritas.
What software do I need to install on the RMAN box ?
What software do I need to install on the remote Oracle database box ?
Thanks,
Brett Morgan.

writes to a NFS-mounted diskRman is writing to disk or tape (when is bundled (libraries needed) with some backup software for tapes such as Veritas). The disk device could be local, or mounted disk form other host or storage (over NFS as Werner mentioned, SMB and others).

Rman incremental backup

Hi,
we are using oracle10g(10.2.0.3).
is it possible to apply rman incremental backup on top of manual full backup?
Note:There is no level 0 backup available
Thanks
With Regards
Umair

Yes, you can.
Register your manual backup in recovery catalog as level 0 backup. Then take a fresh incremental backup. I have demonstrated the same in my article. You may download the same from here .
Go through the section "Rolling forward a backup".
Regards,
S.K.

Quesion about the Basic concept of RMAN incremental backup

I have a problem in understanding the basic concept of two types RMAN Incremental backup ie. Differential and Cumulative. I just don't understand how cumulative incremental backup consumes more space than Differential backup.
Have a look at the scenario in which Differential backup is used.
1. On Sunday midnight, a LEVEL0 backup is taken.
2. On Monday midnight all the blocks that was changed since Sunday midnight are stored in the backup media (tape or disk)
3. On Tuesday midnight all the blocks that was changed since monday midnight are stored in the backup media.
4. On Wednesday midnight, all the blocks that was changed since tuesday midnight are stored in the backup media.
At this point, in the backup media, you have all the changed blocks from sunday midnight to wednesday midnight eventhough it was stored in a daily basis. If you had taken a cumulative backup at wednesday midnight the backup media would have contained the same changed blocks from sunday midnight(LEVEL0) to wednesday midnight, but all at one go instead of daily basis. I don't understand how cumulative backup consumes more space when the backup media contains the same amount of changed blocks as it were in the case of the Differential backup.

Considering the Scenario you given:
Sunday : Level 0 backup.
Monday : You have taken an incremental backup then there will not be any difference in size of backup set for differential or cumulative as the changes from last Level0 backup are considered.
Tuesday : A cumulative backup (n-1) will have changed blocks since Sunday's Level0 backup but a differential backup(n) will only have changed blocks since Monday. So definitely there will be more space consumed by cumulative backups compared to differentials.
Hope it helps ...
Bhupinder

Failed backup/invisible backup file

I tried to do a Time Machine backup of my iMac G5 to my Powerbook G4 using Firewire Target Disk mode. The backup failed and now my Powerbook HD is practically full but I can't erase the failed backup file or write over it either... I can't find the file on the disk to delete it.... any suggestions? Thanks!
Cliff

Clifton Goodwin wrote:
no that folder is really not there... please tell me I don't need to erase my HD!
this really shouldn't be necessary but I don't know where the backups might be hiding. it ought to be somewhere at the top level of the drive.
can you boot from PB? if yes, boot from it and use the instructions on [this page|http://www.pinkmutant.com/articles/TigerMisc.html] to search out what's taking all the space.

RMAN & Hot backup cloning taking long time

Dear DBAs,
We are doing both RMAN & Hot backup cloning foe that taking more time to restore data files to TEST instance. scp taking too much time to copy to target server because of its volume of data (1.5 TB) & Mounting the RMAN backups drive on test server and restoring from that drive taking more than 8 hours.
I heard that some companies are using some device to move heavy volume Hot backup copy from source to dest faster for clone the instance easily with in minutes. What is that device name to take hot backup copies from source and restore it in target server.
Test server Specs
Processor 8 cores with 32GB Memory.
Thanks
DBA

Hot backup is not recommanded for the database size more than 1T.
RMAN backup and restore is the only opiton available for a DBA.
Other option is to use EMC Symmentrix/BCV's/Snapshots. EMC uses pair of disks to achive synch the produciton data with test server. read more about EMC symmentrix or ask your storage team.

11g RMAN UNDO backup optimization

Hi all?
I have tested 11g RMAN UNDO backup optimization
1st I fill the undo tablespace by sql manipulations and not commiting
2nd backed undo_ts up by RMAN (size 24m)
3rd I made a commit
Then backed undo tablespace again but backup_size didn’t change (24m)
Then I made some more manipulations and backed undo_ts again. This time backup_size reduced. (11m)
Then I restarted db and backed up undo_ts again. This time backup size became what I expected (600K)
The question is why 11g rman undo tablespace backup size didn’t reduce after commit?
according to 11g undo optimization it had to
SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
SUM(BYTES)
13172736
SQL> begin
for i in 1..100000 loop
insert into testundo values(i);
end loop;
end;
2 3 4 5 6
PL/SQL procedure successfully completed.
SQL> SQL> update testundo set
id=2 where id>0;
2
update testundo set
ERROR at line 1:
ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
SUM(BYTES)RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
10 Full *24.54M* DISK 00:00:04 10-JUN-10
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142437
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
List of Datafiles in backup set 10
File LV Type Ckp SCN Ckp Time Name
6 Full 577669 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
SQL> commit;
Commit complete.RMAN> backup datafile 6 format 'after commit.backup';
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
11 Full *24.54M* DISK 00:00:02 10-JUN-10
BP Key: 11 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142541
Piece Name: /home/oracle/product/11/Db_1/dbs/after commit.backup
List of Datafiles in backup set 11
File LV Type Ckp SCN Ckp Time Name
6 Full 577705 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
SQL> alter system archive log current;
System altered.
SQL> commit;
Commit complete.
SQL> select count(*) from testundo;
COUNT(*)
100000
SQL> delete from testundo;
100000 rows deleted.
SQL> commit;
Commit complete.
SQL> insert into testundo values(1);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system flush buffer_cache;
System altered.RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
13 Full *11.03M* DISK 00:00:01 10-JUN-10
BP Key: 13 Status: AVAILABLE Compressed: NO Tag: TAG20100610T143359
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
List of Datafiles in backup set 13
File LV Type Ckp SCN Ckp Time Name
6 Full 578410 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
RMAN>
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 393375744 bytes
Fixed Size 1300156 bytes
Variable Size 352323908 bytes
Database Buffers 33554432 bytes
Redo Buffers 6197248 bytes
Database mounted.
Database opened.
SQL> RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
14 Full *600.00K* DISK 00:00:02 10-JUN-10
BP Key: 14 Status: AVAILABLE Compressed: NO Tag: TAG20100610T152843
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
List of Datafiles in backup set 14
File LV Type Ckp SCN Ckp Time Name
6 Full 580347 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
Thanks in advance
Turkel

Hi Turkel,
The space used for undo is also related to the undo retention setting.
As it seems you do a test update and proceed with backups on:
- 14:24:37 (-> 25M)
- 14:25:41 (-> 25M)
- 14:33:59 (-> 11M)
- 15:28:43 (-> 600K)
The first two backups probably are still within the undo retention period for the update.
The third backup shows a partly empty undo (is your setting 900?).
The last falls outside the retention period for the update resulting in the small backup size.
Regards,
Tycho

Creating Standby From RMAN Compressed backup taken on Primary ....

I am creating a Standby from RMAN Compressed backup taken on Primary.
On Primary, I have taken Compressed backup as follows:
RMAN> run
allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG format '/dboracle/orbit_pr_bkp/primary_%U';
backup current controlfile for standby format '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
oracle@apl06635orbvu1:/dboracle/orbit_pr_bkp>ls -ltr
total 51652
-rw-r----- 1 oracle dba 11972608 Jan 7 13:45 primary_0tm1h32n_1_1
-rw-r----- 1 oracle dba 15762432 Jan 7 13:45 primary_0sm1h32n_1_1
-rw-r----- 1 oracle dba 16785920 Jan 7 13:45 primary_0rm1h32n_1_1
-rw-r----- 1 oracle dba 1088000 Jan 7 13:45 primary_0um1h32v_1_1
-rw-r----- 1 oracle dba 32768 Jan 7 13:45 primary_12m1h33r_1_1
-rw-r----- 1 oracle dba 7143424 Jan 7 13:47 primary_cntl.bkp
On Standby, I restored the control file as below:
RMAN> restore standby controlfile from '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
Starting restore at 10-JAN-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output filename=/dboracle/orbit_dr/oradata/ORBIT_DR/controlfile/o1_mf_6lo6nwfr_.ctl
output filename=/dboracle/orbit_dr/flash_recovery_area/ORBIT_DR/controlfile/o1_mf_6lo6nwky_.ctl
Finished restore at 10-JAN-11
But, When I am trying to restore the datafiles, RMAN is throwing error:
RMAN> run {
allocate channel d1 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
allocate channel d2 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
restore database;
2> 3> 4> 5>
released channel: ORA_DISK_1
allocated channel: d1
channel d1: sid=155 devtype=DISK
allocated channel: d2
channel d2: sid=151 devtype=DISK
Starting restore at 10-JAN-11
released channel: d1
released channel: d2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 01/10/2011 05:38:56
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
What would be the correct RMAN command?
Regards, Anirban

After your RESTORE the (standby) controlfile, you must MOUNT the database instance with "ALTER DATABASE MOUNT".
You can also then query the controlfile with a "LIST BACKUP" or "LIST BACKUP SUMMARY" in RMAN to see if the deseired backups have been cataloged in the controlfile.
Don't specify the format for the ALLOCATE CHANNEL when you RESTORE DATABASE. In fact, you don't need to ALLOCATE CHANNEL at all when the device type is the default value of DISK if your are on 10gR2 or above.
Hemant K Chitale

Rman hot backup

hello
i am using rman hot backup script to take backup database everyday but the problem is it is working but not deleting old backup older than 2 days .
also i have question .. my database is in archive log mode and everyday about 6-7 .arch files generating in my archive directory.
it is not deleting the old files but generating new files everyday so adding up to the space.
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string /u03/archive_logs/DEVL
log_archive_dest_1 string
also should i set dest_1 as archive location or just log_archive_dest
whats is the difference.?
my rman script is
RMAN Hot backup.unix script
The RMAN hot backup script rman_backup.sh:
# !/bin/bash
# Declare your environment variables
export ORACLE_SID=DEVL
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export PATH=$PATH:${ORACLE_HOME}/bin
# Start the rman commands
rman target=/ << EOF
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/backup/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/u03/backup/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/u03/backup/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/u03/backup/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
thanks

Ahmer Mansoor wrote:
RMAN never deletes the Backups unless there is a space pressure in the Recovery Area. Instead it marks the Backups as OBSOLETE based on Retention Policy (in your case it is 2 Days),
To confirm it SET DB_RECOVERY_FILE_DEST_SIZE to some smaller value, the RMAN will remove all the Obsolete Backups automatically to reclaim space.Be very careful with this. If you generate a LOT of archivelog files and you exceed this size, on the next archivelog switch your database will hang with "cannot continue until archiver freed". RMAN will not automatically remove anything. RMAN only removes stuff when you program it in your script.
See:
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmconfb.htm#insertedID4 Retention Policy (recovery window or redundancy)
things like:
set retention window and number of copies
crosscheck backup
delete obsolete <-- delete old, redundant, no longer necessary backups/archivelogs
delete expired <-- NOTE: If you manually delete files and do not execute delete expired (missing file), the DB_RECOVERY_FILE_DEST_SIZE remains the same. So, you can clean out the space and oracle will still say the location is "full".
Understand that if you also set this parameter too small and your backup recovery window/redundancy are incorrectly set, you can also exhaust the "logical" space of this location again, putting your database at risk. Your parameter could be set to 100G on a 400G file system and even though you have 300G available, Oracle will see the limit of this parameter.
My suggestion, get in a DEV/TEST environment and test to see how to best configure your environment for RMAN database backups/control file, archivelog backups also taking into consideration OS tape backup solutions. I always configure DISK for RMAN backups, then have some other tape backup utility sweep those locations to tape ensuring that I have sufficient backups to reconstitute my database - I also include a copy of the init.ora file, password file as well as the spfile backup in this location.
>
In case of Archivelogs, It is better to create and execute a Purge Job to remove Archivelogs after backup them on tape.I almost agree. I try to keep all archivelogs necessary for recovery from last full backup online. I try to keep a full backup online as well. much faster at restoring stuff instead of trying to locate it on tape.

Cloning DB on a different server from RMAN Tape backup

RDBMS version           : 11.2.0.2 on Solaris 10
Media Management Layer : Netbackup v7
I have done only backups to Tape. I have never done restore,recovery from Tape.
We have a production DB named NEHPROD running on server qualmh214. Every Monday morning an RMAN Full backup for NEHPROD is taken to Tape.
Production server : qualmh214        DB Name:NEHPROD
run
ALLOCATE CHANNEL c1 TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=qualmh214,NB_ORA_POLICY=qualmh214_rman,NB_ORA_SERV=qualmh238,NB_ORA_SCHED=Daily';
backup database   FORMAT 'NEHPROD_%d_%U_%t.rbk' tag='NEHPROD_full';
}I need to create a Test DB in a different server (qualmh199) by restoring directly from NEHPROD's Full backup in tape .
From qualmh199, how can I connect to the Tape Media server ?
Even If I do connect to the Tape media server, how can i get access to tape backups of another DB? In the RMAN run block you can't specify a DB name. Right?
Even if I get access to another DB's backup , How can i specify which Date's Full backup I need to use to restore ?

From qualmh199, how can I connect to the Tape Media server ?You have to allocate channels to tape & need to mention NB parameters as example below.
in RMAN script
ALLOCATE CHANNEL CH1 DEVICE TYPE SBT_TAPE PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64';
SEND 'NB_ORA_SERV=<server.com>, NB_ORA_CLIENT=<target.server>';
Even If I do connect to the Tape media server, how can i get access to tape backups of another DB? In the RMAN run block you can't specify a DB name. Right?If the libraries are installed and you able to perform, you can go for either duplicate database or simple RMAN restore. You can mention other DB names also
Ex: duplicate target database to 'test';
Even if I get access to another DB's backup , How can i specify which Date's Full backup I need to use to restore ?You can mention TAG's if you are using RMAN restore.

RMAN Failed Backup.

Similar Messages

Maybe you are looking for