Table of contents
Before generating 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, please 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 BigPicture backup and download it
Go to BigPicture App Configuration > Advanced > Database dumps
Press the New dump button, add a description, and confirm (Create dump button)
The new database dump should appear at the top of the list of backups (page refresh may be needed).
Press the Download button to save the backup file to disk.
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 (Restore)
Step 4 - install BigPicture on a staging environment
Cloud
Go to Jira Apps > Find New Apps and search for the BigPicture plugin.
Server
Go to System > Manage apps and install BigPicture.
Step 5 - restore BigPicture backup on a staging environment
Go to BigPicture App Configuration > Advanced > Database dumps
Upload the app database dump (Import button)
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 go to the BigPicture application and verify the correctness of the data.
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, move the switch in the Active column in the App Configuration > Integrations > Connections panel:
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
Dump and restore should be done in the same version of the application (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 | dump created in a higher App version, then restore Example:
| Upgrade the application - upgrade the BigPicture that you are trying to run a 'restore' on to be the same on which the 'dump' file was created. |
Case 2 | dump created in a lower App version than the restore Example:
| Not possible. BigPicture doesn't support rollbacks. |