Subject Re: Lock conflict
Author Adam
> LI-V6.3.2.4731 1.5 Classic, RedHat Enterprise, 9G database
> In the evenings when gbak –g is running the clients are encountering
> conflict on no wait transaction
> Deadlock
> Update conflicts with concurrent update

This is a normal exception in a multi-user environment that has
absolutely nothing to do with gbak. It means two concurrent
transactions are trying to modify or delete the same record.

A backup only reads data (so no risk of lock conflict). A restore must
be done with exclusive access, so again no risk of lock conflict.