> Matt
> >
> > --
> > Matthew Zito
> > GridApp Systems
> > Email: [EMAIL PROTECTED]
> > Cell: 646-220-3551
> > Phone: 212-358-8211 x 359
> > http://www.gridapp.com
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [ma
8211 x 359
> http://www.gridapp.com
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> > Behalf Of Jesse, Rich
> > Sent: Thursday, August 14, 2003 11:49 AM
> > To: Multiple recipients of list ORACLE-L
> > Subject:
Hi!
I usually only tolerate write caching on storage subsystems when we are
dealing with expensive boxes like EMCs Clariion or Symmetrix. I too have
seen caches fail on entry level boxes like Sun A1000 etc...
Tanel.
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL
---
> From: Tanel Poder [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 14, 2003 3:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Storage Cache - WriteThrough or WriteBack
>
>
> Hi!
>
> I usually only tolerate write caching on storage subsystems
&
rom: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Jesse, Rich
> Sent: Thursday, August 14, 2003 11:49 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Storage Cache - WriteThrough or WriteBack
>
>
> Like any good DBA/SA should say "It depends.
I've begun a debate in my organisation about
caches on storage systems.
If an Oracle Database, including Redo Log files,
is on RAID1 or RAID1+0 or RAID5 on the storage/SAN
and the storage/SAN system provides a cache, should
the cache be WriteThrough or WriteBack ?
I prefer WriteThrough -- partic
[EMAIL PROTECTED]>
cc:
Subject: RE: Storage Cache - WriteThrough or WriteBack
As long as your cache is protected somehow, whether its RAIDed (a la EMC) or
mirrored (a la Hitachi), the vast majority of risk associated with
write-back cache is mitigated. Even with prot
