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

From: John Hurley <hurleyjohnb_at_yahoo.com>
Date: Tue, 5 Feb 2013 09:46:03 -0800 (PST)
Message-ID: <1360086363.58047.YahooMailRC_at_web181204.mail.ne1.yahoo.com>

I for one am not a believer in using ASM based storage for either archivelogs or rman disk backups.  Much prefer a regular cooked file system for these items.

Part of every rman backup cycle of a database that uses asm should be making sure that your asm instance and diskgroups are recoverable.

Personally I recommend periodic testing of a recovery to include these steps:

1. blow away all your oracle and grid directory structures
2. recover your oracle and grid software
3. bring up asm instance ( so you better have a backup of init files / stuff like that ).
4. create FORCE your asm diskgroups ( re-initialize them ).
5. recover your database(s) on those disk groups
   • Original Message ---- From: "Christopher.Taylor2_at_parallon.net" <Christopher.Taylor2_at_parallon.net> To: breitliw_at_centrexcc.com Cc: oracle-l_at_freelists.org Sent: Tue, February 5, 2013 11:56:43 AM Subject: RE: ASM and archivelogs - what if....

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.

Chris

-----Original Message-----
From: Wolfgang Breitling [mailto:breitliw_at_centrexcc.com] Sent: Tuesday, February 05, 2013 10:38 AM To: Taylor Christopher - Nashville
Cc: oracle-l_at_freelists.org
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, <Christopher.Taylor2_at_parallon.net> <Christopher.Taylor2_at_parallon.net> wrote:

> Env:
> 10.2.0.4 RAC 3 Nodes RHEL 5.6 64-bit
> 10.2.0.4 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?"
>

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l

Received on Tue Feb 05 2013 - 18:46:03 CET