RE: ASM and archivelogs - what if....

From: mike boligan <>
Date: Tue, 5 Feb 2013 12:33:00 -0800 (PST)
Message-ID: <>


    I know you are on, but if you have 11.2 or are planning on moving to 11.2 soon, you may want to read bug 10388660, it happens when using rman duplicate and have archived redo logs stored on ASM.


  • On Tue, 2/5/13, <> wrote:

From: <> Subject: RE: ASM and archivelogs - what if.... To:
Date: Tuesday, February 5, 2013, 11:54 AM

Can I answer "no" without fear of reprisal? :)

I'm new to ASM and I don't think any of our guys are backing up ASM metadata.  I'll have to poll them.


-----Original Message-----
From: Wolfgang Breitling [] Sent: Tuesday, February 05, 2013 10:38 AM To: Taylor Christopher - Nashville
Subject: Re: ASM and archivelogs - what if....

Nothing directly to do with the archive logs, but you do back up your ASM metadata as well, don't you. That will help in the case of header corruption but of course not in the case of disk corruption. Hence the need for frequent (based on your recovery SLA)  archive log backups to a destination, tape or disk on another, independent storage system (i.e. your DR site).

On 2013-02-05, at 6:23 AM, <> <> wrote:

> Env:
> RAC 3 Nodes RHEL 5.6 64-bit
> ASM 3 Nodes RHEL 5.6 64-bit
> We have our archivelogs stored solely in a diskgroup managed by the ASM instance.  We don't write the archivelogs to a cooked filesystem.
> Nightly we take an RMAN backup and verification to a cooked filesystem.
> I'm curious if I have a potential problem area with this setup in that I ask the question:
> "What happens if I lose my ASM information - such as ASM disk header corruption or a severe SAN problem that corrupts the disk data?"


Received on Tue Feb 05 2013 - 21:33:00 CET

Original text of this message