RMAN - aborted incremental backups and recovery
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: RMAN - aborted incremental backups and recovery

  1. #1
    Join Date
    Oct 2002
    Posts
    807

    RMAN - aborted incremental backups and recovery

    Got a question on RMAN recovery with aborted incremental backups.
    I suppose I can simulate this scenario..but thought I'd post the question here to get your opinion first.

    Lets say I take a "Level 0" backup on Sunday; a "level 1" (cumulative or differential) on Monday and backup archivelogs by the hour.

    Something goes wrong during Monday's Level 1..say the tape gets jammed. And I abort or kill the Incremental backup by doing a "kill -9" and do nothing else.

    Then, say something goes wrong on Tuesday morning and I need to perform a full database recovery. When I issue a "restore database;" followed by a "recover database;" - what happens? Is RMAN intelligent enough to realize that the level1 backup was hosed, and it ought to restore Level0 followed by all the archivelogs? (Or does RMAN expect a DBA to inform the catalog about the failed backup everytime by explicitly removing the failed backup piece or something?. I would hope not!)

    Thanks, Anand

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    If the first piece failed to write to tape, yes RMAN would know to skip that backup. However, if some pieces got written to tape oracle would not know the tape went bad. In that case, you would have to inform RMAN that the backup set was unavailable and do your restore using the archived logs.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  3. #3
    Join Date
    Oct 2002
    Posts
    807
    Aargh..that sucks. How does it work in the real world? Do DBA's really keep track of backups by keeping the catalog upto date and deleting backup pieces manually everytime a backup fails? Or do they back up the rman logfiles as well and leave it at that? Come "show time" (or database recovery time), they learn it the hard way - that one of the incrementals was hosed. Then restore the backup RMAN logfiles to verify that a backup had indeed failed on such and such day. And THEN go about removing the pieces from the catalog?

    Sorry about whining!

    Thanks for your response Jeff.

  4. #4
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187
    The rman logs are emailed to me each morning.

    What's the point of taking backups if they be no good?
    I'm stmontgo and I approve of this message

  5. #5
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    When my backups fail (2 times last year), I fix the recovery catalog, and do a Level 0 at the next opportunity.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  6. #6
    Join Date
    Oct 2002
    Posts
    807
    Yes, I expect to be notified when a backup fails as well and realize the importance of good backups. That wasn't the issue.

    My concern was do you (DBA's in general) immediately follow up on a failed backup by updating the catalog? "We" (I'm the only DBA here though) managed several customers and their databases..and like everyone else, I have lots of things/projects on my plate. It is going to be a management nightmare for me to take the time to update catalogs everytime a backup fails. Backup failures are not so uncommon here..blame it on the data centre, the vendors, the storage or whoever.

  7. #7
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    IMHO, backup & recovery is the most important aspect of a DBA's role. Projects/tasks/etc. are secondary when compared to B&R.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  8. #8
    Join Date
    Oct 2002
    Posts
    807
    Thanks Jeff. Got it. I guess I'm gonna have to do the same.

  9. #9
    Join Date
    Feb 2003
    Location
    Leeds, UK
    Posts
    367
    Am I glad I read this thread! I always assumed that RMAN knew when a backup failed midway it was bad . Looks like I'll be deleting backup sets in future.

  10. #10
    Join Date
    Aug 2002
    Location
    Bangalore, India
    Posts
    405
    Originally posted by Axr2
    Aargh..that sucks. How does it work in the real world? Do DBA's really keep track of backups by keeping the catalog upto date and deleting backup pieces manually everytime a backup fails? Or do they back up the rman logfiles as well and leave it at that? Come "show time" (or database recovery time), they learn it the hard way - that one of the incrementals was hosed. Then restore the backup RMAN logfiles to verify that a backup had indeed failed on such and such day. And THEN go about removing the pieces from the catalog?

    Sorry about whining!

    Thanks for your response Jeff.
    DBAs are there to take care of all those deviations from scheduled routien activities.. no way you avoiding that.. 100% automation is not good and not efficient too..
    -nagarjuna

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width