Installation

Contents 1 Install from package 1.1 Debian / Ubuntu 1.2 Fedora 1.3 RHEL (Red Hat / CentOS) 2 Install from tar archive 2.1 Slackware 2.2 Install from Github (developers only)

Install from package

Debian / Ubuntu

Install backup-manager from your distro repository

sudo apt-get install backup-manager

If you want a cutting-edge version on Ubuntu Karmic, you can use benmur's Ubuntu PPA to grab his Github snapshot releases.

Fedora

Since Fedora 9, you can install Backup Manager from distro repository :

yum install backup-manager

To enable the automation of backup on a daily task, you can go through a personnal cron or simply activate that already present in the package (/etc/backup-manager.conf):

# RPM-specific : Enabled daily cron
export BM_DAILY_CRON="true"

RHEL (Red Hat / CentOS)

Install backup-manager from the EPEL repository (How to use EPEL)

yum install backup-manager

To enable the automation of backup on a daily task, you can go through a personnal cron or simply activate that already present in the package (/etc/backup-manager.conf):

# RPM-specific : Enabled daily cron
export BM_DAILY_CRON="true"

Install from tar archive

Dependencies: If you want to enable the localisation, you need gettext. Perl is needed for FTP and SSH uploads. Everything else is written in Bash.

Download the latest stable or development version from the Backup Manager website & untar in a directory

~/backup-manager $
~/backup-manager $ su
~/backup-manager # make install
~/backup-manager # cp /usr/share/backup-manager/backup-manager.conf.tpl /etc/backup-manager.conf
~/backup-manager #

Edit configuration file

sudo gedit /etc/backup-manager.conf

for info on configuration option please read the documentation

Slackware

Slackware users might like to change the default install locations. The default Makefile installs into the /usr tree, whereas the Slackware way is to install local builds into the /usr/local tree. You could use DESTDIR with make to install into a temporary directory, then build a package and install it, or you could edit the Makefile. For a simple set of source files like Backup-Manager's, I choose to edit the Makefile and install locally. It's very simple.

Copy the Makefile so you have a backup, then edit it. With a few exceptions, you can simply search-replace all instances of /usr with /usr/local.

Just note that the exceptions below are minor and not to be sweated; I list them for completeness. The exceptions are:

• Perl modules: the Makefile by default installs perl modules into /usr/lib/perl5/site_perl/{etc}. Long ago I decided not to create separate library directories for Perl packages and Perl modules I build myself, so I don't attempt to put modules into /usr/local/. Perl is such a mish-mash anyway, and the last thing I need is yet another Perl include path to worry about;
• Localisation files are handled separately with a Makefile in the po sub-directory. You could edit it also to change /usr to /usr/local, or it will install in /usr/share/locale and not /usr/local/share/locale. Since I'm in an en country, localisation is not significant to me and I rarely bother to fiddle with po files (since it won't affect me if they all get hosed). In this case, I can't be bothered and will allow the Makefile to put the files into /usr/share/locale, the default place and not technically the Slackware way which is /usr/local/share/locale;
• Man pages: (You don't need to be concerned about this, it is just a note in case something goes wrong.) Technically, the install should put man pages into /usr/local/man and not /usr/local/share/man, which is what happens if you simply do a search-replace of the Makefile. This doesn't really matter since the latter directory is linked to the first one anyway, at least on my system. You may want to check if this is the case on yours. If not, move the contents of /usr/local/share/man to /usr/local/man and make /usr/local/share/man a link to /usr/local/man.

Install from Github (developers only)

You can grab the very last development version of Backup Manager from our Github repository.

First of all, you need Git to be installed on your system. On Debian/Ubuntu systems:

$ sudo apt-get install git-core

Then, you can clone the repository:

$ git clone git://github.com/sukria/Backup-Manager.git 

Next times you want to update your clone, do the following:

$ cd Backup-Manager
$ git pull git://github.com/sukria/Backup-Manager.git  master

See git documentation for more details.

To actually install Backup Manager, just do as explained in the "Install from tar archive section".