Subject | Re: RE: [IB-Architect] Journaling support? |
---|---|
Author | jerzy.tomasik@ti.com |
Post date | 2000-03-24T05:18:27Z |
--- In IB-Architect@onelist.com, "David Berg" <DaveBerg@T...> wrote:
which leave a corrupted file, however, there are other problems
that are not solved as easily:
1. Drive failure could leave you without any file. Shadowing
or mirroring could solve this, but for a very large database
it's quite expensive.
2. It doesn't help for situations where human errors or acts
of malice force you to restore the database to a point in the
past, hopefully not too distant ;-)
I may have been under a misconception, but what I'm looking for
is a mechanism similar to Oracle's archivelogs, and I thought
that journaling was more or less equivalent.
Bye,
Jerzy
> Interbase doesn't require Journaling because of it's versionedrecord
> support. If the system crashes and restarts, all records markedwith a
> version # corresponding to an uncommitted transaction are markedinvalid and
> thrown away as they are encountered. This allows Interbase torestart
> instantly after a crash without having to reload from a Journal,and with no
> data integrity problems.have when
>
> Further, it avoids many of the locking problems that other servers
> transactions hit the same area, and it guarantees 100%re-readability of
> data within a transaction with no performance or locking penalties.I agree with you that MGA solves the problem for system crashes
which leave a corrupted file, however, there are other problems
that are not solved as easily:
1. Drive failure could leave you without any file. Shadowing
or mirroring could solve this, but for a very large database
it's quite expensive.
2. It doesn't help for situations where human errors or acts
of malice force you to restore the database to a point in the
past, hopefully not too distant ;-)
I may have been under a misconception, but what I'm looking for
is a mechanism similar to Oracle's archivelogs, and I thought
that journaling was more or less equivalent.
Bye,
Jerzy
>------------------------
> -----Original Message-----
> From: jerzy.tomasik@... [mailto:jerzy.tomasik@...]
> Sent: Thursday, March 23, 2000 7:44 PM
> To: IB-Architect@onelist.com
> Subject: [IB-Architect] Journaling support?
>
>
> From: jerzy.tomasik@...
>
> I remember seeing "Journaling" in old InterBase manuals (3.3)
> but I've never used it. Today I've tried to find out how
> to set it up in the 6.0 beta, and to my surprise, I couldn't
> find it anywhere in the documentation. I've gone back to
> version 4.0 and it looks like journaling was already
> removed (for example "enable" keyword not in gfix).
>
> Is there any history behind it? Are there any plans to
> resurrect journaling?
>
> IMHO, journaling is essential for 7x24 applications
> where up to the minute recovery is a must.
>
> Is there an alternative mechanism that I'm not seeing?
>
> Bye,
> Jerzy
>
>
>
>
>
>
> ------------------------------------------------
> Special Offer-Earn 300 Points from MyPoints.com for trying @Backupfiles.
> Get automatic protection and access to your important computer
> Install today:------------------------
> http://click.egroups.com/1/2344/3/_/_/_/953865820/
> ------------------------------------------------
>
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com