Rman backup to disk 2 Minutes; Backup to tape hours

Solaris 10
Oracle 10gR2
MML Netbackup 6.0
I have the following scenario
Rman backup to disk < 2 Minutes; Backup to tape takes hours
and occassionaly fails with a media manager layer error.
Any suggestions to speed up the backup to tape?

A backup of under 2 minutes . . . not very big.
A backup to tape of hours?
I don't think that is your problem . . . I think you need to check and see if your tapes are valid. If Oracle fails at the end of a backup to tape, it sounds like the tapes are 'bad'.
If the tapes are good: Then look at why it is so slow - I would 'guess' network backup.
Can you backup to disk and then send them to tape?
Solaris 10
Oracle 10gR2
MML Netbackup 6.0
I have the following scenario
Rman backup to disk < 2 Minutes; Backup to tape takes
hours
and occassionaly fails with a media manager layer
error.
Any suggestions to speed up the backup to tape?

Similar Messages

RMAN backup to disk vs tape

AIX R 2
Oracle: 10.2.0.4
I have been testing rman backup strategies on a db in noarchivelog (development) using the following command:
(*) note: if db is in noarchivelog then you must do a cold backup - have the db mounted but not opened.
rman> backup database format '/a010/d01/bck/%U'
I have found that rman will backup to disk about 2GB per minute. Now I want to test this to tape to compare metrics.
Question: What configurations does RMAN need to write directly to tape?
What are the backup steps to write to tape? Do I need to specify both the tape channel and also where the format output gets written?
Thanks all.

OK
You need to install the Oracle driver for Tivoli (optionally sold with Tivoli) and install that in your Oracle software tree.
Then you can configure your channels to write to tape (this is documented).
For the rest there is no difference, although there are no directory names.
Sybrand Bakker
Senior Oracle DBA

How Backup on DISK for Standby when Device "Tape" is alredy configured

hello Dba's
For 3 Weeks I've this issue and I start don't get
usualy this database ws backup on Disk but last month we decided to setup the DLL fro Netbackup on TAPE
and I've configured the RMAN for tape and it works fine.
Now I need to Backup on DISK to create my Standby Database, because the Secondary Server doesn't have the DLL/License for TAPE
So i decided to proceed as a backup on Disk but when I try it alyway gpo into TAPE !!!!!
Any help is welcome.
txs
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/export/cf_%F_$ORACLE_SID';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup/export/%d_%D%M%T_full_%U';
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%D%M%T_full_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/9.2/dbs/snapcf_SIEB.scf';
RMAN> allocate channel for maintenance device type 'DISK'
2> ;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ORA_MAINT_DISK_1 channel at 06/29/2010 15:14:44
ORA-19554: error allocating device, device type: DISK, device name:
ORA-27001: unsupported device type
Additional information: 1
RMAN> allocate channel for maintenance device type DISK;
allocated channel: ORA_MAINT_DISK_2
channel ORA_MAINT_DISK_2: sid=236 devtype=DISK
RMAN> run
2> 3> sql "Alter System Switch logfile";
4> sql "Alter System Archive Log Current";
5> Backup database plus archivelog format '/backup/%d_%D%M%T_full_%U';
6> sql "Alter System Switch logfile";
7> Backup current controlfile for standby format '/backup/%U_$ORACLE_SID';
8> sql "Alter System Switch logfile";
9> Backup filesperset 10 ArchiveLog all;
10> }
sql statement: Alter System Switch logfile
sql statement: Alter System Archive Log Current
Starting backup at 29-JUN-10
current log archived
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=118 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
channel ORA_SBT_TAPE_1: starting archive log backupset
channel ORA_SBT_TAPE_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=2879 recid=688 stamp=722953267
input archive log thread=1 sequence=2880 recid=689 stamp=722960690
input archive log thread=1 sequence=2881 recid=691 stamp=722963294
input archive log thread=1 sequence=2882 recid=690 stamp=722963293
input archive log thread=1 sequence=2883 recid=692 stamp=722963296
input archive log thread=1 sequence=2884 recid=693 stamp=722963703
input archive log thread=1 sequence=2885 recid=694 stamp=722963703
input archive log thread=1 sequence=2886 recid=695 stamp=722963705
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10
channel ORA_SBT_TAPE_1: finished piece 1 at 29-JUN-10
piece handle=/backup/SIEB_290620100629_full_qelhf37t_1_1 comment=API Version 2.0,MMS Version 5.0.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:56
Finished backup at 29-JUN-10
Starting backup at 29-JUN-10
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
input datafile fno=00020 name=/u01/oradata/SIEB/data/tbs_siebel_data_01.dbf
input datafile fno=00002 name=/u02/oradata/SIEB/system/undotbs02_02.dbf
input datafile fno=00001 name=/u02/oradata/SIEB/system/system01.dbf
input datafile fno=00011 name=/u01/oradata/SIEB/data/tbs_siebview_01.dbf
input datafile fno=00025 name=/u01/oradata/SIEB/data/undotbs02_01.dbf
input datafile fno=00018 name=/u01/oradata/SIEB/data/tbs_siebel_empty.dbf
input datafile fno=00022 name=/u01/oradata/SIEB/data/users_01.dbf
input datafile fno=00019 name=/u01/oradata/SIEB/data/invoice_app_data01.dbf
input datafile fno=00015 name=/u01/oradata/SIEB/data/tbs_dwhview_01.dbf
input datafile fno=00010 name=/u01/oradata/SIEB/data/dm_casebase_docbase_01.dbf
input datafile fno=00014 name=/u01/oradata/SIEB/data/tbs_siebdw_data_01.dbf
input datafile fno=00016 name=/u01/oradata/SIEB/data/tbs_igd_01.dbf
input datafile fno=00017 name=/u01/oradata/SIEB/data/igd_eim_01.dbf
input datafile fno=00013 name=/u01/oradata/SIEB/data/dm_imdoc_docbase_01.dbf
input datafile fno=00023 name=/u01/oradata/SIEB/data/perfstat_01.dbf
input datafile fno=00012 name=/u01/oradata/SIEB/data/dm_imdoc_audit_01.dbf
input datafile fno=00021 name=/u01/oradata/SIEB/data/tools_01.dbf
input datafile fno=00009 name=/u01/oradata/SIEB/data/dm_casebase_audit_01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10
channel ORA_SBT_TAPE_1: finished piece 1 at 29-JUN-10
piece handle=SIEB_290620100629_full_qflhf39l_1_1 comment=API Version 2.0,MMS Version 5.0.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:12:36
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
input datafile fno=00006 name=/u03/oradata/SIEB/index/tbs_siebbig_index01.dbf
input datafile fno=00024 name=/u03/oradata/SIEB/index/tbs_siebel_index_01.dbf
input datafile fno=00004 name=/u03/oradata/SIEB/index/tbs_siebdw_index_01.dbf
input datafile fno=00005 name=/u03/oradata/SIEB/index/tbs_igd_index01.dbf
input datafile fno=00007 name=/u03/oradata/SIEB/index/dm_casebase_index_01.dbf
input datafile fno=00008 name=/u03/oradata/SIEB/index/dm_imdoc_index_01.dbf
input datafile fno=00003 name=/u03/oradata/SIEB/index/tbs_invoice_index01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10
channel ORA_SBT_TAPE_1: finished piece 1 at 29-JUN-10
piece handle=SIEB_290620100629_full_qglhf419_1_1 comment=API Version 2.0,MMS Version 5.0.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:07:15
Finished backup at 29-JUN-10
Starting backup at 29-JUN-10
current log archived
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting archive log backupset
channel ORA_SBT_TAPE_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=2887 recid=696 stamp=722964956
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10
channel ORA_SBT_TAPE_1: finished piece 1 at 29-JUN-10
piece handle=/backup/SIEB_290620100629_full_qhlhf4es_1_1 comment=API Version 2.0,MMS Version 5.0.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:57
Finished backup at 29-JUN-10
Starting Control File and SPFILE Autobackup at 29-JUN-10
piece handle=c-1097630847-20100629-04 comment=API Version 2.0,MMS Version 5.0.0.0
Finished Control File and SPFILE Autobackup at 29-JUN-10
sql statement: Alter System Switch logfile
Starting backup at 29-JUN-10
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
including standby controlfile in backupset
channel ORA_SBT_TAPE_1: starting piece 1 at 29-JUN-10

Thxs for Reply
But When I type Allocate Channel as you suggested I get Error
ORA-19502: write error on file "qslhf5sr_1_1", blockno 1 (blocksize=8192)
RMAN> run
2> {
3> allocate channel c1 type disk;
4> sql "Alter System Switch logfile";
5> sql "Alter System Archive Log Current";
6> Backup database plus archivelog format '/backup/%d_%D%M%T_full_%U';
7> sql "Alter System Switch logfile";
8> Backup current controlfile for standby format '/backup/%U_$ORACLE_SID';
9> sql "Alter System Switch logfile";
10> Backup filesperset 10 ArchiveLog all;
11> }
starting full resync of recovery catalog
full resync complete
released channel: ORA_SBT_TAPE_1
allocated channel: c1
channel c1: sid=12 devtype=DISK
sql statement: Alter System Switch logfile
sql statement: Alter System Archive Log Current
Starting backup at 29-JUN-10
current log archived
skipping archive log file /u03/archive/SIEB/1_2879.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2880.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2881.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2882.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2883.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2884.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2885.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2886.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2887.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2888.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2889.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2890.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2891.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2892.dbf; already backed up 1 time(s)
skipping archive log file /u03/archive/SIEB/1_2893.dbf; already backed up 1 time(s)
channel c1: starting piece 1 at 29-JUN-10
channel c1: finished piece 1 at 29-JUN-10
piece handle=/backup/SIEB_290620100629_full_qrlhf5on_1_1 comment=NONE
channel c1: backup set complete, elapsed time: 00:02:12
Finished backup at 29-JUN-10
Starting backup at 29-JUN-10
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00020 name=/u01/oradata/SIEB/data/tbs_siebel_data_01.dbf
input datafile fno=00002 name=/u02/oradata/SIEB/system/undotbs02_02.dbf
input datafile fno=00001 name=/u02/oradata/SIEB/system/system01.dbf
input datafile fno=00011 name=/u01/oradata/SIEB/data/tbs_siebview_01.dbf
input datafile fno=00025 name=/u01/oradata/SIEB/data/undotbs02_01.dbf
input datafile fno=00018 name=/u01/oradata/SIEB/data/tbs_siebel_empty.dbf
input datafile fno=00022 name=/u01/oradata/SIEB/data/users_01.dbf
input datafile fno=00019 name=/u01/oradata/SIEB/data/invoice_app_data01.dbf
input datafile fno=00015 name=/u01/oradata/SIEB/data/tbs_dwhview_01.dbf
input datafile fno=00010 name=/u01/oradata/SIEB/data/dm_casebase_docbase_01.dbf
input datafile fno=00014 name=/u01/oradata/SIEB/data/tbs_siebdw_data_01.dbf
input datafile fno=00016 name=/u01/oradata/SIEB/data/tbs_igd_01.dbf
input datafile fno=00017 name=/u01/oradata/SIEB/data/igd_eim_01.dbf
input datafile fno=00013 name=/u01/oradata/SIEB/data/dm_imdoc_docbase_01.dbf
input datafile fno=00023 name=/u01/oradata/SIEB/data/perfstat_01.dbf
input datafile fno=00012 name=/u01/oradata/SIEB/data/dm_imdoc_audit_01.dbf
input datafile fno=00021 name=/u01/oradata/SIEB/data/tools_01.dbf
input datafile fno=00009 name=/u01/oradata/SIEB/data/dm_casebase_audit_01.dbf
channel c1: starting piece 1 at 29-JUN-10
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 06/29/2010 16:00:34
ORA-19502: write error on file "qslhf5sr_1_1", blockno 1 (blocksize=8192)
ORA-27072: skgfdisp: I/O error
Linux-x86_64 Error: 2: No such file or directory
RMAN>

Resume a failed RMAN incremental 0 cold backup to disk

Linux x86-64 10.2.0.4
I'm taking an incremental 0 backup to disk of a database that's mounted. I'm backing up the database to an NFS volume. I lost the NFS mount. Is there any way to resume a backup where it left off at? It complains "ORA-27038: created file already exists" if I restart it. RMAN can easily resume a restore. I don't have the time to redo the whole thing all again. The database is over 10TB. The target isn't up. Is there anything I could do?

Hemant K Chitale wrote:
I lost the NFS mount point, as in it was no longer mounted to the host. If it was any other scenario, I wouldn't be attempting to resume it.and
I still have the previously restored files. I wouldn't be recieving "ORA-27038: created file already exists" otherwise. I am still confused.
I guess that you are talking of a BACKUP not a RESTORE (unlike the sentence that says "previously restored files").I meant backup. I'm also doing a restore for another purpose, so it was on my mind. It was some sort of phsychological slip.
>
"The NFS mount point is no longer mounted.". So what happened to the files that did get written to the NFS mount point ? Did you copy them to tape before the NFS mount point got unmounted ? Or is the NFS server still up and running, with the partial backup intact on it, except that the remote mount is disabled ?
We had a network problem and we lost the NFS mount. Most of the files are there, just not the whole database. I didn't copy them to tape. The whole purpose was to use the backup as a clone by manually recreating the controlfle, and pulling it into another ASM instance on another cluster. We first need to pull it out of the current ASM instance. The NFS volume was remounted, but my concern is being able to resume the backup from where it left off at.
How about running
BACKUP ... NOT BACKED UP SINCE TIME 'date_string'From the documentation : "This option is a convenient way to back up files that were not backed up during a previous failed backup. For example, you back up the database, but the instance fails halfway through. You can restart the backup with the NOT BACKED UP SINCE TIME clause and avoid backing up those files that you already backed up."I'll have to give that a try. It sounds promising.
>
Hemant K Chitale
http://hemantoracledba.blogspot.com

Backup to Disk and Tape

Looking to convert our RMAN Tape backups to Disk using incr merge.
RUN {
RECOVER COPY OF DATABASE WITH TAG 'incr_update';
BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'incr_update'
DATABASE;
Then we want to backup all backupsets to tape for archive. So questions are
1) How do you tell RMAN to only backup backupset that have not been backup up to tape already?
2) Once a week, we would want to backup the full image copy "TAG 'incr_update'" to tape as well.
Thanks...

Thanks for the info... As a follow up question... I see some samples for IMB out there like so:
run {
recover copy of database with tag 'incremental_merge_backup';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'incremental_merge_backup' database;
What is the COPIES=1 for? Can't seem to find any docs on how it affect a IMB.
Thanks..

RMan Backup to Disk Options

Hello,
In Oracle 8.17 on Sun using RMan with a FULL DATABASE backup to Disk can someone please explain:
1. How to specify a tablespace(s) to NOT backup?
2. How to compress the RMan file during the backup (I am low on diskspace).
3. How to break the backup into two pieces and specify a different location for both?
I am not sure if the above are possible. Thanks for you help.
Thanks very much for your advice,
Michael42

Re your 2nd question :-
I've looked into RMAN and on the fly compression ( unix/linux).
It looks like it can't be done well not easily, ( check AskTom or dbForumns if you like).
Several others have tried and RMAN defeats you each time, the problem is that RMAN can't be made to write to STDOUT or STDERR or STD<anything> and thus any "on the fly" compression tools ie:gzip|bzip2| compress just doesn't get a chance at it.
If you are prepared to do some heavy scripting you can use a named pipe into a fixed file name and apply compression through the pipe, but it's a hell of a lot of work and there's a lot that can go wrong.
Re: Your 3rd question :-
Not sure that this will help you 100%, but it may give you an idea or 2.
I splice the DB backup like so; database on one volume and archivelogs on another as follows ...
run {
allocate channel ch1 type disk format '/backupdir1/b_%u_%s_%p.db';
allocate channel ch2 type disk format '/backupdir2/b_%u_%s_%p.arch';
sql 'alter system switch logfile';
set limit channel ch1 kbytes 1024000;
backup (database include current controlfile channel ch1);
set limit channel ch2 kbytes 1024000;
backup (archivelog all delete input channel ch2);
I also limit the size of the pieces.
Hope you get your problems sorted.

RMAN HOT BACKUP ON DISK

Hi All,
I want to take online full hot backup on disk through RMAN.
Is it possible can any one provide me a sample script.
Regards,
Umair

hi
run
crosscheck backup;
delete noprompt obsolete;
allocate channel ch1 type disk;
allocate channel ch2 type disk;
backup
database tag='full_database_backup_and_ctl' include current controlfile fo
rmat '/oracle/backup/rman_bk/fulldb_%u%s%p';
sql "alter system switch logfile";
backup
archivelog all delete input format '/oracle/backup/rman_bk/arch_%u%s%p';
backup current controlfile format '/oracle/backup/rman_bk/ctl_%u%s%p';
Release channel ch1;
Release channel ch2;
Thanks
Kuljeet Pal Singh

RMAN Backup is failling with "RMAN exited with return code '1' " via tape.

Hi Everyone,
Backups are getting failed continously with below error.can you plese suggest me what is problem exactly
L1_OracleL1_Daily completed
Failed: ***-rac-a16-001-vip.*****.dom*
--- Unsuccessful Save Sets ---
** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup savegrp: suppressed 43 lines of output.*
** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup*
** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup Recovery Manager complete.*
** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup The backup process failed:*
** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup RMAN exited with return code '1'.*
** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup Exiting with error:*
** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup RMAN exited with return code '1'.*
****-rac-a16-001-vip.uidl1.dom: RMAN exited with return code '1'.*
** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup*
** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup nsrnmostart returned status of 255*
** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup /usr/sbin/nsrnmobkp exiting.*
Thanks,
Prasanth

Hi Hemanth/imran,
storage team is shown below error for failure of backup in their log.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12502: TNS:listener received no CONNECT_DATA from client
Recovery Manager complete.
The backup process failed:
RMAN exited with return code '1'.
Exiting with error:
RMAN exited with return code '1'.
uidl1-rac-a16-001-vip.uidl1.dom: RMAN exited with return code '1'.
Any changes we need to do
Thanks,
Prasanth

Backup to Disk Performance

Hello Everyone,
We are currently using Backup Exec for Windows 11D to perform an online backup of our 4.6C system to tape. Since we are moving towards a 24x7 operation, we purchased a new server and storage array with hopes of achieving better transfer rates backing up to disk rather than tape.
Our technical details are as follows:
SAP R/3 4.6C server:
HP380
Windows 2003 Enterprise SP2 32-bit
Oracle 10.2.0.2
Db 320 gb
Backup Exec Server:
HP380 G5 64-bit
Backup Exec for Windows 11d with R/3 agent 64-bit
Latest BE build and hotfixes applied
Windows 2003 Enterprise SP2 64-bit
Target drive for backup files:
HP MSA60 Storageworks array
12- 750gb SATA drives in a raid 6 configuration
Our tests have been frustrating and disappointing. To our super dlt tape drive we are able to backup our 330 gb system at approximately 2,500 mb/minute or about 150 gb an hour. To disk, we are getting anywhere from 250 mb/minute to 1,350 mb/minute...half speed at best or much, much worse What seems to happen is that the disk backup will start running at near tape speed. But the longer the backup goes, the slower the backup becomes.
I have tried pre-allocating the .bkf files ahead of time. To pre- create a 100 gb .bkf it takes about 2 hours while the backup idles until the file creation is complete. While not an ideal runtime, I can live with it if the backup would run faster than tape once the file is created. But always the "same slowdown as it goes" seems to occur. When I don't pre-allocate the files and allow the file to grow as the backup runs, the backup will inevitibly hang or crawl at less than a couple of hundred mb/minute.
I'm sure that disk fragmentation is adversely affecting us. But even after we defrag the drives the same thing will occur.
We have a ticket open with Symantec but so far they have not been of much help.
Is anybody using Backup Exec for Windows to backup their SAP on Oracle system to disk? And what db size and backup speed are you achieving? Are there certain settings you find that will improve the backup speed? Any feedback would be greatly appreciated.
Thank you in advance,
Rich

Hi!
I see at least two possible reasons:
1. Is a virus scanner running on your Backup Server?
2. Has the network interface from R/3 to the disks enough bandwidth?
Hope this helps.
Regards,
Volker

Step by Step RMAN configuration for full hot backup daily

Dear experts,
i am new to oracle RMAN , i have gone through couple of RMAN guides for configuration ,
i have oracle e-business suite (R12.1.1) and database is ( 11.1.0.7) on red hat enterprise linux 5.3 . All of this is 64 bit.
i have a database about 175 gb which is as usual growing day by day as data entry is taking place.
Untill now we have a cold backup strategy in the midnight 3 am a script down the database and make abc.tar.gz file of 25 gb approx. . This process takes about 100 minutes. But now due to new sales system we want our database up 24/7 .
So we want to configure RMAN hot backup.
I want to take backup on disk.
daily full hot backup.
backupsets
currently database is in no-archivelog
plz help me to proceed with this .
Edited by: user13376823 on Feb 10, 2011 12:17 PM

user13376823 wrote:
Dear all,
i am using this script for my full hot backup ,
run
allocate channel c1 device type disk format '/opt/R12Backups/rman/%U';
allocate channel c2 device type disk format '/opt/R12Backups/rman/%U';
crosscheck backup;
BACKUP DATABASE FORMAT '/opt/R12Backups/rman/proddb_%u_%p_%c';
sql 'alter system switch logfile';
BACKUP ARCHIVELOG ALL DELETE INPUT FORMAT '/opt/R12Backups/rman/archlog%U';
DELETE NOPROMPT OBSOLETE REDUNDANCY =1 device type disk;
DELETE NOPROMPT EXPIRED BACKUPSET OF DATABASE device type disk ;
BACKUP AS COPY CURRENT CONTROLFILE FORMAT '/opt/R12Backups/rman/copy_of_cf_%U';
BACKUP SPFILE FORMAT '/opt/R12Backups/rman/spfile_%U';
release channel c1;
release channel c2;
1.please tell me that it is covering all aspects of a backup . Can i do complete recovery with this backup in case of disaster?
Define "all aspects".
2. i only get database and controlfile backup at my location. There is no backup of archivelogs , What happened with
that ?Without seeing the output that rman generated from running the above block, and without seeing all of the persistent rman settings, it is impossible to diagnose anything. I will say that your script looks overly complex.
Just to give you a point of comparison, here's my setup. First the persistent rman settings. Take note of anything that is NOT marked as "default";
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 3;
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 '/ora00/app/oracle/product/10.2.0/db_1/dbs/snapcf_vlnxora1.f'; # defaultAnd here is my basic "full backup" script
[oracle@vmlnx01 bin]$ cat rman_full.scr
connect target /
show all;
run {
backup incremental level 0 database tag='bkup_vlnxora1_full';
backup archivelog all not backed up 2 times tag='bkup_vlnxora1_arch';
delete noprompt archivelog all backed up 2 times to device type disk;
list backup summary;
report obsolete;
quit

Advice on having a control file (online) on the same disk as backups

The following database files layout provides a no data loss configuration if the DiskArray #1, which stores the database, fails.
I have every think I need in the flash recovery area (DiskArray #2): backups, archived logs and online redo.
DiskArray #1:
- datafiles
- control file (mirror copy 1)
- Online redo log (mirror copy 1)
DiskArray #2: (flash recovery area)
- control file (mirror copy 2)
- Online redo log (mirror copy 2)
- archived logs
- backups
But some one raise the following scenario:
What happen if the diskArray #2, which has one control file copy, fails?
The instance should abort. Can it corrupt the current online redo, controlfile or a datafile?
If it does I would be in a dead end; of course I have regular offsite backups, but I may lose up to two weeks.
Lossing the database because the backup array fails is not acceptable.
Should I avoid any control file in the backup array?
Oracle recommend having control file copies in separate disk location and one of it in the flash recovery area.
Anyone have suggestions.
I am a bit scared

Can it corrupt the current online redo, controlfile or a datafile?Could that someone tell you why he thinks so ? I have seen loss of controlfile and loss of mirrored (duplexed) redo logs but that doesn't corrupt the good controlfile and redo logs and datafiles. unless someone or some process copies the corrupted files over to the good array !
You'd have to restart the instance with that controlfile excluded from the parameter file.
You'd lose your archivelogs and backups. If you have no tape backups you'd lose the ability to restore as well (being another "someone", I will ask "What happen if the diskArray #1 fails at the same time or 5 minutes after or 6 hours after diskArray #2 ?").
Hemant K Chitale
http://hemantoracledba.blogspot.com

Mid-2010 MBP super slow with 10.9.4 & lots of backups on disk

After four years of recovering beautifully from spills and falls, I think my overly ambitious software updates may have done in my mid 2010 MacBook Pro.
Aside from the usual Internet and word processing, I use my MBP for video editing.
About two months ago, I finally upgraded from Snow Leopard (10.6) to Mavericks (10.9.3) because I wanted to switch from FinalCut Pro X (and my torrented FCP7) to Adobe Premiere CC. I immediately downloaded several Creative Cloud applications and noticed a bit of slowdown, especially when using Premiere. Figuring the Creative Cloud video apps were too much for my old MBP, I deleted everything except Photoshop and Muse, and I purchased a desktop PC for video editing on Premiere (waiting for it to arrive).
I deleted several Creative Cloud applications and about 100 GB of video files (transferred from my Mac HD to an external HD). Immediately after, I saw an available software update and clicked it, upgrading me to the new Mavericks 10.9.4. Right after that, the Creative Cloud desktop app stopped working, so I reinstalled it.
After that, my MBP slowed down considerably. It takes 10-20 minutes to open any application, including Activity Monitor and Disk Utility.
I backed up using Time Machine (took about 8 hours), and I repaired the disk using Disk Utility. Repairing the disk hasn't sped anything up.
I know my hard drive is way too full, but I can't figure out why so much of it is going to backups. Since my hard drive is more than 80% full, shouldn't Time Machine automatically delete local images to bring it back to 80% at the very least? I'm using my external hard drive for Time Machine backups, so I don't know why so many are on Mac HD.
I can think of so many things that could be wrong - I only have 4GB RAM, my hard drive is almost full, and I probably shouldn't have installed Mavericks on such an old system in the first place - I'm not quite sure how to start fixing this problem. I'd like to be able to continue using my laptop for web browsing, MS Office Suite, FCPX, and FCP7. I'd be fine with reinstalling Snow Leopard (I still have the DVD), as long as the files on my hard drive are still accessible.
I'm planning to go to a repair specialist on Monday, but if anyone has advice on fixes I can do in the meantime or things I can do to make his life easier, I'd really appreciate it!
EtreCheck version: 1.9.12 (48)
Report generated July 12, 2014 at 1:34:06 PM EDT
Hardware Information:
MacBook Pro (13-inch, Mid 2010) (Verified)
MacBook Pro - model: MacBookPro7,1
1 2.4 GHz Intel Core 2 Duo CPU: 2 cores
4 GB RAM
Video Information:
NVIDIA GeForce 320M - VRAM: 256 MB
Color LCD 1280 x 800
System Software:
OS X 10.9.4 (13E28) - Uptime: 0 days 1:58:2
Disk Information:
Hitachi HTS545025B9SA02 disk0 : (250.06 GB)
EFI (disk0s1) <not mounted>: 209.7 MB
Macintosh HD (disk0s2) / [Startup]: 249.2 GB (37.49 GB free)
Recovery HD (disk0s3) <not mounted>: 650 MB
MATSHITADVD-R   UJ-898
USB Information:
Apple Inc. Built-in iSight
Apple Internal Memory Card Reader
Apple Inc. BRCM2046 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Computer, Inc. IR Receiver
Apple Inc. Apple Internal Keyboard / Trackpad
Gatekeeper:
Mac App Store and identified developers
Kernel Extensions:
[not loaded] com.flipvideo.IOUSBCameraMassStorage (1.0.1) Support
Launch Daemons:
[loaded] com.adobe.fpsaud.plist Support
[running] com.bradfordnetworks.agent.plist Support
[running] com.flipvideo.FlipShareServer.launchd.plist Support
[loaded] com.google.keystone.daemon.plist Support
Launch Agents:
[not loaded] com.adobe.AAM.Updater-1.0.plist Support
[running] com.adobe.AdobeCreativeCloud.plist Support
[running] com.flipvideo.FlipShare.AutoRun.plist Support
[loaded] com.google.keystone.agent.plist Support
[running] com.hp.help.tocgenerator.plist Support
User Launch Agents:
[not loaded] com.adobe.AAM.Updater-1.0.plist Support
[failed] com.apple.CSConfigDotMacCert-[...]@me.com-SharedServices.Agent.plist
[loaded] com.facebook.videochat.[redacted].plist Support
[running] com.spotify.webhelper.plist Support
User Login Items:
None
Internet Plug-ins:
o1dbrowserplugin: Version: 5.4.2.18903 Support
nplastpass: Version: 2.5.5 Support
Default Browser: Version: 537 - SDK 10.9
OfficeLiveBrowserPlugin: Version: 12.3.6 Support
AdobeAAMDetect: Version: AdobeAAMDetect 2.0.0.0 - SDK 10.7 Support
FlashPlayer-10.6: Version: 14.0.0.145 - SDK 10.6 Support
Silverlight: Version: 5.1.30317.0 - SDK 10.6 Support
Flash Player: Version: 14.0.0.145 - SDK 10.6 Support
QuickTime Plugin: Version: 7.7.3
googletalkbrowserplugin: Version: 5.4.2.18903 Support
iPhotoPhotocast: Version: 7.0
JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
Safari Extensions:
LastPass: Version: 3.1.41
Searchme: Version: 1.3
Audio Plug-ins:
BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
AirPlay: Version: 2.0 - SDK 10.9
AppleAVBAudio: Version: 203.2 - SDK 10.9
iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
User Internet Plug-ins:
UploadManager: Version: (null) Support
EMusic: Version: EMusic 1.0.0 Support
ContentManager: Version: (null) Support
RocketEngine: Version: (null) Support
3rd Party Preference Panes:
3ivx MPEG-4 Support
Flash Player Support
Time Machine:
Auto backup: YES
Volumes being backed up:
Macintosh HD: Disk size: 232.09 GB Disk used: 197.17 GB
Destinations:
My Passport for Mac [Local] (Last used)
Total size: 931.16 GB
Total number of backups: 7
Oldest backup: 2014-06-07 00:28:18 +0000
Last backup: 2014-07-12 14:47:51 +0000
Size of backup disk: Excellent
Backup size 931.16 GB > (Disk size 232.09 GB X 3)
Time Machine details may not be accurate.
All volumes being backed up may not be listed.
Top Processes by CPU:
      5% Creative Cloud
      5% WindowServer
      2% mdworker
      2% mds_stores
      2% mds
Top Processes by Memory:
147 MB com.apple.IconServicesAgent
111 MB Creative Cloud
106 MB Google Chrome
102 MB mds_stores
70 MB Google Chrome Helper
Virtual Memory Information:
1.51 GB Free RAM
1.46 GB Active RAM
293 MB Inactive RAM
499 MB Wired RAM
508 MB Page-ins
0 B Page-outs

Metacalf,
I have the same model MacBook Pro as you, and I’m running OS X 10.9.4 on mine without problems. I’d highly recommend that you upgrade your RAM; our model can work with 16 GB of RAM when Mac OS X 10.7.5 or newer is installed. I’ve got 8 GB in mine, but I’m not doing any video editing; you’d probably find 16 GB to be best. If your video editing is disk-bound, then you’d also benefit by replacing your internal HDD with a SSD.

RMAN never deletes archive log backups

Hi all,
I have same problem as some of you have already faced.
I have some instances 10.2.0.4 running un archive log mode.
I take full hot backup daily.
I setup a rman script to backup and delete obsolete backups according to the following policy:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
and then:
run {
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
CROSSCHECK ARCHIVELOG ALL;
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
crosscheck archivelog all;
delete noprompt archivelog all completed before 'sysdate -2';
DB full backups are being deleted, however archive logs backups are not deleted.
There are no tablespaces in backup or offline mode.
How can I know the reason why some archive log backups are kept ?
Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
Thanks in advance.

Hi Fernando,
This are the ouputpus of the commands:
RMAN> REPORT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> LIST BACKUP OF ARCHIVELOG ALL;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
1090 69.65M DISK 00:00:16 23-FEB-11
BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
List of Archived Logs in backup set 1090
Thrd Seq Low SCN Low Time Next SCN Next Time
1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1411 125.43M DISK 00:00:28 24-FEB-11
BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
List of Archived Logs in backup set 1411
Thrd Seq Low SCN Low Time Next SCN Next Time
1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1600 164.40M DISK 00:00:37 25-FEB-11
BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
List of Archived Logs in backup set 1600
Thrd Seq Low SCN Low Time Next SCN Next Time
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1829 132.24M DISK 00:00:30 26-FEB-11
BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
List of Archived Logs in backup set 1829
Thrd Seq Low SCN Low Time Next SCN Next Time
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2058 218.03M DISK 00:00:48 27-FEB-11
BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
List of Archived Logs in backup set 2058
Thrd Seq Low SCN Low Time Next SCN Next Time
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2298 205.39M DISK 00:00:45 28-FEB-11
BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
List of Archived Logs in backup set 2298
Thrd Seq Low SCN Low Time Next SCN Next Time
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2546 180.29M DISK 00:00:39 01-MAR-11
BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
List of Archived Logs in backup set 2546
Thrd Seq Low SCN Low Time Next SCN Next Time
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
2801 85.40M DISK 00:00:19 02-MAR-11
BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
List of Archived Logs in backup set 2801
Thrd Seq Low SCN Low Time Next SCN Next Time
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3058 137.93M DISK 00:00:30 03-MAR-11
BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
List of Archived Logs in backup set 3058
Thrd Seq Low SCN Low Time Next SCN Next Time
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3324 138.96M DISK 00:00:31 04-MAR-11
BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
List of Archived Logs in backup set 3324
Thrd Seq Low SCN Low Time Next SCN Next Time
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3597 178.07M DISK 00:00:39 05-MAR-11
BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
List of Archived Logs in backup set 3597
Thrd Seq Low SCN Low Time Next SCN Next Time
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3835 198.44M DISK 00:00:43 06-MAR-11
BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
List of Archived Logs in backup set 3835
Thrd Seq Low SCN Low Time Next SCN Next Time
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4131 185.94M DISK 00:00:40 07-MAR-11
BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
List of Archived Logs in backup set 4131
Thrd Seq Low SCN Low Time Next SCN Next Time
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4435 161.37M DISK 00:00:35 08-MAR-11
BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
List of Archived Logs in backup set 4435
Thrd Seq Low SCN Low Time Next SCN Next Time
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4745 79.24M DISK 00:00:18 09-MAR-11
BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
List of Archived Logs in backup set 4745
Thrd Seq Low SCN Low Time Next SCN Next Time
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
5270 135.13M DISK 00:00:31 10-MAR-11
BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
List of Archived Logs in backup set 5270
Thrd Seq Low SCN Low Time Next SCN Next Time
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
RMAN>
For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
I'd like to understand why it happens :-)
Thanks a lot,
Regards,
Diego.

SQL Server backup on disk from DB13 in 6.20

Hello,
is it possible to perform database backups on disk (remote and local) in transaction DB13? Is the Enterprise Manager the only way to perform backups on disks?
The only media type available in DB13 is 'Tape' and I can't change this option (maybe there is no option). SAP Library provides confusing information, as it states that bakcup on disk is possible in DB13, but also points to the documentation of MS SQL Server in order to achieve it.
We have WAS 6.20 in 4.7 ES 1.10 with MS SQL Server 2000.
Thank you.
Antonio Sánchez.

I think there is something called as virtual devices in enterprise manager which can be configured as TAPE device.
This virtual TAPE could be a actual TAPE or a DISK.
Try configuring it and see if it is visible in DB13.
We had done this 2 years ago, don't remember it properly.
good luck.
regards,
siddhesh

PSE8 "Error occurred while writing the disk" during backup

Last night I tried doing a full backup of my PSE8 catalog to DVD-R disks using the PSE8 "backup to CD/DVD" feature. The program told me I would need 17 disks, so I let it run. It was burning the 13th disk when it produced an error stating "An error occurred while writing the disc. Result 13, Command 42, Sense 5, asc 33, ascq 2".
I swapped out the supposedly bad disk for a new one and selected "Retry". It burned for several minutes (what I believe to be the whole disk) before producing the exact same error again. Not wanting to give up on 90 minutes of work, I kept retrying with new blank disks, and it failed on every one in the same way. It would write what seemed like the entire disk and then the same error would appear. This produced 6 coasters in a row before I gave up and cancelled the job (that's 18 disks and 2 1/2 hours of my time wasted).
I'm using a Samsung SH-S182M burner with the most current firmware (SB06), and LG DVD-R disks. I've had no trouble with this burner in any other software. My system has WinXP Pro SP3, 4GB RAM, RAID-0, and an AMD Athlon 64 FX-60 CPU. No lack of hardware resources.
I seem to recall having the same kind of trouble with PSE5 a couple years ago, possibly using a different DVD burner at the time (on the same computer). Since I normally do backups using 3rd-party software and an external hard drive, I only rarely use the PSE8 backup tool. I'm not sure it has ever worked properly for me.
Does anybody know what this error means, and why it doesn't happen until well into the process? And why it suddenly fails on every disk from that point on?

There doesn't seem any issue with disc drive or the DVD media. It could be because of any particular file which Organizer is unable to write. To confirm this, we need to check if the backup to hard disk works fine.

Rman backup to disk 2 Minutes; Backup to tape hours

Similar Messages

Maybe you are looking for