Backing up your server using JungleDisk Server Edition – part 1


This guide assumes you’re using a Debian-based (Ubuntu, Debian) build of Linux, and we’ll be using the 64-bit download from JungleDisk. The instructions don’t really change for the 32-bit version, except for the installer file name.

The first steps:

Go over to the JungleDisk Business page and sign up for, and download, the server edition. Now, this edition comes in two very important parts: The server-side program, and the management-side program.

The server-side program is what runs on your server. That’s the “backup engine” if you will. You will download the program appropriate for your server environment.

The management-side program is the program that you remotely connect to the “server” to configure it. You will download the program appropriate for running on your desktop computer.

It is fine to download the server-side version for Linux and the management-side version for Windows, if that is your configuration. In this case, I’m downloading the Linux .deb server-side installer for 64-bit linux, and the Windows management-side program. I can’t give you the actual download links; you’ll find them in your account page.

Now, on the server, I’m going to install the server-side engine as root. Navigate to the directory where you placed the downloaded file, and run:

sudo dpkg -i junglediskserver_315-0_amd64.deb

That will install the server. Follow the directions. Now, since it’s the deb package, it will automatically set up init scripts to make sure the jungledisk engine runs on startup. However, you will notice that at the end of the setup you were prompted to copy and edit an xml file. Copy /usr/local/share/jungledisk/junglediskserver-license-EXAMPLE.xml to /etc/jungledisk/junglediskserver-settings.xml

cp /usr/local/share/jungledisk/junglediskserver-license-EXAMPLE.xml /etc/jungledisk/junglediskserver-settings.xml

Now use your favorite editor to make a few changes to /etc/jungledisk/junglediskserver-settings.xml:

between and , enter your license key (found in your JungleDisk account).

Now, restart the jungledisk service.

/etc/init.d/junglediskserver restart

Myself, I also added my login user name and password between and respectively, but I don’t think it’s necessary. Worth keeping in mind if something doesn’t work right.

That’s all for the server-side configuration.

Now, on your management-side program, simply run the program and log into your JungleDisk account and your server should appear in the list. Double-click on it and the configuration screen will appear, where you can create backup sets and schedule them as you wish.

Want to correctly backup your MySQL databases in your backup set? See part 2 of this article, coming soon!

Comments are welcome, as always!


, , , , , ,

  1. #1 by NMI on March 28, 2011 - 7:23 am

    Awesome! Thanks for the tip Senior` Beach!

    • #2 by Mike on March 28, 2011 - 7:29 am

      No problem! Be sure to check back for part 2!

  2. #3 by Syamsul on April 2, 2011 - 8:30 am

    Thank you for the helpful tutorial!

    By the way, what would folders would you recommend backing up on a Debian/Ubuntu server to facilitate quick restore on another (in case it dies etc)?

    • #4 by Mike on April 2, 2011 - 12:11 pm

      That’s not an easy question to answer. You would probably want to start with the following:

      /etc (for configuration files)
      /usr/local (any locally-installed programs)

      Mind you, /etc and /usr/local are going to be unnecessarily large backups, and you can’t easily restore them in whole without likely mucking something up along the way.

      And schedule dpkg --list > somefile.txt to get your list of installed packages dumped to a text file.

      I’ll search around, but at the moment I don’t have much else in the way of advice.

  3. #5 by Chris J on August 8, 2011 - 10:21 pm

    The username and password field in the xml file are for if you are using a proxy server. They are not required otherwise. FYI.

    • #6 by Mike on August 8, 2011 - 11:32 pm

      Thank you for clearing that up for me!