Contents: |
|---|
Before you generate a dump file, upgrade the App (to version 8.2.2 or higher).
Follow the steps below if the staging environment is the same as the production environment.
Server → Server
Data Center → Data Center
Cloud → Cloud
Server → Data Center
Steps overview
Before proceeding, read the instructions carefully and copy all steps to the clipboard to keep it on hand.
Create application backup (production environment).
Create Jira backup (production environment).
Restore Jira backup on a staging environment.
Install the application on a staging environment.
Restore application backup on a staging environment.
Step 1 - Create a BigPicture backup and download it
In this part, you need to create a BigPicture backup and download it:
Go to BigPicture/BigGantt App configuration > Advanced > Database dumps.
Click the New dump button.
Add a description.
To confirm, click the Create dump button.
You can track the progress:
The new database dump should appear at the top of the list of backups.
Press the Download button to save the backup file to the disk (if you don't see the item on the list, refresh the page).
Step 2 - Create a Jira backup and download it
Cloud:
Go to System > Backup Manager > Create backup for cloud.
Server:
Go to System > Backup system > Backup.
Step 3 - Restore Jira backup on a staging environment
Cloud:
Go to System > Restore System > Import data (import the Jira backup file).
Server:
Go to System > Restore system.
Restore using the Jira backup file.
Click Restore.
Step 4 - Install BigPicture on a staging environment
Cloud:
Go to Jira Apps > Find new apps.
Search for the BigPicture plugin.
Server:
Go to System > Manage apps.
Install BigPicture.
Step 5 - Restore BigPicture backup on a staging environment
Go to BigPicture App configuration > Advanced > Database dumps.
Click Import.
Upload the app database dump.
Press the Restore button in the line with the backup name.
Confirm the next step by selecting Migrating between instances, e.g., production to staging, and press the Next button.
Check the confirmation box and press the Next button.
Confirm the operation by entering the word RESTORE and clicking the Restore button.
Info: If the BigPicture instance is not new and some work has already been done, this work will be overwritten! BigPicture will automatically dump its current state before restoring it (so the process can be reversed). 
The database recovery process will start.
After the recovery process, the migration from one instance to another is over. You can then go to the BigPicture application and verify the data's correctness.
Additional information
Instance status after restore
Any integration instances after the restore operation will be in a ‘not operational’ state.
This mechanism prevents a situation where two applications make changes in the same integration instance simultaneously.
To activate selected integrations:
Go to App Configuration > Integrations > Connections.
Move the switch in the Active column.
Data center vs server
If the restore process is performed on the DC machine, but the dump file was done on the server machine, a reinstall process of the application will be required:
Application version mismatch
The dump and restore should be done in the same application version (e.g., a backup dump was created in BigPicture 8.2.3, → restore should be done in BigPicture 8.2.3).
App versions | Fix | |
|---|---|---|
Case 1 | A dump is created in a higher App version than the restore. Example:
| Upgrade the application Upgrade BigPicture that you are trying to run the restore action on to be the same on which a dump file was created. |
Case 2 | A dump is created in a lower App version than the restore. Example:
| Not possible. BigPicture doesn't support rollbacks. |