Dear Alan and friends,

Thank you for your response.

The gbak has now been going for >24Hrs and still in exactly the same state ie no change at all to the message displayed from the gbak cmd of

gbak: writing data for table SMDR

and the backup file is exactly the same size as when I earlier sent the query.

Does this still appear normal?

Normally, the sweep, gbak and restore takes about 3 Hrs (if no mass delete of 70Million records was performed).

You mentioned running the gbak with the -g switch. What would happen if I was to cancel this backup and then recommence the gbak with the -g switch ie

gbak -v -t -g -user SYSDBA -password "masterkey" DATABASENAME.FDB DATABASENAME.FBK

will that corrupt the database if I stop during the original gbak? And, would I expect the gbak with the -g option to be less than 3 Hrs (which is the normal Sweep/Backup/Restore duration with no delete).

Anybody else experience this?

Thanking you all in advance.

Theodore

[Non-text portions of this message have been removed]