You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In version 2.5.4.x GBAK crashes / freeze Firebird server on restore over existing database.
In combination with GFIX and FULL shutdown, if you use GBAK with -REP option and try to restore database over existing one, gbak hangs on start and freeze firebird server.
You need to open Windows task manager and kill Firebird server task and after that Guardian restart Firebird Server.
That problem is happened only in combination of these conditions:
1. GFIX - full shutdown
2. GBAK - restore with -REP option
Problem does not exist in Firebird version 2.5.2.26539 or 2.5.2.26540 - other version before 2.5.4.x I did not test.
Workaround 1:
1. GFIX: shutdown full
2. GFIX: online single
Workaround 2:
1. GFIX: shutdown full
2. DELETE database file
3. Restore with GBAK with same name
The text was updated successfully, but these errors were encountered:
summary: CLONE -GBAK crashes / freeze Firebird server on restore over existing database => GBAK crashes / freeze Firebird server on restore over existing database
Submitted by: Darko (irdanet)
In version 2.5.4.x GBAK crashes / freeze Firebird server on restore over existing database.
In combination with GFIX and FULL shutdown, if you use GBAK with -REP option and try to restore database over existing one, gbak hangs on start and freeze firebird server.
You need to open Windows task manager and kill Firebird server task and after that Guardian restart Firebird Server.
That problem is happened only in combination of these conditions:
1. GFIX - full shutdown
2. GBAK - restore with -REP option
Problem does not exist in Firebird version 2.5.2.26539 or 2.5.2.26540 - other version before 2.5.4.x I did not test.
Workaround 1:
1. GFIX: shutdown full
2. GFIX: online single
Workaround 2:
1. GFIX: shutdown full
2. DELETE database file
3. Restore with GBAK with same name
The text was updated successfully, but these errors were encountered: