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

From: <>
Date: Tue, 5 Feb 2013 12:25:25 -0600
Message-ID: <>

Ah I think ASM metadata backup is only on 11g?

After reading/researching, it seems that for 10g you should use a FAILGROUP.

Sigh. There are certain things about Oracle technology (I guess any technology really) that make me feel like I'm back in the 80s once in a while. (Failure of expectations to match reality I guess)


-----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 - 19:25:25 CET

Original text of this message