Skip to content

Update of nbackup documentation #12

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

Merged
merged 21 commits into from
Jul 25, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update firebird-gfix.adoc
sentenses per line
  • Loading branch information
alexeykovyazin authored Jul 25, 2020
commit a857d1ce66a368ab487f25f6e19a3b8d405a60b5
16 changes: 11 additions & 5 deletions src/docs/asciidoc/en/firebirddocs/gfix/firebird-gfix.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -1350,11 +1350,16 @@ gfix -m[end] -ignore _database_name_

In case of a corruption, gfix returns the summary of errors found:

* Number of record level errors - number of corrupted records found during gfix work. These records are not correct - essentially, lost.
* Number of index page errors - number of index pages in bad indices. When even the only key is incorrect in index, gfix marks whole index as bad, so number of pages usually is high. However, since it does not affect user's data, and due to the fact that corrupted indices will be recreated during backup/restore, this can be considered as for your information only.
* Number of transaction page errors - number of transaction pages which were fixed by gfix. Usually if you see this message it means that gfix did its job and now transactions are Ok.
* Number of record level errors - number of corrupted records found during gfix work.
These records are not correct - essentially, lost.
* Number of index page errors - number of index pages in bad indices.
When even the only key is incorrect in index, gfix marks whole index as bad, so number of pages usually is high.
However, since it does not affect user's data, and due to the fact that corrupted indices will be recreated during backup/restore, this can be considered as for your information only.
* Number of transaction page errors - number of transaction pages which were fixed by gfix.
Usually if you see this message it means that gfix did its job and now transactions are Ok.
* Number of BLOB errors - number of bad BLOB pages, it indicates number of bad BLOBs.
* Number of database page errors - this is the overall number of database pages, which were visited and changed/marked as bad by gfix. Again, this is mostly for your information.
* Number of database page errors - this is the overall number of database pages, which were visited and changed/marked as bad by gfix.
Again, this is mostly for your information.

[NOTE]
====
Expand All @@ -1371,7 +1376,8 @@ gbak -create _backup1.fbk_ _new_database_name_

If backup and restore with gbak completed successfully, database is recovered.

Since Firebird 3.0, gbak tools has very useful option: -SKIP_D[ATA]. It allows to specify comma-separated list of tables to be skipped from the backup:
Since Firebird 3.0, gbak tools has very useful option: -SKIP_D[ATA].
It allows to specify comma-separated list of tables to be skipped from the backup:
----
gbak -b -skip_data country,currency localhost/3050:C:\Data\inventory.fdb C:\data\111.gbk -user SYSDBA -pass masterkey
----
Expand Down