Binary representation of the backup file is inconsistent among subsequent backup/restore cycles [CORE2793] #3183
Labels
affect-version: 1.5.4
affect-version: 1.5.5
affect-version: 1.5.6
affect-version: 2.0.0
affect-version: 2.0.1
affect-version: 2.0.2
affect-version: 2.0.3
affect-version: 2.0.4
affect-version: 2.0.5
affect-version: 2.1.0
affect-version: 2.1.1
affect-version: 2.1.2
affect-version: 2.1.3
affect-version: 2.5 Alpha 1
affect-version: 2.5 Beta 1
affect-version: 2.5 Beta 2
affect-version: 3.0 Initial
component: gbak
fix-version: 2.1.4
fix-version: 2.5 RC2
fix-version: 3.0 Alpha 1
priority: minor
type: bug
Submitted by: @dyemanov
Reported in firebird-devel by Jean-Marc Bottura:
- I do a backup with gbak BASE.FDB -> BASE.FBK : ok
- Then a restore/backup BASE.FBK -> BASE1.FDB -> BASE1.FBK :
there are a lot of differences in the format between BASE.FBK and
BASE1.FBK ( a lot of 0x0500 added at the beginning of the FBK, the order
of the fields in the tables records is inverted, and so on ...)
- But if I do another restore/backup BASE1.FBK -> BASE2.FDB ->
BASE2.FBK : surprise ! the BASE2.FBK is exactly the same as the original
BASE.FBK (except date and time in the header)
- And if I do another restore/backup BASE2.FBK -> BASE3.FDB ->
BASE3.FBK : the BASE3.FBK is exactly the same as the BASE1.FBK
- And so on ...
Commits: 7b1f188 12015dd a07da47
The text was updated successfully, but these errors were encountered: