RMAN backup using OSB too slow

Hi all,
We are exploring Oracle Secure Backup in our environment as legato networker alternative. But RMAN backup in OSB is very slow due to sbt wait event(sbtwrite2). it can backup 5GB/hour. We think this not normal behavior. we have checked network throughput between media server and client server. It can send 50 GB data by 30 min.Could you please help us to resolve the problem.
Thanks,

Hello,
What OS do you use? This is a Windows OS or UNIX ? Above all, we need more information about the Hardware and the others plans that ran in this environment.It can be also competition from other jobs.
Kind regards,
Bruno Reis

Similar Messages

  • RMAN backup uses more space than actual DB size

    Hi All,
    Yesterday, we have configured the RMAN backup for an RAC db in HP-UX. The total DB size is 82GB
    but the RMAN took around 250G space for backup and the backup failed. The oracle db is 10.2.0.1.
    $ ls -artl
    total 520626852
    drwxr-xr-x 23 root root 8192 Feb 10 15:49 ..
    drwxr-xr-x 2 root root 96 Feb 10 16:09 lost+found
    -rw-rw-rw- 1 oracle dba 290 Feb 10 20:35 backup.log
    -rw-rw---- 1 oracle dba 22768640000 Feb 10 21:30 bk_4_1_678488912
    -rw-rw---- 1 oracle dba 37469036544 Feb 10 21:40 bk_3_1_678488912
    -rw-rw---- 1 oracle dba 28807331840 Feb 10 21:52 bk_5_1_678490229
    -rw-rw---- 1 oracle dba 22659448832 Feb 10 22:01 bk_6_1_678490845
    -rw-rw---- 1 oracle dba 22775595008 Feb 10 22:14 bk_7_1_678491581
    -rw-rw---- 1 oracle dba 19507593216 Feb 10 22:15 bk_8_1_678492076
    -rw-rw---- 1 oracle dba 18644811776 Feb 10 22:29 bk_9_1_678492883
    -rw-rw---- 1 oracle dba 19040927744 Feb 10 22:31 bk_10_1_678492958
    -rw-rw---- 1 oracle dba 18791776256 Feb 10 22:44 bk_11_1_678493794
    -rw-rw---- 1 oracle dba 15491096576 Feb 10 22:45 bk_12_1_678493889
    -rw-rw---- 1 oracle dba 19860652032 Feb 10 23:00 bk_13_1_678494656
    -rw-rw---- 1 oracle dba 20742381568 Feb 10 23:01 bk_14_1_678494701
    drwxrwxrwx 3 oracle dba 1024 Feb 10 23:01 .
    Why this is happening ? Any bug or i am missing out anything. Please help.
    Regards,
    Anand.

    We are using the belwo scripts,
    rman target sys/system nocatalog msglog /backup/backup.log
    RUN {
    ALLOCATE CHANNEL ch00 TYPE DISK;
    ALLOCATE CHANNEL ch01 TYPE DISK;
    BACKUP
    INCREMENTAL LEVEL=0
    SKIP INACCESSIBLE
    TAG hot_db_bk_level0
    FILESPERSET 5
    FORMAT '/backup/bk_%s_%p_%t'
    DATABASE;
    sql 'alter system archive log current';
    RELEASE CHANNEL ch00;
    RELEASE CHANNEL ch01;
    ALLOCATE CHANNEL ch00 TYPE DISK;
    ALLOCATE CHANNEL ch01 TYPE DISK;
    BACKUP
    filesperset 20
    FORMAT '/backup/al_%s_%p_%t'
    ARCHIVELOG from time 'sysdate - 1' ;]
    #For backing up the archive of the second server.
    ALLOCATE CHANNEL ch02 TYPE DISK connect 'sys/system@qicdbr2';
    BACKUP
    filesperset 20
    FORMAT 'al2_%s_%p_%t'
    ARCHIVELOG from time sysdate - 1 ;
    RELEASE CHANNEL ch02;
    RELEASE CHANNEL ch00;
    RELEASE CHANNEL ch01;
    ALLOCATE CHANNEL ch00 TYPE DISK;
    BACKUP
    FORMAT '/backup/cntrl_%s_%p_%t'
    CURRENT CONTROLFILE;
    RELEASE CHANNEL ch00;
    RMAN> LIST BACKUPSET SUMMARY;
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    1 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    2 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    3 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    4 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    5 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    6 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    7 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    8 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    9 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    10 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    11 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    12 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    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 ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/orahome/OraRAC/dbs/snapcf_QICDB1
    .f'; # default

  • Oracle10g rman backup useing oracle9i

    I will backup my oracle10g database using rman in oracle9i database.
    But it report error in following :
    Recovery Manager: Release 10.2.0.1.0 - Production on Thu Nov 2 23:58:45 2006
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: MAIL (DBID=200451555)
    connected to recovery catalog database
    PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
    RMAN> register database;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of register command at 11/02/2006 23:59:00
    RMAN-06429: RCVCAT database is not compatible with this version of RMAN
    What can I do for backuping oracle10g in oracle9i rman successfully ?

    The recovery catalog schema version must be greater than or equal to the RMAN client version. Therefore, you should create a 10g recovery catalog in the 9i catalog database. Check the RMAN Compatibility Matrix for more information.

  • RMAN Backup using Rman Catalog

    Hi
    can we take backup of oracle9i database using oracle10g RMAN Catalog?
    Thanks
    With Regards
    OH

    I guess this is related to backward compatibility support principle. Target database's controlfile and RMAN catalog is synchronized and different version may have different structure and feature. When we need to completely restore an Oracle instance from backup, RMAN catalog must be able to support target database, and it may not be possible if RMAN catalog version is lower than target database. I hope I get the message across.
    Pls anybody correct me if I am wrong

  • Calling VB Executable using HOST too Slow....

    Hello Friends,
    I have one form containg one program unit, Program unit has one cursor,which contains Employee Id and Email Id, Based on Employee ID Report is generated in HTML Format.Next I am Calling VB Executable using HOST which Sends generated report through mail based on EmailId. I am passing Report File and EmailId using Command line arguments.
    But,It takes too much time to return back to Form from VB application ? It quickly exits VB applications but then it takes too much time to return back to Oracle Forms ?
    What can be the reason ?
    Adi

    exactly, I think we were too impatient.
    It seemed working well after deleting half of snapshots, but just next day it occurred again.
    of course the system is maintaining snapshots just half of the original, but it became slow because unknown reason.
    we've tested something like following because we doubt that zpool was related to the too low performance.
    case 1 : 1 zpool, 1*500MB mkfile, 50*100MB mkfile at any time
    case 2 : 20 zpool, 1*500MB mkfile to ONE zpool, 2~3*100MB mkfile PER zpool at any time
    case 3 : 1 zpool, just 1*500MB mkfile
    in case 1 and 2, 'at any time' means that 100MB mkfile processes were maintained to restart when finished again and again.
    we estimated the time to write 500MB for each case.
    case 1 result : about 6 minutes
    case 2 result : about 16 minutes
    case 3 result : about 4 seconds
    in the case 1, the test was harder than our real-world situation, but it took only 6 minutes.
    our system log told us that writing about 1GB took more than 50 minutes!!!
    do anyone know why the tests above result like this?
    and our zfs performance is still problem.
    please reply anything about our situation.
    we'll of course test the ARC size. thank about this.
    thank you.

  • RMAN backup slow

    Hi,
    I have a Production Database (10204) running on HP Unix (B.11.11).
    Daily morning 6AM, a full RMAN backup runs. The db size is only around 225GB. But it takes 4.5 hours to complete.
    The syntax which I use is given below.
    RMAN> run {
         allocate channel ch1 type "sbt_tape";
         allocate channel ch2 type "sbt_tape";
         allocate channel ch3 type "sbt_tape";
    send
    'NB_ORA_CLIENT=jjcprd04-back.backup.ncsus.jnj.com,NB_ORA_POLICY=JJCPRD04-RMAN';
         backup
         format 'bk_%s_%p_%t'
         (database include current controlfile);
         sql 'alter system archive log current';
         backup
         format 'arch_%d_%s_%p_%t'
         (archivelog all delete input );
    Is there a way to increase the speed of this backup? Currently the backup is way too slow as it takes 4.5 hours to copy 225GB of data!
    Thanks!

    I'll start by stating that backups directly to tape are generally quite slow.
    I'd still recommend moving to disk backups though... and just archiving it to a tape...Hi Jony,
    You can of course backup to disk. Thats a common solution. But you have to deal with space more than everything. In addition to that backing up to disk does not free you from moving/copying your data - depending on your backup strategy - to a long-term storage.
    So you have two different and not conjunct backup operations: the rman backup itself and the job which backups the rman area to another media.
    In recovery cases you might end up with RMAN requesting older backupsets which are not on disk anymore. This will most probably lead to recovery failures and manual intervention which is not desirable in recovery scenarios.
    Another point is the control of the data flow. Backing up via a MML (i.e. "to tape") does not necessarily mean "to tape". Instead it means "to the backup software" which is responsible for managing the backup data. Common scenarios involve backing up the full backups via SAN directly to tape and backing up the archivelogs or incremental backups over LAN which will be stored by the backup software on a hard disk and later copied and/or moved on to tape. The data flow (to SAN / to disk / whereever) is solely controlled by the backup software.
    The advantage here is one continuous backup and restore job. The backup software deals with "where is my saveset located" and requests automatically the needed tapes or disks in recovery scenarios. This makes recoveries far more flexible and comfortable.
    Regarding the throughput i have set up a rather large OLTP database ( 12 TB currently) which is backed up with EMC Networker. Full backups are written via SAN directly to tape. The average speed with four LTO-3 drives is approx. 550 MB/s (the tape drives compress the data in hardware; the database itself is text-only and seems rather good compressable). I guess thats not too bad.
    you can also compress the BACKUPSETS (this generates a little more CPU but less network IO)He said he is on HP-UX. These kind of CPUs tend to be not that fast. Using compression is an option worth testing but there is another point to test when doing compressed backups: The RESTORE TIME.
    Ronny Egner
    My Blog: http://blog.ronnyegner-consulting.de

  • RMAN backup fails using OEM with no output error

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

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

  • Rman backup in noarchivelog mode

    hi all,
    My database(ORCL) is in noarchivelog mode
    I am taking RMAN backup using recovery catalog(backupdb)
    target database(ORCL) is in mount mode
    I am getting following errors:
    RMAN> backup database;
    Starting backup at 01-AUG-08
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10039: error encountered while polling for RPC completion on channel defaul
    t
    RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 a
    nd serial=:2
    RMAN-10002: ORACLE error: ORA-12571: TNS:packet writer failure
    RMAN-03002: failure of backup command at 08/01/2008 15:52:03
    ORA-03114: not connected to ORACLE
    I again tried and then i got these errors:
    C:\Documents and Settings\Administrator>set oracle_sid=backupdb
    C:\Documents and Settings\Administrator>rman catalog rman1/rman
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to recovery catalog database
    RMAN> connect target sys/sys@orcl
    connected to target database (not started)
    RMAN> backup database;
    Starting backup at 01-AUG-08
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 08/01/2008 16:12:40
    RMAN-06403: could not obtain a fully authorized session
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    RMAN>
    please explain
    Message was edited by:
    ArchanaTewatia

    Hi,
    Try to study the errors Correctly ..
    RMAN> connect target sys/aqtechmvardi@orcl
    connected to target database (not started)
    RMAN> backup database;
    Starting backup at 01-AUG-08
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 08/01/2008 16:12:40
    RMAN-06403: could not obtain a fully authorized session
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    Try to mount the Target DataBase it will work.
    Thanks
    Pavan Kumar N

  • Execute RMAN Backup in debugmode

    Hi
    We are running RMAN Backup using perl script.
    We need to run the RMAN backp in debug mode. How we can do this by passing parameter in the perl script itself.
    PS. As we dont need to change the perl script or editing the RMAN script.
    Thanks

    I don't know how your script is being executed, but you could pass in the debug parameter with the command you use to launch RMAN:
    rman target / debug trace='c:\bk_trace.trc'

  • RMAN backup time increased

    Hi All,
    I need details about some diagnostic test regarding RMAN backup on my instance.
    The following are the current configuration of details:
    SQL> select release_name from fnd_product_groups;
    RELEASE_NAME
    11.5.8
    SQL> select * from v$version;
    BANNER
    Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
    PL/SQL Release 9.2.0.8.0 - Production
    CORE 9.2.0.8.0 Production
    TNS for Solaris: Version 9.2.0.8.0 - Production
    NLSRTL Version 9.2.0.8.0 - Production
    ===============================================
    Database Size
    1.5 TB
    Earlier the RMAN backup used to take 20 -23 hours, now for the last 2 months, it has started taking 40 hours.
    We want to identify the reason behind the increase in time.
    Please let us know methods that we can use to diagnose the root cause.
    Thanks
    Peeks

    Hi Talip,
    Thanks for you suggestions.
    I tried the three queries suggested by you, please find below the output:
    SQL>  select set_stamp from v$backup_async_io where to_date(open_time,'dd.mon.rr')='05.mar.12';
    SET_STAMP
    777154038
    777154038
    777154038
    777154038
    777154038
    777154038
    777154038
    777154038
    777154038
    777154038
    777167658
    SET_STAMP
    777167658
    777167658
    777167673
    777167673
    777167673
    16 rows selected.The we checked the effective_bytes_per_second "mb/sec" column for the 777154038 and 777167658 Set_stamps.
    SQL> select device_type "Device",
    type,
    open_time,close_time,
    elapsed_time/100 "Ela",
    effective_bytes_per_second/1024/1024 "mb/sec",
    filename
    from v$backup_async_io
    where set_stamp = &a
    order by close_time desc;  2    3    4    5    6    7    8    9
    Enter value for a: 777154038
    old   8: where set_stamp = &a
    new   8: where set_stamp = 777154038
    Device          TYPE      OPEN_TIME       CLOSE_TIME             Ela     mb/sec FILENAME
    SBT_TAPE        OUTPUT    05-MAR-12       05-MAR-12            13498 3.03509712 bk_87606_1_777154038
    SBT_TAPE        OUTPUT    05-MAR-12       05-MAR-12            13475 3.03425884 bk_87605_1_777154038
    DISK            AGGREGATE 05-MAR-12       05-MAR-12            13476   3.041852
    DISK            INPUT     05-MAR-12       05-MAR-12             2832 2.90395451 /u1141/oradata/PRD1/rbs03.dbf
    DISK            AGGREGATE 05-MAR-12       05-MAR-12            13446  3.0486393
    DISK            INPUT     05-MAR-12       05-MAR-12             2829 2.90703392 /u1141/oradata/PRD1/rbs01.dbf
    DISK            INPUT     05-MAR-12       05-MAR-12             5332 3.07276821 /u1140/oradata/PRD1/ard01.dbf
    DISK            INPUT     05-MAR-12       05-MAR-12             5314 3.08317661 /u1140/oradata/PRD1/applsysx01.dbf
    DISK            INPUT     05-MAR-12       05-MAR-12             5309 3.08608055 /u1140/oradata/PRD1/gld01.dbf
    DISK            INPUT     05-MAR-12       05-MAR-12             5300 3.09132099 /u1140/oradata/PRD1/applsysd01.dbf
    10 rows selected.
    SQL> /
    Enter value for a: 777167658
    old   8: where set_stamp = &a
    new   8: where set_stamp = 777167658
    Device          TYPE      OPEN_TIME       CLOSE_TIME             Ela     mb/sec FILENAME
    SBT_TAPE        OUTPUT    05-MAR-12       06-MAR-12            13323 3.07180786 bk_87607_1_777167658
    DISK            AGGREGATE 05-MAR-12       06-MAR-12            13289 3.08224869
    DISK            INPUT     06-MAR-12       06-MAR-12             2652 3.08898926 /u1141/oradata/PRD1/rbs02.dbf
    DISK            INPUT     06-MAR-12       06-MAR-12             5330  3.0739212 /u1140/oradata/PRD1/invd01.dbf
    DISK            INPUT     05-MAR-12       06-MAR-12             5305 3.08840752 /u1140/oradata/PRD1/arx01.dbf
    SQL>The above output looks fine, but when i checked the long wait uery, it showed high percentage usage for OUTPUT streams. The below is the output:
    TYPE        IO_COUNT      READY SHORT_WAITS LONG_WAITS    LIO_PCT FILENAME
    INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/applsysd01.dbf
    INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/applsysx01.dbf
    INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/ard01.dbf
    INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/gld01.dbf
    INPUT           8225       7711           0        514 6.24924012 /u1141/oradata/PRD1/rbs01.dbf
    INPUT           8225       7711           0        514 6.24924012 /u1141/oradata/PRD1/rbs03.dbf
    OUTPUT         10222       7662           0       2560 25.0440227 bk_87605_1_777154038
    OUTPUT         10242       7678           0       2564  25.034173 bk_87606_1_777154038
    AGGREGATE      40995      38433           0       2562 6.24954263
    AGGREGATE      40995      38433           0       2562 6.24954263
    10 rows selected.
    TYPE        IO_COUNT      READY SHORT_WAITS LONG_WAITS    LIO_PCT FILENAME
    INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/arx01.dbf
    INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/invd01.dbf
    INPUT           8193       7681           0        512 6.24923715 /u1141/oradata/PRD1/rbs02.dbf
    OUTPUT         10232       7669           0       2563 25.0488663 bk_87607_1_777167658
    AGGREGATE      40963      38403           0       2560 6.24954227So, as per the output please suggest possible solutions to decrease the backup time, if not possible any other option.
    Is there any problem with the tape device or is it an oracle issue.
    Thanks
    Peeks

  • Rman Backup to tape in sun solaris 8.0

    Hi all,
    We have a tape drvie that is being cnfigured on /dev/rmt/0I want to know how to take rman backup using tape as we having less disk space on the sun box.
    please suggest me......
    below script is correct or not.....
    RMAN> run {
    2> allocate channel c1 type 'sbt_tape'
    3> parms="ENV=(BACKUP_DIR=/dev/rmt/0m)";
    4> backup tablespace system;
    5> }

    Hemant.....
    According to the link which you have provided explains that
    there must be a file libobk.so, ext might differ, but in my sun box there is no such file and
    $ ls libo*
    libocci.so        libocijdbcst9.a   libolapapi9.so    libordim9.so
    libocci.so.9.0    libocr.so         liboraawt.so      libordimt9.a
    libocci9.a        libocrbackend.so  liboraioser.so    libordsdo9.a
    libocijdbc9.so    libodm9.so        liboraolap9.a     libowm2.so
    libocijdbc9_g.so  libodmd9.so       libordim9.a
    $another thing is that
    what is NSR_GROUP,NSR_SERVER >
    $ echo $NSR_SERVER
    $ echo $NSR_GROUP
    it is not dispalying anything in the oracle env

  • Rman backup fails

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

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

  • How can I make Time Machine use the ethernet cable to Time Capsule instead of the wireless connection? Wireless is too slow; has been taking 40 hours to create an initial 142 GB backup.

    How can I make Time Machine use the ethernet cable to Time Capsule instead of the wireless connection? Wireless is too slow; has been taking 40 hours to create an initial 142 GB backup.

    Plug in ethernet .. in the computer.. turn off wireless.

  • Rman backup is too slow

    Hi
    I have oracle database (11gR1) 64 bit installed on Windows 2003 R2 64 bit server. MY DB size is almost 152 GB and its running in archive log mode. When i run RMAN online backup , Its taking too much time almost it has taken 22 Hours and still its running , I am not sure why it is consuming this much time ..
    I am using below RMAN script ...
    run {
    allocate channel ch1 type disk;
    backup FILESPERSET 32
    format 'F:\RMAN_BACKUP\%d_t%t_s%s_FULL' tag Full_DATABASE_07_july_13
    (database)
    CURRENT CONTROLFILE SPFILE;
    SQL "alter system archive log current";
    backup FILESPERSET 200
    format 'F:\RMAN_BACKUP\ARC_%d_%s_%t'
    (archivelog all);
    release channel ch1;
    Kindly help me and whats wrong in this please tell me . Also tell me if any other information needed ..
    Thanks & Regards,
    Vikash Jain

    hi, Till now RMAN backup not completed for single time so i cant tell how long it takes.
    I tried with parallelism 2 also but it is also not working.
    CONFIGURE DEFAULT DEVICE TYPE TO disk;   
    # backup goes to disk
    CONFIGURE DEVICE TYPE disk PARALLELISM 2;
    # three channels used in parallel
    CONFIGURE CONTROLFILE AUTOBACKUP ON;     
    #controlfile and spfile take backup automatically
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'F:\RMAN_BACKUP\%d_t%t_s%s_FULL' MAXPIECESIZE 10G; # 1st channel 
    CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT 'F:\RMAN_BACKUP\%d_t%t_s%s_FULL' MAXPIECESIZE 10G; # 2nd channel
    run {
          allocate channel chnnel1 type disk;
        allocate channel chnnel2 type disk;
    backup database tag Full_DB_090713_With_CH_02;
    SQL "alter system archive log current";
        backup archivelog all format 'F:\RMAN_BACKUP\ARC_%d_%s_%t';
    release channel chnnel1;
    release channel chnnel2;
    this also having below error ..
    RMAN-03009: failure of backup command on chnnel1 channel at 07/12/2013 10:38:31
    ORA-19502: write error on file "D:\APP\ADMINISTRATOR\PRODUCT\11.1.0\DB_1\DATABASE\86OEH1S5_1_1", block number 1476225 (block size=8192)
    ORA-27072: File I/O error
    OSD-04008: WriteFile() failure, unable to write to file
    O/S-Error: (OS 112) There is not enough space on the disk.
    channel chnnel1 disabled, job failed on it will be run on another channel
    released channel: chnnel1
    released channel: chnnel2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on chnnel2 channel at 07/12/2013 10:42:08
    ORA-19502: write error on file "D:\APP\ADMINISTRATOR\PRODUCT\11.1.0\DB_1\DATABASE\87OEHG94_1_1", block number 1476097 (block size=8192)
    ORA-27072: File I/O error
    OSD-04008: WriteFile() failure, unable to write to file
    O/S-Error: (OS 112) There is not enough space on the disk.
    I checked there is enough space on F drive but still its showing the above error , Also i cant see backup pieces in "F:\RMAN_BACKUP\" location ... I am sure whats wrong with the above script ...
    Thanks & Regards,
    Vikash Jain

  • RMAN backups running slow with Catalog , Running fine using control file.

    I am facing a weird scenario
    RMAN backups are running fine with Control file but are failing using Catalog
    There are other databases configured on the same catalog and they are running fine leaves us to suspect this is issue with Database.
    Can you please suggest what need to be checked in such scenario
    DB: 11.2.0.2
    OS: Aix 6.1
    Catalog : 11.2.0.2

    Hi,
    Basically its not only with backups, simple list incarnation also taking a lot of timeDo sql tracing on your catalog session and target db session while running the 'list incarnation' command for your problem dbs and a normal dbs.
    Regards,
    Tycho

Maybe you are looking for