Work portal and Scheduler backups

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Maintenance and administration > Backing up Bizagi >

Work portal and Scheduler backups


As part of common maintenance and administration tasks, it is of critical importance to always be able to rely on backups for the possibility to restore your project to a previous state, should an unexpected event occur.

In addition to database backups, you should always take backups of the files used by Bizagi components, i.e the Work portal and the Scheduler service.

Apart from the initial backup of these components, it is recommended to take backups just before making changes to them.

Backing up these files can be done just before doing certain procedures, such as a Bizagi version upgrade or a fix applied (Bizagi does not generate code, meaning also that such files do not change or grow over time -within the daily execution of processes).

For more information, refer to Backing up Bizagi.



Work portal and Scheduler backups

Create copies of the folders and files structure as used by the Work portal and Scheduler.

In order to create backups of these files and configurations, copy these folders into a secure location (preferably in an external device or in cloud storage).

You should back up such folders and files where these components are installed.

The paths to these are:


Work portal: Files found at

C:\Bizagi\Projects\[your_project]\Web Application\.

Scheduler: Files found at






Consider backing up additionally:

Case attachments, which by default are stored in the Docs folder if you are not using an ECM and if you are not using a dedicated file server for this purpose.

Recall backing up case attachments should be done a lot more frequently than files of the Work portal and Scheduler (ideally, with the same frequency as database backups).

Other components and files which make part of your implementation's bespoke code and customizations.

This includes any .dll assemblies, style sheets and overrides, etc, or other components you consider relevant.