Firebird server fbserver (SS) or fb_inet_ server (CS) /bin Command-line tools isql, gbak, nbackup, gsec, gfix, gstat, etc. /bin Sample database employee.fdb /examples/ empbuild Firebird comes with two utilities for backing up and restoring your databases: gbak and nbackup (note: nbackup is broken in 2.1; fixed with errors in 2.1.1; completely fixed in 2.1.2). Both can be found occasional restores should be a scheduled part of your database management activity. Warning Except in nbackup's lock mode, do not use external proprietary backup utilities or file-copying tools such as WinZip

files $(install)/doc Firebird server firebird $(install)/bin Command-line tools isql, gbak, nbackup, gfix, gstat, etc. $(install)/bin Plugins libEngine13.so, libSrp.so, libudr_engine.so, etc. $(install)/plugins $(install)\doc Firebird server firebird.exe $(install) Command-line tools isql.exe, gbak.exe, nbackup.exe, gfix.exe, gstat.exe, etc. $(install) Plugins engine13.dll, srp.dll, udr_engine.dll, etc Backup Firebird comes with two utilities for backing up and restoring your databases: gbak and nbackup. Both can be found in the Firebird installation directory (Windows) or its bin subdirectory (Linux)

Firebird. In Firebird 1.5 it is the only supplied utility of this kind while Firebird 2.x also has the nbackup utility which is described in another document. In this manual, we will discuss: • Command-line chances of a successful restore of that database are slim. You must either always use the gbak or nbackup tools which know how the database works, or, use gfix to shut the database down completely before ssh firebird@tuxqa "ls data" employee.fdb tuxrep_empqa.fdb 6.13. Using External Tools Gbak and nbackup are the best tools to use when backing up and/or restoring Firebird databases. They have been extensively

automatic firing of database triggers. So far, they are: gbak -nodbtriggers isql -nodbtriggers nbackup -T Two-phase Commit In a two-phase commit scenario, TRANSACTION COMMIT triggers fire in the prepare been limited to SYSDBA and administrators only. For example: • Run utilities such as gbak, gfix, nbackup and so on • Shut down a database and bring it online • Trace other users' attachments • Access CREATE_USER_TYPES Add/change/delete non-system records in RDB$TYPES Chapter 13. Security 577 USE_NBACKUP_UTILITY Use nbackup to create database copies CHANGE_SHUTDOWN_MODE Shut down database and bring online TRACE_ANY_ATTACHMENT

longer used. The field was converted to be the SCN number to avoid an ODS change and is now used by nbackup. pag_reserved Four bytes, unsigned. Bytes 0x0c - 0x0f. Reserved for future use. It was originally 0x53 on the page. Holds the number of pages in the database currently locked for a backup using nbackup. This field is only valid in the header page of the first file in a multi-file database. The remaining

automatic firing of database triggers. So far, they are: gbak -nodbtriggers isql -nodbtriggers nbackup -T Two-phase Commit In a two-phase commit scenario, TRANSACTION COMMIT triggers fire in the prepare the prefix RDB$. List of System Tables RDB$BACKUP_HISTORY History of backups performed using nBackup RDB$CHARACTER_SETS Names and describes the character sets available in the database RDB$CHECK_CONSTRAINTS a view RDB$BACKUP_HISTORY RDB$BACKUP_HISTORY stores the history of backups performed using the nBackup utility. Column Name Data Type Description RDB$BACKUP_ID INTEGER The identifier assigned by the

introduction of an additional system generator, called RDB$BACKUP_HISTORY. It is used for the new NBackup facility. • Even though the SEQUENCE syntax is preferred, the RDB$GENERATORS system table and its