I notice an issue with regard to the use of GBAK on the server.
I have an application open which accesses the gdb file via a TCP connection
string
servername:drive:\path\file.gdb

I also have a batch file on the server which runs
gbak -b -user SYSDBA -password masterkey drive:\path\file.gdb
drive:\path\file.gbk

Now, while the application is open, this gbak command fails because of
connection string conflict.
But even when I change the gbak command to
gbak -b -user SYSDBA -password masterkey servername:drive:\path\file.gdb
drive:\path\file.gbk

it also fails.
If I run gbak from the workstation it works fine (Services API).
Is this, in fact, the plan? Is there a way around this? Or is this pointing
at something in my setup?
thanks
Alan