Size of backup set

Hi,
can we define a value for BACKUP SET in RMAN configuration ? For me BACKUP SET is a logic notion then it has no sens to have a value. But in a NETBACKUP template I see :
Size of backup piece (KB): 15000000
Size of backup set (KB): 15000000
At least the both size can not be equal.
What do you think about ?
Many thanks.

A backup set can have 1 or more backup pieces so if it has only 1 backup piece (which is your case) then the size of backup set and backup piece will be same and if it has more than 1 backup piece then the size of backup set would be the sum of the size of all the pieces in that set.
Daljit Singh

Similar Messages

Can not restore data files from backup set

I am trying to restore Server A's backup data to Server B (they are all oracle11g) using rman. The restore commands is below:
rman target /;
shutdown immediate;
startup nomount;
restore controlfile from '/usr/local/oracle/backup/20100418/ctl_xxx'
alter database mount;
catalog start with '/usr/local/oracle/backup/20100418/';
restore database;
recover database;
alter database open resetlogs;
For the first time, it works. But when i tried to restore another backup data by the same way:
rman target /;
shutdown immediate;
startup nomount;
restore controlfile from '/usr/local/oracle/backup/20100425/ctl_xxx'
alter database mount;
catalog start with '/usr/local/oracle/backup/20100425/';
restore database;
recover database;
alter database open resetlogs;
The second time, i found that rman restore the old backup data, which means that it restore the data file under '/usr/local/oracle/backup/20100418/' instead of '/usr/local/oracle/backup/20100425/'.
So I run 'list backup of database summary' to see the backup set lists in control file.
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
910 B 0 A DISK 18-APR-10 1 1 NO TAG20100418T020007
945 B 0 A DISK 25-APR-10 1 1 NO TAG20100425T020007
But when i run ‘restore database preview summary’ to see the backup set list to restore
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
910 B 0 A DISK 18-APR-10 1 1 NO TAG20100418T020007
there's no backup set 945 at all. that's why i could not restore data file under '/usr/local/oracle/backup/20100425/' at the second time.
So, why two backup list is different ? how can i restore datafile under '/usr/local/oracle/backup/20100425/' ?
My backup script is below:
run{
allocate channel c1 type disk;
backup incremental level 0 as backupset format '$DIR/`date +%Y%m%d`/data_%d_c0_%T_%u' database;
sql 'alter system archive log current';
backup archivelog from time 'sysdate-14' format '$DIR/`date +%Y%m%d`/log_%d_%T_%u';
backup current controlfile format '$DIR/`date +%Y%m%d`/ctl_%d_%T_%I_%u';
release channel c1;
Thanks
Edited by: user13055376 on 2010-4-29 上午1:20

yeah, I am sure Tag: TAG20100425T020007 exists
RMAN> list backupset 945;
List of Backup Sets
BS Key Type LV Size Device Type Elapsed Time Completion Time
945 Incr 0 6.40G DISK 00:05:46 25-APR-10
BP Key: 945 Status: AVAILABLE Compressed: NO Tag: TAG20100425T020007
Piece Name: /usr/local/oracle/backup/20100425/data_QIANGL_c0_20100425_thlbvjt7
List of Datafiles in backup set 945
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/system01.dbf
2 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/sysaux01.dbf
3 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/undotbs01.dbf
4 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/users01.dbf
5 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/dict01.dbf
6 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/support01.dbf
7 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/supportindex01.dbf
8 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/log01.dbf
9 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/logindex01.dbf
10 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/lobindex01.dbf
11 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/data01.dbf
12 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/indexes01.dbf
13 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/image001.dbf
14 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/tongbuimage001.dbf
15 0 Incr 2498880165194 25-APR-10 /usr/local/oracle/oradata/qiangl/imagebackup001.dbf
My purpose is to use the newest backupset of Server A to update Server B. So if Server A crush, Server B will be useful. Is there any other way to do that ?
retention policy :'configure retention policy to redundancy 4'
And Server A do LV0 backup every 7 day, and do LV1 backup ervery other day.
Edited by: user13055376 on 2010-4-29 上午3:45

Database restore from a particular backup set using rman

Hi all,
My OS: UNIX
DB : 10.2.0.1
As i checked the database it will indicate datafile 5 is header corruption.
yesterday i take complete online backup of the database using RMAN but now when i run restore database command it will show as
ORA-19870: error reading backup piece /cms/BACKUP/ora_BSCS_set149_piece1_20111206_4lmth1qj_1_1
ORA-19573: cannot obtain exclusive enqueue for datafile 6
Database is open and datafile is physically present there
So can anyone tell what to do next
Edited by: Vikas Kohli on Dec 9, 2011 9:58 AM

here are the result for the same:
Starting restore at 09-DEC-11
using channel ORA_DISK_1
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
147 Incr 0 1.10G DISK 00:14:10 06-DEC-11
BP Key: 147 Status: AVAILABLE Compressed: YES Tag: TAG20111206T085858
Piece Name: /cms/BACKUP/ora_BSCS_set149_piece1_20111206_4lmth1qj_1_1
List of Datafiles in backup set 147
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/system01.dbf
2 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/undotbs01.dbf
3 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/sysaux01.dbf
4 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/users01.dbf
5 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/DATA.dbf
6 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/users02.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
149 Incr 1 11.49M DISK 00:00:07 07-DEC-11
BP Key: 149 Status: AVAILABLE Compressed: YES Tag: TAG20111207T082737
Piece Name: /cms/BACKUP/ora_BSCS_set151_piece1_20111207_4nmtjkbr_1_1
List of Datafiles in backup set 149
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/system01.dbf
2 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/undotbs01.dbf
3 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/sysaux01.dbf
4 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/users01.dbf
5 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/DATA.dbf
6 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/users02.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
151 Incr 1 115.07M DISK 00:01:24 08-DEC-11
BP Key: 151 Status: AVAILABLE Compressed: YES Tag: TAG20111208T075327
Piece Name: /cms/BACKUP/ora_BSCS_set153_piece1_20111208_4pmtm6nn_1_1
List of Datafiles in backup set 151
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/system01.dbf
2 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/undotbs01.dbf
3 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/sysaux01.dbf
4 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/users01.dbf
5 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/DATA.dbf
6 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/users02.dbf
no backup of log thread 1 seq 411 lowscn 9068988025356 found to restore
no backup of log thread 1 seq 412 lowscn 9068988167985 found to restore
no backup of log thread 1 seq 413 lowscn 9068988203392 found to restore
List of Archived Log Copies
Key Thrd Seq S Low Time Name
263 1 3 A 05-DEC-11 /u01/app/oracle/admin/BSCS/arch/BSCS/1_3_769127125.dbf
273 1 13 A 07-DEC-11 /u01/app/oracle/admin/BSCS/arch/BSCS/1_13_769127125.dbf
Media recovery start SCN is 9068988123314
Recovery must be done beyond SCN 9068988123314 to clear data files fuzziness
Finished restore at 09-DEC-11

Determine set until time from particular backup set

Hi Gurus,
First of all thank you for everybody reading my question.
I am using database control file instead of recovery catalog.
database 10gr2
10.2.0.3
os is suse linux
Is there way (any magic query)
you can determine sec part correctly for set until time looking backup set:
7544 B F A DISK 28-AUG-11 1 1 YES PROD_FULL_BKUP_08.28.2011
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux3 DEVICE TYPE DISK;
#SET UNTIL SEQUENCE 10008 thread 1;
SET UNTIL TIME "TO_DATE('28-Aug-2011 03:40:32', 'dd-mon-YYYY hh24:mi:ss')";
DUPLICATE TARGET DATABASE TO "11demo"
I try hit and try for determining sec part.
is there a proven way.
'28-Aug-2011 03:40:31' worked
'28-Aug-2011 03:40:38' didn't
'28-Aug-2011 03:40:35' didn't.
1)
I look os time stamp set for backup.
-rw-r----- 1 oracle oinstall 9281626112 2011-08-28 03:40 o1_mf_nnndf_PROD_FULL_BKUP_08_75mxdb7v_.bkp
2) I add start time(03:00:00) +elapsed time.
channel ORA_DISK_1: backup set complete, elapsed time: 00:40:35
thanks

I can get
" list backup of archivelog all"
BS Key Size Device Type Elapsed Time Completion Time
7576 1.51G DISK 00:05:04 02-SEP-11
BP Key: 7576 Status: AVAILABLE Compressed: YES Tag: ROD_ARC_09.02.2011
Piece Name: /u02/flash_recovery_area/ROD/backupset/2011_09_02/o1_mf_ annnn_ADVPROD_ARC_09.02.20_7616s3fm_.bkp
List of Archived Logs in backup set 7576
Thrd Seq Low SCN Low Time Next SCN Next Time
1 205824 3898563613 01-SEP-11 3898573074 01-SEP-11
you can get "SET UNTIL SEQUENCE thread "
correctly,
But How does one find out the exact time the backup was completed?
I simply used the timestamp from the Rman backup as an approximate indicator.
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: system01.dbf'
released channel: aux1
released channel: aux2
released channel: aux3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/01/2011 12:53:48
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 13891 lowscn 4013222506 found to restore
Edited by: 880674 on Sep 2, 2011 7:07 AM

Clone database with backup sets from another server

Hi, I want to clone a database in Host A with a backup set stored in Host B.
My script in Host A (where i want the cloned DB to be created) is as follows:
ORACLE_SID=test8; export ORACLE_SID
rman target sys/XXX@OriginalDB_in_HostB catalog prodifs/prodifs@CatalogDB_in_HostB
connect auxiliary / ;
configure channel device type disk clear;
configure default device type to disk;
configure device type disk parallelism 3;
run{
set until scn 317776086;
set newname for datafile 1 to '/o2/oradata/test8/system01.dbf';
set newname for datafile 2 to '/o2/oradata/test8/undotbs01.dbf';
duplicate target database to test8
logfile
group 1 ('/o1/oradata/test8/redo0101.rdo','/o2/oradata/test8/redo0102.rdo') size 104858112,
group 2....;
How do I specify in this script that backup files to be restored are not saved in current Host (A) but in Host B? Is it something that i should edit in the "configure channel" sentence ?
A workaround for this is to copy all backup files from HostB to the same location in HostA but I would prefer to do it in a more elegant way. Thanks and regards,
Leandro

Hi,
You have to set DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT parameters.
Duplicating a Database on a Remote Host with the Same Directory Structure
http://download-uk.oracle.com/docs/cd/B14117_01/server.101/b10734/rcmdupdb.htm#1006630
go through below link
http://dbataj.blogspot.com/2006/12/duplicating-database-with-recovery.html
hope this helps
regards
Taj

Why my Input/output size of backup increased

I have a following rman backup script
run {
backup as compressed backupset incremental level 1 cumulative device type disk tag 'Baan_bkup$LEVEL_0' data
base;
recover copy of database;
backup device type disk tag 'Baan_bkup$LEVEL_0' archivelog all not backed up;
backup archivelog until time 'sysdate-3' delete all input;
crosscheck backupset;
crosscheck archivelog all;
delete noprompt obsolete;
delete noprompt expired backup;
running once daily for almost three weeks. the first 9 days, the input/output sizes were fractional (ex 3G/88M), then it switched to ~16G/1.3G and stayed that level. Because this is test DB server, basically there is no activity on it except the mentainace activity by DB itself.　So how did it happen to cause the size change?　The real backup sets only maintain at 3 days level as the script.　My database size is 16.88G of 10g R2 on RH EL3

That is the behavior in 9i and 10g1. In 10gR2 things change.
Unused Block Compression Of Datafile Backups to Backup Sets
When backing up datafiles into backup sets, RMAN does not back up the contents of data blocks that have never been allocated. (In previous releases, this behavior was referred to as NULL compression.)
RMAN also skips other datafile blocks that do not currently contain data, if all of the following conditions apply:
The COMPATIBLE initialization parameter is set to 10.2
There are currently no guaranteed restore points defined for the database
The datafile is locally managed
The datafile is being backed up to a backup set as part of a full backup or a level 0 incremental backup
The backup set is being created on disk.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#RCMRF98765

Mac mini refuses to recognize existing TM backup set

I just got my mac mini fixed with a new logic board, and I have it connected to a 250GB external FW drive. Time machine was running on a partition on the external drive quite happily since I bought it in November, but since getting it back from the repair, it refuses to recognize that there is an existing backup set on the drive. The hard drive is identical after the repair, machine name is identical, etc.
The machine name is "Wintermute" and there is an existing directory in Backups.backupdb - when I try to run a backup run, it creates a directory "Wintermute 2" and bails out with insufficient disk space (it's trying to do a full backup)
If I right-click Time Machine in the dock and select "Browse Other Time Machine disks" I can select the existing backup and it seems to be OK. However, I can't seem to continue adding to that backup set!
Any suggestions?

Here are the contents of my backup volume if it helps at all:
bash-3.2$ ls -al
total 16
drwxrwxr-x 13 skye skye    510 Jan 18 09:32 .
drwxrwxrwt@ 5 root admin   170 Jan 18 10:50 ..
-r--------   1 skye skye     16 Nov 3 17:03 .0016cbac0d11
-r--------   1 root wheel    16 Jan 18 09:32 .0016cbac4103
-rw-rw-r--@ 1 skye skye   6148 Jan 18 09:48 .DS_Store
drwx------   3 skye skye    102 Nov 3 16:57 .Spotlight-V100
drwxrwxrwt@ 3 skye skye    102 Nov 29 20:34 .TemporaryItems
d-wx-wx-wt   3 skye skye    102 Jan 18 10:50 .Trashes
-rw-r--r--   1 skye skye      0 Nov 3 16:57 .com.apple.timemachine.supported
drwx------ 10 skye skye    340 Jan 18 10:50 .fseventsd
drwxr-xr-x+ 3 root skye    102 Jan 18 11:03 Backups.backupdb

Is there a way to only catalog backup set not in the catalog? "CATALOG START WITH" generates double entry.

The DB version is 11.1.0.7.
The "CATALOG START WITH" not only catalog backup set that are not in the RMAN catalog, but also catalog a second copy for files that are already in the catalog.
Files are not a second copy; they are the same file in the same directory.
Having two copies in the catalog, through an error when deleting explicitly the backups.
We have to add the force clause to avoid the error.
RMAN> delete FORCE backup tag 'offsite-1';
The force clause ignores any I/O error.
The delete is part of our scheduled offsite backup script, which returns a false positive error when the force clause is ommited.
I don't want the force clause, in order to be notify if the backup set that are expected to be on disk are no more there, e.g., if someone had deleted files manually at the OS level bypassing rman.
Is there a way to only catalog backup set not in the catalog?
or May be remove the copy #2 entry from the catalog?
Find bellow a test case example:
RMAN> list backup summary TAG 'OFFSITE-1';
List of Backups
===============
Key     TY LV S Device Type Completion Time    #Pieces #Copies Compressed Tag
12      B F A DISK        11-JUN-13 09:41:45 1       1       NO         OFFSITE-1
13      B F A DISK        11-JUN-13 09:43:31 1       1       NO         OFFSITE-1
14      B A A DISK        11-JUN-13 09:43:33 1       1       NO         OFFSITE-1
15      B F A DISK        11-JUN-13 09:43:34 1       1       NO         OFFSITE-1
RMAN> CATALOG START WITH 'C:\backups\offsite_disk\IBISdatabase\scheduled_offsite';
searching for all files that match the pattern C:\backups\offsite_disk\IBISdatabase\scheduled_offsite
cataloging done
List of Cataloged Files
=======================
File Name: C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\scheduled_offsite\06OBTJEP_1_1
File Name: C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\scheduled_offsite\07OBTJI3_1_1
File Name: C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\scheduled_offsite\08OBTJI5_1_1
File Name: C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\scheduled_offsite\09OBTJI6_1_1
RMAN> list backup summary TAG 'OFFSITE-1';
List of Backups
===============
Key     TY LV S Device Type Completion Time    #Pieces #Copies Compressed Tag
12      B F A DISK        11-JUN-13 09:41:45 1       2       NO         OFFSITE-1
13      B F A DISK        11-JUN-13 09:43:31 1       2       NO         OFFSITE-1
14      B A A DISK        11-JUN-13 09:43:33 1       2       NO         OFFSITE-1
15      B F A DISK        11-JUN-13 09:43:34 1       2       NO         OFFSITE-1
RMAN> DELETE BACKUP TAG 'OFFSITE-1';
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
24      18      1   1   AVAILABLE   DISK        C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\06OBTJEP_1_1   <<--- same file
30      18      1   2   AVAILABLE   DISK        C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\06OBTJEP_1_1   <<--- same file
25      19      1   1   AVAILABLE   DISK        C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\07OBTJI3_1_1
31      19      1   2   AVAILABLE   DISK        C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\07OBTJI3_1_1
26      20      1   1   AVAILABLE   DISK        C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\08OBTJI5_1_1
32      20      1   2   AVAILABLE   DISK        C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\08OBTJI5_1_1
27      21      1   1   AVAILABLE   DISK        C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\09OBTJI6_1_1
33      21      1   2   AVAILABLE   DISK        C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\09OBTJI6_1_1
deleted backup piece
backup piece handle=C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\06OBTJEP_1_1 RECID=24 STAMP=821470356
deleted backup piece
backup piece handle=C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\07OBTJI3_1_1 RECID=25 STAMP=821470356
deleted backup piece
backup piece handle=C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\08OBTJI5_1_1 RECID=26 STAMP=821470356
deleted backup piece
backup piece handle=C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\09OBTJI6_1_1 RECID=27 STAMP=821470357
Deleted 6 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: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece    C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\06OBTJEP_1_1
RMAN-06214: Backup Piece    C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\07OBTJI3_1_1
RMAN-06214: Backup Piece    C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\08OBTJI5_1_1
RMAN-06214: Backup Piece    C:\BACKUPS\OFFSITE_DISK\IBISDATABASE\SCHEDULED_OFFSITE\09OBTJI6_1_1

Hi JM,
Your demo with Oracle 10.2.0.5
At line 36 you answered "No" to "Do you really want to catalog the above files (enter YES or NO)?".
Just repeate your demo and answer Yes.
Even if he might have replied with "YES" then also, the RMAN search for the files which it can recognize as a valid rman backup file. Else it would show the list of files which are not recognized by RMAN as a valid file.
RMAN> catalog start with '/home/oracle/scripts';
using target database control file instead of recovery catalog
searching for all files that match the pattern /home/oracle/scripts
List of Files Unknown to the Database
=====================================
File Name: /home/oracle/scripts/RMAN_BACKUP.sh
File Name: /home/oracle/scripts/rman_clone.log
File Name: /home/oracle/scripts/Db_Refresh.sh
File Name: /home/oracle/scripts/rman_erp.scr
File Name: /home/oracle/scripts/RMAN_14FEB.log
File Name: /home/oracle/scripts/nid.sh
File Name: /home/oracle/scripts/Full_Clone.sh
File Name: /home/oracle/scripts/rman_staging.scr
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
no files cataloged
List of Files Which Where Not Cataloged
=======================================
File Name: /home/oracle/scripts/RMAN_BACKUP.sh
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/rman_clone.log
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/Db_Refresh.sh
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/rman_erp.scr
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/RMAN_14FEB.log
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/nid.sh
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/Full_Clone.sh
RMAN-07517: Reason: The file header is corrupted
File Name: /home/oracle/scripts/rman_staging.scr
RMAN-07517: Reason: The file header is corrupted
About the RMAN catalog, it will not catalog the same file twice. It will only catalog the files which are not known to the database.
See this demo. (/backup/RMAN/STAGING/ is the location where all the backup pieces are.)
RMAN> catalog start with '/backup/RMAN/STAGING/';
searching for all files that match the pattern /backup/RMAN/STAGING/
no files found to be unknown to the database
This was the location based test, Another demo showing piece by piece catalogging .
RMAN> list backuppiece '/backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00';
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
1323    1321    1   1   AVAILABLE   DISK        /backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00
RMAN> catalog backuppiece '/backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00';
cataloged backup piece
backup piece handle=/backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00 RECID=1324 STAMP=821717283
RMAN> list backuppiece '/backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00';
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
1324    1321    1   1   AVAILABLE   DISK        /backup/RMAN/STAGING/ERP_CNTRL_c-13949842-20130724-00
Hope its understandable, if any query please revert.
Happy to Help.
Thanks and Regards,
Prashant

Backup set /piece info

Hi,
Application guy deleted few rows.
So I am asked to do tablespace point time recovery in 11.2.0.3 on aix using old backup(two week before taken).
I would like to check how many backup set and piece name in a L0 backup.Is there any query?
Most of the V$backup_* views contains the following columns
RECID
STAMP
SET_STAMP
SET_COUNT
what is the use of it?
We taking backup in disk on production machine.We going to do TPIR on test machine.So that we moved particular backup set to tape.Os team changed TPO file settings.
While restoring control file,we got the following info.
channel t1: no autobackup in
Even we specified until time clause.
How to check what are the control file's and backup piece aviable in a tape?
Thanks.

Try:
SPOOL LOG TO rman_bkp_ts.log
RUN {
SET UNTIL TIME 'trunc(sysdate)-14';
RESTORE TABLESPACE
ORCL_DATA, ORCL_INDEX, SYSAUX, SYSTEM, UNDOTBS1, USERS
PREVIEW;
}:p

Retention Policy to delete both backup sets and archivelogs automatically

I configured the Recovery Window-Based Retention Policy for my database for the window=14 days. I also set up a crontab to do a full backup every Monday. So say in a month, there will be 30 archive logs and 4 full DB backup sets.
Now that I understand if the FRA gets filled up, older archive logs that are not needed for the 14 days recoverable window will be automatically deleted. My questions is what happen to the old backup sets? Will they get deleted automatically too if there is no space left in FRA? Or I need to use "DELETE OBSOLETE" to delete them?
Thanks.

One of the advantages of the FRA is, in case of space pressure obsolete objects (obsolete due to the defined retention policy) are deleted automatically. That's true for backups and archivelogs. The objects are NOT deleted automatically after the retention policy expires, but only when additional space is needed. That does not mean you don't have to care about FRA space consumption. You may have unusual amounts of archivelogs, additional backups and flashback logs (if flashback database is configured), which fill up the FRA.
Werner

HT201250 How do you let time machine know that a restored drive does not need a brand new backup set and just append to the old one?

I had an external drive failure and had to buy a brand new drive. I was able to restore my info onto a new drive, about 1.5 TB of data. When I go to launch time machine now with the new drive connected and my backup connected, it treats the new drive as if it had different data and wants to create a whole new backup set when it should just append. How do I get around this?
I could just reformat the backup drive and start fresh again but would rather not do that if I can avoid it, just in case there were errors in copying etc.

Hi
I should have been more clear, sorry. I work from a laptop. I have 2 external drives - one for my projects which failed but has since been replaced and restored from a backup. My 2nd external drive is the time machine backup drive.
When my project drive crashed, I bought a brand new drive and restored it using my time machine backup drive.
Now the data exists on 2 drives - the time machine backup drive, and the new drive. When I connect the backup drive now, it thinks my new drive has new data, probably since it is a new device/drive, and wants to do a brand new backup, when in fact the data already exists on that very drive. It shouldn't have to back up all 1.5 TB when nothing has changed!
Unless there is a way to tell time machine to simply append to the old backup, I think it will try and do a new backup (1.5 TB). I'm thinking maybe I should just initialize my time machine backup drive now and start over so it is only one backup set of 1.5 TB instead of (2) sets of 1.5 TB!

Restore from Time Capsule backup set

What is the procedure to recover the other paritions (multiple) which are backed up using time machine?
I am using Time capsule to maintain automated backups of my Macbook Pro. Backups to the Time capsule are performing correctly and I can see "pink" breakpoints when I enter time machine which means the backup sets are available on my time capsule. I have 3 partitions on my MBP hard drive and all these drives are included in backups to be done.
When I tried to recover my entire backup set to a new machine I was able to restore all the contents of my boot drive (mac os partition) but the data on other partitions is not recovered. I tried multiple times with different options to recover my data on other partitions but no success. What is the procedure to recover the other paritions which are backed up using time machine? Please refer the attachment to understand my partitions which are backed up but not restored?
I really need help on this matter as I need to streamline restore process in my organization using time capsule.
Thanks in advance.
Kind Regards,
Gurdev Singh

Me.. oh no.. I would never be so foolish as to depend on TM to do any such things.
Look at another Pondini reference.
http://pondini.org/OSX/SetupOther.html
As you have discovered what looks like a simple restore turns out to be nighmarish.. that is the nature of TM.

Catalog a backup set

Hi,
I have my backups on tape, backups of database and archived redo log files. Is it possible that if we could register existing backup sets on tapes to our catalog if these backups' record is missing from our control file (I have a scenario where i don't have backups entry in my control file and i am using controlfile as catalog).
Thanks

You cannot catalog backup sets if the backup sets are only on tape even with Oracle 11g:
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsynta008.htm#RCMRF109

How to extract controlfile from backup set?

Hi
If I use this "INCLUDE CURRENT CONTROLFILE" in backup command direct to tape and no catalog, How to extract controlfile from backup set from tape?
Thanks,
Taohiko
Edited by: taohiko on Sep 17, 2009 7:54 AM

yes
list backup of controlfile
will show you where controlfile backup piece reside with backup piece name
after then
restore controlfile from 'backup_piece_naem_with_its_full_path_from_above_command_result';Khurram

How can I find out if the rollback optimal parameter size has been set ?

What is the command to find out if the rollback optimal parameter size has been set? And what is the command to find out what is the rollback optimal parameter set to?

You can find the OPTIMAL size in v$rollstat.optsize

Size of backup set

Similar Messages

Maybe you are looking for