Rman backup strategy

hi,
just wanted to hear some thoughts from some pros..
platform: oracle 9i on windows
i switch from user-managed backups to rman recently. My full nightly backups are abt 20GB in size on completion.
we backup to tape, but i want to keep some disk backups for faster recovery.
i do not have disk space to keep more than 3 backups at any time. Cleanup will be regular and tedious. If i use a utility like gzip after, i can get it down to abt 4-5 GB and thus keep alot of backups on disk.
Does it make sense to compress all backups "older than the latest", and reduce the size so i can keep abt a week on disk?

Backup & Recovery Check List
Alejandro Vargas
Oracle Support Israel.
Rman Recovery Scenarios And Configuration
1. Complete Closed Database Recovery. System tablespace is missing
2. Complete Open Database Recovery. Non system tablespace is missing
3. Complete Open Database Recovery (when the database is initially closed). Non
system tablespace is missing
4. Recovery of a Datafile that has no backups.
5. Restore and Recovery of a Datafile to a different location.
6. Control File Recovery
7. Incomplete Recovery, Until Time/Sequence/Cancel
download the pdf format of full document in the below link:
google it oracle backup and recovery scenarios
[PDF]
Backup & Recovery Check List
File Format: PDF/Adobe Acrobat - Quick View
Oracle Support Israel. User Managed Recovery Scenarios And Configuration .... 4. recover automatic database using backup controlfile; ...
static7.userland.com/oracle/gems/.../BackupAndRecoveryChecklist.pdf
It will be very useful and helps you.
regards,
Rajeysh

Similar Messages

RMAN Backup Strategy Comment Needed

Hi,
Currently I'm trying to implement a backup strategy with RMAN.
Scenario: My side we're 5 days operational (Monday to Friday). I'm planning my backup as follow:
Mon – Incremental level 1 differential
Tue – Incremental level 1 differential
Wed – Incremental level 1 cumulative
Thurs – Incremental level 1 differential
Fri – Incremental level 0 (aka full database backup)
I planned Mon,Tues and Thurs as an incremental differential, while Wed as an incremental cumulative. With Wed as a cumulative backup, my thinking is that if my db is to fail on Thurs/Fri, my recovery will need to apply fewer backups but at the expense of storage.
Any comment or view about the strategy will be greatly appreciated.
Thanks and Regards
Eugene (ET)

hi,
there is Oracle suggested backup strategy
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm
other
http://books.google.cz/books?id=3aEIIqRHkY8C&pg=RA1-PA326&lpg=RA1-PA326&dq=oracle+rman+backup+stratery&source=bl&ots=DrnVZ3tZPs&sig=QajKM0SXbpoa3eWZgl5kmwmSUPI&hl=cs&ei=o6xcSvSaCpKwsAbmu8yVDA&sa=X&oi=book_result&ct=result&resnum=4
Regards,
Tom

Starting a RMAN backup strategy

Hi,
I took an incremental level 0 backup using RMAN while the database was in mount mode.
Are the archive logs from before the update still necessary in order to perform a recovery?
If not, how do I delete them using RMAN so that my next backup using 'backup database plus archivelog...' won't backup them?
Thanks.

Hi,
Are the archive logs from before the update still necessary in order to perform a recovery?Only if you need to roll forward to a point in time from a previous backup.
Can you post the output of:
show retention policy;If you know the exact start time of the level 0 backup you could delete the old archivelogs with.
delete copy of archivelog all completed before "to_date('define_time_here','YYYY-MM-DD:HH24:MI:SS')";Regards,
Tycho

Synchronous multimaster replication Backup strategy using RMAN

Hi all,
I am using synchronous multimaster replication. my question is backup strategy has to perofirm in all the master site or only in any of 1 mastersite? what all problems will encounter in RMAn backup in my scenario please help me out with your suggestion
nagaraj.K
[email protected]

You ask: "I want to configure backup strategy using RMAN. any one can help me that"
And the answer is clearly no we can not.
An RMAN backup strategy depends on your SLA (Service Level Agreement) with your customers that you didn't post. What is your down-time window? What is your skill set?
You ask: "How to configure for RMAN Incremental backup?"
Read the docs at http://tahiti.oracle.com for your version (which you didn't mention).
You ask: "What will be backup space and there size ?"
We have no idea. Are you going to create an image copy or a backup set? Read the docs and learn the difference. Are you going to turn on compression? Are you going to back up only changed blocks? We don't know.
You ask: "how to manage growing online archiving files?"
Again we can't help you without knowing your SLA. How many MG/GB are they? What period of time do you need to retain them to meet your SLA? When you figure this out back up to tape those you don't need to keep on the server.
You ask: "how to manage growing data and there disk space?"
This is one we can answer: BUY MORE DISK! That was easy.
You ask: "How we can give good performance our CPU and memory?"
Do you really expect that we can with zero knowledge of your environment, your version, your application, etc. distill into a few short paragraphs the collective wisdom of Cary Millsap, Jonathan Lewis, and the rest of the Oak Table Network membership?
Of course we can not. So what you need to do is buy Cary's book, Jonathan's book, and take their classes.
You ask: "we need keep all archive log in backup files or we need to remove old archive files?"
Remove the old ones after being absolutely sure you have a good backup.
You ask: "where we can take backup tape drive,SAN,disk removable hard disk? which one is better?"
No one solution is better than the other. They are all adequate.

RMAN backup in ORACLE RAC database

Hi there,
We are using RMAN backup strategy for taking backups from one node(eg.node1).Database is RAC database, version 9.2.3. and OS is Solaris 5.10.
this is the configuration which we use, as follows:
Connecting to Prod.Database using catalog database.
rman catalog=rman/rman@CATDB target=sys/oracle@PRODDB(node 2).
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 30;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanback/_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 5;
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 '/rmanback/CMWPROD_%s.bak';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS/oracle@PRODDB(node2)';
CONFIGURE MAXSETSIZE TO 7 G;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/9.2.3/dbs/snapcf_CMWPROD1.f';
As the above config shows RMAN is connecting to PROD DB (node 2). But we need to take backups (datafiles and as well as archive logs) from two nodes (i.e from node 1 and as well as node 2).
Is there any possibility for taking backups from two nodes?
Thanks,
Balu.

Duplicate thread
RMAN configuration in ORACLE RAC database
Khurram

WHAT IS BEST STRATEGY FOR RMAN BACKUP CONFIGURATION

Hi all,
my database size is 50GB I want TAKe WEEKLY FULL BACKUP AND INCREMENTAL BACKUP
WITHOUT RECOVERY CATALOG.by follwing commands
weekly full database backup
run
backup as compressed backupset
incremental level=0
device type disk
tag "weekly_database"
format '/sw/weekly_database_%d_t%t_c%c_s%s_p%p'
database;
I want do CONFIGURE RMAN BY FOLLWING stragtegy
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 days.
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO
'\SW\AUTOCFILE_'%F';
and other is by default
sql>alter system set control_file_record_keep_time=15 days;
os--aix6 and for two database 10g2 and 11g2
what is best configuration strategy for rman backup.AND BACKUP WITH RECOVERY CATALOG OR WITHOUT RECOVERY CATALOG
PLEASE TELL ME
Edited by: afzal on Feb 26, 2011 1:45 AM

For simply two databases, there really wouldn't be a need for a recovery catalog. You can still restore/recover without a controlfile and without a recovery catalog.
From this:
afzal wrote:
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 days.I am assuming you want to keep two weeks worth of backups, therefore these:
alter system set control_file_record_keep_time=15 days;
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 daysShould be:
RMAN> sql 'alter system set control_file_record_keep_time=22';
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14;22 would give you that extra layer of protection for instances when a problem occurs with a backup and you want to ensure that data doesn't get aged out.

Long-term retention backup strategy for Oracle 10g

Hello,
I need design a Archivelog, Level 0 and Level 1 long-term retention backup strategy for Oracle 10g, It must be based in Rman with tapes.
¿Somebody could tell me what it's the best option to configure long-term retention backups in Oracle?, "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1825 DAYS;" It's posibble ?
Regards and thanks in advance

Hello;
RECOVERY WINDOW is an integer so yes its possible. Does it make sense?
Later My bad, this is Oracle 11 only ( the gavinsoorma link ) . Getting harder and harder to think about 10. Don't think I would use RECOVERY WINDOW.
I would let the tape backup system handle the retention of your rman backups.
Using crosscheck and delete expired commands you can keep the catalog current with the available backups on tape.
Oracle 10
Keeping a Long-Term Backup: Example
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmbackp.htm#i1006840
http://web.njit.edu/info/oracle/DOC/backup.102/b14191/advmaint005.htm
Oracle 11
If you want to keep 5 years worth of backups I might just use KEEP specific date using the UNTIL TIME clause :
keep until time 'sysdate+1825'More info :
RMAN KEEP FOREVER, KEEP UNTIL TIME and FORCE commands
http://gavinsoorma.com/2010/04/rman-keep-forever-keep-until-time-and-force-commands/
Best Regards
mseberg
Edited by: mseberg on Dec 4, 2012 7:20 AM

Backup strategy for ebs R12?

Hi,
I have a couple of questions regarding to backup strategy for ebs R12.
Let's say that we have one application server and one database server running, and we would like to have a backup periodically for both servers.
This means that we want to have the exactly same backup of configurations and other files for the application server and the database server in case of any fatal crashes in the servers.
I went through some discussion threads and it seems common way is to use RMAN for the data of database and file system copy for application and database servers. But, I would like to know what's the best way or recommended way for the backup strategy for data and server files of Oracle e-business suite.
Do you guys have any suggestion for this?
Thanks in advance.
Cheers,
SH

Hi SH;
I suggest check first our previous discussion
backup and recovery startegy for EBS
Re: Backup System
Backup Policy for EBS can
If you make search you can find many other thread which is mention same question
For your issue basicly what we do
1. For our prod db, if possible we take weekly cold backup(sunday) and take rman backup also daily(full backup, but it depends system you can prefer to take incremental)
2. For our system we take file system backup weekly(OS base)
3. For application we take backup every sunday(for some system 15 days or 30 days period). The most important point here if your system prod, and if you need to apply patch to your system you need to have valid backup and also need backup for after patching
One other important issue is we run preclone sh before take backup for apps and db tier
Regard
Helios

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

Best pratices for RMAN backup management for many databases

Dear all,
We have many 10g databases (>40) hosted on multiple Windows servers which are backup up using RMAN.
A year ago, all backup's were implemented through Windows Scheduled Tasks using some batch files.
We have been busy (re)implementing / migrating such backup in Grid Control.
I personally prefer to maintain the backup management in Grid Control, but a colleague wants now to go back to the batch files.
What i am looking for here, are advices in the management of RMAN backup for multiple databases: do you guys use Grid Control or any third-party backup management tool or even got your home-made solution?
One of the discussion topic is the work involved in case that the central backup location changes.
Well... any real-life advices on best practices / strategies for RMAN backup management for many databases will be appreciated!
Thanks,
Thierry

Hi Thierry,
Thierry H. wrote:
Thanks for your reaction.
So, i understand that Grid Control is for you not used to manage the backups, and as a consequence, you also have no 'direct' overview of the job schedules.
One of my concern is also to avoid that too many backups are started at the same time to avoid network / storage overload. Such overview is availble in Grid Control's Jobs screen.
And, based on your strategy, do you recreate a 'one-time' Oracle scheduled job for every backup, or do your scripts create an Oracle job with multiple schedule?
You're very welcome!
Well, Grid Control is not an option for us, since each customer is in a separate infrastructure, and with their own licensing. I have no real way (in difference to your situation) to have a centralized point of control, but that on the other hand mean that I don't have to consider network/storage congestion, like you have to.
The script is run from a "permanent" job within the dba-scheduler, created like this:
dbms_scheduler.create_job(
        job_name        => 'BACKUP',
        job_type        => 'EXECUTABLE',
        job_action      => '/home/oracle/scripts/rman_backup.sh',
        start_date      => trunc(sysdate)+1+7/48,
        repeat_interval => 'trunc(sysdate)+1+7/48',
        enabled         => true,
        auto_drop       => false,
        comments        => 'execute backup script at 03:30');and then the "master-script", determines which level to use, based on weekday from the OS. The actual job schedule (start date, run interval etc) is set together with the customer IT/IS dept, to avoid congestion on the backup resources.
I have no overview of the backup status, run times etc, but have made monitoring scripts that will alert me if/when a backup either fails, or runs for too long. This, in addition with scheduled disaster/recovery tests makes me sleep rather well at night.. ;-)
I realize that there (might be) better ways of doing backup scheduling in your environment, since my requirements are so completely different than yours, but I guess that we all face the same challenges in unifying the environments as much as possible, to minimize the amount of actual work we have to do. :-)
Good luck!
//Johan

Need to Configure RMAN backup in 8.1.7.4.1

I have been asked to design a backup and recovery strategy for our production and test databases
I got 2003 Enterprise server with 3 disks of each 300gb.
There are 10 databases running in versions 8,9,10 with 5 production and 5 UAT database.
The sum of the Db will be around 70Gb
I got 200Gb free space in 2 disks
how can i design a BACKUP startegy here. I have palnned to use RMAN backups.
Any useful links and proper guiding from you people expected.
Right Now there is only export backup in Night.
I have informed them we are running the Db in risk,.They have asked me to comeup with a plan.
Any help please
Message was edited by:
Maran.E

Maran,
>
Is it possible to backup 8.1.7.4.1 by 10g database.
i can create a recovery catalog in 10g and wil i be able to backup a 8 and 9 Db
>
I have test 10g catalog with 9i. No idea with the 8i.
I guess, 8i(817) is more comportable with 10g and it should work.
Have a try with your test database and also cross check the metrix with different version in the Metalink.
Jaffar
Good news Maran,
I just come across of the following note which explains the RMAN compatibility between 8 - 10g versions.
RMAN Compatibility Oracle8i 8.1.7.4 - Oracle10g 10.1.0.4
Doc ID: Note:307022.1
In case, if you dont have access to metalink, the punch line from the note is :
SUMMARY
=======
Is best practice to use 'rule of thumb'. Always used the target database RMAN executable and the latest release of Oracle for your recovery catalog.
If you are going to use a lower version RMAN executable to backup higher version databases remember you are restricted to only the features available
in the database your using. But the executable you are using must be able to handle the feature or configuration you are using. Case and point the
RMAN-06466 error above where in 9.0.1 there is no concept of "AS BACKUPSET".
Because configure commands were executed some options in the controlfile were not understood when parsed by the lower version RMAN.
Message was edited by:
Syed Jaffar

Production Database Advance backup Strategy

Hi,
Now I am taking the backup with Rman Scripts daily after 6 PM. But the problem is that my company can not afford any data loss. I want to implement the backup advance backup startegy. Please I am going implement the advance backup strategy. Environment is
1.EBS R12.0.4
2.Database 10g R2.
4.Plateform RHEL AS 4.0.
Please guide me step by step how can I implement this backup startegy.
Help will be highly appreciated.
Regards.
pzdba

Now I am taking the backup with Rman Scripts daily after 6 PM. But the problem is that my company can not afford any data loss. I want to implement the backup advance backup startegy. Please I am going implement the advance backup strategy. Environment is What is you current backup mode
What kind of advance strategy are you looking for
If you are in archivelog mode and have your archivelogs
If you are backing up full
if you are backing up to the disk and your mirrored that disk in case of loosing disk failure
What kind of advance backup strategy you need more ?
what you need is testing the consistency of you backups. If they are consistent if you can recover the database it means you dont have data loss option with your current strategy.
Also you need to be sure about the time of backup to cover your needs.

Questions on Oracle EBS backup strategy

Hi all,
Currently I am planning the backup strategy for the EBS. May I know apart from backup the database using RMAN, is there anything (e.g. log files) that I need to backup such that I can fully restore the system?
Thanks a lot in advance.
Alex

I see that this is your first post, and you have not searched on this forum or on google about n-number of responses to your question that various people have already asked.
You didn't mentioned the applicaiton version you are using.
Anyways, you need to take the complete backup of the application tier directories i.e., appl_top, common_top, inst_top, etc.

Testing Rman Backup

Im testing my Rman backup.
We do our backup with the following command:
BACKUP AS COPY DATABASE TAG = 'Full Copy 2007/03/11 19:15:02';
On another machine, im testing the recovery like the following:
rman TARGET / NOCATALOG
startup nomount;
SET DBID my_bd_id;
RESTORE CONTROLFILE FROM '/mnt/jukprod_rman/rman_backup/20070311/c-3976015942-20070311-00';
alter database mount;
RESTORE DATABASE UNTIL TIME "TO_DATE('20070311 21:35:00','YYYYMMDD HH24:MI:SS')" PREVIEW;
Problem:
Rman wants 2 months of archive logs!!
no backup of log thread 1 seq 80017 lowscn 10641963078 found to restore
To
no backup of log thread 1 seq 85592 lowscn 13248466314 found to restore
That is 5575 archive logs that Rman needs. 100 Megs in size.
so Rman needs 557 gig of archive!
Whats wrong here?
How come Rman needs all those archive?
Why would rman need archive older that the backup since we did a backup as copy?
We want full backup with not need older archive logs.

Hi,
I don't think that BACKUP AS COPY is a real backup for future RESTORE command. May be you could use this statement for next commands:
BACKUP DATAFILECOPY
SWITCH DATAFILE TO
For good backup strategy you have to use statement like
BACKUP DATABASE INCREMENTAL LEVEL=0 PLUS ARCHIVELOG DELETE INPUT;
or simply
BACKUP DATABASE.
Than you have many old backups and you would like to restore in point of past
you have to use SET command.
If you use COPY of datafiles you have to do next:
restore spfile;
startup nomount
run{
set newname for_all_datafile_to_copy;
RESTORE CONTROLFILE FROM '/mnt/jukprod_rman/rman_backup/20070311/c-3976015942-20070311-00';
alter database mount;
switch all;
recover database;
open resetlogs;
Sergey

RMAN backup destination

Hi
Is there any way to mention the RMAN backup destination for datafiles and archivelog files with their exact name?
e.g
backup as backupset
format 'c:\backup\'
filesperset 1
database plus archivelog all;
Backup will be stored in c:\backup with the actual name of the files.
Destination has to be other than the FRA.
Regards

Does this mean if I use non FRA then 'delete force
noprompt obsolete;' will not delete the obsole
backups from non FRA destinations?
-- but I have checked it is deleting even from the
non FRA location also.
no i didnt mean to say that i mean to say if you dont use FRA for backup strategy then you are also not using OMF (Oracle managed files) cause one of the parameter db_recovery_file_dest_size define location of RMAN backups which enable also the OMF and its advantegous to use OMF cause it reduce wasted disk space consumed by obsolete files by deleting itself when FRA pressure goes to 85%.
You can mock up this situtaion by enabling FRA which in turn enable OMF and start taking backup iteratively when oracle see the space goes to 85% then OMF will remove the earliest obsolete files,you can check it in yours oracle alert log files where you will find
Deleted oracle managed files '<filename>'
I hope yours confusion is cleared now.
Khurram

Rman backup strategy

Similar Messages

Maybe you are looking for