You are not logged in.
Here's the PKGBUILD -- got a little more tweaking to do before I upload it to the AUR. This is my first package for Arch.
What it is:
Snebu is a snapshot style backup program I wrote, to get upgraded functionality from the rsync/snapshot I was using previously.
How it works:
A file listing (with meta data, including file mod time / ctime) is submitted to the backup server, which returns a list of files that it needs to complete the backup (any file that is already on the server gets referenced into the new backup run). The client side then submits the needed files via tar. File metadata from the tar input gets extracted and recorded in a database (sqlite3 based), individual files get compressed, SHA1 summed, and written to the filesystem (using the SHA1 as the file name). This gets full file-level deduplication, not only between snapshots but also across the whole file system, and across multiple clients backed up to the same server.
How it is different from rsnapshot
The backup catalog (which files belong to which backup, and associated metadata (owner, size, mod date, SHA1 checksum, etc) are recorded in a database, making for easy searching and reporting. This also eliminates the need to have root access to where the files are stored (the backup server can run everything under a "backup" user account).
How its different from Amanda, Bacula, etc.
Ease of set up -- single system setup is a breeze -- just install, configure a config file to point to where your backup media is mounted, configure include/exclude lists, and run. Backing up to a remote server, or pulling from a bunch of clients, also involves minimal setup.
Data integrity considerations:
The file data is stored in lzop compatible files, in the file system. The metadata (telling you which file, meta data, and server each file belongs to) is in several related tables with foreign key enforcement enabled. Also, individual backup sets' metadata can be exported to a tab-delimited file, and re-imported into another DB instance. Also, this SQLite db should either be located on internal storage, and backed up to the external media after each days backups are completed, or be stored on the backup media itself (note, this is slower, as USB drive access is typically pretty bad).
Note, I've been dogfooding this in a Red Hat environment for the past year or so, but am finally getting around to the polish and code cleanup. More updates are on the way. Documentation is at www.snebu.com.
Here's the PKGBUILD file.
pkgname=snebu
pkgver=1.02a
pkgrel=1
pkgdesc="A snapshot style multiple-client backup program"
url="www.snebu.com"
license=('GPLv3')
depends=('sqlite')
arch=('i686' 'x86_64')
source="https://github.com/derekp7/snebu/releases/download/v1.02a/snebu-1.02a.tar.gz"
md5sums=('f29e3e974016b6e6cbc760085ab7221e')
build() {
cd "$srcdir/${pkgname}-${pkgver}"
make
}
package() {
cd "$srcdir/${pkgname}-${pkgver}"
make install DESTDIR="${pkgdir}" BINDIR=/usr/bin
}
Offline