RMAN Retention need to setup

Hi
I have to setup a RMAN backup with retention (last 2 backups should be available and last 15 day's archive should be available on the disk).
Backup frequency is weekly once.
I can able to run the backup with
I am using nocatalog. and using the below script where i can have only one copy of the backup on the disk .
==============
run
delete NOPROMPT backup;
configure channel 1 device type disk format 'd:\disk1\HOT_%U';
configure channel 2 device type disk format 'd:\disk1\_HOT_%U';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\disk1\%F';
backup as compressed backupset database;
backup archivelog all delete input;
===================
Thanks.

What is your question?
Why do you use delete NOPROMPT backup, and what are you trying to accomplish configuring 2 disk channels?

Similar Messages

RMAN report need backup

We have an incremental level-1 backup Mon-Sat and cold full backup on Sundays with retention policy of 7 days. While troubleshooting some backup issues (space issue, expired backups) I ran the following commands and trying to understand the output.
RMAN> report need backup database;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
100 146 /orahprdidx/hprd/psindex05.dbf
RMAN> report unrecoverable;
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
RMAN> report need backup days = 7 database;
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
100 146 /orahprdidx/hprd/psindex05.dbf
RMAN> report obsolete recovery window of 7 days;
no obsolete backups found
RMAN>
I looks like I need 146 days worth of archive log files to recover the psindex05.dbf. If so, what I could do to bring that into the 7 days policy?
The database is fine, I am not trying to recover the database.
This was setup by someone and now I am taking over with minimum RMAN experience.
I appreciate any help in this subject.

The datafile was offline. I guess it was created my mistake and hanging in there. Once I do the cleanup it should go away.

RMAN Retention Policy - redundancy vs recovery window

Hi All,
I'm wondering what the most commonly used rman retention policy is, to provide point-in-time recovery. We have 2 oracle servers, one using redundancy policy (3) and the other using recovery window (2 days). I would like to standardize them but am not confident in which direction I should go in.
I'm tempted to lean towards redundancy but wanted to pose the question to a wider, experienced audience for any things to think about/watch out for. Also, I assume the restore process would the same for either.
Thanks in advance.

Redundancy based retention policy means how many backups of each datafile must be retained and Recovery windows based retention policy is a period of time which starts with current time and goes backward in time upto the point of recoverability.
Oracle suggests and its Best practice is "Recovery Window" .( I don't know the reason though)
Two things you need to consider:
1) You might need more space in case of "recovery window" because it depends upon the schedule of the backup. In "redundancy" , your space consumption will be same.
2) You need to keep "recovery window" time less than the value of "control_file_Record_keep_time" so your backup records won't be overwritten in controlfile.
We use "Recovery Window"

What are the mandatory fields needed to setup/register the SIP phone manually in CUCM

What are the mandatory fields needed to setup/register the SIP phone manually.Also, if someone can let me know the mandatory fields for Cisco based SIP phone and also the third party SIP hard phones like Avaya or any other Third party SIP phones both Soft phone and physical phone requirements...in CUCM
Please suggest...I need to know if MAC address is mandatory for all Cisco SIP phone to setup

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/bccm-712-cm/b09sip3p.html
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-version-70/112110-phone-add-00.html

Query on RMAN Retention Policy

Hi, I have my Retention policy set to Redundancy 2
I have taken 3 backups so far ( 2 Backup Sets, 1 Image Copy )
When I check report obsolete I get the following
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           1      05-SEP-13
Backup Piece       1      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp
Backup Set           2      05-SEP-13
Backup Piece       2      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp
Backup Set           3      05-SEP-13
Backup Piece       3      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp
Backup Set           4      05-SEP-13
Backup Piece       4      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp
Backup Set           5      27-SEP-13
Backup Piece       5      27-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp
Backup Set           7      27-SEP-13
Backup Piece       7      27-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp
Archive Log          305    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc
Archive Log          306    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc
Archive Log          307    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc
Archive Log          308    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc
Backup Set pieces 1,2,3,4 basically equate to my oldest backup - hence under redundancy of 2, I can see why that is obsolete
5 and 7 were simply Control File/SPFILE backups from Auto Backup and the 2 newer backups of these have been taken since ( i.e. backupset pieces 9 and 10 )
Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
any advice appreciated,
Jim

Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
- Yes you can get the database to the date which ever you want , using recover database until time.
Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
- can you please provide the output of below command
RMAN> show all;
Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
- You can restore the database back to two days or 5 days based on your requirement. You nee to recover the database using until time option.
Thanks,
http://gssdba.wordpress.com

I need to setup 7800 Series IP Phones in the CUCM 8.6.2 which by default are not support but will work after install the software. Anyone have document from Cisco as I remember I seen once before.

I need to setup 7800 Series IP Phones in the CUCM 8.6.2 which by default are not support but will work after install the software. Anyone have document from Cisco as I remember I seen once before.

Hi Ali,
I'll just add this reference to the good tips from my friend Manish (+5)
Support for the 7800 series in CUCM 8.6.2 was first added with this
Device Pack;
Cisco Unified Communications Manager
Device Package 8.6(2)(24104-1)Release Notes
Cisco Unified Communications Manager Device Package Release 8.6(2)
adds support for the Cisco IP Phones
7821, 7841, and 7861 running SIP firmware release 10.1(1).
The steps are in this doc
http://www.cisco.com/web/software/282074299/107528/cmterm-devicepack-8.6.2.24104-1_Readme.pdf
You might as well install the latest 8.6.2 Device pack
cmterm-devicepack8.6.2.24112-1.cop.sgn
Cheers!
Rob
"Seek it out and ye shall find "
- OneRepublic

Hi I need to setup my email account on my ipad2 coz I deleted, accidentalli it ask me for a server os something like that can u help me please

Hi I need to setup my email account on my ipad2 coz I deleted, accidentalli it ask me for a server os something like that can u help me please

I'm from Kuwait and there is no technical support for our hope I find a solution to have

Do we need to setup traditional ABAP Transport Management System on XI?

I was confused that do we need to setup ABAP transport Management System on XI, since the IR and ID object will use CMS or File to transport between DEV->QAS->PRD. If we still need, could you pls let me know why we need it?
one more question is: if we maintained some parameter in XI dev, say, we maintained Integration Server patameter to let system can moniter Syn message, if we want this paramter used in XI QAS, is that the only way to maintain it mannully in QAS, or we have other way to make it? thank you for your help

Zhang,
You are absolutely correct. You transport all your ID and IR objects using CMS or File transports.
But lets suppose you have developed some zprograms or abap mapping in XI. This basically reside on the ABAP stack. So for this objects to transport we will follow the procedure what we do normally to transporting the R3 objects. So what ever you develop on the ABAP stack we need to transport to QA and to Prod using ABAP transport system.
---Satish

Need to setup monitoring aon multiple ports for IDS

I have a cisco 3845. I need to need to setup monitoring aon multiple ports for IDS on 2 ports. How do I do this.
Also,
Is there a way to make ports on the switch portion act like hubs.
Thanks

I assume that you are referring to the Ethernet Switch Module in the 3845. If so it should support SPAN. Here is a SPAN configurations guide:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122z/122zj15/fz1636nm.htm#1820129

Do I need to setup TMS for SolMan?

Hi,
I am new to SolMan. I need to setup in order to use Maintenance Optimizer.
Does SolMan need to have TMS configured like other SAP solutions, Dev, QA and Prod? Or there is only one Solman setup and it does everything we need?
Thank you.

Usually there will be only one Solution manager in the landscape . You mainly use this for central monitoring, Maintenance Optimizer , creating Keys, Service Desk , proj documentation etc and you are not doing any development work in here. So it does not make sense to have Dev, QA and PRD for solution manager. But you can have a sandbox which will help you to test the Support packs before applying directly in production. Maintenance Optimizer can be configured with Solution manager .
Thanks
Prince Jose

RMAN REOPRT NEED BACKUP

i do not really understand the 'INCREMENTAL' option of "RMAN REOPRT NEED BACKUP" command.
like the one below:
RMAN> REPORT NEED BACKUP INCREMENTAL 3 DATABASE;
Whats the significance of the word 'INCREMENTAL' .
I need help please.
thank you

Yes, of course.
An incremental backup is a partial backup. It doesn't contain the entire database, just those bits of the database which have changed since the last appropriate backup.
That's why you can't just restore an incremental backup and open your database: the backup you've just restored only has some of the database blocks in it.
Imagine Monday's backup happens to capture blocks 5, 10, 15, 20, 25... and so on.
Tuesday's backup captures blocks 2, 4, 6, 8, 10, 12.. and so on
Wednesdays captures blocks 1, 3, 7, 9, 11 and so on.
On Thursday, you lose File 1. To restore it, you need blocks 1, 2, 3, 4, 5, 6 and 7. Getting all those blocks means loading Monday's tape and restoring block 5; loading Tuesday's tape and restoring blocks 2, 4 and 6; and finally loading Wednesday's tape and restoring blocks 1, 3 and 7.
You get everything back, but it takes you three goes and lots of tape loading.
Alternatively, On Thursday morning I could do a new complete backup (that therefore includes blocks 1, 2, 3, 4, 5, 6, 7, 8, 9... and so on). When I lose File 1 on Thursday afternoon, I simply have to restore blocks 1, 2, 3, 4, 5, 6 and 7 from the one Thursday morning tape.
The command you first asked about understands that the incremental restore process is a slow way of doing things and is suggesting to you that anything listed could do with a nice, new complete backup so that you would be able to restore from that new backup rather than the three old ones.

RMAN retention policy

Hi,
on 10g R2 on AIX6.1 , I have the followings :
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;My backup script :
RMAN> run
      allocate channel t1 type disk;
      backup as compressed backupset format '$dir/df_%d_%T_%s_%p' database;
      sql 'alter system switch logfile';
      backup as compressed backupset format '$dir/al_%d_%T_%s_%p' archivelog all delete input;
      backup as compressed backupset format '$dir/ctl_%d_%T_%s_%p' current controlfile;
crosscheck backup;
delete noprompt obsolete;
delete noprompt expired backup of database;But I have the backup files of 3th of March yet :
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1 recid=171 stamp=744800219And the only file it deletes is :
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           13404 18-MAR-11
Backup Piece       13408 18-MAR-11          /appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1
deleted backup piece
backup piece handle=/appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1 recid=331 stamp=746072971
Deleted 1 objectsShould not RMAN delete the backup files of before 15 of March ? Why it does not ?
Thank for explanation ? Or more.

Thank to all.
We backup it every night (FULL at WE and incremental in week).
list backup of database;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
7145    Full    571.86M    DISK        00:01:55     03-MAR-11
        BP Key: 7151   Status: AVAILABLE Compressed: YES Tag: TAG20110303T085658
        Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1
List of Datafiles in backup set 7145
File LV Type Ckp SCN    Ckp Time Name
1       Full 75445711   03-MAR-11 /data01/bases/MYDB/system01.dbf
2       Full 75445711   03-MAR-11 /data01/bases/MYDB/psundots01.dbf
4       Full 75445711   03-MAR-11 /data01/bases/MYDB/psdefault.dbf
BS Key Type LV Size       Device Type Elapsed Time Completion Time
19112   Full    772.42M    DISK        00:03:05     01-APR-11
        BP Key: 19118   Status: AVAILABLE Compressed: YES Tag: TAG20110401T121403
        Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110401_60_1
List of Datafiles in backup set 19112
File LV Type Ckp SCN    Ckp Time Name
8       Full 152751106 01-APR-11 /data01/bases/MYDB/ptprc.dbf
10      Full 152751106 01-APR-11 /index01/bases/MYDB/pttbl.dbf
15      Full 152751106 01-APR-11 /data01/bases/MYDB/pttlrg.dbf
19      Full 152751106 01-APR-11 /data01/bases/MYDB/ptprjwk.dbf
20      Full 152751106 01-APR-11 /data01/bases/MYDB/ptaudit.dbf
24      Full 152751106 01-APR-11 /data01/bases/MYDB/amlarge.dbf
26      Full 152751106 01-APR-11 /data01/bases/MYDB/apapp.dbf
27      Full 152751106 01-APR-11 /data01/bases/MYDB/aparch.dbf
34      Full 152751106 01-APR-11 /data01/bases/MYDB/aucapp.dbf
35      Full 152751106 01-APR-11 /data01/bases/MYDB/auclrge.dbf
37      Full 152751106 01-APR-11 /data01/bases/MYDB/bdapp.dbf
38      Full 152751106 01-APR-11 /data01/bases/MYDB/bdlarge.dbf
40      Full 152751106 01-APR-11 /data01/bases/MYDB/bilarge.dbf
42      Full 152751106 01-APR-11 /data01/bases/MYDB/caapp.dbf
50      Full 152751106 01-APR-11 /data01/bases/MYDB/cuaudit.dbf
54      Full 152751106 01-APR-11 /data01/bases/MYDB/cularge.dbf
58      Full 152751106 01-APR-11 /data01/bases/MYDB/dpwork.dbf
60      Full 152751106 01-APR-11 /data01/bases/MYDB/eobfapp.dbf
64      Full 152751106 01-APR-11 /data01/bases/MYDB/eocmwrk.dbf
71      Full 152751106 01-APR-11 /data01/bases/MYDB/eoecwrk.dbf
74      Full 152751106 01-APR-11 /data01/bases/MYDB/eoepapp.dbf
75      Full 152751106 01-APR-11 /data01/bases/MYDB/eoeplrg.dbf
77      Full 152751106 01-APR-11 /data01/bases/MYDB/eoewapp.dbf
81      Full 152751106 01-APR-11 /data01/bases/MYDB/eoiulrg.dbf
84      Full 152751106 01-APR-11 /data01/bases/MYDB/eoltapp.dbf
85      Full 152751106 01-APR-11 /data01/bases/MYDB/eoppapp.dbf
88      Full 152751106 01-APR-11 /data01/bases/MYDB/eotplrg.dbf
93      Full 152751106 01-APR-11 /data01/bases/MYDB/faapp.dbf
95      Full 152751106 01-APR-11 /data01/bases/MYDB/fawork.dbf
101     Full 152751106 01-APR-11 /data01/bases/MYDB/fgwork.dbf
107     Full 152751106 01-APR-11 /data01/bases/MYDB/fowork.dbf
109     Full 152751106 01-APR-11 /data01/bases/MYDB/fsapp1.dbf
112     Full 152751106 01-APR-11 /data01/bases/MYDB/glapp.dbf
122     Full 152751106 01-APR-11 /data01/bases/MYDB/inlarge.dbf

Rman retention window doubt

Hello, i have RMAN backup in the way of backupsets on two node 11gR2 RAC on linux standard edition.
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name MGW are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_mgw2.f'; # default
RMAN>And now i dont understand why RMAN is not deleting backupsets that are older then 24 hours , although i have set
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS.
I have in my rman script that is executing every day @ 23:00 this:
backup as COMPRESSED BACKUPSET database FORMAT '/home/oracle/rman/%U' plus archivelog delete input;
delete noprompt obsolete;And now i see in my rman backup folder that there is backupset from yesterdey 23:00 ,and also from the day before yesterday 23:00.
[oracle@data02 rman]$ ls -l
total 51889864
-rw-r----- 1 oracle asmadmin 26454474752 Jul 14 00:19 0bmhcc1s_1_1
-rw-r----- 1 oracle asmadmin     1245184 Jul 14 00:19 0cmhcg84_1_1
-rw-r----- 1 oracle asmadmin 26626334720 Jul 15 00:18 0fmhf0ep_1_1
-rw-r----- 1 oracle asmadmin     1245184 Jul 15 00:18 0gmhf4ih_1_1
-rw-r--r-- 1 oracle oinstall           0 Jul 14 16:52 aa_1_1I thoght that if i have run my rman script today @ 23:00 , than that will do backup but also delete backup from the day before because i have set
retention to 1 day .
Can you please say why i am wrong in this ?

The RMAN retention policy doesn't just keep the amount of days specified. It calculates the interval from the end of the current time and extends back in time for the number of days specifed.
So for example if you set the backup retention policy to 1 day today. Then RMAN will keep the backups for 15th July, 16th July.
Then on the 17th July, the 15th July backup will be obsolete.
I.e.
Current date   Status                                 Recovery Point
15th July        available                               15-1 = 14th July
16th July        available                               16-1 = 15th July
17th July        backup of 15th July obsolete 17-1 = 16th July
So your backup for today wouldn't be marked as obsolete until the 17th July.
5 Configuring the RMAN Environment
However, if you have a fixed-date database then you should be setting the retention policy to redundancy instead of recovery window.
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

When we create a permitted payee do you need to setup the permitted payee

Hi,
If a headoffice is setup in 3 different company codes. Then when we create a permitted payee do we need to setup the permitted payee in all 3 company codes.
Pls suggest.
Regards,
Shree.J

Hi,
Incase if i maintained one vendor number say 100100 for company code 1000, 2000, 3000 and 4000, then do i need maintained permitted payee say 5000 for all the above company code.
regards,
sree.j

RMAN -Retention policy doubt

Hi,
I have doubt on RMAN retention policy.
we are taking daily cumulative backup and weekly Full database backup.
And our retention policy is "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS"
My assumption is that RECOVERY window of 3 days will hold the backups of 3 days and delete the previous backups,since we are taking cumulative backups,and using them database can be recovered.
we used below commands to take cumulative backup.
backup incremental level 1 cumulative as COMPRESSED BACKUPSET tag '%TAG' database include current controlfile;
backup as COMPRESSED BACKUPSET tag '%TAG' archivelog all not backed up;
Regards,
mannu

Thanks for reply.
A recovery window is a period of time that begins with the current time and extends backward in time to the point of recoverability. The point of recoverability is the earliest time for a hypothetical point-in-time recovery, that is, the earliest point to which you can recover following a media failure. For example, if you implement a recovery window of one week, then this window of time must extend back exactly seven days from the present so that you can restore a backup and recover it to this point. You implement this retention policy as follows:
In our case:
Jan 24---Level 0 Full backup
Jan 25-Cumulative backup
Jan 26-Cumulative backup
Jan 27--->Cumulative backup
Jan-28 ----->cumulative backup
What would be my point of recoverability? How my recovery window period of 3 days work here.
Regards,
Mannu

RMAN Retention need to setup

Similar Messages

Maybe you are looking for