Data backups for Deployment Migrations On-premise to Cloud

Dana Medhaug
Dana Medhaug
  • Updated

Author: Dana Medhaug

Date: December 12, 2023

Audience: Everyone

Summary: Traditional and KOTS channels

During deployment migrations, customers are required to provide database backups and assets (attachments, avatars, reports, diagrams, equations, and metrics). The following is a list of backup types.

Backup Options:

  1. To create a backup of your data on Jama Connect®, log in as root and download the .jama backup file from the backup tab. This file contains all the necessary information, including the database and various assets like attachments, reports, diagrams, equations, and metrics. It is an excellent option for small to medium-sized data sets and is compatible with MSSQL and MySQL. When you click to download the .jama backup, the file will be located in the /data/contour/backups directory for native replicated installations; for KOTS installs, the file will be located in the core-0 pod in the /home/contour/tenant/tenant_name/backup directory on the application server. Customers can exec into the core-0 pod to retrieve the backup file by using
    kubectl exec --stdin --tty core-0 /bin/bash
  2. To create a backup file in .xml format, you can follow the same steps for creating a .jama backup file from the backup tab. However, you need to log in as the root user of the application. The XML backup option helps move from MSSQL to MySQL and has a large dataset. In such scenarios, the .jama option is not suitable. Please note that the XML backup file contains only the database, not the assets. You must back up the assets separately. After clicking the button to download the XML backup, the file will be located in the /data/contour/backups directory for native replicated installations; for KOTS installs, the file will be located in the core-0 pod in the /home/contour/tenant/tenant_name/backup directory on the application server. Customers can exec into the core-0 pod to retrieve the backup file by using
    kubectl exec --stdin --tty core-0 /bin/bash
  3. MSSQL proprietary backup: MSSQL backup for extensive data; separate asset backup; refer to MSSQL guide MSSQL documentation
  4. MySQLDump: The MySQLDump file is for customers already on MySQL with extensive data. We provide the command below for them to take the MySQLDump.
    mysqldump --max-allowed-packet=25M --single-transaction --skip-add-locks --routines --set-gtid-purged=OFF -u root -p databasename > databasename.sql
  5. Backing up assets: When any option other than a .jama file is needed, the assets must be backed up and sent to us separately. We do this by having customers "tar up" the assets. They must navigate to /data/contour and run the command below.
    tar -czvf assets.tar.gz avatars/ attachments/ diagrams/ reports/ equations/ metrics/

     With KOTS installations, the customer must exec into the core-0 pod, navigate to the /home/contour/tenant/tenant_name/ directory, and use the tar command above to tar their assets.


Taking the backup:

  1. .jama backup, log in as the root user, and select option #3 in the backup tab
    2023-12-12_09-23-56.png
  2. .xml backup, log in as the root user and select option #2 in the backup tab
    2023-12-12_09-23-56.png

Data Set Sizing

Small - XML = 1G or less, .jama = 2GB or less, MySQLDump = 1G or less

Medium - XML = 2G - 3G, .jama = 2GB - 3G, MySQLDump = 2G - 3G

Large - XML = 3G or more, .jama = 3GB or more, MySQLDump = 3G or more

 

Please feel free to leave feedback in the comments below.

 

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.