RMAN Backup successful check - efficient method

I am looking for efficient single method/commands to check weekly RMAN backups -ok. eg july03-july10 all backup ok, if someone can post single command to check weekly backup(or from this date to this date) would help...
Right now i just, i just go to backup log dir and do
grep -i 'ERROR' *07-08-2009.log
grep -i 'ERROR' *07-09-2009.log and for each date....which is not so efficient & its manual

Generate a script to check V$RMAN_STATUS and V$RMAN_OUTPUT

Similar Messages

Backup validate check logical database

What is exactly the following RMAN command do? I want to know Is it doing a full backup or not?
rman> backup validate check logical database' . Kindly help me.

RMAN does not physically backup the database with this command. But it reads all blocks and checks for corruptions.
If it finds corrupted blocks it will place the information about the corruption into a view:
v$database_block_corruption;
Now we can tell RMAN to recover all the blocks which it has found as being corrupt:
RMAN> blockrecover corruption list; # (all blocks from v$database_block_corruption)
Use below link for reference.
http://luhartma.blogspot.com/2006/04/how-to-check-for-and-repair-block.html
-Bharath

Rman Backup time error

Today i saw this error in our production backup time .
Please let me know how to leave out from this.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/27/2011 01:13:47
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 05/27/2011 01:10:52
ORA-19566: exceeded limit of 0 corrupt blocks for file
N:\USERS01.DBF
Regs,
Brij

Also, be aware that rman: backup validate (check logical) command could not show the corrupted blocks if that block are newer used(or used before, but freed later for example). In this case, rman validate does not populate V$database_block_corruption but it also does not allows you to continue with your backup.
So the solution will be, as previous posters said, either set the limit for the sustained number of corrupted blocks or format/repair the corrupted block.
For checking the corrupted blocks you could also use db verify utility(dbv). This will definitely show you the details about corrupted blocks, even they are not used ever.

RMAN : BACKUP OPTIMIZATION ON

Hi All,
I have a doubt about BACKUP OPTIMIZATION ON parameter..
If Any one worked, can u tell me the exact use of this parameter....
Regards,
Prabhu.

Used to enable or disable backup optimization. Backup file optimization can assist in reducing the space used to backup the database. When performing an RMAN backup, a check is done on the file before backup to see if the file already exists in a backupset with the same information: (dbid, checkpoint, and resetlogs data).
For archive logs, the same file means the same dbid, thread, sequence, and resetlogs data. If the DELETE INPUT option is used, RMAN deletes all the files that would have been backed up, even when the file is not included due to file optimization.
The two possible values for backup optimization is ON and OFF as shown in the following example syntax:
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE BACKUP OPTIMIZATION ON;
Use caution when enabling backup optimization if you use a media manager that has an expiration policy. The media manager can expire tapes containing backups (using its media control software), and RMAN will not make new backups because of optimization. One way to protect from this is to run CROSSCHECK periodically to synchronize the repository with the media manager.
Also note that you should consider how backup optimization works with regards to the RETENTION POLICY. RMAN will only work with files within the retention period. For example, consider performing a backup with optimization enabled and a retention period of 3 days. RMAN will only compare the datafile with backup sets within the 3 day period - even if the datafile it is about to backup hasn't changed within that 3 days.
ofcourse the best reference is here

How to ensure the rman backup is successful?

Hi,
we have scheduled rman backup jobs.
1. But how do we ensure all the rman backups are successful?
2. if the rman writes directly to tape, how do we ensure all tape backups are successful?
thanks
andrew

But what is incremental merge, couldn't find in the 10g manual?check it out on http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmquick.htm#BRADV89354
do you use image backup in real production environment?Of course. We have a standard to to use image copies that way.
what do you suggest to do with rman normal way of backup or go for image backup?Depends on your specific situation. Like anything else, I prefer to provide some rationale on the recommendation.
Image Copies with Incremental Merge
Pros:
(1) one one full backup taken ever; no need to take another full backup
(2) the restore time is the same, regardless of the day of the week the db failed
(3) every day the incremental merge's success means the backup was good - an automatic validation
(4) it allows you to quickly switch to copy, rather than restore
Cons:
(1) Space requirement is more (since it's a bit to bit copy)
(2) can't do a point in time recovery from the disk alone
(3) can't go to the tape directly; must be a disk based backup.
Backupsets with Incremental Backup
Pros:
(1) space requirement is lower (since only never-used blocks are not copied)
(2) point in time recovery is possible
(3) direct backup to tape possible (no need for disk backup)
Cons:
(1) restore time varies depending on the day of the week the db failed
(2) you have to take a full backup regularly, perhaps once a week
(3) no validation unless you use validate backupset (takes resources)
So, as you can see, there are pros and cons to each approach. You have to decide for yourself which one weighs more (or less) to come to a conclusion.
Hope this helps.
Arup Nanda

How to check & resolve block corruption if no RMAN backup is there?

*<<+MY Findings+>>*
to check block corruption :
(run command)
select * from v$database_block_corruption;
DB_VERIFY is useful in these situations:
When block corruption is expected;
Forecast any future problems w.r.t. database file/ block corruption;
When you restore files from a tape. It will help knowing if the first file pulled from tape is corrupt, instead of spending hours to extract all of them.
to check block corruption
DBVerify
C:\>dbv userid=nfadmin/nfadmin file=+DG1/nfdb/datafile/low_s_data.304.782536883 feedback=10000 blocksize=8192
can use DBMS_REPAIR to detect and repair corrupt blocks in tables and indexes
BEGIN
DBMS_REPAIR.admin_tables (
table_name => 'REPAIR_TABLE',
table_type => DBMS_REPAIR.repair_table,
action => DBMS_REPAIR.create_action,
tablespace => 'USERS');
DBMS_REPAIR.admin_tables (
table_name => 'ORPHAN_KEY_TABLE',
table_type => DBMS_REPAIR.orphan_table,
action => DBMS_REPAIR.create_action,
tablespace => 'USERS');
END;
Question* :::how to check & resolve block corruption if no RMAN backup is there?

http://www.oracle.com/technetwork/database/focus-areas/availability/maa-datacorruption-bestpractices-396464.pdf
http://www.oracle-base.com/articles/misc/detect-and-correct-corruption.php

RMAN - Last Successful backup

Dear Experts,
RDBMS - 11.1.0.7
I would like to know if anyone of you have experienced this issue.
Below is my backup report (queried from recovery catalog) and see DB1 database, I see Last successful Incremental backup date showing 01/01/0001 while the actual date was from a week back. However, Archivelog backup shows correct dates. Any thoughts?
NAME           DBID DBBKP            ARCBKP
DB1   2145674345 01/01/0001 00:00 09/10/2012 07:54
DB2   1634931935 01/01/0001 00:00 08/10/2012 19:09
DB3    901592423 01/01/0001 00:00 09/10/2012 07:54


select start_time,end_time,status from v$rman_status
order by 1
or
select
SESSION_KEY, INPUT_TYPE, STATUS,
to_char(START_TIME,'mm/dd/yy hh24:mi') start_time,
to_char(END_TIME,'mm/dd/yy hh24:mi') end_time,
round((end_time-start_time)*1440,2) "Minutes"
from V$RMAN_BACKUP_JOB_DETAILS
order by session_key desc;
Asif @ How to find RMAN backups are successful

Query to check how far RMAN backup completed?

is there a way to check how far RMAN backup been completed. What is through put etc.
Let me know if you know any.
Thanks,
RK

Additional info...Monitoring RMAN Through V$ Views and Query V$ Views to Identify Bottlenecks.

How to check RMAN backup report or log

Hi Guys,
I have RMAN schduled to backup my database daily.
Please what are the steps to check the report of the backup to see what was actually backed up and if it backup up ok
Thanks

Use "LIST BACKUP" to display information about backup sets, proxy copies, and image copies. With LIST command you can list the following:
- Backups and copies that do not have the status AVAILABLE in the RMAN repository
- Backups and copies of datafiles that are available and can possibly be used in a restore operation
- Specified archived logs, backup sets, backup pieces, control file copies, datafile copies, and proxy copies
- Backups and copies restricted by tag, completion time, recoverability, or device
- Incarnations of a specified database or of all databases known to the repository
- Stored scripts in the recovery catalog
Examples on how to use LIST command are listed below:
RMAN> LIST BACKUP;
RMAN> LIST EXPIRED BACKUP;
RMAN> LIST BACKUP OF DATABASE;
RMAN> LIST BACKUP SUMMARY;
RMAN> LIST BACKUP BY FILE;
RMAN> LIST ARCHIVELOG ALL;
RMAN> LIST COPY OF DATABASE ARCHIVELOG ALL;
RMAN> LIST COPY OF DATAFILE 1, 2, 3;
RMAN> LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 1437;
RMAN> LIST BACKUPSET OF DATAFILE 1;You can use the VALIDATE keyword of the BACKUP command to do the following:
- Check datafiles for physical and logical corruption
- Confirm that all database files exist and are in the correct locations
For example, you can validate that all database files and archived redo logs can be backed up by running a command as follows:
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;I suggest you read Oracle® Database Backup and Recovery Manuals:
http://www.oracle.com/pls/db102/portal.portal_db?selected=3

How to check the size of rman backups to tape

instead of asking tsm person to check, how do I check how big is a rman backup sent to tape?

query to find the backupset sizes
SQL> select ctime "Date"
2       , decode(backup_type, 'L', 'Archive Log', 'D', 'Full', 'Incremental') backup_type
3       , bsize "Size MB"
4 from (select trunc(bp.completion_time) ctime
5          , backup_type
6          , round(sum(bp.bytes/1024/1024),2) bsize
7     from v$backup_set bs, v$backup_piece bp
8     where bs.set_stamp = bp.set_stamp
9     and bs.set_count = bp.set_count
10     and bp.status = 'A'
11     group by trunc(bp.completion_time), backup_type)
12 order by 1, 2;
Date      BACKUP_TYPE    Size MB
03-JUL-10 Archive Log       7.31
03-JUL-10 Full             29.81
03-JUL-10 Incremental    2853.85
04-JUL-10 Archive Log       3.59
04-JUL-10 Full              7.45
04-JUL-10 Incremental       3.05

How is RMAN backup different than the other conventional methods of backup

Hello to all,
I have a question if somebody can please answer my queries
How & Why is RMAN backup different than the other conventional methods of backup.
What is different in the way a database is backed up using RMAN.
I am very well aware of the capabilites of RMAN to recover from a loss , but I did like to know as to how RMAN makes it possible to go about it.
Please answer
Altaf

You can start with the reading of the Oracle docs:
Backup and Recovery Basics
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/toc.htm
Backup and Recovery Quick Start Guide
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14193/toc.htm
Backup and Recovery Reference
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/toc.htm

How to find RMAN backups are successful

Hi,
I am using RMAN for 10g databases. How can i ensure that the backups am taking thru RMAN are successful? is there any command.

select
SESSION_KEY, INPUT_TYPE, STATUS,
to_char(START_TIME,'mm/dd/yy hh24:mi') start_time,
to_char(END_TIME,'mm/dd/yy hh24:mi') end_time,
round((end_time-start_time)*1440,2) "Minutes"
from V$RMAN_BACKUP_JOB_DETAILS
order by session_key desc;
Regards
Asif Kabir

Manually check the rman backup output

Can anybody guide me how to manually check the rman backup output,
There are like 300+ DBs and we are using recovery catalog .....
Plz send me some example to do that....like i have to check list, report or rman logs?

1) set environment variable
$ export NLS_DATE_FORMAT='DD-MON-YYYY HH24:MI:SS'
RMAN> connect target * connect catalog *
RMAN> list backup summary;
RMAN> list backup of database completed between "to_date('2007-12-20 03:00:00','YYYY-MM-DD HH24:MI:
SS')" and "to_date('2007-12-20 06:00:00','YYYY-MM-DD HH24:MI:SS')";
My manager ask me to check rman backup report manually & this is what i am forwarding him that i will check , let me know if its not right........

Sql to check RMAN backup size

Hi All
Kinldy tell me how i can check the RMAN Backup size from sql command. I am taking Full,Incrimental,Cumulative and Archive log backup.
Thanks
Krishna

try this,
SQL> select ctime "Date"
2       , decode(backup_type, 'L', 'Archive Log', 'D', 'Full', 'Incremental') backup_type
3       , bsize "Size MB"
4 from (select trunc(bp.completion_time) ctime
5            , backup_type
6            , round(sum(bp.bytes/1024/1024),2) bsize
7     from v$backup_set bs, v$backup_piece bp
8     where bs.set_stamp = bp.set_stamp
9     and bs.set_count = bp.set_count
10     and bp.status = 'A'
11     group by trunc(bp.completion_time), backup_type)
12 order by 1, 2;
Date      BACKUP_TYPE    Size MB
03-JUL-10 Archive Log       7.31
03-JUL-10 Full             29.81
03-JUL-10 Incremental    2853.85
04-JUL-10 Archive Log       3.59
04-JUL-10 Full              7.45
04-JUL-10 Incremental       3.05

Can not recover table from rman backup

For testing I want to recover deleted table from rman backup.
I have make vm of oracle 11g. the following step i have applied but could not recover the table.
rman> backup database ;
On sqlplus create login as scott/tiger
create table scott.emp1(col1 varchar2(10));
insert into emp1(col1) value('Yasir ') ;
commit ;
select * from emp1 ;
it shows me one row successfully.
Now i have login the sys as sysdba
sqlplus> alter system switch logfile ;
after this i have drop the table .
Now to recover the table i have restored database on same vm.
rman>restore database ;
rman> recover database ;
rman> alter database open ;
on sqlplus i have issued
sqlplus> select * from scott.emp1 ;
table or view does not exist.
any help how to recover the deleted table from rman backup

Hi,
Check this test case
SQL> create table TEST2 as select * from emp;
Table created.
SQL> select count(*) from TEST2;
COUNT(*)
15
SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
TO_CHAR(SYSDATE,'DD-
10-SEP-2013 10:57:05
SQL> alter system switch logfile;
System altered.
SQL> drop table TEST2 purge;
Table dropped.
SQL> shu immediate
[oracle@vnode MYSHELL]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DDTEST (DBID=1667776968, not open)
RMAN> run{
set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
restore database;
recover database;
alter database open resetlogs;
}2> 3> 4> 5> 6>
media recovery complete, elapsed time: 00:00:02
Finished recover at 10-SEP-13
database opened
RMAN> exit
SQL> set lin 200 pages 100
SQL> select count(*) from test2;
COUNT(*)
15
HTH

RMAN Backup successful check - efficient method

Similar Messages

Maybe you are looking for