| Subject | Re: [ib-support] Problem in backing up |
|---|---|
| Author | Ann W. Harrison |
| Post date | 2003-01-08T20:45:16Z |
At 01:31 PM 1/6/2003 +0100, Pete Clark wrote:
(or any other humanly comprehensible language). What was in
the mind of the writer, I think, is that yours is a secondary
attachment. Since all of us consider ourselves primary,
confusion is rampant.
from gbak or in the server log?
database can be corrupted - most of them make no difference
unless you touch the bad page, at which point the error goes
from benign to catastrophic. That's why things like sweep
and backup tend to get these errors - they read all the data.
However, they won't find bad index pages since neither reads
indexes on user data.
to fix the problem can easily cause data loss. You'll tend
to lose a whole page of records if you lose any. With worse
luck, you can lose a whole set of pages of data. Worse luck
still can leave you with nothing you can see at all, even
though all the data is actually there. Happily, both the
IBSurgeon guys and I can usually get data back - oddly enough
a single page of lost data is harder to get than a whole database.
what you find out.
Regards,
Ann
www.ibphoenix.com
We have answers.
>Surely there should be a full stop, as inNot all programmers are great masters of the English language
>-secondary server attachments. Cannot validate databases
>
>I thought that it meant
>"The secondary server attachments are not able to validate the database"
>which made no sense at all to me...
(or any other humanly comprehensible language). What was in
the mind of the writer, I think, is that yours is a secondary
attachment. Since all of us consider ourselves primary,
confusion is rampant.
>I just hope that this is what I should be doing - remember, theDid you happen to notice if there were any error messages, either
>original problem was that I could not back up the database.
from gbak or in the server log?
>I would love to understand about how the database can function whenNo, not usually. There are lots of different ways that the
>apparently faulty - I would guess that the database would slow down a
>lot when working with a faulty structure.
database can be corrupted - most of them make no difference
unless you touch the bad page, at which point the error goes
from benign to catastrophic. That's why things like sweep
and backup tend to get these errors - they read all the data.
However, they won't find bad index pages since neither reads
indexes on user data.
> I would also guess that oneIf an index is corrupt, then no data is lost, though trying
>or more records could be lost. Is that correct?
to fix the problem can easily cause data loss. You'll tend
to lose a whole page of records if you lose any. With worse
luck, you can lose a whole set of pages of data. Worse luck
still can leave you with nothing you can see at all, even
though all the data is actually there. Happily, both the
IBSurgeon guys and I can usually get data back - oddly enough
a single page of lost data is harder to get than a whole database.
>Loss of data is not important to me,Loss of data is extremely important to me, so do let us know
what you find out.
Regards,
Ann
www.ibphoenix.com
We have answers.