From JumpBox Documentation Wiki

How can I troubleshoot Backup or Restore?

Caution The instructions or information on this page may damage your JumpBox if performed incorrectly or used carelessly. It is advised that you test these instructions on a test JumpBox to ensure that you understand the process and that these instructions apply to your specific JumpBox release. Proceed with extreme caution. (details)

First you should make sure you are familiar with how backup and restore work, what the limitations are and have read the other FAQs. If you really think you have a problem or have been directed to this FAQ by JumpBox support then you can proceed with the suggestions on this page. Proceeding without knowing what you are doing could lead to data loss.

Running Manual Backup

If you are getting error email from the nightly backup job or the "Run Now" doesn't generate a backup you can manually run the backup by SSHing into the JumpBox as admin and running the following command:

 sudo ruby /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb start_backup_real

This command assumes that you have already configured your backup settings and will fail if it is not configured.

Running Manual Restore

If you know you have a good backup and an error is occuring during the restore process you can use the following process to see more detailed output from the restore.

• Enable SSH on the destination JumpBox.
• SCP the backup to /tmp on the JumpBox. Ensure that you have enough space for at least two times the backup file. Some of the JumpBoxes (like Trac and Redmine) may need 3-4 times the backup file size for this procedure. If you do not have enough space, the backup will fail. See the JumpBox Disk Space FAQ to learn how to make more space.
• SSH into the JumpBox as the admin user.
• Run the following command, you must provide the complete path to the backup file followed by the JumpBox version of the backup:

 sudo ruby /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb run_restore_real \
 /tmp/jb-drupal6-1.1.12_drupal_f41a67a471c911deae46030c29921241_20090831182324.tgz 1.1.12

Note the command is split onto two lines using the \ character, you can put it all on one line and remove the \ if you prefer. The general form of the command is:

 sudo ruby /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb run_restore_real PATHTOFILE VERSION

You will see some output on the command line but should not see anything that looks like an error or stack trace.

If you are working with a JumpBox Engineer, provide all of the output from the backup and or restore commands used above.