Re: [Veritas-bu] RMAN backup status

2 + 2 makes 4 cents.


I also have user backups of my oracle ( and informix) databases.

The policies have "user" schedules.
The scripts are on each of the servers with the database.

The scripts are scheduled via cron.

The scripts do the backup of the database, and in my scripts I check
return codes.

So if the backups fail anywhere my testing for return codes will send an
email to the DBA's that the database backup failed.  The Netbackup
people also get the emails.  So in the morning I can verify that if I
got a failed backup; that the dba's fixed it and reran it.

I rely more on my scripts to test at each stage then to just hope the
master tells me what I want to know.

Using the scripts give us more control, and gives the DBA's more control
without having to give them access to the Netbackup console.

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Wayne T
Smith
Sent: Friday, January 16, 2009 2:50 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] RMAN backup status

My 2 cents ...

The master server view of an Oracle Agent backup is just part of the
story.

    * Your script/template can fail to perform one of its functions and
      not even try to backup something critical.  From the Master, the
      backup looks perfect.  As a minimum, you must have and
      periodically examine logs from your client backup scripts.
    * Your script/template might try to backup archive redo log files,
      but if rman finds none to be backed up, the backup, already
      started, is reported by the master as failed.

In the 1st case, the master is ignorantly optimistic; in the 2nd case, 
the master is ignorantly pessimistic.  Each case can probably be 
minimized by sufficient programming in the client script, but I'll guess

that many or most scripts used today aren't perfect in this sense.

You might also want to look into RMAN's "RESTORE DATABASE VALIDATE;" as 
part of your verification of Oracle backups.  It doesn't physically 
write anything, but does at least some of what you seem to want to be 
able to confirm, albeit from a different perspective.

cheers, wayne

nbujohnson wrote, in part,  on 2009-01-13 1:49 PM:
> Thanks for the script Carl, but this is also a client based script
which i have to schedule on each db client .what i am looking here is a
script which i can scedule on my matser & which report all the rman
failures only,basically i need a single report which can be easily
checked for all the rman failures.
>
> Thanks,
> John
>
>
+----------------------------------------------------------------------
> |This was sent by nbujohnson AT googlemail DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
>
+----------------------------------------------------------------------
>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>   
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu