Subject | Is gifix after backup/restore redundant? |
---|---|
Author | Bob Murdoch |
Post date | 2005-02-03T15:33:04Z |
Early last year, after a bout with a corrupted database, I implemented
a nightly backup/restore, and then run gfix -v -f against the newly
restored database. This process ensures a one-day old roll back in
the case of an emergency.
Now that the database is 21GB, the gfix portion of the process is
taking over an hour. I'm wondering whether this is a redundant
function, since the database has just been successfully restored?
A simple question - is there any chance that a newly restored database
could be anything less than 'perfect'?
tia,
Bob M..
a nightly backup/restore, and then run gfix -v -f against the newly
restored database. This process ensures a one-day old roll back in
the case of an emergency.
Now that the database is 21GB, the gfix portion of the process is
taking over an hour. I'm wondering whether this is a redundant
function, since the database has just been successfully restored?
A simple question - is there any chance that a newly restored database
could be anything less than 'perfect'?
tia,
Bob M..