{"id":433,"date":"2013-04-29T16:19:42","date_gmt":"2013-04-29T19:19:42","guid":{"rendered":"http:\/\/www.viazap.com.br\/?p=433"},"modified":"2013-04-29T16:19:42","modified_gmt":"2013-04-29T19:19:42","slug":"gbak-firebird-backup-and-restore","status":"publish","type":"post","link":"https:\/\/blog.clusterweb.com.br\/?p=433","title":{"rendered":"GBAK – Firebird Backup and Restore"},"content":{"rendered":"

GBAK is Firebird’s command line tool for online backup and restore of a complete database.<\/p>\n

GBAK is able to perform a backup while the database is running. There is no need to shut down the database during a GBAK backup. GBAK will create a consistent snapshot of the database at the time it starts running. You will, however, notice a perfomance degradation during the backup, so it is a good idea to backup at night. As GBAK visits all pages of the database, so it will also perform a garbage collection on the database.<\/p>\n

General Syntax<\/h2>\n
gbak <options> -user <username> -password <password> <source> <destination><\/pre>\n
Backup<\/h4>\n
For backups, <source> is the database you want to back up, <destination> is the file name of the backup file. The usual extension for the backup file is .fbk for Firebird and .gbk for InterBase.<\/p>\n
Only SYSDBA or the database owner can perform a backup. For multi-file databases, specify only the name of the first<\/i> file as the database name.<\/p>\n
Restore<\/h4>\n
For restores, <source> is the backup file and <destination> is the name of the database that is to be built up from the backup file. You will have to specify the -C option for restore.<\/p>\n
General Options<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n
-nodbtriggers<\/pre>\n<\/td>\n
Suppresses Database Triggers from running [Firebird 2.1]<\/td>\n<\/tr>\n
\n
-pas[sword] <password><\/pre>\n<\/td>\n
Database password<\/td>\n<\/tr>\n
\n
-fet[ch_password] <filename><\/pre>\n<\/td>\n
Instead of -password: Fetch password from the file so it is not visible in the command line. When <filename> is stdin, the user will be prompted for the password. [Firebird\u00a02.5]<\/td>\n<\/tr>\n
\n
-m[etadata]<\/pre>\n<\/td>\n
Only backs up\/restores metadata (schema). No table data will be re\/stored.<\/td>\n<\/tr>\n
\n
-role <role><\/pre>\n<\/td>\n
Connect as role<\/td>\n<\/tr>\n
\n
-se[rvice]\r\n  <hostname>:service_mgr<\/pre>\n<\/td>\n
Backup: Creates the backup file on the database server, using the Service Manager.
\nRestore: Creates the database from a backup file on the server, using the Service Manager.
\nAll file names (backup file, log file) must be specified as viewn from the server’s perspective.<\/td>\n<\/tr>\n
\n
-u[ser] <username><\/pre>\n<\/td>\n
Database user name<\/td>\n<\/tr>\n
\n
-v[erbose] or<\/pre>\n
-v[erify]<\/pre>\n<\/td>\n
Verbose output of what GBAK is doing<\/td>\n<\/tr>\n
\n
-y <filename><\/pre>\n<\/td>\n
Redirect all output messages to <filename>
\nThe file must not<\/i> exist before running GBAK!<\/td>\n<\/tr>\n
\n
-y suppress<\/pre>\n<\/td>\n
Quiet mode: suppress any output<\/td>\n<\/tr>\n
\n
-z<\/pre>\n<\/td>\n
Show GBAK version and server version<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Backup Options<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n
\n
-b[ackup_database]<\/pre>\n<\/td>\n
Back up. This switch is optional.<\/td>\n<\/tr>\n
\n
-co[nvert]<\/pre>\n<\/td>\n
Converts external tables to internal tables<\/td>\n<\/tr>\n
\n
-e[xpand]<\/pre>\n<\/td>\n
Creates an uncompressed backup<\/td>\n<\/tr>\n
\n
-fa[ctor] n<\/pre>\n<\/td>\n
Blocking factor for tape device<\/td>\n<\/tr>\n
\n
-g[arbage collect]<\/pre>\n<\/td>\n
Does not perform garbage collection during backup, so the backup will be faster. When you plan to da a Restore or Sweep anyway after the backup.<\/td>\n<\/tr>\n
\n
-ig[nore]<\/pre>\n<\/td>\n
Ignores checksum errors while backing up<\/td>\n<\/tr>\n
\n
-l[imbo]<\/pre>\n<\/td>\n
Ignores limbo transactions while backing up<\/td>\n<\/tr>\n
\n
-m[etadata]<\/pre>\n<\/td>\n
Only backs up metadata (schema). No table data will be stored.<\/td>\n<\/tr>\n
\n
-nt<\/pre>\n<\/td>\n
Non-transportable format (use only when you know you will restore on same platform and database version)<\/td>\n<\/tr>\n
\n
-t[ransportable]<\/pre>\n<\/td>\n
Creates a transportable backup (transportable between platforms and server versions). This is the default.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Restore Options<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n
-bu[ffers]<\/pre>\n<\/td>\n
Set cache size for restored database<\/td>\n<\/tr>\n
\n
-c[reate_database]<\/pre>\n<\/td>\n
Restore to a new database (the target database file MUST NOT exist)<\/td>\n<\/tr>\n
\n
-fix_fss_d[ata] <charset><\/pre>\n<\/td>\n
Repair malformed UNICODE_FSS data during Restore [Firebird 2.5]<\/td>\n<\/tr>\n
\n
-fix_fss_m[etadata] <charset><\/pre>\n<\/td>\n
Repair malformed UNICODE_FSS metadata during Restore [Firebird 2.5]<\/td>\n<\/tr>\n
\n
-i[nactive]<\/pre>\n<\/td>\n
All indexes will be restored as INACTIVE<\/td>\n<\/tr>\n
\n
-k[ill]<\/pre>\n<\/td>\n
Does not create shadows that are defined in the backup<\/td>\n<\/tr>\n
\n
-m[etadata]<\/pre>\n<\/td>\n
Only restores metadata (schema). No table data will be restored.<\/td>\n<\/tr>\n
\n
-mo[de] read_write<\/pre>\n<\/td>\n
Restores to a read\/write database (This is the default)<\/td>\n<\/tr>\n
\n
-mo[de] read_only<\/pre>\n<\/td>\n
Restores to a read-only database<\/td>\n<\/tr>\n
\n
-n[o_validity]<\/pre>\n<\/td>\n
Does not restore validity constraints. So you can restore data that does not meet these constraints and could not be restored otherwise.<\/td>\n<\/tr>\n
\n
-o[ne_at_a_time]<\/pre>\n<\/td>\n
Usually the restore takes place in one single transaction for the whole database. This switch puts a commit after each table. So you can use this to partially restore databases with corrupt table data.<\/td>\n<\/tr>\n
\n
-p[age_size] <size><\/pre>\n<\/td>\n
Sets page size of new database. <size> can be one of 1024, 2048, 4096, 8192. Default is 1024.<\/td>\n<\/tr>\n
\n
-r[eplace_database]<\/pre>\n<\/td>\n
Restores over an existing database. This can only be performed by SYSDBA or the owner of the database that is overwritten. Do NOT restore over a database that is in use! [Firebird 1.0, 1.5]<\/td>\n<\/tr>\n
\n
-rep[lace_database]<\/pre>\n<\/td>\n
New abbreviation for the old -replace_database [Firebird 2.0]<\/td>\n<\/tr>\n
\n
-r[ecreate_database] o[verwrite]<\/pre>\n<\/td>\n
[Firebird 2.0] Restores over an existing database. This can only be performed by SYSDBA or the owner of the database that is overwritten. Do NOT restore over a database that is in use!-r is equivalent to -c. Only the “overwrite” option will restore over an existing database.<\/td>\n<\/tr>\n
\n
-use_[all_space]<\/pre>\n<\/td>\n
Normally, on restore, database pages will be filled to about 80\u00a0%. With the use_all_space option, database pages will be filled to 100\u00a0%. (Useful for read-only databases which will see no more modifications.)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Examples<\/h2>\n
A regular Backup<\/h4>\n
gbak -v -t -user SYSDBA -password \"masterkey\" dbserver:\/db\/warehouse.fdb c:\\backups\\warehouse.fbk<\/code><\/p>\n
Backup with output to a logfile<\/h4>\n
del c:\\backups\\warehouse.log
\ngbak -v -t -user SYSDBA -password masterkey -y c:\\backups\\warehouse.log<\/b> dbserver:\/db\/warehouse.fdb c:\\backups\\warehouse.fbk<\/code><\/p>\n
A regular Restore<\/h4>\n
gbak -c<\/b> -v -user SYSDBA -password masterkey c:\\backups\\warehouse.fbk dbserver:\/db\/warehouse2.fdb<\/code><\/p>\n
Restore to an already existing database (Firebird 1.0, 1.5)<\/h4>\n
gbak -c -r<\/b> -v -user SYSDBA -password masterkey c:\\backups\\warehouse.fbk dbserver:\/db\/warehouse.fdb<\/code><\/p>\n
Restore to an already existing database (Firebird 2.x)<\/h4>\n
gbak -r o<\/b> -v -user SYSDBA -password masterkey c:\\backups\\warehouse.fbk dbserver:\/db\/warehouse.fdb<\/code><\/p>\n
Create a read-only database<\/h4>\n
gbak -c -v -mode read_only -use_all_space<\/b> -user SYSDBA -password masterkey c:\\backups\\warehouse.fbk c:\\files\\warehousedb.fdb<\/code><\/p>\n
Multi-file backups<\/h2>\n
Syntax for backup<\/h4>\n
gbak [options] <database> <target file 1> <size 1> <target file 2> <size 2> ... <target file n><\/code><\/p>\n
NOTE: Do not specify a size for the last file. It will always be filled to take up what is left over, no matter how large.<\/p>\n
Size can be given in bytes (8192), kilobytes (1024k), megabytes (5m), or gigabytes (2g)<\/p>\n
Syntax for restore<\/h4>\n
gbak -c [options] <source file 1> <source file 2> ... <source file n> <database><\/code><\/p>\n
Restoring to a multi-file database<\/h2>\n
gbak -c [options] <source file> <db file 1> <size 1> <db file 2> <size 2> ... <db file n><\/code><\/p>\n
NOTE: Do not specify a size for the last database file. It can always grow unlimited to take up the rest.<\/p>\n
Size can be given in bytes (8192), kilobytes (1024k), megabytes (5m), or gigabytes (2g)<\/p>\n
Restoring from a multi-file backup to a multi-file database<\/h4>\n
gbak -c [options] <source\u00a0file\u00a01> <source\u00a0file\u00a02> ... <source\u00a0file\u00a0n> <db\u00a0file\u00a01> <size\u00a01> <db\u00a0file\u00a02> <size\u00a02> ... <db\u00a0file\u00a0n><\/code><\/p>\n
Backup and Restore at the same time<\/h2>\n
Use this when you want to test the physical and logical health of your database or to copy a database to another location using a proper Backup-&-Restore cycle.<\/p>\n
Note that stdin<\/i> and stdout<\/i> get special treatment from gbak here, so don’t use “\/dev\/stdin” or “\/dev\/stdout”.<\/p>\n
Syntax<\/h4>\n
gbak -c [options] <source database> stdout<\/b> |<\/b> gbak -r [options] stdin<\/b> <target database><\/code><\/p>\n
Backing up and Restoring the Security Database<\/h2>\n
Firebird 1.0, 1.5<\/h3>\n
You can perform a regular backup of the security database.\u00a0 The security database resides in the Firebird directory. It is named<\/p>\n
    \n
  • ISC4.gdb<\/i> in Firebird 1.0 and<\/li>\n
  • security.fdb<\/i> in Firebird 1.5.<\/li>\n<\/ul>\n
    Firebird 2.x (using the Service Manager)<\/h3>\n
    Firebird 2.x does not allow regular database access to the security database. Its name is now security2.fdb<\/i><\/p>\n
    The only way to access the security database is via the Service Manager. As GBAK can also use the Service Manager (Option -se), you can run a backup using this option. However, the backup file will also be written to the server machine.<\/p>\n
    General Syntax:<\/p>\n
    gbak <options> -user <username> -password <password> -service <servername>:service_mgr <sec-db-name> <backup-filename><\/pre>\n
    Example:<\/p>\n
    gbak -v -t -user sysdba -password masterkey -service dbserver:service_mgr<\/b> c:\\Programme\\Firebird2\\security2.fdb C:\\Backups\\Security2.fbk<\/pre>\n
      (in this case, Security2.fbk will be written to the C:\\Backups folder of dbserver!)<\/pre>\n
    When your database server listens on a non-default port:<\/p>\n
    gbak -v -t -user sysdba -password masterkey -se dbserver\/3051<\/b>:service_mgr c:\\Programme\\Firebird2\\security2.fdb C:\\Backups\\Security2.fbk<\/pre>\n
    Firebird 2.1\/2.5<\/h3>\n
    In Firebird 2.1 there is a new option -no_dbtriggers that suppresses database triggers from running during backup\/restore. So you can suppress any unwanted behaviour for the connection that GBAK needs to establish for the database.<\/p>\n
    Restoring the Security Database<\/h2>\n
    It is not possible to restore the security database while Firebird is running. In case your security database gets destroyed, this is what you can do:<\/p>\n
      \n
    • Stop the Firebird service\/daemon<\/li>\n
    • Replace the current security database with a new one. If anything else fails, re-install the Firebird server<\/li>\n
    • You should now have a working SYSDBA login and password. If not, re-install the Firebird server …<\/li>\n
    • Start the Firebird service\/daemon<\/li>\n
    • Using GBAK, restore your backup of the security database to a temporary place (like C:\\Temp\\security2.fdb)<\/li>\n
    • Stop the Firebird service\/daemon again<\/li>\n
    • Now copy the file from the temporary place to the correct place in the Firebird folder<\/li>\n
    • Start the Firebird service\/daemon<\/li>\n
    • Now you should have your “old” security database back.<\/li>\n
    • Good Luck! \ud83d\ude42<\/li>\n<\/ul>\n
      Upgrading a Security Database to Firebird 2.0<\/h2>\n
      There is a special chapter “Dealing with the New Security Database” about this in the Firebird 2.0 Release Notes, which get installed to the doc<\/i> subdirectory of your Firebird directory. You should also take a look at the misc\\upgrade\\security\\security_database.txt<\/i> file, which explains in detail how to do it.<\/p>\n","protected":false},"excerpt":{"rendered":"
      GBAK is Firebird’s command line tool for online backup and restore of a complete database. GBAK is able to perform a backup while the database is running. There is no need to shut down the database during a GBAK backup. GBAK will create a consistent snapshot of the database at the time it starts running. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[91,42,51,68],"tags":[248,162,246,247],"class_list":["post-433","post","type-post","status-publish","format-standard","hentry","category-banco-de-dados","category-leitura-recomendada","category-linux-linuxrs","category-redes-2","tag-backup","tag-firebird","tag-gbak","tag-restore"],"_links":{"self":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/433","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=433"}],"version-history":[{"count":1,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/433\/revisions"}],"predecessor-version":[{"id":434,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/433\/revisions\/434"}],"wp:attachment":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=433"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=433"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=433"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}