I'm not aware of any issues but the information here isn't really detailed.
When a backup starts it uses a snapshot isolation so anything not yet committed will not be in the backup.
You don't have to close connections, just make sure transactions are complete if you don't want information missed.

Jason Wharton

--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
IBO (4.3.A) and Interbase (open source 6.0.2.0) with Delphi 5 . Converting some apps from Paradox to IB using IBO.

1. In one app I want to automatically back up the database at 3AM. I have a process working within the app which starts
and waits for a gbak (backup and restore) batch job to run and complete. With the 'old' Paradox database, all files were
closed, backed up and re-opened so everything was up to date. Is this something I need to be concerned about with
IBO and Interbase? If I set the IBO database connection to false before the backup will that 'close' the gdb??

2. The Paradox app used dbiSaveChanges after dataset posts. Is this a concern with IBO, Interbase? Does the default
IBO transaction management take care of this? (Not yet using explicit transaction control).

Thanks.