Re: Separating online redo logs from database files
Date: Thu, 8 Apr 2010 10:50:20 -0400
Message-ID: <y2n9256898f1004080750ha5cc6241p24de71a9857d609f_at_mail.gmail.com>
I don't bother separating them out anymore. These days disks are getting bigger and bigger. I can't afford to isolate the redo logs, its too much wasted space. Especially for small environments.
In large SAN environments you probably won't be able to have any control over it anyways.
On Thu, Apr 8, 2010 at 9:25 AM, Denis <denis.sun_at_yahoo.com> wrote:
> > What are general pros and cons on separating redo logs from database
> files? Both database and redologs are already residing on RAID1
>
> > volumes. So this separation would only mean – move redo logs to separate
> mount point (RAID1, still).
>
>
>
>
>
> From my experience and at least in my env, I think seperation of redo and
> data file into different mont point is desirable. We use NetApp snapshot as
> backup solution. When restoring data files, we can choose not to restore
> redo log files if they are separated. Learned from the storage team,
> Snapshot restore can not proceed at data file level as RAMN does. Hope I got
> this impression right.
>
>
>
>
>
> Yu "Denis" Sun
>
> Oracle DBA
>
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Apr 08 2010 - 09:50:20 CDT