doubt window retention RMAN

Similar Questions

• Recovery window retention policy removes the archive logs before backup?

  Hi all

  Oracle 11G on Windows 2008 R2

  This afternoon, I've changed my retention policy RMAN "RETENTION POLICY 3 REDUNDANCY"on RECOVERY WINDOW OF 3 DAYS RETENTION POLICY

  However, I checked tonight and after that my daily backup, all the archive before backup logs had been removed! So that means I don't think I can restore to any point in time, before my daily backup. All newspapers .arc were there after the backup. Then I tried another test and began the daily backup again. During the backup process, archive logs were deleted again! Now, I don't have any archives of newspapers...

  Is this good behavior OF RETENTION POLICY RECOVERY WINDOW? I thought that she would keep all the files needed for to restore me to any point in time for the previous 3 days. When I used a REDUNDANCY, with my daily backups, he kept 3 days of backups + archiving logs so that I could restore point-in-time at any point. How can I use WINDOW RECOVERY so that I can actually restore to any point in time for the 3 days?

  I wanted to change WINDOW of recovery, since I read that using the REDUNDANCY, it keeps only X copy a backup (so if I ran the backup 3 times a day, I would have only these 3).

  Thanks in advance.

  After a database RESTORE, Oracle tries to RECOVER a DATABASE.  He tries to 'find' the archivelogs for this phase in the location expected archivelog.  If they are NOT present in the location expected archivelog, it attempts to restore backups before applying them.

  Since your BACKUP... DELETE ENTRY deletes the archivelogs after that that they are saved, Oracle will have to use backups to recover the archivelogs.

  Hemant K Collette

• Doubt about the RMAN command

  Friends, what exactly makes the command "change archivelog than any overlap"? Thanks in advance.

  Must be the same as:

  crosscheck archivelog all;
  

• RMAN retention policy

  Hello everyone, I think to create a retention policy, but the problem is if I want to have the backup that ran daily from detention for 15 days and each backup run a monthly backup for a year which is the best option to set up the recovery window retention policy, because if I set with 365 days I'm going to keep daily backups for the whole year, suggest or advise

  Hello

  set the retention policy for 15 days (daily policy):

  RMAN > CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 60 DAYS;

  And add keep until 'sysdate + 365' monthly backup.

  RMAN > backup format incremental level 0 '% d.n0.%T.set_%s_%t' TAG data = 'BK_DATA_monthly_20150501' keep until 'SYSDATE + 365' opens a session;

  If you can make backup maintenance with delete obsolete;

  RMAN > remove force noprompt obsolete;

  
  

  It works with oracle 9i, 10g and 11g

• How to increase my period of retention with RMAN

  I think that 7 days of backup is enough for me in case of emergency.
  
  Can I do this?
  
  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  
  For now, it is:
  

  RMAN> show all
  2> ;
  
  RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
  .
  .
  .

  Well, it isn't if you would like to mention the 7 day recovery window retention policy, this means that the oldest backup a week will be lost. I've explained here. See if it helps,
  http://www.DBA-Oracle.com/t_rman_recovery_window_retention.htm

  Aman...

• What is the difference between redundancy and recovery for retention window?

  Hi all
  
  I'm still trying to get a grip on this concept of planning RMAN backup.
  
  I recently came across a situation like this.
  
  I have backups on a redundancy of 1.
  
  I have instance1, who had a job of GRID to run backups RMAN as follows
  
  Database incremental level = 0 a week at sea at 02:30
  I have backups daily, incremental level = 1 every night
  I have backups of the log of the archives through the day.
  
  What happened, was apparently on a TUE some time, the development team remove data in almost all of the tables in the schema.
  The this didn't discover until noon or so on Wednesday.
  
  I went to try to restore... and RMAN could not do. I had found a SNA for early TUES, they did... but I got the following error:
  
  RMAN > RUN
  2 > {}
  3 > SET up to this THAT SNA 4590383198282.
  4 > RESTORE database;
  5 > RECOVER DATABASE;
  {6 >}
  
  executing command: SET until clause
  
  From restoration to the 28 April 10
  allocated channel: ORA_SBT_TAPE_1
  channel ORA_SBT_TAPE_1: SID = 639 device type = SBT_TAPE
  channel ORA_SBT_TAPE_1: NMO v4.5.0.0
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 638 type device = DISK
  
  File number of the data file = 1 name=+DATADG/instance1/datafile/system.284.697137287
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the command restore at 2010-04-28 15:53
  ORA-01180: cannot create the data file 1
  ORA-01110: data file 1: '+ DATADG/instance1/datafile/system.284.697137287 '.
  
  What I did... of research, it seems that since I don't have a level 0 incremental of before, he could not reset the database in time. Precedent has been removed since, I guess I had a redundancy of 1.
  
  So, I thought that I had a week of backup they way I put it... but that assumes that the errors are found fairly quickly before the next level = 0 backup.
  
  I want at least 1 to 1.5 weeks of worth of backups. I have the problem that we do have many tapes in rotation, so I can't go because too long..may 2 x weeks at the top.
  
  I'm revising my strategy, but I am confused that I read about the difference between retention RMAN setting with window of recovery / redundancy.
  
  Can someone give me an explanation how do you understand? I read on the web and in books to oracle, and for some reason, it is not clear to me what is the best way to go... especially when I see this window of redundancy and recovery can affect?
  
  Thank you in advance,
  
  Cayenne

  Redundancy = 1 means rman will mark any more old than the backup of the last full or incremental backup of level 0 as obsolete. So it is very likely that the backup that you need for this restore has been removed after work Wednesday morning.

  The recovery window will tell rman to keep (or not obsolete brand) all necessary backups to restore to any point in time in the recovery window.

  Bjoern

• Confusion of RMAN CONTROL_FILE_RECORD_KEEP_TIME

  Hi all
  
  Please clear my doubts
  
  Database version: 10.2.0.3
  
  window of recovery of 30 days on 30 oct
  
  I put the window of recovery for 30 days and all backups of the last 30 days are listed when I log in the recovery catalog. But when I log into target controlfile only 15 days backups are displayed. My CONTROL_FILE_RECORD_KEEP_TIME = 7 which is minimum 7 days.
  
  This means that if I have connection with controlfile then my recovery windows is 15 days and when it is 7 days why controlfile i listing 15 days backups? I need to increase the CONTROL_FILE_RECORD_KEEP_TIME = 30 to synchronize with rman catalog?
  
  In additon obsolete report by cantrolfile list 30 oct to 14 nov obsolete backups
  
  Concerning
  
  Published by: hungry_dba on November 29, 2010 16:31

  >
  I put the window of recovery for 30 days and all backups of the last 30 days are listed when I log in the recovery catalog. But when I log into target controlfile only 15 days backups are displayed. My CONTROL_FILE_RECORD_KEEP_TIME = 7 which is minimum 7 days.

  This means that if I have connection with controlfile then my recovery windows is 15 days and when it is 7 days why controlfile i listing 15 days backups? I need to increase the CONTROL_FILE_RECORD_KEEP_TIME = 30 to synchronize with rman catalog?
  >

  CONTROL_FILE_RECORD_KEEP_TIME specifies the number of days, entries related backup (backups, archivelogs) remain guaranteed, before the old entries are allowed to be crushed. It defaults to 7 (days). Incidentally, you'll get that same old backups are listed as your controlfile was already big enough to keep these entries - there where more recent backups not much needed space in the controlfile.

  If you are backing up a recovery catalog database, the entries in the controlfile are automatically taken in the catalogue (resynced). In other words: If you take backups at least once within 7 days, your controlfile information is taken in the catalog recovery automatically. Otherwise, you should do the following
  (a) manually resynchronize
  (b) make backups more often
  (c) increase accordingly CONTROL_FILE_RECORD_KEEP_TIME

  If you do not use a recovery catalog database, you need to adjust slightly higher than the time is your CONTROL_FILE_RECORD_KEEP_TIME recovery window retention policy.

  Kind regards
  Uwe Hesse

  http://uhesse.WordPress.com

• Another process or feasible by RMAN?

  Server A: Database 11.2.0.4.0

  Server B: catalog RMAN 11.2.0.4.0

  C Server: storage of the backup files.

  It is the plan of database - backup full backup every day at 21:00 Server C and tape backup every night at 23:30.

  The process is to have 3 backup files to Server Cmaximum.

  The question

  (1) if I need to recover from a week ago, it is possible to do?

  If I Configure the recovery window retention policy and have RMAN delete the files from the Server C, RMAN will not be able to recognize the backup files restored from backup tape from a week earlier, correct? RMAN will see the file as obsolete, correct?

  (2) if I remember well 10 problems with your backup RMAN script, it is not advisable to set up a short retention policy to recovery window. This means, I'll need to have a separate tasks scheduled to remove the backup Server Cfiles? Or RMAN has any mechanism to do so?

  Thank you

  Friend

  So I guess you have 3 nights of backups on Server C, which can be more than 3 files backupset.

  (1) you can restore a backup of the Ribbon, as long as it goes back to Server C, then you can recataloguer all RMAN backups think are not available.

  So the question is how many nights of tape backup do you keep?

  (2) let RMAN determine what is obsolete and may be removed. Gift; t remove it manually using the command of the o/s.

• RMAN 9i, no catalogue, issue of additional levels

  Hello
  
  I need to clarify here.
  I have a db oracle 9.2.0.1 race prod and have a backup, planning as follows:
  No catalogue
  Sunday: Level 0
  Monday - Saturday: level 1
  Retention policy to recovery of 15 days window
  
  Last month, we had problems with additional levels. Every 3 or 4 days since a level 0 backup, launch, level1 rman backup cannot find parts previous backup level 1, so it makes a backup of level 0 of these data files (and we can not effort it.) The DB is large [full backup around 1'2 TB] and we do not have enough free space on the partition backup). But the files still physically exist.
  RMAN backs up in several backuppieces. The first is by far bigger than the others (about 650 GB of backup completes.) and it has about 60 files of data. At first, I thought that the problem comes here because all the lost data in the log files indicates are stored in this huge backuppiece, the next day we tried to launch a level 1 backup, but the problem still remains BUT pointing to different data files stored in different backuppieces lost. The only solution is to delete and make a backup of lvl 0, which is very risk and not desired. (by the way, if someone can explain to me why some backup pieces are larger than others and what rman criteria are used to store data files in the backup items I'll be happy.)
  
  As I read, in no cataloged backups (im not very familiar with them) the controlfile retains all the data used by rman. I found that the view V$ _CONTROLFILE_RECORD_SECTION report the number of records affected and used for backups stored in the controlfile, but I do not understand how oracle treats of these records.
  I did the following in a smaller database test:
  first values in view state:

  select type,records_used,records_total,records_used/records_total*100 "PCT_USED" from sys.v_$CONTROLFILE_RECORD_SECTION WHERE type like ('BACKUP%') order by 1
  
  TYPE                           RECORDS_USED RECORDS_TOTAL PCT_USED
  ------------------------------ ------------ ------------- --------
  BACKUP CORRUPTION                         0           371     0.00
  BACKUP DATAFILE                         220           245    89.80
  BACKUP PIECE                            200           200   100.00
  BACKUP REDOLOG                          528           528   100.00
  BACKUP SET                              312           409    76.28
  BACKUP SPFILE                            56           131    42.75

  Then I did a level 0 backup. He did 5 backuppieces in my score
  Display values has changed as follow:

  TYPE                           RECORDS_USED RECORDS_TOTAL PCT_USED
  ------------------------------ ------------ ------------- --------
  BACKUP CORRUPTION                         0           371     0.00
  BACKUP DATAFILE                         225           245    91.84
  BACKUP PIECE                            200           200   100.00
  BACKUP REDOLOG                          528           528   100.00
  BACKUP SET                              318           409    77.75
  BACKUP SPFILE                            57           131    43.51

  (?.. don't understand.) Data files, the sets and spfile has increased as I have requirements... but number of pieces still?..)
  
  Finally, I deleted the backupsets of 13 days ago (in total 10 backuppieces)

  TYPE                           RECORDS_USED RECORDS_TOTAL PCT_USED
  ------------------------------ ------------ ------------- --------
  ACM OPERATION                             6            64     9.38
  ARCHIVED LOG                            280           280   100.00
  BACKUP CORRUPTION                         0           371     0.00
  BACKUP DATAFILE                         225           245    91.84
  BACKUP PIECE                            200           200   100.00
  BACKUP REDOLOG                          528           528   100.00
  BACKUP SET                              318           409    77.75
  BACKUP SPFILE                            57           131    43.51

  (? the number of used records did not get down... I've read that these records are reusable, so I think that mark just oracle it registers as 'reusable' instead of delete [I right?])
  
  
  If I'm right with my guess, that it can fit with my problem in the big PB, because I checked the display before and after the backup and the results haven't changed:

  TYPE                           RECORDS_USED RECORDS_TOTAL PCT_USED
  ------------------------------ ------------ ------------- --------
  BACKUP CORRUPTION                       185           185   100.00
  BACKUP DATAFILE                         704           704   100.00
  BACKUP PIECE                            355           355   100.00
  BACKUP REDOLOG                          107           107   100.00
  BACKUP SET                              204           204   100.00
  BACKUP SPFILE                           207           226    91.59

  All files except spfile records are 100% usage (and do not understand why because I backed up too). When these values are set? How can I increase them? Should what criteria I use? I have not found much info on how no backup catalogued deals with rman (or I didn't search with the right keywords).
  
  I have no idea because I'm not familiar with no backup catalogued.
  Can someone help me?
  
  Thanks in advance.
  
  Published by: user5737038 on 23 / dic / 2011 01:46
  
  Published by: user5737038 on 23 / dic / 2011 01:48

  Hi user5737038,

  control_file_record_keep_time is set to 0
  ...
  If this parameter is set to 0, then the reusable sections never expand, and records are reused as needed

  I guess you know what to do now...
  (window retention in days + interval in days of level 0 + 1 day)
  C,
  T

• question of 'report must save window of recovery '.

  Hello
  
  I have a question about the report need backup recovery window.
  When I execute this command and get the result (for example 3A need backup datafile) is not only information for me and I can do nothing to help him do?
  I mean the following situation:
  I got the 3 day recovery window retention policy.
  Yesterday I made my backup and it's the only one I (and archivelogs until now).
  I pass the "report need backup 3 day recovery window.
  
  Everything I do, backup now or not, I can't return to situation 3 days ago because I do not have the proper backup.
  So, it's a situation this command shows me the files requiring a backup and I'm able to do something with it?
  
  Sousou.

  I don't think the scenario you describe is correct. It is my understanding that if you set a retention of "n" days policy, rman will retain all the backups needed to recover to any point in the "n" days. If that means backups of maintaining the older than "n" days, it's what he'll do.

  Say that your retention policy is 7 days. August 1st, you take a full backup (level 0). After that, you take daily incremental 1 and backkup your archivelog files. But you don't take another level zero backup full until August 15. Must keep this Aug 1 RMAN backup and increments that ensued to recover to any point in the last seven days and it do.

• 'main' arguments when starting program - how does communicate requests for file to Windows programs?

  Someone know what Windows up or sends to a program when it is first started? I don't know yet what to look under. In particular, if I double click on a document (say a data file that I generated with my LabWindows/CVI program) and I have my default program for this file under Windows, how is my program knows it when it starts? (I.e. a double-click on a Word document starts Word and opens this document.) In addition, what happens if my program is already running? No doubt, Windows sends a message to the programs telling them that the user has requested to open a file of the appropriate type.

  Windows passes the name of the file you clicked on the application as a command line parameter: the attached program lists simply all the command line arguments received in order to check how it works. I did a few tests by creating a '. '. XYZ"file and then associate this program with it. Then, I created a new operation 'Print', defined in this way:

  

  and received the correct settings, I simply double click on the file and when I click right on it and choose 'print '.

  (Note: argv [0] is always the name of the program itself: command line options, if any, starts at index 1).

  I can't say anything about your second question: I know that the CVI has a way to see if another instance of the application is running (see the CheckForDuplicateAppInstance command in the utility library), but I don't know how it is implemented.

• What happened when RMAN 1 level 1 is running and start a 2nd

  Hello

  I have some doubts on the RMAN backup,

  (1) what will happen when the first backup which is cumulative level 1 is running and second level 1 is launched.

  Example,

  Each work day 4 h level 1 is running and not completed and 9 AM is started before complete 04:00, in this situation, what would happen if 04:00 will be shut down properly and 09:00 will start correctly or any error will be through?

  (2) what happens when level 1 is running and not completed when the use of level 0 is the beginning.

  (3) is 1 / my dismissal and have only a level 0 and other many cumulative level 1 filled with hard drive backup and it reached assigned size. How I can take more away level 1 and how can I take level 0. If I don't have enough memory.

  When my redundancy policy is 1 so I would have 2 valid level 0 then then a level 0 backup will become obsolete and can delete.

  Help, please.

  (1) 2nd level 1 will take place at the same time.

  (2) level 0 will start and operate concurrently.

  (3) you need to extend the backup volume. If you can't do that let down backups, then do the 0 level.

• RMAN Tablespace restoration

  Hi guys,.

  I tried to restore the tablespace using RMAN full backup.

  I couldn't restore tablespace,

  I've added DB and DB auxiliary also

  C:\Windows\System32 > rman target sys@test catalog rman@catdb auxiliary sys@dup

  Recovery Manager: release 11.1.0.6.0 - Production on Tue Apr 1 16:14:03 2014

  Copyright (c) 1982, 2007, Oracle.  All rights reserved.

  target password database:

  connected to target database: TEST (DBID = 2141887982)

  Catalog database recovery password:

  connected to the recovery catalog database

  database Assistant password:

  connected to the auxiliary database: DUP (DBID = 214554882)

  RMAN > recover tablespace test until time ' to_date (April 1, 2014 13:54 ',' DD - MON).

  (-'AAAA HH24:MI:SS) ' DESTINATION AUXILIARY = a: \testDB\clone';

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-00558: error occurred during parsing of order entry

  RMAN-01009: syntax error: found 'test': expected an a: 'double-quoted-string,

  identifier, single-quoted-string ".

  RMAN-01007: in the file column 20 line 1: entry standard

  Thanks in advance

  > I have demolished tablespace at 17:54

  Do you mean you deleted the data file?  Or you deleted the tablespace?  A tablespace coward belongs more to the database.

  Hemant K Collette

• Backup Controlfile RMAN

  Hello

  If I configured the RMAN for using backup controlfile option:

  RMAN > configure controlfile autobackup on;

  I always have to do this:

  SQL ' ALTER DATABASE BACKUP CONTROLFILE TO "${CTRLBKP}" ";

  I have a script to backup RMAN (written by someone else) who issues the SQL above once the backup is complete.

  My understanding is that if the controlfile is automatically RMAN backup, there is no need to run the SQL above.

  Please notify.

  Hello

  no need to take backup using sql.

  You can also read this if you have the slightest doubt:configuration of RMAN environment

  HTH

• Memory Hot add, windows 2008 R2 standard?

  Hey guys, reading some contradictory documents on this subject, I would be able to hot add memory in Windows 2008 R2 Standard on Vsphere 4.0 without a reboot?

  I did the hot add in vcenter, but the module memory shows as an error on Windows Server, you cannot start device code (10) error...

  This will require a reboot?

  Thank you

  Kevin

  not compatible with the standard edition

  No doubt Windows ENTERPRISE ONLY feature.