Icon View Incident Report

Serious Serious
Reported By: Rick Leffler
Reported On: 8/8/2011
For: Version 4.30 Build 6
# 3483 Backup and Restore Not Using Correct Backup Headers

I've just encountered some strange problems that I've never had before. And because it has to do with the Backup/Restore features it is rather unsettling because I'm always nagging my customers to back up regularly using my app's built-in utility (which just makes DBISAM Backup/Restore calls.)

When I try to restore a backup file (.bkp) that was created with a slightly prior DBISAM v4.30 build (prior to 6) I get an error saying "Cannot read Backup Info". This happens when I use MY app (compiled with 4.30 build 6) or DBSYS.exe of the same version.

If I revert to a build of my app that was compiled with DBISAM v4.30 prior to build 6, then I am able to restore that very same backup file that fails when I try to use DBSYS.exe 4.30 build 6, or MY app that was compiled with same DBISAM version.


Comments Comments
This is a critical problem caused by some changes to the ANSI string handling for the backup file header in the backup and restore code when getting DBISAM ready for 64-bit. Any new backups created with 4.30 B6 will need to be discarded and replaced with a new backup created using 4.30 B7. If you absolutely need to restore a backup that was created with 4.30 B6, then please contact us and we will arrange to manually restore it for you.


Resolution Resolution
Fixed Problem on 8/10/2011 in version 4.30 build 7


Products Affected Products Affected
DBISAM Additional Software and Utilities
DBISAM CLX Client-Server
DBISAM CLX Client-Server with Source
DBISAM CLX Standard
DBISAM CLX Standard with Source
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard
DBISAM ODBC Standard with Source
DBISAM ODBC Trial
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial

Image