Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
musman asked how to recover a bad chunk or copy one chunk to another. PC User (Art S. Kagel) said to replace the drive, relink the chunk path and restore the dbspace from archives, and to use mirroring or RAID1/3/4/10 in future, not RAID5. Tim Schaefer asked why Informix mirroring; Art said it was easiest to implement for a site with no redundancy.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
musman@my-deja.com — — source: Informix-list mailing list archive (1991-1998)
Hi
If one chunk goes bad, what are the various methods to recover the
chunk or how to copy one chunk to another.
Any suggestions?
regards
usman
musman@iffco.com
Sent via Deja.com http://www.deja.com/
Before you buy.
↪ replying to musman@my-deja.com
PC User — — source: Informix-list mailing list archive (1991-1998)
musman@my-deja.com wrote:
> Hi
>
> If one chunk goes bad, what are the various methods to recover the
> chunk or how to copy one chunk to another.
>
The best you can do is replace the bad drive, relink the chunk path link
to the new
partition/device, and restore the entire dbspace from the latest
archive(s).
>
> Any suggestions?
Several:
Informix Mirroring!
OS Mirroring!
RAID1!
RAID3!
RAID4!
RAID10!
Art S. Kagel
PS - Notice the conspicuous absence of RAID5.
↪ replying to PC User
Tim Schaefer — — source: Informix-list mailing list archive (1991-1998)
Art,
I'm curious why you recommend Informix mirroring.
Thanks in advance...
Tim
PC User wrote:
>
> musman@my-deja.com wrote:
>
> > Hi
> >
> > If one chunk goes bad, what are the various methods to recover the
> > chunk or how to copy one chunk to another.
> >
>
> The best you can do is replace the bad drive, relink the chunk path link
> to the new
> partition/device, and restore the entire dbspace from the latest
> archive(s).
>
> >
> > Any suggestions?
>
> Several:
>
> Informix Mirroring!
> OS Mirroring!
> RAID1!
> RAID3!
> RAID4!
> RAID10!
>
> Art S. Kagel
>
> PS - Notice the conspicuous absence of RAID5.
--
.
.-
.--
.---
.---- Tim Schaefer
.----- tschaefe@bellsouth.net
.---- http://www.inxutil.com
.---
.--
.-
.
↪ replying to Tim Schaefer
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
Tim Schaefer wrote:
> Art,
>
> I'm curious why you recommend Informix mirroring.
I's a viable option. If M. Musman lost data when a chunk went south,
obviously
the site is not using ANY redundancy and Informix mirror is the quickest and
easiest
to implement. Most of the other redundancy options would require
reconfiguring
their entire disk farm. Therefore I placed that option at the top of the
list. Looking
back I probably placed the options in order of increasing preference.
Art S. Kagel
>
>
> Thanks in advance...
>
> Tim
>
> PC User wrote:
> >
> > musman@my-deja.com wrote:
> >
> > > Hi
> > >
> > > If one chunk goes bad, what are the various methods to recover the
> > > chunk or how to copy one chunk to another.
> > >
> >
> > The best you can do is replace the bad drive, relink the chunk path link
> > to the new
> > partition/device, and restore the entire dbspace from the latest
> > archive(s).
> >
> > >
> > > Any suggestions?
> >
> > Several:
> >
> > Informix Mirroring!
> > OS Mirroring!
> > RAID1!
> > RAID3!
> > RAID4!
> > RAID10!
> >
> > Art S. Kagel
> >
> > PS - Notice the conspicuous absence of RAID5.
>
> --
> .
> .-
> .--
> .---
> .---- Tim Schaefer
> .----- tschaefe@bellsouth.net
> .---- http://www.inxutil.com
> .---
> .--
> .-
> .
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.