You are responsible for making backups of your database and application server. On your application server you must regularly back up user data and take snapshots.
Snapshots are backups of the admin console settings. They are commonly used when migrating Jama to new hardware or during disaster recovery.
|•||The installed Admin Console|
|•||The current docker containers that make up Jama|
|•||Your license provided by Jama|
Note: Snapshots do not include the contents of the database, the contents of the /data directory or the log files.
Snapshots are made manually by selecting Start Snapshot on the Admin Console Dashboard. A maximum of 3 snapshots (by default) are kept on the application server.
|•||Snapshots can be stored in a custom directory, like /data/snapshots. Identify and configure this directory under Admin Console > Settings (gear icon) > Console Settings > Snapshots.|
|•||A snapshot should be made before every update of Jama.|
|•||A snapshot can be taken while the Jama application is running without interruption.|
|•||Snapshots are stored on the application server. Be sure to back them up regularly to a remote volume. It is best to store them within the /data directory so you only have one directory to back up.|
|•||If making a snapshot fails, the dashboard shows technical detail of the failure including the file or folder involved. Since this error message is generated from the underlying file system, (for example, readdirent: errno 523) it is likely a problem with the underlying file system that you must investigate separately from the Jama installation.|
|•||Additional Snapshot options can be configured through the Admin Console >Settings.|
Snapshots can be restored as follows:
|1.||Restore the snapshot directory using the same path on the new server as the old server. For example /var/lib/replicated/snapshots or /data/rsnapshots|
|2.||Ensure the data and database have been restored or are accessible to the new server.|