New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backup Transportable Format of FB 2.0 cannot restored by FB 1.5.3 [CORE1131] #1553
Comments
Modified by: ohenri (ohenri)description: A backup (Transportable Format) made in Firebird DBMS Version 2 should be restorable by any other Firebird DBMS Version, A backup made by Firebird 2.0 cannot be restored by Firebird 1.5.3, even if the backup made by FB 2.0 has only options which are also available in 1.5.3. FB 1.5.3 GBACK say's (when trying to restore a backup bade by GBAK of FB 2.0): => A backup (Transportable Format) made in Firebird DBMS Version 2 should be restorable by any other Firebird DBMS Version, A backup made by Firebird 2.0 cannot be restored by Firebird 1.5.3, even if the backup made by FB 2.0 has only options which are also available in 1.5.3. FB 1.5.3 GBACK say's (when trying to restore a backup made by GBAK of FB 2.0): |
Commented by: Sean Leyne (seanleyne) This is expected, as designed functionality. A backup is never backward compatible, only forward. There is a technique to allow for a backup of a 2.0 database to be made using the 1.5 GBak executable. Please post a message to the Support mail list for details on this solution. |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] |
Commented by: ohenri (ohenri) In general and for most DBMS like UDB, Oracle etc, a backup is always backward compatible. There are good reasons to do so, because a fallback to an older DB version is often the last chance to keep a system avalilable in a short time (when the new version is failing). And the term "Transportable Format" say's it is transportable between platforms, but it does not specify 'of the same versions'. Anyway, thanks for the hint, but I already pumped back the DB's manually. |
Commented by: Claudio Valderrama C. (robocop) You can do that with FB2.1's gbak. C. |
Modified by: Claudio Valderrama C. (robocop)issuetype: Bug [ 1 ] => Improvement [ 4 ] Fix Version: 2.1 [ 10041 ] assignee: Claudio Valderrama C. [ robocop ] |
Modified by: Claudio Valderrama C. (robocop)status: Resolved [ 5 ] => Reopened [ 4 ] resolution: Won't Fix [ 2 ] => |
Commented by: @hvlad > And the term "Transportable Format" say's it is transportable between platforms, but it does not specify 'of the same versions'. This is your own wrong interpretation Claudio, am i right that this new gbak 2.1 functionality independent of "transportable" flag and will work with any backups kind ? |
Commented by: @dyemanov Claudio, while your v2.1 changes are welcome, they don't make the backup file backward compatible :-) |
Commented by: Claudio Valderrama C. (robocop) Transportable only says that you won't have problems if you take the backup to a machine with different endianess. Trying to put as much as possible in an old server is orthogonal. |
Commented by: ohenri (ohenri) Thank you all for your comments. Indeed, I was not amused about the fast close of that ticket, but naturally I have to accept it, and I do. But now, let me explain. I tested FB 2, ok so far. Then, some weeks later, problems arised, and I noted them into the bugtracker. And so, how to fallback to FB 153? Then I run into other FB2-problems (poor performance) with another application, and again I needed to goback to FB153, and must do this by manual work since backup/resore does not work. That's the reason why I placed this bug. I know this is not really a discussion platform - so if you remove my last comment, it's ok for me. |
Commented by: @dyemanov Closed again as "Won't fix, by design". I don't think we can make the backup *file* readable by any GBAK version. Downgrade is supported via two other alternatives. This is not ideal, but I doubt we could offer anything better in the short term. |
Modified by: @dyemanovstatus: Reopened [ 4 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] Fix Version: 2.1 [ 10041 ] => assignee: Claudio Valderrama C. [ robocop ] => |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: Marius (marius) I agree on some of the reasons for breaking the gbak support in FB2 and this item staying closed ;-) It would be very nice if there would be some guidelines explaining how to do this downgrade + some links to tools (if there are any needed). We don't use any of the additional technical stuff from FB2, is there any risk we will lose data with a downgrade?? |
Modified by: @pcisarWorkflow: jira [ 11601 ] => Firebird [ 14721 ] |
Submitted by: ohenri (ohenri)
A backup (Transportable Format) made in Firebird DBMS Version 2 should be restorable by any other Firebird DBMS Version,
(naturally as long as the backup does not consist options which the restoring DBMS does not support).
A backup made by Firebird 2.0 cannot be restored by Firebird 1.5.3, even if the backup made by FB 2.0 has only options which are also available in 1.5.3.
FB 1.5.3 GBACK say's (when trying to restore a backup made by GBAK of FB 2.0):
gbak: opened file D:\XWatchDB\XWatch01X_200.bak
ERROR: Expected backup version 1, 2, or 3. Found 7
The text was updated successfully, but these errors were encountered: