RMAN Full Hot Backup Daily

Hi,
I have Production Database going to live this week..
this is my RMAN Backup script for taking daily Full Hot Backup night 12pm...
I have enabled FLASH_RECOVERY_AREA
DB_RECOVERY_FILE_DEST=/backup/flash_recovery_area
log_archive_dest=/backup/archivelog
log_archive_format='arch_%d_%S_%T';
=========================================================
rman target=/
configure controlfile autobackup on;
run
allocate channel c1 device type disk;
crosscheck backup;
backup as compressed backupset database;
sql 'alter system switch logfile';
crosscheck backup;
release channel c1;
exit
===========================================================
Above script is scheduled usgin cron job...
=============================================================
Here I am not taking the archive logs backup...because..by default..archive logs are created in 2 places
(a) FLASH RECOVERY AREA
(b) /backup/archivelog
so archive logs are created by date wise in Flash Recovery Area....
I have flash recovery area structure like this for ever day
/backup/flash_recovery_area/PROD/archivelog/29_09_2007
/backup/flash_recovery_area/PROD/autobackup/29_09_2007
/backup/flash_recovery_area/PROD/archivelog/30_09_2007
/backup/flash_recovery_area/PROD/autobackup/30_09_2007
Above are 2 days backups of 29th and 30th....
I can simply send those 30_09_2007 and 29_09_2007 directories to TAPE Drive....
=======================================================================
When disaster recovery, i can restore those directories to flash_recovery_area and do the recovery using rman...
=============================================
Friends...am i goin in correct way..if anything wrong...please correct me..
my doubt is..I am not used any command of backuping up archivelogs in rman script.......becasue..archive logs are created in flash_recovery_area by date wise......
am i correct..

Hi,
Thanks for the reply,
My requirement is......Full Hot Backup daily at 2 AM......Daily i have to take this...so i scheduled this using cron job......I need to maintain 7 days backup in backup location.....
Here is my script
# Export Environment Variables
export ORACLE_HOME=/oradata/oracle
export ORACLE_SID=PROD
export PATH=$PATH:$ORACLE_HOME/bin
# RMAN Full Backup
rman target / catalog rman/rman << EOF
configure controlfile autobackup on;
configure retention policy to redundancy 7;
run
crosscheck backup;
backup as compressed backupset database;
sql 'alter system switch logfile';
backup as compressed backupset archivelog all;
backup as compressed backupset current controlfile;
crosscheck backup;
crosscheck archivelog all;
delete noprompt obsolete;
delete noprompt expired backup;
exit=============================================================
Can u please verify that, script is good or not
Message was edited by:
bsubbu
Message was edited by:
bsubbu

Similar Messages

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

Full Hot Backup using RMAN?

Dear all,
I want to take a full hot backup every week on sunday and the followings are the commands.
run
allocate channel ch1 type disk format '/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup
incremental level 0
database
plus archivelog delete input;
backup current controlfile;
backup spfile;
release channel ch1;
I have the following questions:
1) Am I need to define a directory named as "'/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck", so that the backup copies will put it here,right?
2) What format needs to be save in where and how to run it on weekly schedule basis?
3) I saw above script with "channel ch1", can I change it to "channel ch2"?
I am a beginner using RMAN, please let me know.
Best Regards,
amy

Which database version on which OS (looks like Unix/Linux)?
You have to create the directory '/db/BACKUP/RMAN', 'backup_%d...' is the filename created by RMAN.
%d Specifies the name of the database;
%t Specifies the backup set time stamp, which is a 4-byte value derived as the number of seconds elapsed since a fixed reference time. The combination of %s and %t can be used to form a unique name for the backup set;
%s Specifies the backup set number. This number is a counter in the control file that is incremented for each backup set. The counter value starts at 1 and is unique for the lifetime of the control file. If you restore a backup control file, then duplicate values can result. Also, CREATE CONTROLFILE initializes the counter back to 1;
%p Specifies the piece number within the backup set. This value starts at 1 for each backup set and is incremented by 1 as each backup piece is created;
%U Specifies a system-generated unique filename (default).
For scheduling a cron job could be defined or you use Enterprise Manager (10g and higher)
Channel name doesn't matter.
Werner

FULL HOT Backup failing with a 6 on media management layer....

Hi all,
My thanks in advance for reading and any posts. Appologies for the long post, but wanted to make sure I got all information required into the post
*******************The background*************************
We are currently doing full hot backups of all production databases to tape. The database we use is RAC install (9.2.0.6.0) on Linux Redhat Enterprise 4 (database on OCFS). We use a seperate Solaris 8 box with 2 HP Ultium tape drives over a standard Cat5 line (100mb), we use Veritas Netbackup 5.1 as our media manager and we use an RMAN repositry on another box. Currently the backup is taking on average 17 hours to complete (something that I have been through with Oracle).
We use the below rman script to do the full database backup.
DATE=`date +%m%d%Y-%H%M%S`; export DATE
USER=`id | cut -f2 -d"(" | cut -f1 -d")"`
ORACLE_SID=ausl5; export ORACLE_SID
ORACLE_USER=oracle; export ORACLE_USER
ORACLE_HOME=/u01/oracle/product/9.2.0 export ORACLE_HOME
#delete log files older than 35 days
find /var/adm/netbackup -name "auslive*" -mtime +35 -type f -exec rm {} \;
#if [ "${USER}" = "root" ]
#then
# su - ${ORACLE_USER} "cd /rac/DBA/scripts/BACKUP/" #-c "${CMD_STRING}"
# SUCCESS=$?
#else
# eval "/rac/DBA/scripts/BACKUP"
# SUCCESS=$?
#fi
<<EOF su - oracle
<<EOF1 /u01/oracle/product/9.2.0/bin/rman msglog /var/adm/netbackup/AUSLIVE_b
ackup.${DATE} append
connect target sys/fowler@rman_ausl5
connect catalog rman/rman@rman
#change archivelog all validate;
run {
allocate channel ch1 type sbt_tape PARMS="BLKSIZE=1048576";
#allocate channel ch2 type sbt_tape PARMS="BLKSIZE=1048576";
#allocate channel ch3 type sbt_tape;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
CONNECT = 'SYS/fowler@rman_ausl5';
#CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
CONNECT = 'SYS/fowler@rman_ausl3';
#CONFIGURE CHANNEL 3 DEVICE TYPE 'SBT_TAPE' CONNECT = 'SYS/fowle
r@rman_ausl4';
change archivelog all validate;
###=============== Veritas Calls =========================
send "NB_ORA_CLASS=ORAhot_AUSLIVE";
#send "NB_ORA_CLIENT=sunatlsunx008";
send "NB_ORA_CLIENT=sunatlsunx008";
send "NB_ORA_SCHED=full";
###=====================main backup sections =============
backup
incremental level=0
filesperset 15
format "bk_%s_%p_%t"
tag "hot_${ORACLE_SID}_${DATE}"
database;
sql "alter system archive log current";
change archivelog all validate;
backup
filesperset 10
format "ct_%s_%p_%t"
current controlfile;
sql "alter system archive log current";
backup
filesperset 150
format "al_%s_%p_%t"
archivelog all not backed up 2 times;
change archivelog all validate;
backup
filesperset 50
format "al_%s_%p_%t"
archivelog until time 'SYSDATE-4' delete input;
change archivelog all validate;
release channel ch1;
#release channel ch2;
#release channel ch3;
exit
EOF1
EOF
Now due to the backup taking so long, we often have archive log backups that kick off. We generally get Restore Validates of this backup once a week.
*********************************Problem*******************************
Getting to the problem, the media manager generally completes the job with a 6, which in Veritas means that the backup failed to back up the requested files. I guess that this could be something to do with the media manager layer. But myself and my colleagues are of the opinion that this is something to do with the archive log backups running inbetween (hence the change archivelog all validate; appearing so many times in the script).
Has anyone got any ideas?
Thanks again for any posts / ideas,
Mark.

No I mean, it really tries to backup everything; control file, archive logs etc...
Yeah I will admit its a bit strange, didn't code it myself. The idea was to do a bit a of house keeping at the same time with the archived redo logs (hence the file system stuff with the archived redo logs).
You see we thought that this might be causing the issue.
any ideas are welcomed,
thanks again,
Mark.

Incomplete Recovery Fails using Full hot backup & Archive logs !!

Hello DBA's !!
I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
3) Restored all Hot backup files from Tape to Test Server.
4) Restored all archive logs from tape to Test server.
5) Restored Latest Binary Control file from Tape to Test Server.
6) Now, Started recovery using following command from SQL prompt.
SQL> recover database until cancel using backup controlfile;
7) Open database after Recovery Completion using RESETLOGS option.
Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
Let me know What should be the reason behind recovery failure !
Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
Atul Patil.

oh you made up a new thread so here again:
there is nothing wrong.
You restored your backup, archives etc.
you started your recovery and oracle applyed all archives but the archive
'/oracle/EPR/oraarch/1_9624_601570270.dbf'
does not exist because it represents your current online redo log file and that is not present.
the recovery process cancels by itself.
the solution is:
restart your recovery process with:
recover database until cancel using backup controlfile
and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
type cancel!
now you should be able to open your database with open resetlogs.

Parrallelization of RMAN Full Database Backup Confusion

Hi,
I am running Oracle 10gR2 on Solaris 5.10 on sparc machine having 16 CPUs.
I am using following RMAN script to take full database backup:
#!/bin/bash
ORACLE_HOME=/u01/app/oracle/product/10g
PATH=$ORACLE_HOME/bin:$PATH
ORACLE_SID=mtcedwp
export ORACLE_HOME ORACLE_SID PATH
rman target / <<EOF
run
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 8;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
ALLOCATE CHANNEL d1 DEVICE TYPE DISK;
ALLOCATE CHANNEL d2 DEVICE TYPE DISK;
ALLOCATE CHANNEL d3 DEVICE TYPE DISK;
ALLOCATE CHANNEL d4 DEVICE TYPE DISK;
ALLOCATE CHANNEL d5 DEVICE TYPE DISK;
ALLOCATE CHANNEL d6 DEVICE TYPE DISK;
ALLOCATE CHANNEL d7 DEVICE TYPE DISK;
ALLOCATE CHANNEL d8 DEVICE TYPE DISK;
BACKUP TAG ATHEER_FULL_DB DATABASE FORMAT '/u01/BACKUPS/WEEKLY_DB_BACKUP/backup_%U';
CROSSCHECK BACKUPSET;
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
RELEASE CHANNEL d1;
RELEASE CHANNEL d2;
RELEASE CHANNEL d3;
RELEASE CHANNEL d4;
RELEASE CHANNEL d5;
RELEASE CHANNEL d6;
RELEASE CHANNEL d7;
RELEASE CHANNEL d8;
EOFWill the above script take the 8-way parrallel backup? or do I need to configure location for every channel separately?
regards

This channel can be allocated manually or can be pre-configured by using
automatic channel allocation.
The number of allocated channels determines the maximum degree of
parallelism that is used during backup restore or recovery. For example if
you allocate 8 channels for a backup operation 8 background processes for the
operation can run concurrently.
Parallelism of backup sets allocates multiple channels and assigns
files to specific channels. You can configure parallel backups by setting a
PARALLELISM option of the CONFIGURE command to a value greater than 1 or by
manually allocating multiple channels.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1012864

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

Recovery using Full BCV backup & archive logs

Hello DBA's ,
I have Last Sunday's Full BCV (Buisness Copy Volume) backup (i.e. ..... the tablespaces were taken into Backup mode then Sync the BCV, then split the BCV , take the backup of BCV and take the tabespaces in normal mode in short what we call as HOT BACKUP ........ ) & also I am taking only archive log & control file backup Daily.
Now I want to Run my database on Different Server using the above FULL BCV & daily backed up Archive logs & Control file.
Kindly update me- Can I go for following recovery steps for above scenario.
1) Install ORACLE software on new server.
2) Restore the last Sunday's FULL BCV (Hot backup)
3) Restore the archive log from last Sunday's Full BCV backup.
4) Restore the latest backed up control file.
5) Mount the database.
6) Recover the database using backed up control file & archive logs.
7) Open the database with RESETLOGS option.
Please Guide me whether I can Fully Recover/Start database on this new server using above steps. ---OR---- " Are there any more files except data files that need to be backed up daily after Full BCV ? " ---OR ---- More suggestions are Welcome.
I want to test this scenario bcz.
a) I can't afford daily BCV due to lack of storage with current retention given by buisness.
b) I can't afford long time taken by RMAN for backup & recovery, as it disturbs my other backup shedules, also RTO should be very low as per my buisness requirement.
c) Currently we are not thinking for any another Backup options.
OS platform -- SOLARIS 10
Database version -- ORACLE 9i/10g
Atul.

Hello everybody ....
Actually I am doing the above scenario practically and I am facing the problem that when I am applying my archive logs using backup controlfile until cancel, the recovery completes upto the available Archive logs/sequence. But it throws the following error along with it ......
ORA-00279: change 7001791222 generated at 01/13/2008 07:23:42 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9623_601570270.dbf
ORA-00280: change 7001791222 for thread 1 is in sequence #9623
ORA-00278: log file '/oracle/EPR/oraarch/1_9622_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
So, I opened my database using Last (Sunday's) full hot backup only and it opens successfully without applying any archives.
Now, my question is... why my database doesn't open with OPEN RESETLOGS option when I am recovering it using command " RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; "
I want to recover my database upto Saturday then What should I do ?
Please help me out !
Atul.

Making atabase clone (but without data=rows) from hot-backup

Hi,
I am newbie in Oracle administration. I am using Oracle 10g database. I would like to clone database i.e. make an exact copy of tablespaces, tables, indexes, triggers, functions etc. but without data.
What is the most efficient way to do it.? I am having the full hot backup of another database. Is it possible to restore a that backup using rman but without data (=rows) on the fresh installed oracle database
Thanks for any advice
Groxy

I don't think RMAN has the feature you are looking for.
For this purpose, it could be easier to use:
- either old export with FULL=Y ROWS=N
- or new data pump export with CONTENT=METADATA_ONLY.
However in both cases you would need to recreate the empty database before importing the export file.
Message was edited by:
Pierre Forstmann

Hot Backups - Oracle 9i, 10g and 11g

Are all hot backups run outside of RMAN as an OS file copy? If so, isn't this a very risky exercise.
I understand that RMAN will check for corruption where as hot backups won't. RMAN can also track backups in a recovery catalog.
If using a hot backup, it seems like corrupt data could be backed up with the good data.
What exactly are the advantages of using a hot backup. It is understood that the databases can be up during a hot backup, but can't they also be up with an incremental RMAN backup?

I think you need to read the documentation again. Check on tahiti.oracle.com
A cold backup is when the database is shutdown (can be done by file copy or rman)
A hot backup is when the database is running (can be done by file copy or rman)
RMAN has the advantages of backing up at block level, and going directly to tape, and compression, and incremental backup, and block checking, and backup from ASM, and catalog ......
File copy has the advantage of being logically simple (e.g you can see exactly what is happening when you copy a file).

Minimum privilege for hot backup

Hi,
Dears,
which privilege is required to take hot backup i want create user to take hotbackup with minimum privilege .now i take hotbackup with SYS user but this is danger because another department should be take hotbackup.
best regards
allahmorad

Allahmorad wrote:
Hi,
Dears,
which privilege is required to take hot backup i want create user to take hotbackup with minimum privilege .now i take hotbackup with SYS user but this is danger because another department should be take hotbackup.
best regards
allahmoradalter database,alter system, create session is enough privileges to make vast changes in your database.So there is not such priveleges.(as fortmann suggested).
I will suggest you to use the rman for hot backup.
Hope this help :)
--neeraj

Frequency of Hot backups using RMAN

Hello.
After years of running various inhouse utilities to backup our Oracle databases we are now going to implement RMAN in our shop. We are running Oracle 10.2.0.4 EE databases on Solaris servers in Archivelog mode, so we'd like to perform "hot" backups. A caveat to this is that we also have "standby" databases that we manually manage via a series of scripts that works rather well and helps our CIO sleep at night.
So what we're trying to do is tackle one obstacle at a time. We'd like to implement RMAN hot backups (including archivelogs) without having RMAN remove the archivelog backups that are out there. We simply want RMAN to backup the archivelog files, we'll manage their movement and removal ourselves for the time being.
The script I have put together simply issues: Backup database plus archivelog format='/dumps/rman/F_Database_%d_set%s_%T_%U';
The configuration settngs (we want at least a 2 day recovery period) are:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 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 '/dumps/rman/controlfiles/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/dumps/rman/W_Database_%d_set%s_%T_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/xora01/app/oracle/product/10g/dbs/snapcf_glprd.f'; # default
We are using an RMAN catalog.
So my question is, if I perform the backup of the database (using the above command) once or twice a week and back-up only the archivelogs on a daily basis, would I be covered and save space at the same time? I think this might cover me as far as the archivelogs are concerned as well until my management is more comfortable with RMAN and allows us to install/use Data Guard.
Thanks for you opinions/suggestions...

Hi,
So my question is, if I perform the backup of the database (using the above command) once or twice a week and back-up only the archivelogs on a daily basis, would I be covered and save space at the same time? I think this might cover me as far as the archivelogs are concerned as well until my management is more comfortable with RMAN and allows us to install/use Data Guard.Your idea also not bad to save disk space. it is also depends on database size and space availability on your server.
or else you can go for weekly once fulll backup, remaining days incremental backups & archivelog backups.
rman incremental backups take only chanegd blocks so it wont occupy much space
1) sunday - full backup - level 0
2) monday - inc1 & arch
3) tuesday - inc2 & arch
4) wednesday - inc1 & arch
5) thursday - inc2 & arch
6) friday - inc1 & arch
7) saturday - inc2 & arch... & so on...
Thanks

RMAN Hot Backup Errors.

Hello Everyone
I would appreciate if someone can assist me in resolving a problem. Starting from December of last year, we were able to take daily hot backups of our ORACLE 10g database server successfully with no issues. Presently we have been experiencing a number of errors in the logs, even though the script has not been changed. The main errors are as follows:
RMAN-03009: failure of backup command on t1 channel at 05/08/2007 00:01:19
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
In investigating the errors, it seemed to be associated to the tablespace not being put offline or backup mode cleanly, I assumed this was due to persons working later, so I scheduled the backup for a later time but I still got the same error in the log the following day. Can you assist me in resolving this problem please?

Is the db running in ARCH mode?
Error:     ORA 19602
Text:     cannot backup or copy active file in NOARCHIVELOG mode
Cause:     You tried to copy or backup a file that was not closed cleanly, and
     the database was in NOARCHIVELOG mode. This is not allowed because when
     restored, the file will require redo application before it is usable,
     and redo is not currently being saved beyond the contents of the online
     redo logs.
Action:     Take the tablespace offline clean or close the database and retry the
     copy or backup. Take the tablespace offline clean or close the database
     and retry

Rman hot backup

hello
i am using rman hot backup script to take backup database everyday but the problem is it is working but not deleting old backup older than 2 days .
also i have question .. my database is in archive log mode and everyday about 6-7 .arch files generating in my archive directory.
it is not deleting the old files but generating new files everyday so adding up to the space.
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string /u03/archive_logs/DEVL
log_archive_dest_1 string
also should i set dest_1 as archive location or just log_archive_dest
whats is the difference.?
my rman script is
RMAN Hot backup.unix script
The RMAN hot backup script rman_backup.sh:
# !/bin/bash
# Declare your environment variables
export ORACLE_SID=DEVL
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export PATH=$PATH:${ORACLE_HOME}/bin
# Start the rman commands
rman target=/ << EOF
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/backup/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/u03/backup/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/u03/backup/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/u03/backup/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
thanks

Ahmer Mansoor wrote:
RMAN never deletes the Backups unless there is a space pressure in the Recovery Area. Instead it marks the Backups as OBSOLETE based on Retention Policy (in your case it is 2 Days),
To confirm it SET DB_RECOVERY_FILE_DEST_SIZE to some smaller value, the RMAN will remove all the Obsolete Backups automatically to reclaim space.Be very careful with this. If you generate a LOT of archivelog files and you exceed this size, on the next archivelog switch your database will hang with "cannot continue until archiver freed". RMAN will not automatically remove anything. RMAN only removes stuff when you program it in your script.
See:
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmconfb.htm#insertedID4 Retention Policy (recovery window or redundancy)
things like:
set retention window and number of copies
crosscheck backup
delete obsolete <-- delete old, redundant, no longer necessary backups/archivelogs
delete expired <-- NOTE: If you manually delete files and do not execute delete expired (missing file), the DB_RECOVERY_FILE_DEST_SIZE remains the same. So, you can clean out the space and oracle will still say the location is "full".
Understand that if you also set this parameter too small and your backup recovery window/redundancy are incorrectly set, you can also exhaust the "logical" space of this location again, putting your database at risk. Your parameter could be set to 100G on a 400G file system and even though you have 300G available, Oracle will see the limit of this parameter.
My suggestion, get in a DEV/TEST environment and test to see how to best configure your environment for RMAN database backups/control file, archivelog backups also taking into consideration OS tape backup solutions. I always configure DISK for RMAN backups, then have some other tape backup utility sweep those locations to tape ensuring that I have sufficient backups to reconstitute my database - I also include a copy of the init.ora file, password file as well as the spfile backup in this location.
>
In case of Archivelogs, It is better to create and execute a Purge Job to remove Archivelogs after backup them on tape.I almost agree. I try to keep all archivelogs necessary for recovery from last full backup online. I try to keep a full backup online as well. much faster at restoring stuff instead of trying to locate it on tape.

RMAN hot backup at remote machines

Hi Friends,
Please let me know how to backup in rman hotbackup on remote machines
like i want to have rman hotbackup on remote machines
my production box is in us & and backup box is in india
Please lighten me on this

Excellent response. I want to clear few doubts? If you can respond, I would
greatly thankfull to you
I just inherited a system that uses RMAN, which I am not an expert with.
We planed to do a full online backup on the weekend and incremental (hot?) backups
every night.
1. on windows 2003 hostware database server c:\backup\rman\... we planed to take backup
what if i lost my c:\ drive fails
but i have enough storage in remote server
how can i safeguard my backups agains disk failures etc & pull and preserve in remote machines?
Please lighten me in this regard
Thanks in advance
Magu

RMAN Full Hot Backup Daily

Similar Messages

Maybe you are looking for