Hi All,

We have a client that has been using our DBISAM based software. They
went to do a restore this morning and received an ERROR. On getting the
backup I found the same problem and the log told me it was an ERROR 9217

I've read the other post on this newsgroup and wonder is there any way
to rectify the backup? They have tried to previous backups and the same
error occurs.

Is there a particular 'over the top setting' certain anti-virus software
products can have set that will cause a modification to data being
written during a backup?

In the past I have have ASCII license files corrupted when certain
clients receive them cause of their anti-virus programs scanning
incoming email and so I have to place it in a zip file before emailing,
but this is crazy that an anti-virus program would corrupt data being
written to the hard drive (they are meant to  protect, instead they
bloat and cause more problems as we know, damn them

Thanks guys,

Phil

Problem found! It ended up being a left over temporary table that was
corrupted, causing the restore to fail. Each time the client made a
backup the backup would work but on restoring it would fail.

I changed the PrivateDirectory to another location and deleted the left
over temp table and all works now.

Just thought I'd mention it incase anyone else has a similar problem.

Thanks all!

Phil,

<< Problem found! It ended up being a left over temporary table that was
corrupted, causing the restore to fail. Each time the client made a backup
the backup would work but on restoring it would fail.

I changed the PrivateDirectory to another location and deleted the left
over temp table and all works now. >>

Yes, having the PrivateDirectory set to the same directory as any normal
database directory will cause issues with the backups because the backup
does not lock any temporary tables, but will pick them up during the backup
process anyways, resulting in a partial read of the table.

--
Tim Young
Elevate Software
www.elevatesoft.com