Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve GFIX abilities to full database integrity check [CORE2212] #2640

Open
firebird-automations opened this issue Nov 27, 2008 · 1 comment

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Smirnoff Serg (wildsery)

Votes: 2

For now, GFIX check of database did not guarantee full integrity, that backup-restore сycle did.
After GFIX works on database we may still get invalid (unrestorable) backup.

Please add the new option with check full data and structure integrity.
Of course, it must works faster than standart backup-restore сycle.

In terms of multigigabyte database, it will be salvation. Reserve server with full-day restoring is obsolete, choked with data.

@firebird-automations
Copy link
Collaborator Author

Modified by: Smirnoff Serg (wildsery)

description: For now, GFIX check of database did not guarantee full integrity, that backup-restore sycle did.
After GFIX works on database we may still get invalid (unrestorable) backup.

Please add the new option with check full data and structure integrity.
Of course, it must works faster than standart backup-restore sycle.

In terms of multigigabyte database, it will be salvation. Reserve server with full-day restoring is obsolete, choked with data.

=>

For now, GFIX check of database did not guarantee full integrity, that backup-restore сycle did.
After GFIX works on database we may still get invalid (unrestorable) backup.

Please add the new option with check full data and structure integrity.
Of course, it must works faster than standart backup-restore сycle.

In terms of multigigabyte database, it will be salvation. Reserve server with full-day restoring is obsolete, choked with data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant