StartPause - Start Pause
When pausing the server no more transactions can be committed until pausing the server is stopped (StopPause). The server can pause only after finishing all running transaction commits.
The ...Pause commands can be used for keeping the database in a consistent state while backing up the database without closing the server. Pause commands should not be used when running long transactions as large imports or database reorganizations.
Transactions will not be committed anymore after pausing the server. The timeout interval for committing transactions is 10 minutes. When not being able to start committing the transaction within the time interval the transaction is canceled.
Any application may access the database in the pause state as long as not writing to the database, i.e. as long as not storing transactions to the database.
When the server cannot pause after the given timeout interval or 5 minutes the command stops without pausing the server. For allowing storing data to the database again one has to call the StopPause command.
StartPause servere port [timeout]
server - server url or IP address
port - port number for the server passed when starting the server
timeout - The StartPause command waits "timeout" seconds (default: 300) for committing active transactions. When any commit is still running after the timeout interval, the server will not pause (error 323).