On 2014-01-15, at 5:40 PM, <hvlad@...> <hvlad@...> wrote:

>
> This is too strong statement. To verify it we need to know physical backup
> state of the database. gstat -h will show it (and it not requires admin privileges).

I am able to run this on the original server, are there some additional switches you would like? Here is what I got with -h, and I see that "force write, backup lock" at the bottom, which I suspect is interesting...

Database "../data/company.fdb"
Database header page information:
Flags 0
Checksum 12345
Generation 753393
Page size 4096
ODS version 11.2
Oldest transaction 734639
Oldest active 734640
Oldest snapshot 734640
Next transaction 734721
Bumped transaction 1
Sequence number 0
Next attachment ID 18032
Implementation ID 26
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 3
Creation date Sep 1, 2012 10:22:08
Attributes force write, backup lock

Variable header data:
Database backup GUID: {407742FD-11DE-43CD-60B7-CBCCC1AA866E}
Sweep interval: 20000
*END*