This article describes the process taken by our system when generating daily backups (.lxp files). It may be helpful to customers who have scheduled runs setup to start around the same time as the backup.
When the backup starts, it kicks of this process:
1. Wait for any outstanding REST requests to be completed
2. Block most new incoming REST requests (excluding token validation and some simple operations that won't cause DB interaction)
3. Suspend execution of new jobs associated with schedules
4. Suspend initiation of any new node executions
5. Suspend updating the database with the results of any nodes completing
Note: There may have been nodes that started execution before the backup started, that complete during the backup window, for example a long database query.
Once the backup completes, any nodes that completed execution during the backup window will have their results persisted to the database. Therefore, it is possible to get messages written to the log files from a node that started execution prior to the backup - but this should not impact the successful creation of the backup.