You might think that Luckybackup is a tool only an end-user could love. Not so. Although Luckybackup is simple to use, open source, and free it’s a worthy candidate for business backup as well. Oh sure, you’re not going to image your machines with this backup tool, but you can backup your data. In this article I am going to show you how to install and use Luckybackup.

Installation

Installation is simple. If you’re lucky Luckybackup will be found in your distributions repositories. If that’s the case, just fire up your package manager tool, search for “luckybackup” (No quotes), select Lucky Backup for installation, and click apply. That’s it. If you’re not luck, and Lucky Backup isn’t in your repositories, then you will have to go to the Lucky Backup download page and download the binary for your distribution. Once you have that file it’s as simple as either letting your browser auto-detect and let a tool like GDebi install the package, or install from command line like so:

rpm -ivh luckybackup-XXX.rpm

Where XXX is the release number.

Using Lucky Backup

Figure 1

I am going to walk you through the steps for creating a remote backup using Lucky Backup. The remote backup I am going to illustrate uses ssh for the network transportation. For simplicities sake I am going to illustrate how you can do a backup with user intervention. To really make this work, you will want to set up password-less secure shell communication. You can see how this is done in my article “Five handy secure shell tips and tricks“.

Once installed open up a terminal window and issue the command luckybackup. This command will open up the user-friendly gui (see Figure 1) where you add all of the backups you want to create.

Let’s walk through the steps of creating an ssh-based backup.

Step 1: Click the Add button.

Figure 2

Step 2: Fill in the necessary pieces of information in the new window (see Figure 2). This information will include:

• Name: Name to give the backup.
• Type: Full or incremental.
• Source: What you want to backup.
• Destion: Directory on local or remote host to store backup.

REMOTE TAB:

• User remote host: Check this box.
• Destination: Check this box.
• User: Username on remote machine.
• Host: IP Address of remote machine
• Ssh: Check this box.

Step 3: Click Okay to save your settings.

Step 4: Click Start to begin the backup process.

If your backup was setup correct you will immediately be informed such and, in the terminal window where you started Lukcybackup from, you will prompted for the remote users password. Enter the password in that terminal window and hit enter. Your backup will begin.

As I mentioned earlier, to avoid having to be prompted for your password (this will be necessary for scheduled backup) you will need to set up password-less secure shell.

Final thoughts

That was simple. That is exactly how a backup tool should work. Give Lucky Backup a try, you may not find a Linux backup tool as simple to use.

All available network connections are discovered and added to the list of possible destination nodes. The user may select some or all of the nodes for the process. The source files can come from any directory of a connected computer. Depending on the settings of the application the files get overwritten if they exist or backed up first and then overwritten.

The user does have the option to copy selected files to only one network node by dragging and dropping files onto that node in the program interface. Otherwise the files will be copied to all selected destination nodes.

Remote Batch Copy can query and display network information of each node and also search for nodes that do not appear in the list that is automatically generated at program start.

The software program comes with a second mode called Delete Remote Files which is the exact opposite of the default operation. Selecting this mode will delete the selected files from all remote locations that have been added to the queue.

Configurations can be saved in sessions to be able to perform the configured operations again. Unattended Batch Copies can be executed this way which basically means that the whole operation will run in silent mode in the background requiring no user interaction.