RE: ASM & split-mirrors

From: Hubler, Daniel <daniel.hubler_at_aurora.org>
Date: Mon, 4 Mar 2013 01:30:07 +0000
Message-ID: <850425C04FB76547AC0ED12C5F7E0B800F06FB_at_HEIMSEAT021.ahc.root.loc>

That sounds pretty routine.
Thanks.
One thing is bothering me. . . . .

When the LUNs are established on the TARGET side, they will have different names/identifiers than on the source side.

That is, /dev/diska on the source side will become /dev/diskx on the target.

How does that get reconciled within ASM?

From: Ls Cheng [mailto:exriscer_at_gmail.com] Sent: Sunday, March 03, 2013 12:47 PM
To: Hubler, Daniel
Cc: oracle-l_at_freelists.org
Subject: Re: ASM & split-mirrors

Hi

The process is not much different compared with other File System Split Mirrors.

Make sure each each Disk Group contains only one database, redo and controlfiles are not in FRA or DATA diskgroups. For ASM I suually have 4 Disk Groups

DATA
ARCH (or FRA)
REDO1
REDO2 When doing Snap or third mirror:

source:

1. alter system archive log current
2. alter database begin backup
3. snap data disk group LUNs
4. alter database end backup
5. alter system archive log current
6. snap archived log disk group LUNs
7. backup controlfile

target (no disk groups and database exists):

1. present the snap to the server or servers (if RAC)
2. in ASM mount the disk groups, DATA, ARCH
3. create init.ora and make controlfile point to DATA and ARCH Disk Groups
4. startup nomount
5. restore controlfile from the backup
6. alter database mount
7. recover database until cancel using backup controlfile
8. rename redo logs so they point to DATA and ARCH disk groups
9. alter database open resetlogs
10. change db name with NID if you want to call it something else

I think I havent missed any step

Regards

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

Received on Mon Mar 04 2013 - 02:30:07 CET