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
GBAK should validate data during backup, not restore [CORE424] #768
Comments
Commented by: Alice F. Bird (firebirds) Date: 2005-04-06 04:33 As I said before, unrestorable backups aren't backups. The Just imagine this scenario: I've got a daily backup tool If GBAK generated an error during backup six months ago, In fact, I'm not exactly asking for an integrity checker. If By the way, if GBAK is intended for moving data only, then |
Commented by: Alice F. Bird (firebirds) Date: 2005-04-05 22:49 I disagree, GBAK not should be responsible for checking There is the need to have a integrity checker, but this should Given the design of the GBAK utility, I wonder if we should be Comments? |
Commented by: Alice F. Bird (firebirds) Date: 2004-05-25 17:54 Maybe simpler would be a way for GBAK to ignore this NOT Or, more generally, provide a flag to restore only data without It would allow one to correct the DB structure (like redefining I'm stuck in this situation currently from a precious table GBAK |
Modified by: @pcisarWorkflow: jira [ 10448 ] => Firebird [ 14736 ] |
Commented by: Cosmin Apreutesei (cosmin_ap2) I happily made lots of useless backups myslef with gbak, never knowing they were useless, because of this. CORE1030 is a related request. |
Submitted by: ironman-lok (ironman-lok)
Votes: 11
SFID: 859615#
Submitted By: ironman-lok
GBAK detects some validation errors (like NOT NULL
fields with null values) during the restore, but no errors
occurs during backup.
Example: create a table, insert some rows, then use
alter table to add a NOT NULL field. Then you make a
backup, and GBAK won't detect any error, but when you
try to restore that backup (even with -n), a validation
error will occur.
I'm not sure if it's a bug or a feature request, however,
IMHO that validation should be done during BACKUP, as
an unrestoreable backup isn't a backup.
PS: Sorry if I've made any mistake in my spelling or
something, my english isn't perfect.
The text was updated successfully, but these errors were encountered: