At 04:51 PM 24/04/2009, you wrote:

>Previously had posted in the support group, maybe that was the wrong group thus nobody answered, sorry.
>
>Hi all
>
>I had previously tried backing up a database using FlameRobin and had an error I am getting the same error using gbak with the following command line:
>"C:\Program Files\Firebird\Firebird_2_1\bin\gbak.exe" -v -y c:\trashcan\c10.lg -z -b -user sysdba -password masterkey vso3.fdb c:\trashcan\c10.bak
>
>The last part of the log is as follows:
>gbak: writing data for table BEA3
>gbak:0 records written
>gbak: writing data for table TEA3
>gbak: ERROR:invalid BLOB ID
>gbak: ERROR: gds_$receive failed
>gbak:Exiting before completion due to errors
>
>Please advise.

First things first: sort out the gbak parameters so that it's perfectly clear to gbak, which file is which. I'll put these on separate lines to make it easier to follow, but of course it is one single command line:

"C:\Program Files\Firebird\Firebird_2_1\bin\gbak.exe"
-b d:\full\path\to\vso3.fdb {OR, BETTER, USE AN ALIAS}
c:\trashcan\c10.bak {MAKE SURE THIS FILE DOES NOT EXIST}
-v -y c:\trashcan\c10.lg {MAKE SURE THIS FILE DOES NOT EXIST}

Don't know why you included -z in there, I'm sure.

If you still get the *same* error then you'll need to query the blobs in table TEA3 to find out which blob[s] in which record[s] have been corrupted.

./heLen