When working in a Bizagi Studio project to automate processes, the database for that project will store all the information relevant to those processes and their implementation (Bizagi being data-driven).
Information not contained in the database will mainly be any documents attached to the processes, which are stored by default in a file server, or at an integrated ECM system.
You may create a database backup of your Bizagi project for any the following purposes:
1. For contingency measures, in order to have a snapshot of your Bizagi project at certain stage.
This is useful and recommended before carrying out a major change such as a version upgrade, in which you may want to have the possibility to restore the project back to a previous state.
2. For Bizagi support service, in order to provide our support team the means to track and diagnose a specific issue.
This is useful to debug and find a solution to issues in your project.
3. To easily move a project from one server to another, or clone it to reuse that implementation as a template (applies while the project is still in automation stages).
Furthermore, moving a project considers the possibility to set up a teamwork collaboration architecture by keeping the progress of a project that has been already worked on.
It is not adequate to use backups for any other purpose than the ones mentioned above.
For instance, to publish your processes into a Production or Test environment, you should never use backups and use instead Bizagi Deployment features.
Bizagi offers a Deployment Wizard to easily promote processes and keep track of incremental changes in such processes (for new process versions and continuous improvement).
To create a backup of your Bizagi project's database, refer to the chapters below.
•If you are using SQL Server, refer to SQL Server backup.
•If you are using Oracle, refer to Oracle export.