Overview
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 restore a database backup so that can go back to a previous state of the database.
For information about the uses of a database backup with Bizagi, refer to How to create a backup of your Bizagi database.
|
It is not adequate to use backups for any other purpose than the ones mentioned in the link 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 restore a backup of your Bizagi project's database, refer to the chapters below.
•If you are using SQL Server, refer to SQL Server restore.
•If you are using Oracle, refer to Oracle import.