There are a couple of steps to take in order to take a complete backup of Jama. At a high level, you will need to:
- Back up the database
- Grab a copy of the data folder*
Backup the Database
There are a few different ways to backup the Jama database:
- Create a proprietary database backup using native backup tools. This is the recommended backup method and you can find more information on backing up MySQL here and MSSQL here.
- Create a .jama file. The instructions for doing this are the same as if you were taking a backup when migrating from on-premises to hosted. The .jama file is most useful for migrating between different databases, but can also be used as a backup.
- Create a .xml file. The .xml file is most useful for migrating between different databases, but can also be used as a backup.
Grab a copy of the data folder*
Jama does not store things like attachments or reports directly within the Jama database. In addition to backing up the database, you need to make sure you also get a copy of those files. You can do this in one of three ways:
- Direct file copy
- Take a snapshot
- Create a .jama backup
Direct file copy
If you perform a direct file copy, you will need to target the following files and folders:
- Attachments: data/contour/attachments/
- Avatars: /data/contour/avatars/
- Backup: /data/contour/backup/
- Diagrams: /data/contour/diagrams/
- Metrics: /data/contour/metrics/
- Reports: /data/contour/reports/
Take a snapshot
Jama 8.0 introduces a new snapshot feature. More details about what is included in a snapshot and how to create/restore them can be found in the Jama Help Guide.
*If you have made modifications to the log4j.properties file to change Jama's default logging behavior, you will also need to back up that file manually. That file can be found in /data/log4jconfig.