<< Click to Display Table of Contents >>

Navigation:  Automation Server > Automation Server configuration and administration guide > System maintenance and monitoring >



As with any system, backups of your Automation Server give you the option to:

Roll back unapproved changes to restore your system to a previous state, with as little downtime as possible.

Rely on a snapshot that serves as a restore point for contingency measures (in case of an unplanned event which affects your operations).

For these reasons, creating backups of Bizagi is an important task for system maintenance and administration.

For more information, refer to System administration.



Back up an operational Automation Server information at the database, its component files, and its case attachments, following the procedures described below.


1. Make database backups frequently

For Automation Server, database backups are the main tool for responding to any contingency, so generate these frequebtly.

It will be up to you and your policies to determine the frequency of making backups. Bear in mind that the higher the frequency, the lower the possibility of losing data when facing an unexpected event or disaster.


For this, consider:

We strongly recommend that you make database backups daily, at a minimum.

However and according to your analysis, sizing of the project or corporate policies, you may choose to make backups more frequently.

Backups may be created automatically by scheduling the use of agents and tools as provided by the database engine products themselves.

We strongly recommend that you make additional backups prior to any procedure which involves major changes in the database.

For instance, if you are planning a deployment of processes and new versions, or if you are planning a Bizagi version upgrade or certain changes in your implementation that require verification, then it is a best practice to make a database backup so you have a restore point to roll back changes to if (the results derived from the changes are not as expected).


For more information regarding how to create backups manually, refer to Database backups.


2. Make backups of other components, according to how often these change

In addition to the database, make backups within the Bizagi System to cover other components as well:


Files of the Work portal (Web application) and the Scheduler service

We strongly recommend that you make an initial backup of the files used by these components as soon as the configuration is properly set.

Make another backup, just before making any changes that would affect the Work portal or the Scheduler.

You can back up these files just before doing a procedure that changes them, such as a Bizagi version upgrade or applying a fix. Bizagi does not generate code, meaning that these files do not change or grow during daily execution of processes.

For more information about how to make backups of these files, refer to Work Portal and Scheduler backups.


Attachments (case files and documents uploaded from the processes).

By default, case attachments are not stored directly in the database, but separately in an ECM system or file server.

Make backups of the attachments of process instances, wheter they are stored in an ECM or on a file server according to your own-defined policy, at least once a day.

For more information about how to make backups of these attachments, refer to Attachments backups.