Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 10 total
Thread Serious problem with backup/restore in 1.06
Fri, Oct 2 2009 4:57 AMPermanent Link

Michael Reisch
I have a really serious problem with EDB 1.06. I start a backup of my database including
catalog. Then I delete the files in that directory and restore this backup again
(including the catalog). Then I get the errormessage:

ElevateDB Error #1301 Error resoring the database pro-Report 2 (Unknown error occured with
the file C:\Dokumente und Einstellungen\All
Users\Dokumente\gripsware\proReport2_Stark\Data\Media.EDBBlb (ElevateDB Error #1201 An
error occured while uncompressing data (Invalid stored block lengths)))

and the restore process fails.

The Media table is corrupt then, and when I use Repair Table then will be a lot records
deleted. Then EDBBlb file is 600 kB after that instead of 2900 kB.

When I use Winzip the zip filesize is 21,635,077 bytes (elevate EDBBkp filesize 19,774,963
bytes ?!?!). After unzipping the zip-file in my empty directory all works correct.

Can I trust my EDBBkp files????

regards
Michael
Fri, Oct 2 2009 9:26 AMPermanent Link

Jan-Erik Johansen
<<An error occured while uncompressing data (Invalid stored block lengths)))>>

I've had the same issue but forgot to report it. (V2.X Unicode)

Workaround: Don't compress the backup.

To me it looks like the problem is with blobs (images), in most cases they are optimized in the first place and compression only adds to the time it takes to
do the backup.

Tim,
If you backup/restore of the testproject I sent you, you should be to reproduce.

--
Jan-Erik
Fri, Oct 2 2009 12:12 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Michael,

<< I have a really serious problem with EDB 1.06. I start a backup of my
database including catalog. Then I delete the files in that directory and
restore this backup again (including the catalog). Then I get the
errormessage: >>

There was this incident report that was corrected a while ago:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.02&type=f&incident=2935

Apart from that, we don't have any outstanding issues with the backup or
restore.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Oct 2 2009 12:13 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jan-Erik,

<< If you backup/restore of the testproject I sent you, you should be to
reproduce. >>

I'll check it out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Oct 2 2009 12:14 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Michael,

Also, I'd like to clarify that the restore error that was the basis for that
incident report was an issue with the decompression, and not an issue with
the backup files themselves.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Oct 2 2009 12:46 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jan-Erik,

<< If you backup/restore of the testproject I sent you, you should be to
reproduce. >>

I can't reproduce this with the database that you sent me.  When was the
last time that you tried this ?  Is it possible that it was before this
date:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.02&type=f&incident=2935

You indicated that you were using 2.02 B8 until recently, so I suspect that
this is the case.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Oct 2 2009 1:09 PMPermanent Link

Jan-Erik Johansen
Tim,

You are correct, the issue was using 2.02.Build8, I didn't realize there was an issue on this already.
I'll try a backup/restore using the 2.03B4 later today, really looking forward to B4 btw Smile
(if anything shows up I'll let you know)

--
Jan-Erik
Fri, Oct 2 2009 6:00 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jan-Erik,

<< You are correct, the issue was using 2.02.Build8, I didn't realize there
was an issue on this already. >>

No problem.  I'm just glad that it's most likely the same issue. Smiley

<< I'll try a backup/restore using the 2.03B4 later today, really looking
forward to B4 btw Smile(if anything shows up I'll let you know) >>

Thanks, that would be great.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Oct 7 2009 5:39 AMPermanent Link

Michael Reisch
Tim,

sorry about my late response, I was ill the last few days.

<<
Also, I'd like to clarify that the restore error that was the basis for that
incident report was an issue with the decompression, and not an issue with
the backup files themselves.
>>
I cannot follow your argumentation. Do you mean that Backup is OK, only Restore fails?
What can I do? I work still with the 1.06 as you see. Is this a problem there?

Sorry, but I don´t understand what you mean, and what can I do against...

If you wish I can send you the backup file, but it is 26 MB.

Best regards
Michael
Wed, Oct 7 2009 1:28 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Michael,

<< sorry about my late response, I was ill the last few days. >>

Sorry to hear that, but I'm glad that you're back on your feet (or at least
in front of the computer Smiley.

<< I cannot follow your argumentation. Do you mean that Backup is OK, only
Restore fails? >>

Yes, the issue was with the decompression during the restore.

<< What can I do? I work still with the 1.06 as you see. Is this a problem
there? >>

Probably.  It was a problem through 2.00 and 2.01 also.

<< If you wish I can send you the backup file, but it is 26 MB. >>

You can email that to me as an attachment.  Our mail server will take an
attachment up to 32MB.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image