Balancing RMAN backup set

I currently put RMAN in place to back up my database with 2 threads, but what I see is that there is a pretty big difference in the size of backup sets created by the two channels. Usually I see backup sets generated from channel 1 head to about 14 GB where the backup games generated since channel 2 come in about 56 GB. Is there a way I can get this to create two backup sets, so they are more balanced in terms of size. I hope that it would also reduce the execution time of my backups. Here are the parameters and the command I use:
SET UP THE DEVICE TYPE DISK PARALLELISM BACKUPSET BACKUP TYPE COMPRESSED 2;
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 10 G FORMAT ' / dbbackups/%U';

RMAN % > tag FULL_BACKUP; database backup
thanks,.

John

Inequality that you are experiencing is due to the fact that RMAN channel (in 10g and below) save a data file one at once. And a data file cannot be shared on multiple channels. There is a handy feature in 11g, which is used to breaking large files of data into sections.

Thus, when someone asks why would you want to have multiple files for a tablespace when it's much easier to only have to deal with one? This seems to be a valid reason.

Tags: Database

Similar Questions

  • Backup with rman backup sets

    Hi experts. I know about backup of backup without rman example sets but I want to know is there a way to backup with rman backup sets.

    Perhaps it works for your condition.

    RMAN > backupset backup is complete before ' sysdate-1';

    Kind regards

    Shivananda

  • RMAN backup setting

    Hi all

    11.2.0.1

    AIX 6.1


    I ran using rman backup:

    run

    {

    overlap archivelog all;

    cross-checking of backup;

    delete expired backup noprompt.

    delete noprompt expired archivelog all;

    delete noprompt obsolete;

    backup database format more archivelog compressed backupset 'db_ %U;

    backup current controlfile to format ensures "%U ctrl_stby_";

    backup current controlfile "%U ctrl_" format

    }

    Given that I did not specify the full path of the directory, I assume that it will use the default FRA.

    Then I checked the FRA and I see theres files


    Oracle@server:/U02/Oracle/fast_recovery_area/prod/backupset/2013_09_20 > ls-l

    Total 1011824

    -rw - 1 oracle dba 1114112 20 September 17:58 o1_mf_ncsnf_TAG20130920T175850_93r72vvp_.bkp

    -rw - 1 oracle dba 1114112 20 Sep 18:04 o1_mf_ncsnf_TAG20130920T180300_93r7fnny_.bkp

    -rw - 1 oracle dba 515825664 20 Sep 18:04 o1_mf_nnndf_TAG20130920T180300_93r7bnlb_.bkp



    What are these files? Where are the format "db_ %U" and "%U ctrl_stby_" and "ctrl_ %U" I mentioned above?


    Thank you very much

    zxy

    I guess that's archielog of backup.

    Please after the release of rman backup cmd or rman list backup cmd.

  • the backup rman backup sets in multiple locations

    Hello

    I had 100 GB of data.

    But my/U01 point size is 55Go of editing

    the point size of editing/U02 is 60 GB

    How can I take a full backup of database

    run
    {
    backup format u01/oradata/test/'backup_%d_%s_%t.bkp' database;
    }

    How can I include/u02 as the u01 get filled it must copy in u02

    Thanks in advance

    Run {}
    data file backup 1 marker "";
    .
    .
    .
    .
    .
    data file backup marker n '';
    .
    .
    .
    .
    .
    backup current controlfile "" format
    ARCHIVELOG backup format '' entry delete;
    };

    Published by: orant575 on July 1, 2009 13:04

  • How to judge the backup set is available (with RMAN)?

    Hi all, after you back up the database, how to judge the backup set is available?

    SQL > SELECT * FROM V$ VERSION;

    BANNER
    ----------------------------------------------------------------
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    AMT for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
     rman target /
    
    Recovery Manager: Release 11.2.0.1.0 - Production on Mon Jul 9 12:28:51 2012
    
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    
    connected to target database: CATDB (DBID=2328696599)
    
    RMAN> crosscheck backupset;
    
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=24 device type=DISK
    crosschecked backup piece: found to be '*AVAILABLE*'
    backup piece handle=D:\ORACLE\FAST_RECOVERY_AREA\CATDB\BACKUPSET\2012_06_14\O1_MF_NNNDF_TAG201206
    14T153439_7XMHL0JL_.BKP RECID=34 STAMP=785950480
    crosschecked backup piece: found to be '*AVAILABLE*'
    backup piece handle=D:\ORACLE\FAST_RECOVERY_AREA\CATDB\BACKUPSET\2012_06_14\O1_MF_ANNNN_TAG201206
    14T153546_7XMHN2C6_.BKP RECID=35 STAMP=785950546
    crosschecked backup piece: found to be '*AVAILABLE*'
    backup piece handle=D:\ORACLE\FAST_RECOVERY_AREA\CATDB\AUTOBACKUP\2012_06_14\O1_MF_S_785950547_7X
    MHN4MH_.BKP RECID=36 STAMP=785950548
    crosschecked backup piece: found to be '*AVAILABLE*'
    backup piece handle=D:\ORACLE\FAST_RECOVERY_AREA\CATDB\AUTOBACKUP\2012_06_14\O1_MF_S_785953535_7X
    MLKN66_.BKP RECID=37 STAMP=785953539
    crosschecked backup piece: found to be '*AVAILABLE*'
    backup piece handle=D:\ORACLE\FAST_RECOVERY_AREA\CATDB\AUTOBACKUP\2012_06_14\O1_MF_S_785971797_7X
    N4D6YF_.BKP RECID=38 STAMP=785971798
    crosschecked backup piece: found to be '*AVAILABLE*'
    backup piece handle=D:\ORACLE\FAST_RECOVERY_AREA\CATDB\AUTOBACKUP\2012_06_29\O1_MF_S_787249342_7Y
    V4001O_.BKP RECID=39 STAMP=787249359
    Crosschecked 6 objects
    
    RMAN> list backupset;
    
    using target database control file instead of recovery catalog
    
    List of Backup Sets
    ===================
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    26      Full    320.44M    DISK        00:01:03     14-JUN-12
            BP Key: 34   Status: AVAILABLE  Compressed: YES  Tag: TAG20120614T153439
            Piece Name: D:\ORACLE\FAST_RECOVERY_AREA\CATDB\BACKUPSET\2012_06_14\O1_MF_NNNDF_TAG201206
    14T153439_7XMHL0JL_.BKP
      List of Datafiles in backup set 26
      File LV Type Ckp SCN    Ckp Time  Name
      ---- -- ---- ---------- --------- ----
      1       Full 3712551    14-JUN-12 D:\ORACLE\ORADATA\CATDB\SYSTEM01.DBF
      2       Full 3712551    14-JUN-12 D:\ORACLE\ORADATA\CATDB\SYSAUX01.DBF
      3       Full 3712551    14-JUN-12 D:\ORACLE\ORADATA\CATDB\UNDOTBS01.DBF
      4       Full 3712551    14-JUN-12 D:\ORACLE\ORADATA\CATDB\USERS01.DBF
      5       Full 3712551    14-JUN-12 D:\ORACLE\ORADATA\CATDB\CATMETADATA01.DBF
      6       Full 3712551    14-JUN-12 D:\ORACLE\ORADATA\CATDB\UNDO2.DBF
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    27      99.50K     DISK        00:00:00     14-JUN-12
            BP Key: 35   Status: AVAILABLE  Compressed: YES  Tag: TAG20120614T153546
            Piece Name: D:\ORACLE\FAST_RECOVERY_AREA\CATDB\BACKUPSET\2012_06_14\O1_MF_ANNNN_TAG201206
    14T153546_7XMHN2C6_.BKP
    
      List of Archived Logs in backup set 27
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    47      3712495    14-JUN-12 3712583    14-JUN-12
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    28      Full    9.45M      DISK        00:00:02     14-JUN-12
            BP Key: 36   Status: AVAILABLE  Compressed: NO  Tag: TAG20120614T153547
            Piece Name: D:\ORACLE\FAST_RECOVERY_AREA\CATDB\AUTOBACKUP\2012_06_14\O1_MF_S_785950547_7X
    MHN4MH_.BKP
      SPFILE Included: Modification time: 14-JUN-12
      SPFILE db_unique_name: CATDB
      Control File Included: Ckp SCN: 3712594      Ckp time: 14-JUN-12
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    29      Full    9.45M      DISK        00:00:07     14-JUN-12
            BP Key: 37   Status: AVAILABLE  Compressed: NO  Tag: TAG20120614T162535
            Piece Name: D:\ORACLE\FAST_RECOVERY_AREA\CATDB\AUTOBACKUP\2012_06_14\O1_MF_S_785953535_7X
    MLKN66_.BKP
      SPFILE Included: Modification time: 14-JUN-12
      SPFILE db_unique_name: CATDB
      Control File Included: Ckp SCN: 3715284      Ckp time: 14-JUN-12
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    30      Full    9.45M      DISK        00:00:02     14-JUN-12
            BP Key: 38   Status: AVAILABLE  Compressed: NO  Tag: TAG20120614T212957
            Piece Name: D:\ORACLE\FAST_RECOVERY_AREA\CATDB\AUTOBACKUP\2012_06_14\O1_MF_S_785971797_7X
    N4D6YF_.BKP
      SPFILE Included: Modification time: 14-JUN-12
      SPFILE db_unique_name: CATDB
      Control File Included: Ckp SCN: 3735186      Ckp time: 14-JUN-12
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    31      Full    9.45M      DISK        00:00:23     29-JUN-12
            BP Key: 39   Status: AVAILABLE  Compressed: NO  Tag: TAG20120629T162221
            Piece Name: D:\ORACLE\FAST_RECOVERY_AREA\CATDB\AUTOBACKUP\2012_06_29\O1_MF_S_787249342_7Y
    V4001O_.BKP
      SPFILE Included: Modification time: 29-JUN-12
      SPFILE db_unique_name: CATDB
      Control File Included: Ckp SCN: 5138750      Ckp time: 29-JUN-12
    

    Please do not forget to change the status thread answer whether it is possible when believe you your thread replied, he pretend to wasting time in other forums users while they are looking outstanding which is not answered, thank you for understanding

    Published by: Julien Hesenov on July 9, 2012 12:42

  • RMAN backup location must change and remove obsolete

    Dear Experts,

    I'm working on the following environment,

    Operating system: Windows server 2012 R2

    Oracle version: 11.2.0.1.0 release

    Type of RMAN backup: Cumulative (preferred by the direction and I can't change it in differential backup)

    My current situation,

    I set up RMAN and H: drive for purposes of backup and G: for Archivelog.

    Recently, my city was covered by the flood waters and the server works not for a week so that we delete obsolete level 0 does not work.

    Currently there is not enough space to run a level 1 and level 0, while I should change the backup location.

    My Question is,

    (1) I need to change this location of drive H: to G: drive backup backup correctly without error not enough space.

    (2) after having taken a level 1 and level 0, depending on my 1 redundancy, RMAN mechanism should delete obsolete backup disk without failure G: and H:.

    Kindly help me how to get to my need. This will help me, thanks in advance

    You can

    1. replace the DB_RECOVERY_FILE_DEST G:

    2 run backups

    3. wait for the DELETE OBSOLETE delete obsolete backups of H:

    and then

    4. change the DB_RECOVERY_FILE_DEST return h as it was more early

    In this way, you don't have to use the FORMAT or CHANNEL of CONFIGURE commands (I was referring to CONFIGURE CHANNEL, not ALLOCATE CHANNEL) to change the destination of the backup

    Hemant K Collette

  • Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

    Here's my question after tons of research and test without have the right solutions.

    Target:

    (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

    (2) I created physical standby database "stbydb" on the server "node2".

    (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

    (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

    (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

    (6) I do RMAN backup (database and archivelog) on the site of relief only.

    (7) I want to use this backup for full restore of the database on the primary database.

    He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

    Here is how to save, on the database pending:

    (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

    (2) RMAN > backup database;

    (3) RMAN > backup archivelog all;

    I got elements of backup and copied to primary db Server something like:

    /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

    /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

    /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

    So here's how to restore, on the main site:

    I clean all the files (data files, controlfiles oder all gone).

    (1) restore spfile from pfile

    RMAN > startup nomount

    RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

    (2) modify pfile to convert to db primary content. pFile shows below

    *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

    * .audit_trail = "db".

    * full = '12.1.0.2.0'

    *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

    * .db_block_size = 8192

    * .db_domain = "

    *.db_file_name_convert='/testdb/','/testdb /'

    * .db_name = "testdb".

    * .db_recovery_file_dest ='/ orafra'

    * .db_recovery_file_dest_size = 10737418240

    * .db_unique_name = "testdb".

    *.diagnostic_dest='/opt/Oracle/DB '

    * .fal_server = "stbydb".

    * .log_archive_config = 'dg_config = (testdb, stbydb)'

    * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

    * .log_archive_dest_state_2 = 'ENABLE '.

    *.log_file_name_convert='/testdb/','/testdb /'

    * .memory_target = 1800 m

    * .open_cursors = 300

    * runoff = 300

    * .remote_login_passwordfile = "EXCLUSIVE."

    * .standby_file_management = "AUTO".

    * .undo_tablespace = "UNDOTBS1.

    (3) restart db with updated file pfile

    SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

    SQLPLUS > the judgment

    SQLPLUS > startup nomount

    (4) restore controlfile

    RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

    RMAN > change the editing of the database

    (5) all elements of backup catalog

    RMAN > catalog starts by ' / home/oracle/backupset / '.

    (6) restore and recover the database

    RMAN > restore database;

    RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

    (7) open resetlogs

    RMAN > alter database open resetlogs;

    Everything seems perfect, except one of the file log roll forward pending is not generated

    SQL > select * from v$ standby_log;

    ERROR:

    ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

    ORA-27037: unable to get file status

    Linux-x86_64 error: 2: no such file or directory

    Additional information: 3

    no selected line

    I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

    So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

    And I got the same missing log file.

    The problem is:

    (1) complete alert.log filled with this error, not the concern here

    (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

    (3) I can't delete and re-create this log file

    Then I tried several and found:

    The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

    For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

    SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

    GROUP # SEQUENCE # USED STATUS

    ---------- ---------- ---------- ----------

    4 19 ACTIVE 133632

    5 0 0 UNASSIGNED

    6 0 0 not ASSIGNED

    7 0 0 UNASSIGNED

    So until I take the backup, I tried on the primary database:

    SQL > alter system set log_archive_dest_state_2 = delay;

    This was the Group of standby_log side Eve #4 was released:

    SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

    GROUP # SEQUENCE # USED STATUS

    ---------- ---------- ---------- ----------

    4 0 0 UNASSIGNED

    5 0 0 UNASSIGNED

    6 0 0 not ASSIGNED

    7 0 0 UNASSIGNED

    Then, the backup has been restored correctly without missing standby logfile.

    However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

    Finally, my real questions come:

    (1) what I do may not do on parameter change?

    (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

    I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

    And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

    I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

    Your idea is very much appreciated.

    Thank you!

    Hello

    1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

    2nd--> when we opened the ORL database should be deleted and created

    3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

    DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

    THREAD # SEQUENCE # GROUP # STATUS

    ---------- ---------- ---------- ----------

    1 233 4 ACTIVE

    1 238 5 ACTIVE

    DR sys@cdb01 SQL > select * from v$ logfile;

    GROUP # STATUS TYPE MEMBER IS_ CON_ID

    ---------- ------- ------- ------------------------------ --- ----------

    3 /u03/cdb01/cdb01/redo03.log no. 0 online

    /U03/cdb01/cdb01/redo02.log no. 0 2 online

    1 /u03/cdb01/cdb01/redo01.log no. 0 online

    4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

    /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

    DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

    method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

    DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

    -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

    DR sys@cdb01 SQL > alter database force claire logfile 4;

    change the database group claire logfile 4

    *

    ERROR on line 1:

    ORA-01156: recovery or current flashback may need access to files

    DR sys@cdb01 SQL > alter database recover managed standby database cancel;

    Database altered.

    DR sys@cdb01 SQL > change the database group claire logfile 4;

    Database altered.

    DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

    -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

    DR sys@cdb01 SQL >

    If you do, you can recreate the controlfile without waiting for redo log entry...

    If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

    Thank you

  • Hello, no SPFILE in a backup set.

    Good afternoon, No SPFILE in a game of backup.
    Available:
    hot backup
    Log archiving
    controlfile
    name of the database
    SID
    DBID
    I need to recover data to a new server

    Hello

    Hello, no SPFILE in a backup set.

    1. what type of backup took you?

    2. so you tell backup to hot is available, then you might be knowing the oracle_sid.

    3. create some dummy pfile and try to restore (or otherwise with rman, you can begin with instance - pfile)

    -Pavan Kumar N

  • RMAN backup gets already

    Hi all;

    RMAN > set the channel 1 device type disc format ' / u01/rmanbkp ";

    new RMAN configuration settings:

    CONFIGURE the CHANNEL 1 DEVICE TYPE DISK FORMAT ' / u01/rmanbkp ";

    new RMAN configuration settings are stored successfully

    output channel: ORA_DISK_1

    RMAN > list backup;

    specification does not match the backups in the repository

    RMAN > backup database tag = "NORMAL_BKP_15_jul_15";

    From 25 July 15 backup

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 20 type of device = DISK

    channel ORA_DISK_1: from complete compressed datafile backup set

    channel ORA_DISK_1: specifying datafile (s) in the backup set

    Enter a number of file datafile = 00005 name=/u03/app/oracle/oradata/crms/tbs02.dbf

    Enter a number of file datafile = 00001 name=/u02/app/oracle/oradata/crms/system01.dbf

    Enter a number of file datafile = name=/u01/crmsx4.dbf 00024

    channel ORA_DISK_1: starting piece 1 to July 25, 15

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 25/07/2015 10:30:26

    ORA-19504: cannot create the file ' / u01/rmanbkp.

    ORA-27038: created file already exists

    Additional information: 1

    There is no file physically in/u01/rmanbkp

    DB version: 11.2.0.1 on (Redaht)

    RMAN > set the channel 1 device type disc format ' / u01/rmanbkp ";


    Specify format with extension, something like below

    RMAN > set up the channel 1 device type disk format ' / u01/rmanbkp/backup%U';

    http://docs.Oracle.com/CD/B28359_01/backup.111/b28273/rcmsubcl010.htm

  • content managed rman backup crushing and selection procedure of the tape media

    Hello Experts.

    I have a question about the backupset rman tape media manage tape of the osb.

    [ENV]

    Exadata rman backup assistance OSB(version: 10.4.0.3.0) SL500 LTO5 4 Tape Drive with rman scripts and full backup is working well.

    1 Appendix backup on OS crontab

    -Each backup full day at 00:00 AM

    2 rman view all:

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    using the control file of the target instead of recovery catalog database

    RMAN settings for database with db_unique_name TESTDW are:

    CONFIGURE RETENTION POLICY TO 3 DAY RECOVERY WINDOW;

    CONFIGURE BACKUP OPTIMIZATION # by default

    CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';

    SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.

    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    3 rman backup scirpts

    Run {}

    allocate channels c01 type 'sbt_tape' connect 'sys/manager@testdw1';

    allocate channel c02 type 'sbt_tape' connect 'sys/manager@testdw2';

    allocate channel c03 type 'sbt_tape' connect 'sys/manager@testdw1';

    allocate channels c04 type 'sbt_tape' connect 'sys/manager@testdw2';

    Backup section size 900g database;

    output channel c01;

    output channel c02;

    output channel c03;

    output channel c04;

    }

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    1st quarter > after several weeks and I run the command as "#obtool u admin Pei welcome1 lsvol-L lib1.

    and are used in many media of rman backup band (about 50EA media, perhaps 46EA are full and 4EA are appendble)

    So, I issue the command 'lsvol - a - c' and could not display expired on all media content.

    Why OSB no has not select and replace the tape media despite the rman rman default retention policy (3days) all show the setting.

    Why OSB does not have the expired status of rman content on tape media?

    -> I need the rman (delete expired, delete obsolete etc...) command to share the summary status of OSB and rman rman?

    Q2 > selection procedure for the tape media all backup rman

    Suppose the total number of tape media is 5EA. (1,2,3,4,5) with an available tape LTO5 drive.

    Status: 1 (full-rman content already expired), 2 (content integral-rman not expired), 3 (editable, remaining space), 4 (new media), 5 (currnet wring media)

    If OSB burn now 5 and reach at the end of the Strip and possibly another media, media to be selected by the OSB?

    Advanced thanks.

    If I place the order obsolete in the rman script as 'delete type 'SBT_TAPE' noprompt obsolete device;' the results will be the same as your

    the syntax because rman default setting (CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS ;) has already been fixed on the command "Show all", right? @)

    Yes.

    I use the catalog of recovery on a different database and backup script has catalog db connection string.

    And if I only use controlfile instead of recovery catalog to save the backup information and put in place "control_file_record_keep_time" a default of 7 days to 365 days, "remove obsolete" command to remove several weeks backupset works well, is it not?

    Possible problem are existing backups for several weeks if you left default control_file_record_keep_time. Change now will not help unless you catalog later manually all the old pieces not catalogued on tape backup.

    After you clean up the situation and particularly to remove obsolete in your script, rman, you will never make problems with control_file_record_keep_time from this moment. By default will do just fine because it is larger than your window of recovery.

    Kind regards

    Mitja

  • How to restore RMAN backups

    Hello

    I tried to include works of RMAN Oracle 12 c

    If I use the following command, I should have the backuppiece and the archivelog saved in a folder:

    RMAN > BACKUP database DATA PLUS ARCHIVELOG;

    If I ran this command in 4 different days, which I ended up having 4 folders with different inside files

    I guess that, in these files, I have the data files and the archivelogs

    Now I move these folders to tape, re-cutting the backups and delete expired

    Say that in a month, I need one of these backups if I put a band records and I added start with 'c:\path_of _restored_folder _L', so I added all files in the folder that I restored from tape

    Now, if I try to restore the basis of all is well but when I run the recover, it is missing some archiving logs it says

    If I put all the files for 4 days then he finds the archivelog she needs and pick up without problem

    on this basis I understand that in the folder containing a backuppiece of a specific day there is the newspaper of archive that I needed to recover from the DB, is that true? How can I know if the backups folder I need to replace in order to have all the required log archiving?

    At the moment my DB retrieves only if I handed out the Ribbon last backup folder, if I handed out the previous, it restores, but is not recover

    Also I have this configuration of the oracle recovery 3 days window maintains backups in order to be able to restore and recover the last 3 days and he simply deletes all obsolete if the FRA is full

    I tried earlier to set up the window of 3 days as a test recovery

    I ran a few backups and after that I ran the 5th FRA leak out of space and the backup fails

    I expect rman to remove the old backup and make way for a new that I have 5 backuppiece and the FRA is full, why he not do?

    Thank you

    The default behavior of RECOVER is to make a full recovery - right until the transactions today.  So it must all archivelogs.

    If you want to restore and recover to a point in time, use the SET clause to THAT specify a sequence of the newspaper or time or SNA.  Oracle will then not get beyond that point in time - that is to say he will not seek further archiving logs.

    (Ideally, when you restore an old backup, I also begins to restore the old controlfile, then using this controlfile).

    If you use the FRA in this way

    a. set db_recovery_file_dest_size and db_recovery_file_dest

    b. * not * used a FORMAT clause in the BACKUP command

    Oracle will recognize all backups in the FRA (you can check by querying V$ FLASH_RECOVERY_AREA_USAGE before and after the backup).

    In this case, Oracle can and will automatically purge outdated backups - that is to say any backup older than the retention period, provided that there is at least a L0 or backup complete closest to the retention period.  You should see messages to this effect in the alert of the instance database log file.

    Hemant K Collette

  • RMAN backup command gets failure


    Hello;


    Merry Christmas to all


    It's the test database (10.2.0.1) on RHEL 4.8, Rman backup command was already.

    I don't understand why I got the error? What was the reason?


    RMAN > backup the database archivelog;

    From backup 25 December 14

    Current archived log

    using the control file of the target instead of recovery catalog database

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: sid = 141 devtype = DISK

    channel ORA_DISK_1: from archive newspaper backupset

    channel ORA_DISK_1: specification of archive log backup set

    archive log entry thread = 1 sequence 2 recid = 1 stamp = 867230647 =

    archive log entry thread = 1 = 3 = 2 = 867233039 stamp recid sequence

    archive log entry thread = 1 sequence 4 recid = 3 = 867233044 stamp =

    archive log entry thread = 1 sequence 5 recid = 4 = 867233122 stamp =

    archive log entry thread = 1 sequence = recid 6 = 5 = 867233128 stamp

    archive log entry thread = 1 sequence = recid 7 = 6 = 867233214 stamp

    archive log entry thread = 1 sequence 8 recid = 7 = 867233453 stamp =

    archive log entry thread = 1 sequence 9 recid = 8 = 867233493 stamp =

    archive log entry thread = 1 sequence 10 recid = 9 = 867233559 stamp =

    channel ORA_DISK_1: starting piece 1 to December 25, 14

    channel ORA_DISK_1: finished piece 1 to December 25, 14

    piece handle=/home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/backupset/2014_12_25/o1_mf_annnn_TAG20141225T101241_b9q5g4jo_.bkp tag = TAG20141225T101241 comment = NONE

    channel ORA_DISK_1: complete set of backups, time: 00:00:16

    Backup over at December 25, 14

    From backup 25 December 14

    using channel ORA_DISK_1

    channel ORA_DISK_1: from full datafile backupset

    channel ORA_DISK_1: specifying datafile (s) in backupset

    input datafile fno = 00001 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/system01.dbf

    input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/sysaux01.dbf 00003

    input datafile fno = 00005 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/example01.dbf

    input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/undotbs01.dbf 00002

    input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/users01.dbf 00004

    channel ORA_DISK_1: starting piece 1 to December 25, 14

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of command thus backup archivelog to 2014/12/25 10:13:54

    ORA-19502: write error on file ' / home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/backupset/2014_12_25/o1_mf_nnndf_TAG20141225T101301_%u_.bkp ', blockno 8833 (blocksize = 8192)

    ORA-27072: IO file error

    Linux error: 2: no such file or directory

    Additional information: 4

    Additional information: 8833

    Additional information: 348160

    > > Physical directories are available

    $ pwd

    /Home/Oracle/Oracle/product/10.2.0/Db_1/flash_recovery_area/ORCL

    [oracle@RAC1 ORCL] $ ls-l

    total 12

    drwxr-x - 3 oracle oinstall 4096 Dec 25 09:24 archivelog

    drwxr-x - 3 oracle oinstall 4096 Dec 25 09:18 backupset

    drwxr-x - 2 oracle oinstall 4096 Dec 24 17:16 onlinelog

    ORA-19502: write error on file ' / home/oracle/oracle/flash_recovery_area/ORCL/backupset/2014_12_26/o1_mf_nnndf_TAG20141226T233412_%u_.bkp ', blockno 37505 (blocks ize = 8192)

    I don't understand why is it taking over as "%u" rather than place a unique value for him. Is it the file with System FRA has enough space?

    DF h/home/oracle/oracle/flash_recovery_area/ORCL/backupset.

    Kind regards

    Shivananda

  • Why RMAN backup tablespace UNDO?

    DB version: 11.2.0.4

    OS: Oracle Linux 6.4

    I found the following log RMAN backup Level0. Is the UNDO data in the tablespace, undo being saved really useful during the restoration?

    If the UNDO data are not used for recovery, then these data impossible recreated duing ALTER DATABASE OPEN files just like the REDO Log files and Temp tablespace?

    Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs1_5.dbf 00024

    ch04 chain: total departure from 1 to 30 - SEP-2014 00:59:18

    channel ch10: finished piece 1 to 30 - SEP-2014 01:01:03

    piece handle = STGlv0_23191_1_20140710 tag = comment STG_BK_LEVEL0_140709 = Version of the API 2.0, MMS Version 1.1.1.0

    channel ch10: complete set of backups, time: 00:41:21

    channel ch10: start the incremental level 0 datafile backup set

    channel ch10: specification-datafile in the backup set (s)

    Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs2_2.dbf 00025

    channel ch10: total departure from 1 to 30 - SEP-2014 01:01:03

    channel ch11: finished piece 1 to 30 - SEP-2014 01:01:48

    piece handle = STGlv0_23201_1_20140710 tag = comment STG_BK_LEVEL0_140709 = Version of the API 2.0, MMS Version 1.1.1.0

    channel ch11: complete set of backups, time: 00:23:18

    channel ch11: start the incremental level 0 datafile backup set

    channel ch11: specification-datafile in the backup set (s)

    Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs2_3.dbf 00026

    You must include the UNDO Tablespace in backup. You NEED restored and used in the database to recover.

    At any time, there will be transactions not yet validated.  The CANCELLATION option maintains this information.   The open air after a recovery must be able to restore uncommitted operations and it must be able to read the CANCELLATION.

    Hemant K Collette

  • RMAN backup runs twice (sequential) even if it is not configured in this way

    Hello

    I started experimenting with RMAN as another way for backup (currently we use backup with storage). I'm running a few tests every day to check the overhead and time there and also check the storage space needed for our system.

    At first, everything seems fine, I tested a few default options and then started to configure the RMAN suite better our needs.

    The problem:

    During my recent tests found that RMAN's backup of my database twice, but I could not find out where I configure it to run this way.

    I even put a basic Vanilla with the same features, but it produces a single backup set.

    I enclose my test RMAN environment configuration, and I hope that someone will be able to indicate where I configured RMAN to do 2 sets of backup.

    RMAN > show all.

    Db_unique_name MSCA RMAN database configuration settings are:

    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default

    CONFIGURE BACKUP OPTIMIZATION # by default

    SET UP DEFAULT DISK DEVICE TYPE; # by default

    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

    SET UP THE DEVICE TYPE DISK BACKUP FOR PARALLELISM BACKUPSET TABLET 1 TYPE;

    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT ' / oracle/MSCA/db/rman_bkup/MSCA/df_%d_%T_%U.rmn' MAXPIECESIZE 10 G;

    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

    CONFIGURE ENCRYPTION OF DATABASE # by default

    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default

    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / oracle/MSCA/db/rman_bkup/msca_dbs/snapcf_MSCA.f';

    Here is the result of the end of the backup set 1. You can see it took 2 hours, then immediately, he began another work of backup (highlighted in RED)

    channel ORA_DISK_1: finished piece 5 to 02 - OCT-14

    piece handle=/oracle/MSCA/db/rman_bkup/MSCA/df_MSCA_20140902_09phg6h0_5_1.rmn tag = TAG20140902T115927 comment = NONE

    channel ORA_DISK_1: full game backup, duration: 02:05:08

    channel ORA_DISK_1: from complete compressed datafile backup set

    channel ORA_DISK_1: specifying datafile (s) in the backup set

    Thank you

    Saar

    You present, evidence that it is '2 backups of a database'.  I see two backupsets, each with a different set of data files in your ad.  If the backup is spanning two backupsets - you probably more than 64 files of data.

    Hemant K Collette

  • Oracle 10.2.0.3 move an rman backup

    We do a rman level 0 every weekend and level 1 every day. I want to keep away the last copies of weeks on another hard drive to save space. I guess that is done from rman? If so, can what commands I use?

    jdaniel1127 wrote:

    Currently have 10.2.0.3 on Windows Server 2008...

    I have configured the channels as follows:

    channel 1 device type disk format='f:\rman_backups\rman%u.bus' (this corresponds to the current files on g:\backups\)

    Channel 2 device type disk format='f:\archive_logs\arc%s%r.%t' (this corresponds to the current archive on g:\oracle\ora10gtemp\database\)

    I have 11 files in the backup (3 to 7/29, 1 for 7/30, 3 for 8/2, 2 for the 8/7 and 8/8 2) 8/7 and 8/8 are incremental...

    I had 80 files from 2012 until today of the archive logs (10 M each...)

    I'm moving all archive logs and files backup of G: that 652 g free to F: which has 4.6 free...

    RMAN > backup backupset disk device;

    From backup 8 August 14

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: sid = 146 devtype = DISK

    entry count = 4 = 787850080 = July 5, 12 creation_time stamp backupset

    channel ORA_DISK_1: starting piece 1 to August 8, 14

    channel ORA_DISK_1: backup G:\ORACLE\ORA10GTEMP\DATABASE\C-4285664692-2012 piece

    0705-00

    room handle=F:\RMAN_BACKUPS\RMAN04NFB8R0_1_4.BUS comment = NONE

    channel ORA_DISK_1: finished piece 1 to August 8, 14

    channel ORA_DISK_1: complete set of backups, time: 00:00:03

    entry count = 5 stamp = 787850384 = July 5, 12 creation_time backupset

    channel ORA_DISK_1: starting piece 1 to August 8, 14

    channel ORA_DISK_1: backup G:\BACKUPS\RMAN05NFB94G_1_1.BUS piece

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 11:40 08/08/2014:

    17

    ORA-19505: impossible to identify the file 'G:\BACKUPS\RMAN05NFB94G_1_1.BUS '.

    ORA-27041: could not open the file

    04002 - OSD: could not open the file

    S/O-error: (OS 2) the system cannot find the file specified.

    ORA-19600: input file is backup piece (G:\BACKUPS\RMAN05NFB94G_1_1.BUS)

    ORA-19601: output file is backup piece (F:\RMAN_BACKUPS\RMAN05NFB94G_1_2.BUS)

    It seems that your element of backup G:\BACKUPS\RMAN05NFB94G_1_1.BUS gone "bath of crowd".  In other words, a person removed at the OS level... and so rman always think it is, but finds then this isn't.

Maybe you are looking for