Incremental Backup TAG missing?

run {
RECOVER COPY OF DATABASE WITH TAG 'PROD_INC_UPD'
UNTIL TIME 'SYSDATE-7';
BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'PROD_INC_UPD'
DATABASE;
First time I run it, I see the following, the tag is there.
channel ORA_DISK_1: starting datafile copy
input datafile fno=00002 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\PROD\UNDOTBS01.DBF
channel ORA_DISK_2: starting datafile copy
input datafile fno=00004 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\PROD\USERS01.DBF
output filename=E:\FLASH_RECOVERY_AREA\PROD\DATAFILE\O1_MF_UNDOTBS1_4W8NRGOT_.DBF tag=PROD_INC_UPD recid=243 stamp=682036713
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
Now, after a day I run it again, it is using the random tag.
channel ORA_DISK_1: finished piece 1 at 21-MAR-09
piece handle=E:\FLASH_RECOVERY_AREA\PROD\BACKUPSET\2009_03_21\O1_MF_NNND1_TAG20090321T060510_4W9GYQ3V_.BKP tag=TAG20090321T060510 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
What did I do wrong?

Hi,
Can we use the compress option with image copy at the beginning( first time incremental run)?
Currentlly i am using the same scripts ( the first time is running is on sun and then every day).==> not sure that i am use the right strategy.
aslo i am confused the previous scripts with the following scripts:
on other database i have, i used the following scripts:
this script run only on Sun:
run{
sql'alter database recover managed standby database cancel'; ==> to stop the recovery, so i dont have to shutdown and mount standby database, then i can take Consistent backup ( right or wrong)
delete obsolete; ==> will only run in the weekend to delete the last backup level 0
allocate channel c1 type disk;
allocate channel c2 type disk;
backup format '/data/backup/RMAN_BACKUP/DBCONTROLFILE_%U'(current controlfile);
backup incremental level 0 tag "WEAKLY FULL BACKUP" filesperset 5 format '/data/backup/RMAN_BACKUP/DB_%U'(database);
release channel c1;
release channel c2;
then every day i am running this:
run{
sql'alter database recover managed standby database cancel';
allocate channel c1 type disk;
allocate channel c2 type disk;
backup format '/data/backup/RMAN_BACKUP/DBCONTROLFILE_%U'(current controlfile);
backup incremental level 1 tag "Daily incremental BACKUP" filesperset 5 format '/data/backup/RMAN_BACKUP/DB_%U'(database);
release channel c1;
release channel c2;
my biggest confuse between 2 strategy:
the "Recover copy of Database" is usefull for recovery purpore so i dont have to apply more than 1 worth day of archives in case i want to restore.
but the others strategy that i provided above, i dot know how i am suppose to use when i need to resore my database lets say in wed i get crash,
so if i lunched restore database, it will use the backup Level 0 From sun, but not the incremental backup or this is what i am thinking(maybe wrong).
the reason i am saying that is because when i lunched list backup, the only backup i have is from Sun and i dont have any backup from incremental.
i preferd to use the scripts above for simple reason is the compress options i have.
Finally My DB is 10.1.0.4 on Linux with 8 CPU
please clear my confusion and show me the light here.

Similar Messages

  • RMAN backup  tag question

    I am little confused even after I read the RMAN doc. If I have a full level 0 backup tag "mybk$level_0" database, then my level 1 incremental backup tag has to be the same - "mybk$level_1" or "mybk$level_0".
    I just run the incremental backup through the whole weekend and noticed the each run would generated two identical "spfile, controlefile" backup, one before the archivelog backup, one after it. Why?

    The tag name can be the same as what you set. Tag names can be of different names and different formats, does not need to be a specific name. You can replace mybk with myarchive if you think that is more meaningful. You can also attach date and time variable with the tags to make them more meaning full.
    It doesn't have to be this way,
    { backup incremental level 1 cumulative device type disk tag 'mybk%LEVEL_1' database;
    recover copy of database;
    backup device type disk tag 'mrarchive' archivelog all not backed up; }
    If you are calling the rman backup from shell script you can attach the dates to tags as below.
    export TDATE=`date +%a%m%d%y`
    tag="Archive_${TDATE}"
    or
    tag "Archive_${TDATE}"
    Below note if from one of the online resources available:
    Tags for Backups and Image CopiesYou can assign a user-specified character string called a tag to backup sets and image copies (either copies created by RMAN or copies created by an operating system utility). A tag is a case-insensitive symbolic name for a backup set or file copy such as weekly_backup. You can specify the tag rather than the filename when executing the RESTORE or CHANGE command. The maximum length of a tag is 30 characters.
    If you do not specify a tag name, then by default RMAN creates a tag for backups and copies (except for control file autobackups) in the format TAGYYYYMMDDTHHMMSS, where YYYY is the year, MM is the month, DD is the day, HH is the hour (in 24-hour format), MM is the minutes, and SS is the seconds. For example, a backup of datafile 1 may receive the tag TAG20020208T133437. The date and time refer to when RMAN started the backup. If multiple backup sets are created by one BACKUP command, then each backup piece is assigned the same default tag.
    When applied to a backup set, a tag applies to a specific copy of the backup set. If you do not duplex a backup set, that is, make multiple identical copies of it, then a one-to-one correspondence exists between the tag and the backup set. For example, BACKUP COPIES 1 DATAFILE 7 TAG foo creates one backup set with tag foo. However, you can back up this backup set and give this new copy of the backup set the tag bar. So, the backup set has two identical copies: one tagged foo and the other tagged bar.
    Tags do not need to be unique, so multiple backup sets or image copies can have the same tag name, for example, weekly_backup. When a tag is not unique, then with respect to a given datafile, the tag refers to the most current suitable file. By default, RMAN selects the most recent backups to restore unless qualified by a tag or a SET UNTIL command. The most current suitable backup containing the specified file may not be the most recent backup, as can occur in point-in-time recovery.
    For example, if datafile copies are created each Monday evening and are always tagged mondaypmcopy, then the tag refers to the most recent copy (assuming that no SET UNTIL command is issued before restore or recovery). Thus, if complete recovery is desired, this command switches datafile 3 to the most recent Monday evening copy:
    SWITCH DATAFILE 3 TO DATAFILECOPY TAG mondaypmcopy;
    Tags can indicate the intended purpose or usage of different classes of backups or file copies. For example, datafile copies that are suitable for use in a SWITCH can be tagged differently from file copies that should be used only for RESTORE.
    Note:
    If you specify a tag when specifying input files to a RESTORE or SWITCH command, then RMAN considers only backup sets with a matching tag when choosing which backup to use

  • Is incremental backup possible for archivelog.

    Hi expert
    i want to plan weekly and daily backup with windows redundancy 14 days.
    full archivelog backup script
    run
    BACKUP AS COMPRESSED BACKUPSET
    INCREMENTAL LEVEL = 0
    DEVICE TYPE DISK
    TAG = 'WEEKLY_ARCHIVELOG'
    FORMAT '/oracle/ITB/db/apps_st/rman_backup/weekly_archivelog_%d_t%t_s%s_p%p'
    ARCHIVELOG FROM TIME 'SYSDATE-7';
    daily backup script
    run
    BACKUP AS COMPRESSED BACKUPSET
    INCREMENTAL LEVEL = 1
    DEVICE TYPE DISK
    TAG = 'DAILY_INCREMENTAL_ARCHIVELOG'
    FORMAT '/oracle/ITB/db/apps_st/rman_backup/daily_incremental_archivelog_%d_t%t_s%s_p%p'
    ARCHIVELOG FROM TIME 'SYSDATE-1';
    my question that if i will take backup then, will be any gap in sequnce
    and second question is that ---is there incremental backup possible for archivelog.
    os =aix6 and database 10g2

    afzal wrote:
    Dear Sir,
    ok question number 2 is clear that incremental backup is not possible but still confuse
    about sequence
    if i did take backup of 17 feb at 12 o'clock seq 1,2,3,4
    after that i did take backup 18th fab 1 pm then it will take from 6,7,8-------seq 5 is missing
    please please correct my archive log script for weekly and daily backup with windows redundancy 14 days
    again please correct my script
    thnaksWHy you think the archive log file number 5 will be missing? RMAN automatically archives current redo log files and backups it
    Why you don't test your backup script by your own and check results? Never trust anyone on your critical databases' backups, do it by your own!
    Kamran Agayev A.
    Oracle ACE
    My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

  • Create standby using incremental backup

    can I create standby database using a backup of primary which was created using below command? ( incremental backup level 0)
    BACKUP INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE TAG 'mybackup_date' PLUS ARCHIVELOG DELETE INPUT;
    v11.2.0.2
    physical standby

    Hello;
    Probably not. The backup command is missing this key piece :
    backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';Since you are using 11R2 you can use "Create a Standby database from an active database using RMAN"
    Example :
    http://www.visi.com/~mseberg/standby_creation_from_active_database_using_rman.html
    Or
    RMAN duplicate for Data Guard standby
    http://www.visi.com/~mseberg/duprman2.html
    Best Regards
    mseberg

  • Restore Tablespace incremental backup is not work as after reimage oracle

    TheTablespace incremental backup Restore is not work as after reimage the oracle database or restore tablespace in standby machine(another machine) is not working .its working in the same machine without reimage .after reimage not working please clarify me ,
    I need the solution as soon as please reply as soon as .
    Commnads used:
    This is the step is followed but i am getting backup or control file not found error.Its works i the application server is not reimaged ;
    please give your valuable suggestion .
    Product Used:oracle 11g in linux environmnet
    1)Before taking backup get SCN number for restore.
    Command applied: Select current_scn from v$database;
    2)running Full backup of database
    Command applied:
    configure controlfile autobackup on;
    backup database plus archivelog;
    CROSSCHECK BACKUP;
    exit;
    3)Running level 0 incremental backup
    Before taking backup get SCN number for restore.
    Command applied:
    BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
    exit;
    3) Running level 1 incremental backup
    Before taking backup get SCN number for restore.
    Command applied:
    BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
    4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
    Command applied:
    SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
    5)TSPITR Restore command
    Command applied:
    run
    RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
    SQL 'ALTER TABLESPACE TEST ONLINE';
    please calrfiy my following question:
    1. After reimage(reinstall oracle database with application ).The aboove scenario is not working
    2. After fullbackup what are the files needs to copy from (opt/oraclle/base/flash_recovery_area/dbname/) to repository because daily cleanup script will keep the data as sysdate -1 .
    For fullbacckup we are currently copying entire (flash_recovery_area/dbname) database folder to repoistory.
    3. after incremental backup what are the files needs to copy from (opt/oraclle/base/flash_recovery_area/dbname/..) to repository because daily cleanup script will keep the data as sysdate -1
    For incremenatl backup currently we are copying (flash_recovery_area/dbname/backupset/<currentdate> and flash_recovery_area/dbname/autobackup/<currentdate>) folder to repoistory.
    4.During restore we are copy entire things from repository to flash_recovery_area finaly apply the above mentioned restore command.
    Tabelspace incremenatl restore is possible after reimage application server(fresh database)/another server with same database(standby machine) ....?
    If we missing something in backup side please clarify me how to retore the tablespace incremental / level 0 tablespacae after reinstallion of server/another standby server.
    Any information please let me know .I need the solution as soon as please reply as soon as .

    Try the Recovery Manager (RMAN) instead. This forum is for feedback about the 11g XE Beta.

  • Can't make an incremental backup in PSE 10 Organizer

    I don't understand why I can't make an incremental backup in PSE 10 Organizer. I made my first full backup to my external drive a week ago. Today I tried to make an incremental backup. After selecting Incremental Backup from the file menu, a new screen appears asking for the Backup Path, and so I entered (by selecting) the full path name on my external drive where I made my original backup. But, next, it wants to know the name of the "Previous Backup file." I have absolutely no idea what the program wants at this point. What particular file does it want me to enter as the "previous backup file"?? There are hundreds of files in my backup directory. The backup directly does have a file called "Backup.tly" which I entered, hoping that this is the file it wants, but then I get this error message: "I:\Pictures\Adobe\Backup.tly does not contain a backup set for the current catalog. Please locate the last backup you made for this catalog." What am I missing here?
    Many thanks for your help,
    Jeff

    Hi Jeff
      Once you have a full back up you can make incremental back ups but you need to follow a set routine. It’s not very intuitive.
    Start by creating a new folder or label a new CD/DVD Disk - it’s best to use dates e.g. “PSE10 incr backup 2012-0104”
    Press Ctrl+B and check Incremental, then click Next
    Highlight your drive containing the last backup and click the bottom Browse button (previous back up file) then navigate to the TLY file and click open.
    Click the Browse button above and navigate to your new folder “PSE10 incr backup 2012-0104”
    Click Done.
    If your full backup originally contained 500 images, the incremental backup will only contain changes since the last backup e.g. files B000501.jpg, B000502.jpg etc
    If you ever have to do a complete restore you start with the TLY file from the latest incremental backup. The program automatically recognizes the number of incremental steps and you will be prompted to insert a disc or navigate to the appropriate drive.
    Incremental backup’s are obviously much quicker to write to disk but I recommend that you periodically perform another full backup and delete any earlier backups.

  • Restoring a catalog from backup and incremental backups on external Hard drive

    Hello!
    I recently bought a new computer where I installed again Elements 8 (that's the one I'm currently using). From my old computer, I have an initial complete catalog backup which was saved in a folder (I called this folder "Complete catalog backup") on an external hard drive. I also made then subsequent incremental backups which were saved in different folders called "Incremental backup 1", "incremental backup 2" etc. on the same external hard drive. Apparently in Element, I discovered that incremental backups can't be saved in the same folder as initial complete backup!
    How should I proceed now to restore my catalog on my new computer? I know how to do it when one has only a complete initial catalog backup, but now I have also several incremental backups (contained in folders "incremental backup 1", "incremental backup 2" etc.), I just don't know how to proceed.
    Some help would be very much appreciated.
    Thanks a lot

    First and foremost: Forget re-importing. You would loose all your edits. Importing is strictly only for images that have never been imported before.
    The remedy for "missing" photos is to re-link them.
    In Lr / Grid View right-click the top-most folder in the folders panel. By "top-most" I mean the parent folders of all folders. If you have several parent folder right-click one of them.
    Then select <Find Missing Folder>, navigate to the corresponding folder on your new drive E and select it. Do this for every other parent folder. If the folder names and structure haven't changed Lr will find the sub-folders on its own.
    For more see here: http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm

  • RMAN: Increment backup very slow

    Hi All,
    We have Datawarehouse database having size around 7TB. Increment backup performance is extremely poor it is taking approx 14hrs to complete the process. We have also enabled block change tracking but failed to meet target.
    Below mentioned DB info & RMAN configuration parameters:
    DB: 11.1.0.6
    OS: Linux 2.6.18-128.el5 x86_64
    System has 16 processor when more than two process per CPU i.e. 32
    CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/d01copy/control_bkp/autobackup_control_file%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 13 BACKUP TYPE TO COMPRESSED BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2';
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.1.0/dbs/snapcf_PRODDB.f'; # default
    Thanks in advance.

    Thnaks for reply.
    Have you configured Compressed backups?
    --> Yes. with below command.
    RMAN> backup as compressed backupset incremental level 1 tag=$v_tag database;
    Have you allocated channels ?
    --> Yes.
    allocate channel backup_disk1 type disk format '$v_bdest/%U' maxpiecesize 10G;
    allocate channel backup_disk2 type disk format '$v_bdest/%U' maxpiecesize 10G;
    allocate channel backup_disk3 type disk format '$v_bdest/%U' maxpiecesize 10G;
    allocate channel backup_disk4 type disk format '$v_bdest/%U' maxpiecesize 10G;
    allocate channel backup_disk5 type disk format '$v_bdest/%U' maxpiecesize 10G;
    What is the Large pool size configured? try to increase.
    --> large_pool_size=1073741824
    Is backup to DISK or TAPE? mentioned in script?
    --> Backup goes to DISK only.
    How is DISK performance?
    --> How can we calculate DISK performance on LINUX?
    Regards,

  • Problem while appling incremental backup on standby 10.2.0.4

    Hi,
    While recovering incremental backup on standby database, we are facing problem.
    Even though we have cataloged the backup we want to recover, when we issue "RMAN> recover database noredo;" recovery fails as rman tries to recover from the backup which are not avaliable on disk.
    RMAN> recover database noredo;
    Starting recover at 20-OCT-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=531 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=530 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=529 devtype=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: sid=528 devtype=DISK
    channel ORA_DISK_1: starting incremental datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00012: /u02/oradata/p1sipmdm/data/p1sipmdm_cmx_temp2.dbf
    destination for restore of datafile 00013: /u05/oradata/p1sipmdm/index/p1sipmdm_cmx_indx3.dbf
    destination for restore of datafile 00027: /u05/oradata/p1sipmdm/data/p1sipmdm_cmx_temp4.dbf
    destination for restore of datafile 00042: /u01/oradata/p1sipmdm/index/p1sipmdm_cmx_indx9.dbf
    destination for restore of datafile 00046: /u03/oradata/p1sipmdm/data/p1sipmdm_cmx_data19.dbf
    destination for restore of datafile 00068: /u06/oradata/p1sipmdm/index/gnw_death_ors_x04.dbf
    destination for restore of datafile 00076: /u07/oradata/p1sipmdm/data/p1sipmdm_cmx_data24.dbf
    channel ORA_DISK_1: reading from backup piece /backup/rman_backup/p1sipmdm/qimouvjj_1_1
    channel ORA_DISK_2: starting incremental datafile backupset restore
    channel ORA_DISK_2: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00010: /u06/oradata/p1sipmdm/index/p1sipmdm_cmx_indx2.dbf
    destination for restore of datafile 00022: /u07/oradata/p1sipmdm/data/p1sipmdm_cmx_data7.dbf
    destination for restore of datafile 00025: /u03/oradata/p1sipmdm/data/p1sipmdm_cmx_temp3.dbf
    destination for restore of datafile 00030: /u09/oradata/p1sipmdm/data/p1sipmdm_cmx_data10.dbf
    destination for restore of datafile 00069: /u02/oradata/p1sipmdm/index/gnw_death_ors_x05.dbf
    destination for restore of datafile 00083: /u08/oradata/p1sipmdm/data/system09.dbf
    destination for restore of datafile 00086: /u08/oradata/p1sipmdm/data/gnw_producer01.dbf
    channel ORA_DISK_2: reading from backup piece /backup/rman_backup/p1sipmdm/qmmov08s_1_1
    channel ORA_DISK_3: starting incremental datafile backupset restore
    channel ORA_DISK_3: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00006: /u02/oradata/p1sipmdm/data/p1sipmdm_cmx_data2.dbf
    destination for restore of datafile 00009: /u05/oradata/p1sipmdm/index/p1sipmdm_cmx_indx1.dbf
    destination for restore of datafile 00032: /u09/oradata/p1sipmdm/index/p1sipmdm_cmx_indx6.dbf
    destination for restore of datafile 00067: /u03/oradata/p1sipmdm/index/gnw_death_ors_x03.dbf
    destination for restore of datafile 00080: /u08/oradata/p1sipmdm/data/p1sipmdm_cmx_data27.dbf
    channel ORA_DISK_3: reading from backup piece /backup/rman_backup/p1sipmdm/qkmov07b_1_1
    channel ORA_DISK_4: starting incremental datafile backupset restore
    channel ORA_DISK_4: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00020: /u07/oradata/p1sipmdm/data/p1sipmdm_mdm_data3.dbf
    destination for restore of datafile 00072: /u01/oradata/p1sipmdm/data/docgen_data01.dbf
    channel ORA_DISK_4: reading from backup piece /backup/rman_backup/p1sipmdm/qnmov0ev_1_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 10/20/2011 22:54:39
    ORA-19870: error reading backup piece /backup/rman_backup/p1sipmdm/qimouvjj_1_1
    ORA-19505: failed to identify file "/backup/rman_backup/p1sipmdm/qimouvjj_1_1"
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Actual files are located at /u07/oradata/p1sipmdm_bkp/ location .. when we issue list backup summary rman shows these backups that we want to use..
    RMAN> list backups;
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11210 Incr 4.88G DISK 00:00:00 20-OCT-11
    BP Key: 12907 Status: AVAILABLE Compressed: YES Tag: TAG20111020T101659
    Piece Name: /u07/oradata/p1sipmdm_bkp/pmsipmdp_1empinlp_1_1
    List of Datafiles in backup set 11210
    File LV Type Ckp SCN Ckp Time Name
    4 Incr 8428228181070 20-OCT-11 /u01/oradata/p1sipmdm/data/users01.dbf
    7 Incr 8428228181070 20-OCT-11 /u03/oradata/p1sipmdm/data/p1sipmdm_cmx_data3.dbf
    16 Incr 8428228181070 20-OCT-11 /u01/oradata/p1sipmdm/data/p1sipmdm_cmx_data6.dbf
    18 Incr 8428228181070 20-OCT-11 /u06/oradata/p1sipmdm/data/p1sipmdm_mdm_data1.dbf
    29 Incr 8428228181070 20-OCT-11 /u05/oradata/p1sipmdm/data/undotbs03.dbf
    41 Incr 8428228181070 20-OCT-11 /u02/oradata/p1sipmdm/data/p1sipmdm_cmx_data15.dbf
    79 Incr 8428228181070 20-OCT-11 /u06/oradata/p1sipmdm/data/p1sipmdm_cmx_data26.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11211 Incr 80.00K DISK 00:00:00 20-OCT-11
    BP Key: 12908 Status: AVAILABLE Compressed: YES Tag: TAG20111020T101659
    Piece Name: /u07/oradata/p1sipmdm_bkp/pmsipmdp_1impioai_1_1
    SPFILE Included: Modification time: 20-OCT-11
    please advice.
    Regards,
    Abhay.....

    Hi,
    Backups are cataloged and they are persent on te server but on another location.
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11210 Incr 4.88G DISK 00:00:00 20-OCT-11
    BP Key: 12907 Status: AVAILABLE Compressed: YES Tag: TAG20111020T101659
    Piece Name: /u07/oradata/p1sipmdm_bkp/pmsipmdp_1empinlp_1_1
    List of Datafiles in backup set 11210
    File LV Type Ckp SCN Ckp Time Name
    4 Incr 8428228181070 20-OCT-11 /u01/oradata/p1sipmdm/data/users01.dbf
    7 Incr 8428228181070 20-OCT-11 /u03/oradata/p1sipmdm/data/p1sipmdm_cmx_data3.dbf
    16 Incr 8428228181070 20-OCT-11 /u01/oradata/p1sipmdm/data/p1sipmdm_cmx_data6.dbf
    18 Incr 8428228181070 20-OCT-11 /u06/oradata/p1sipmdm/data/p1sipmdm_mdm_data1.dbf
    29 Incr 8428228181070 20-OCT-11 /u05/oradata/p1sipmdm/data/undotbs03.dbf
    41 Incr 8428228181070 20-OCT-11 /u02/oradata/p1sipmdm/data/p1sipmdm_cmx_data15.dbf
    79 Incr 8428228181070 20-OCT-11 /u06/oradata/p1sipmdm/data/p1sipmdm_cmx_data26.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11211 Incr 80.00K DISK 00:00:00 20-OCT-11
    BP Key: 12908 Status: AVAILABLE Compressed: YES Tag: TAG20111020T101659
    Piece Name: /u07/oradata/p1sipmdm_bkp/pmsipmdp_1impioai_1_1
    SPFILE Included: Modification time: 20-OCT-11

  • Restore using incremental backup with noarchivelog mode

    Hello experts,
    We are running SAP on Oracle databse(IN NOARCHIVELOG MODE) for which we are having full offline backup on every sunday and post which incremental backups on rest of the days. We have scenario to do restore db to the state till last friday's incremental backup.
    Please let us know the procedure for restoring till that point. If possible using brtools utility(which is SAP specific).
    Thank You
    Regards,
    Venkateshwar

    If you do not want to read the whole doc This is the snippet for you.
    Recovering a NOARCHIVELOG Database with Incremental Backups
    Restoring a database running in NOARCHIVELOG mode is similar to restoring a database in ARCHIVELOG mode. The main differences are:
    Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
    Media recovery is not possible because no archived redo logs exist.
    You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. The incremental backups must be consistent, like all backups of a database run in NOARCHIVELOG mode, so you cannot make backups of the database when it is open.
    When you are recovering a NOARCHIVELOG database, specify the NOREDO option on the RECOVER command to indicate that RMAN should not attempt to apply archived redo logs. Otherwise, RMAN returns an error.
    To recover a NOARCHIVELOG database with incremental backups:
    After connecting to the target database and the recovery catalog, place the database in a mounted state:
    STARTUP FORCE MOUNT
    Restore and recover the database.
    For example, you can perform incomplete recovery with the following commands:
    RESTORE DATABASE
    FROM TAG "consistent_whole_backup";
    RECOVER DATABASE NOREDO;
    Open the database with the RESETLOGS option.
    For example, enter the following command:
    ALTER DATABASE OPEN RESETLOGS;

  • Incremental Backups Interface Problem???

    Maybe it's just me, but doing a simple task like backing up (full / incremental) should be very simple, and I'm having a problem. I should be able to select a backup location (a preference), do a Full backup, then do an Incremental...as many as I want...and at some time I may want to do a Full backup again. But it seems it's much more complex than that...
    Here's what I'm doing (obviously wrong):
    I've done a Full backup on Drive D in some directory, say 'My Backup'. Fine, I think I have a Full backup.
    Now later, I want to do an incremental, and I'm prompted to select a destination Drive (it's D), and then "chose browse to load your previous backup file."
    OK, I browse to my D | My Backup directory (that's the previous and ONLY backup location), but I'm warned that a backup file already exists, and do I want to overwrite it. Huh???
    An Incremental doesn't overwrite a Full Backup. What am I supposed to Browse to?
    And what does "Load previous backup file to determine size" have anything to do with a simple need to create an incremental backup file?
    Help hasn't helped. I'm missing something.
    I'd really appreciate if anyone can tell me what I'm doing wrong. I obviously don't want to overwrite a Full backup with an Incremental.

    See excellent answer in Technical side of the forum
    Michael Sobieski, "Problem with Full - Incremental Backup in 5.0" #1, 19 Oct 2006 8:21 am

  • Online RMAN incremental backups...

    Oracle10g RHEL4 AS
    HI All,
    I wanted to know what options can use to do an online incremental backup without using so much space. Currently, our flash recovery area is only 8G and when I ran an incremental backup it got filled after backing up only 3 datafiles. The command that I used was as follows:
    run {
    sql 'alter system switch logfile';
    allocate channel t1 DEVICE type DISK;
    RECOVER COPY OF DATABASE WITH TAG 'incr_update';
    BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'incr_update'
    DATABASE;
    sql 'alter system archive log current';
    release channel t1;
    Is there any option that I can use to compress or make smaller these incremental backups? Or is this perhaps happening because this is the first backup and it is making a Level 0 backup first and then future backups will be Level 1? Either way I would like to know how I can shrink the backups that are being generated.
    Thank you.

    Is there any option that I can use to compress or make smaller these incremental backups? You could try the backup set compression.
    Or is this perhaps happening because this is the first backup and it is making a Level 0 backup first and then future backups will be Level 1?Yes this is likely.
    You may also reduce used space in the FRA if you decrease your recovery retention policy (depending of course of your restore/recovery requirements).

  • Duplicate database and incremental backups

    Hello,
    I'm currently investigating options to maintain a test server that is "relatively" up-to date compared to the production server.
    This is my first contact with RMAN and I went through the manuals but as I did not have a chance to play with it I might have missed something.
    This is an Oracle 11.2 (not sure about the full version number) on a Redhat Enterprise Linux.
    The test server needs to be writeable and need to be re-synced with the production server approx. once or twice a month. Due to the size of the database (~600GB) we are looking into solutions that could make use of the incremental backups that are already taken on the production database.
    While initiating the test server using RMAN DUPLICATE seems to be straight forward, I'm unsure on how the "syncing" can be done in the most efficient way - especially because we are changing the data on the test server.
    From the description of the RMAN RECOVER command it's not clear to me if this could be used to "recover" the test database based on the incremental backups to the "current state" of the production database even if the test database has been changed. After reading some posts here, this does not seem to be the case.
    Would a restore point make such an incremental restore possible? Creating a (named?) restore point right after the duplication, then once the tests are finished do a flashback to the restore point and then apply the incremental backups that have accumulated since then.
    Another options seems to be to create a Standby Database. Then when performing the tests we turn the Standby Database into a Snapshot Standby Database open it in read/write and run the tests. Once we are done, we switch it back to a physical standby. That switchback will rewind the changes and the accumulated redo logs are applied thus "incrementally" catching up with production - which is essentially what we want.
    Is there any other solution to this? Or is using a snapshot standby the most efficient solution? If at all possible we would like to avoid transferring the 600GB each time we want to re-sync the test database.
    Thanks in advance
    Thomas

    Thomas;
    RMAN Incremental Backups to Roll Forward a Physical Standby Database might offer some help.
    There's a great example of it here :
    http://www.oracle-ckpt.com/?s=standby+scn&op.x=0&op.y=0
    If you go the Snapshot route make sure you have the space for the Archive on both databases. Also double check you flash recovery area, again on both databases. If you have an issue you may have to use the roll forward.
    Best Regards
    mseberg

  • Rman and block tracking changes (incremental backups)

    Hi all,
    i am using rman to backup my production database. i want to use the block tracking option in order to do incremental backups faster.
    how can i backup the tracking file?
    thanx

    Hi,
    Do we need to take backup of the tracking file?
    I was wondering how the backup of a tracking file will help us. If we lost some of our hard disk and then we restore an old tracking file, then how oracle will be able to catch up the missing changes?
    Tracking file is useful only for a very quick locating the datablocks that were changed after the last backup. It doesn't help us in during restore process. I think we will need a full backup of the database, if we loose the tracking file.
    HTH
    Regards,
    Badri.

  • Question on Differential Incremental Backup script.

    Version:11g
    OS : AIX 5.3
    I only have theoretical knowledge of RMAN. I am planning to implement Differential Incremental Backup for my database. My strategy is
    a. Weekly level 0 backup at Sunday morning 2:00 am
    b. Daily Level 1 Differential Incremental Backups at 2:00 am from Monday to Saturday.
    c. Backup all archived log filesFirst script to perform level 0 backup -- This script will be run by a cron job every Sunday morning 2:00 am
    ==================================================================
    run {
    allocate channel ch1 device type disk;
    backup incremental level 0 format '/u07/rman_backup/FULL_%d_%u' database tag "weekly_full";
    backup format '/u07/rman_backup/RMAN_CTL%s:%t:%p.bkp' current controlfile;
    release channel ch1;
    allocate channel ch1 device type disk;
    backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' DELETE INPUT TAG "archivelogs");
    release channel ch1;
    }The below script is to perform level 1 Differential Incremental Backups for the next 6 days. This script will be run daily
    at 2:00 am monday to saturday by a cronjob. I'll create 6 scripts like below, the only difference being the TAG "Monday-level1","Tuesday-level1"...etc.
    =======================================================
    run {
    allocate channel ch1 device type disk;
    backup incremental level 1 format '/u07/rman_backup/RMAN_DBF_%s:%t:%p.bkp' database tag "Monday-level1";
    backup format '/u07/rman_backup/RMAN_CTL<%s:%t:%p>.bkp' current controlfile;
    release channel ch1;
    allocate channel ch1 device type disk;
    backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' delete input tag "archivelogs");
    release channel ch1;
    }Question 1.
    Is my level 1 script correct ?
    Question2.
    Will the above scripts for level 0 and level 1 automatically delete the
    obsolete level 0 and level 1 backup files when a new weekly cycle starts?
    Any more enhancements(or corrections) you gurus want to suggest?

    Above scripts seems to be correct.
    Why you don't test it on test environment?
    These codes don't delete obsolete backups of the database. Then just delete backed up archived redo log files due to DELETE INPUT command
    If you use retention policy to recovery window of 7 days, to delete obsolete backups you need to run CROSSCHECK command and then DELETE OBSOLETE to delete all obsolete backups
    My suggestions
    - Practice it on test environment
    - Read documentation before performing any tests
    - Try to understand each line of these scripts based on documentation

Maybe you are looking for