Volume Duplication Policy for RMAN Backups

Hi,
I wish to configure a volume duplication policy for RMAN backups. Both the source media family and duplicate media family are 'content managed' as per the documentation. However, the duplication policy 'trigger' is defined as if the media family is 'time managed', which does not seem to make sense in 'content-managed' media families used by RMAN.
Does anyone have any guidelines on how RMAN volume duplication can be set up so that my duplicates are valid?
Thanks

Yes. I understand. The reason I used time-managed volumes in the tutorial is that with time-managed volumes a duplicate may have different retention and rotation than the original. The procedure for time or content managed duplicates are the same.
A content managed tape may be duplicated to the same or different media family. If to a different media family, the retention would be same...since content managed but it could have a different rotation policy...if desired. For example, if you wanted original tapes left onsite but the duplicates to go offsite for "x" time, then create a new content managed media family and a desired rotation policy...associate that rotation policy to new media family and duplicate tapes to that media family with desired rotation policy. In that scenario, your original media family would have a duplication policy and possible a rotation policy. The new media family would just have a rotation policy.
Donna

Similar Messages

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.

I am running a MacBook Pro with 10.7.5 and I downloaded the OS X 10.10.2 Update Combo, however when I try and open the package the error message "This volume is used for TimeMachine-backups". Which is not true. I´m using TimeCapsule.

I am running a MacBook Pro with 10.7.5 and I downloaded the OS X 10.10.2 Update Combo.
When I try and open the package after accepting the lincence-agreement and upon choosing the install-volume the error message appears: "This volume is used for TimeMachine-backups".
Which is not true. I´m using a timecapsule for backups.
How can I proceed?

I am using a MacBook Pro (2010) with 2.53 GHz Intel Core i5, 4GB, 1067 MHz, DDR3, Startvolume Macintosh HD.
After downloading the package and starting upgrading it asks acceptance of the license-agreement. After that it asks for the volume were to install. And when I click on the Startvolume Macintosh HD (which is the only available on the machine) it says: "The volume is already being used for Time Machine-Backups".
It doesn´t offer to skip that point or to reconfigure the Time Machine settings.
The point is that my Time machine is not and has never used the Mac HD for Backups. In the past I have used an external drive and since 05/2014 I am using a Time Capsule which is appropriately addressed in the Time Machine settings.

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

Choice a remote drive for RMAN backup

I want to use my AIX (OS 5.3L) as a remote server for RMAN backup, under the 10g R2. The two most likely drives that still has lots space are hdisk1 and hdisk3. However, the hdisk1 is in rootvg with my test Oracle 10g appl on. Although the hdisk3 is in appvg and but it is the data storage for oracle of local machine. Both drives are quite busy based on the memory monitor and iostat. so How to make a choice for which drive is more proper as a remote drive?

As i play more with the NFS on AIX, i noticed more about the user/group attributes of the files and directory. Mainly, they are different on either side, even more strangely that the new file created on the server side has different user/group attribute , not as oracle/oinstall of original (client side) It worries me whether there will be problem when RMAN does the recovery later.
Secondly, the NFS only allows to write into one level of the directory, which is assigned NSF. As I know, the whole RMAN backup creates backupset files at several levels down from my flash_recovery_area.
Message was edited by:
user508054

Shell script for RMAN backup

Hi,
on 10G R2 in AIX 6.1
I'm looking for Shell script for RMAN backup.
Moreover , if we should connect like this :
rman nocatalog target sys/password@myDB << EOF
backup as compressed backupset format '$savdir/ctl_%d_%T_%s_%p' current controlfile;
exit
EOFHow to avoid writting password in shell script ?
Thank you.

user522961 wrote:
Can you please tell me in case of having a catalog , how to connect to catalog without writting password in script ? I mean , how to write the following in a way without password :
#!/usr/bin/ksh
export ORACLE_SID=myDB
ORACLE_ENV_ASK=NO
. /usr/local/bin/oraenv
export savedir=/backups/myDB
rman target / << EOF
connect catalog rman/password@myrepository
backup as compressed backupset
format '$savdir/ctl_%d_%T_%s_%p'
include current controlfile;
exit
EOF:p

Write a ms dos script for rman backup

Hi all,
i wanna write a dos batch file to take the rman backup..
i have written one...actually there are 2 files. one is for login purpose...other one is for sql commands
rman.bat-->
rman target sys/sysadmin@hnbhrm @'c:\rm.sql'
==============================
rm.sql-->
configure retention policy to recovery window of 7 days;
configure controlfile autobackup on;
run {
alter system switch logfile;
crosscheck archivelog all;
crosscheck backupset;
backup database plus archivelog;
DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'sysdate -1';
DELETE NOPROMPT OBSOLETE REDUNDANCY = 1;
========================================
but i have problem in first file rman.bat. it doesnt run at all. but if i write sqlplus / as sysdba instead of rman thing.. then it works fine.
can anybody tell me whats happening over there please..? Have i done this correctly? or u have some other simple way to do this...
both files are located in C drive.. and oracle is installed to E drive... oracle path has set already.
can anybody please give me a hand to solve this issue please...
Thanks in Advance,
Max

write a ms dos script for rman backupImpossible. rman does not support MS-DOS. It is not a 16bit real mode application that can be run inside the MS-DOS operating system.
So get your terminology straight - the Windows console is a character based 32bit virtual machine. It is not MS-DOS. It never was MS-DOS. Do not confuse the two simply because of superficial similarities. A stick-it note can be yellow - but because it is yellow does not mean it is a banana.

User Permission for RMAN Backups

Oracle 10g Database Enterprise Edition R 10.2
I have created a user admin and i want to run backups from admin user. Kindly let me know what user permissions i have to grant for rman successful backups?
Thanks!

The rman "client" executable must connect to the Database AS SYSDBA.
Therefore, technically it doesn't require a separate user account in the target database, although you could setup a user, grant SYSDBA to the user and have remote_login_passwordfile configured to allow connections.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Script for RMAN backup

kindly send the script for RMAN bacup

Hi,
About RMAN backup
http://dbataj.blogspot.com/2007/01/about-rman-backups.html
About RMAN architechture
http://dbataj.blogspot.com/2007/01/recovery-manager-architecture.html
About RECOVERY CATALOG
http://dbataj.blogspot.com/2006/12/recovery-catalog.html
RMAN backup script
http://dbataj.blogspot.com/2007/01/hotfullrmanbkpscirpt.html
above is my own work on RMAN you have to edit according you needs.
regards
Taj

DBID for RMAN backup with format '%u'

Hi all:
(I've post this at c.d.o.s. too, but no answers...)
This is Oracle 10.2.0.3 on Enterprise Linux 5.
I've been given two backups from an Oracle Database: one 'cold' and
one 'hot'. They both come from a lost server.
The fact is that they have been made with the format '%u' (eight
alphanumerics) and I must recover the database on a new server. I
cannot get the DBID from the backup files name because of this format
'%u'.
The backups have been made with CONTROLFILE AUTOBACKUP ON (or so I'm told).
How can I get the DBID to recover the DB on a new server?
Thanks in advance.
Cheers.
Carlos.

"I don't know where you read this, it's wrong. "Oracle® Database Backup and Recovery Advanced User's Guide
10g Release 2 (10.2)
2 RMAN Backups Concepts
Control File and Server Parameter File Autobackups
How RMAN Performs Control File Autobackups
"The RMAN behavior when the BACKUP command includes datafile 1 depends on the CONFIGURE CONTROLFILE AUTOBACKUP setting. If control file autobackups are ON and the backup includes datafile 1, RMAN writes the control file and SPFILE to a separate autobackup backup set. If control file autobackups are OFF and the backup includes datafile 1, then RMAN includes the current control file and SPFILE in the same backup set as the datafiles."
Cheers.
Carlos.

Email notification for rman backup log results

Hi,
Good Day!
is this possible to send email notification about the rman database backup results (succesfull or failed) without using local O/S utilities/services like cron jobs or/and sendmail services?
pl. note: Instead of local O/S' sendmail services, we would like to utilize the organizational - email server's address and email - account which is already running for other email correspondance.
Plateform details
+++++++++++++
Database: 10.2.0.3
O/S: HP-UX 11.31
An urgent response will be highly obliged.
Thanks
Regards,
X

You can use dbms_scheduler to check for teh configured job and it's status and then using the utl_mail package,can send an email. This would require the smtp srever address of yours .
Please refrain from using urgent word in the subseuent posts of yours. All the threads and the members of this and any other forum are alike and so are their issues/questions. For urgent request, please raise a sev 1 SR with support.
HTH
Aman....

Reduce Time for Rman Backup

Dear Experts;
rman for 0 level backup is taking about 5:26 hours, backup size is now 312gb I have enabled block track checking & it reduces time for incremental level 1 from 2hour to almost 3 minutes.
database shows biggest tablespace is "users"
I want valuable suggestions for reducing its time or is there any way to break 0 level backup. I can allocate channels but ultimately it will take time when taking "users" tablepace backup
Right now I am taking backup at usb drive & its version is 2.0
Regards

As you are taking backup to a usb drive there is not much that can be done to improve the speed. If you are concerned about the backup being slow.. then you could think of taking the backup on local disk( which would be faster and more efficient) and then move the backups from the disk to usb drive.
This can be done in a single backup script as 2 part operation.
1) take backup to disk.
2) copy the backup to usb drive and delete the backups from the disk.
There are many additional features that u can add to enhance it thoe.
Regards,
V

Development System Backup - Best Practice / Policy for offsite backups

Hi, I have not found any recommendations from SAP on best practices/recommendations on backing up Development systems offsite and so would appreciate some input on what policies other companies have for backing up Development systems. We continuously make enhancements to our SAP systems and perform daily backups; however, we do not send any Development system backups offsite which I feel is a risk (losing development work, losing transport & change logs...).
Does anyone know whether SAP have any recommendations on backuping up Development systems offsite? What policies does your company have?
Thanks,
Thomas

Thomas,
Your question does not mention consideration of both sides of the equation - you have mentioned the risk only. What about the incremental cost of frequent backups stored offsite? Shouldn't the question be how the 'frequent backup' cost matches up with the risk cost?
I have never worked on an SAP system where the developers had so much unique work in progress that they could not reproduce their efforts in an acceptable amount of time, at a acceptable cost. There is typically nothing in dev that is so valuable as to be irreplaceable (unlike production, where the loss of 'yesterday's' data is extremely costly). Given the frequency that an offsite dev backup is actually required for a restore (seldom), and given that the value of the daily backed-up data is already so low, the actual risk cost is virtually zero.
I have never seen SAP publish a 'best practice' in this area. Every business is different; and I don't see how SAP could possibly make a meaningful recommendation that would fit yours. In your business, the risk (the pro-rata cost of infrequently needing to use offsite storage to replace or rebuild 'lost' low cost development work) may in fact outweigh the ongoing incremental costs of creating and maintaining offsite daily recovery media. Your company will have to perform that calculation to make the business decision. I personally have never seen a situation where daily offsite backup storage of dev was even close to making any kind of economic sense.
Best Regards,
DB49

Restoring for RMAN backup

hi,
I have my prod database in oracle RAC two node. And i create a similar test setup for doing the testing.
Now i need to backup(hot) the data from prod and want to restore in test environment.
Even the test node is the two node RAC and with same directory structure.
The only difference is the DB name and instance names.
so anyone please help me which method i have to go for restoring the backup from prod.
Recover catalog is there.

The documentation has irrefragable answers on your questions:
http://download-uk.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb001.htm#i1008888
Regards,
Andrey

Recovery window for tape backups

Hope someone can answer to my questions.
With RMAN you can maintain the number of tape backups that are needed for recovery purpose through the “delete obsolete recovery window” command. E.g. the command below ensures tape backups be kept for recovery within 31 days:
delete noprompt obsolete recovery window of 31 days device type 'SBT_TAPE';
Q:
1) If I use a disk area as pseudo tape area in my backups (through ORACLE.DISKSBT library parameter), I guess the above "delete noprompt obsolete recovery window" command would work on the pseudo tape area as well?
2) At my site the pseudo tape area is backed up to tape nightly through the system backup job, and the tape backups are kept for about 1 month by the tape system. To save space in the pseudo tape area on disk can I just set a small recovery window in the above DELETE command (say 1 day) , and relies on the actual tape system retention policy for oracle backups? How would this affect oracle’s ability to do recovery?
Thanks

1) I would never use a 'faked' tape as a permanent solution - only to test tape backup scripts - , as it slows down the backup/recovery process. From RMAN's point of view a pseudo tape works like a real tape, so all valid commands apply.
2) When you delete a backup, RMAN forgets it. RMAN is not aware of still available backups in the tape system, you have to recatalog the backups. That means overhead in manual maintenance and a source for possible errors.
Werner

Volume Duplication Policy for RMAN Backups

Similar Messages

Maybe you are looking for