sukria.net

A big thank to the grml team !

As backup-manager is not yet included in the official Debian tree and as it might take some time to be, grml now handles bug reports for the backup-manager project. As their Bug Tracking System is powered by debbugs (the same as official Debian team use) it would be really nice to use.

If you use backup-manager and want to report a bug, feel free to use the grml´s BTS !

Well, it seems that today is a real productive day for backup-manager !

I´ve released a new version of my backup tool to support the --conffile new option which was suggested by Michael. This new option allow you to specify different configuration files to backup-manager so that you can launch several instances of it simultaneously.

This new option required to rewrite the locking system which was global.
With this release, thanks to the new locking system, you can laucnh one backup-manager process per conffile you use.

This is pretty cool, it allows us to make really tricky things like that :

# backup-manager --conffile /etc/backup-manager-some-zip-rules &
# backup-manager --conffile /etc/backup-manager-some-tarballz-rules &
# backup-manager --conffile /etc/backup-manager-huge-archives-rules &
# backup-manager --conffile /etc/backup-manager-system-archives-rules &

We can also imagine a cronjob that will launch daily backup-manager with each /home/user/.backup-manager found to allow user to run their own backup rules

Here is the full changelog for the 0.5.0 release :

backup-manager (0.5.0-1)

• removed hard-coded path to the conffile to be more flexible.
• Added the –conffile option for giving to backup-manager an alternate
  configuration file.
• Adding the facility of handling multiple occurences of backup-manager
  to allow one backup-manager process per diffrent conffile used (locking
  system enhanced).
• New command line parsing system which is smarter than before and more
  flexible.

Jump to my personal repository or use my source list for the new deb

There was a minor bug in backup-manager 0.4.0 which broke the --force option.

You can grab the 0.4.1 release in my personal repository which fixes this bug.

Changelog is :

backup-manager (0.4.1-1)

• bugfix in backup-manager: –force didn´t work properly.
• Reference in debian/copyright to the GPL.

Thanks to Michael Prokop (The grml project leader) who has submited a nice patch for handling tar.bz and tar archives, I have enough changes to make a new release of backup-manager.

I´ve took the time to clean up every dirty things that remains in the package (most of it were lintian problems) and added Michael´s patch.

A new option is also added : –force which can tell to backup manager to overwrite existing archives.

I´ve also took the time to set a nice web page dedicated to backup-manager, this will be the real place to look at for news about backup-manager !

Thanks a lot to Michael for his patch and his nice comments and ideas

There was a major bug in the 0.3.0 release which is now fixed.

Archives didn´t have a good name when backup-manager was launched without the --verbose flag.

Please upgrade to backup-manager 0.3.1.

Thanks to Rached for reporting me that bug

Well, after some work, here we are !

A big change in this release is the support of scp transfert, based on ssh key authentification. User won´t need anymore to set ftp accounts in order to transfert archives (but it´s still available).

I´ve also added some manpages for backup-manager and backup-manager-upload.

Here is the changelog :

backup-manager (0.3.0-1)

• Added scp transfert mode based on key authentification.
• /etc/backup-manager.conf is chmoded 600.
• Added a lock system to prevent parallel processing.
• Lots of changes in backup-manager-upload, new command line.
• backup-manager can be run for just uploading files with the ´–upload´ flag.
• change of dependences : libnet-perl and ssh ar only suggested.
• Added man pages for backup-manager and backup-manager-upload.
• backup-manager-upload can use a specific private key for ssh authentification.

To grab backup-manager 0.3.0, just use my sources.list :

deb http://www.sukria.net/debian ./
deb-src http://www.sukria.net/debian ./

Feel free to report me bugs, this is a work in progress project !

By the way, a big thank to Andreas “Jimmy” Gredler for his nice post about backup-manager and for his comments

I’ve uploaded to my repository a new version of backup-manager, a small tool to manage quickly a list of backups.
The major change of this release is the debconf use for configuration.

backup-manager is designed to archive a list of directories and to keep them for a given number of days. User has the facility to set some remote host for uploading the files with FTP.

quoting the package description :

The idea is to specify all the important directories of the system.
backup-manager will generate tarballs (or zipped files) of all the specified directories.
Archives can be uploaded daily to a list of remote hosts.
Cleaning is done with purging each too old archive according to a specified number of days.

You can grab it from my repository :

apt-get install backup-manager

If you have a personal web server based on Apache, you´ll certainly be interested in using the lingerd daemon :

Lingerd is a daemon designed to take over the job of properly closing network connections from an http server like Apache.
[...]
Lingerd is particularily useful in Apache webservers that generate dynamic pages.

After some days of insane debian/rules hacking, I am proud to announce
that apache-lingerd is packaged.

Closing the #187460 RFP would be great !

You can get my package on my personal repository :

Add those lines to your /etc/apt/sources.list:

deb http://www.sukria.net/debian ./
deb-src http://www.sukria.net/debian ./

and install the package :

# apt-get update
# apt-get install apache-lingerd