Today we're going to create menu icons for launching our backups whenever we darned well feel like it, set up a simple network backup scheme, and create automatic scheduled backups.

Last week we got our backup hardware in order, so today we're going into detail on backing up our data to a locally-attached backup device. We'll learn how to configure which files to backup, and create an easy one-word-command backup.

You know how when someone accidentally deletes their files or their hard drive crashes or some other apocalyptic event occurs, the first thing people ask is “where is your backup”? Of course, we’ve all seen it (*ahem* been there :/ ). It’s a bit unintuitive, because backups have no equivalent in the real world. If you drive your car into a lake, there’s no way to get it back.

There are tons of possible backup solutions for the Linux desktop (and/or server). I have covered a number of possible solutions here on Ghacks. One of my favorite (and the one I use most often) is Luckybackup (see my article “Luckybackup: Linux backup made easy“), but that doesn’t mean there aren’t plenty of really good solutions.

I've been thinking a lot about backups recently and am starting to implement what I see as a fairly comprehensive backup system. Since it doesn't seem like there is enough good information about realistic backups systems and how people really use them, I am going to keep posting anything useful I learn. Before I get in to all the technical bits, I'm going to start with the planning stage.

You need several different methods of backing up your mail server. One of those methods is using a compressed tar file of all of the important configuration files and directories that have content for Postfix. In addition, you will need to add a timestamp for your backups to you can go back and dig out mail from the archives if needed.

"This HOWTO will describe how to install BackupPC and how to create a simple backup using backuppc. BackupPC can offer a nice solution for both simple and complex backups..."

If you aren’t doing remote backups you are at risk. In this post we discuss the problems with incremental sync backups and encryption and how to effectively produce encrypted remote backups that are bandwidth efficient. We will leverage an existing FTP server or show you how to set one up on your friends computer so you can swap data and never have to pay for a backup service again.

When you rent a dedicated server nowadays, almost all providers give you FTP backup space for your server on one of the provider's backup systems. This tutorial shows how you can use duplicity and ftplicity to create encrypted (so that nobody with access to the backup server can read sensitive data in your backups) backups on the provider's remote backup server over FTP. ftplicity is a duplicity wrapper script (provided by the German computer magazine c't) that allows us to use duplicity without interaction (i.e., you do not have to type in any passwords).