FirebirdSQL logo

-⁠FIX_FSS_M[ETADATA]

Fix malformed UNICODE_FSS metadata.

Syntax
-FIX_FSS_M[ETADATA] charset-name

This switch forces gbak to fix malformed UNICODE_FSS metadata during a restore.

Malformed metadata string will be attempted to be read using the specified character set charset-name, and then transformed to UNICODE_FSS.Specifying the wrong character set name may result in logical corruption of the strings in your metadata.

Caution

Do not use this switch without a clear understanding of what it does.Incorrect use could corrupt your database instead of fixing things.Always keep a copy of the original database and its backup.

This switch, and the preceding one, should not be required under normal circumstances.However, if a restore operation fails with a "malformed string" error, the message output from gbak will refer the user to one or both of these switches to fix the malformed UNICODE_FSS data or metadata as appropriate.

Note
Introduced in Firebird 2.5.

-⁠I[NACTIVE]

Do not activate indexes after restore.

This switch can be used to restore a database when a previous restore attempt failed due to index errors.All indexes in the restored database will be inactive, and as a consequence all primary key, unique key and foreign key constraints as well.

-⁠K[ILL]

Kill (do not recreate) shadow database.

This switch restores the database but doesn’t recreate any shadow files that existed previously.

-⁠MO[DE]

Restore database in read-only or read/write mode.

Syntax
-MO[DE] { READ_ONLY | READ_WRITE }

This switch allows the database being restored to be set to the given access mode when opened.By default, the mode is taken from the database that was backed up.

Caution

This option should not be confused with the replica mode configured through [gbak-cmdline-replica].For example, a database created with -⁠REPLICA READ_ONLY is still writable by the replicator connection, while a database created with -⁠MODE READ_ONLY is not writable at all.