simple stupid backup tool
Bernhard Froehlich 08bf1209c0
Fix keep_weekly in core::clean() to keep sundays backups as weekly backups
1 week ago
lib Fix keep_weekly in core::clean() to keep sundays backups as weekly backups 1 week ago
rc.d Run rc startscript in background to avoid blocking startup of the system 2 weeks ago
LICENSE Initial commit 3 weeks ago
Makefile Fix file permissions for ssbt binary 3 weeks ago Document init(8) startscript 3 weeks ago
ssbt Implement rsync+zfs support by managing ZFS snapshots for the archive 3 weeks ago

ssbt (Simple Stupid Backup Tool)

You create a backup on your machine and ssbt will periodically collect and archive it.

  • Simple setup and maintenance
  • Automatic cleanup of old backups
  • sftp support (including chrooted sftp)
  • rsync support over ssh
  • zfs snapshot support
  • 1st class FreeBSD support (Linux support planned)

But why yet another backup solution?

Backups should be simple and reliable to make sure they are as painless as possible. I know there are a lot of tools out there with fancy webinterfaces, agents for whatever service you might run, multiuser, cross platform and much more. You will not find any of those features here.

What you will find is a simple shellscript which will periodically log into your machines with ssh(1) and pull tar archives from there which get archived.

You can continue to create your backups with tar(1) and be sure those are archived on your backup master.


Backup Master

Either download the release tarball and run make install or clone the git repository and run make install.

# git clone
# make install

The only mandatory setup is to set the backup directory for ssbt and make sure that it exists. If you want to run ssbt as non root (which is recommended!) then make sure the directory has proper owner/group and permissions.

# sysrc ssbt_dir="/backup"
# mkdir /backup

# adduser backup
# sysrc ssbt_user="backup"
# chown backup:backup /backup

It is recommended to use SSH certificates instead of passwords and create a dedicated ssh key that you can copy to all clients for fetching backups.

# ssh-keygen

You are good to go now. In this example we now add our first client

# mkdir /backup/

If ssh(1) setup was done properly a ssbt pull will transfer the backups.

# ssbt pull


To automate periodic pulls add this command to your crontab(5). It will be the same as pull + clean + status and will only create output if an error occurs or no recent backup for a host exists. If cron(8) is configured properly this will generate an email for you.

# ssbt cron

init(8) startscript

In case you want to run an automatic ssbt pull on machine startup you need to enable it:

# sysrc ssbt_enable="YES"


If you are using ZFS and have bigger amounts of slowly changing data then the type rsync+zfs will be relevant for you. It allows to transfer changed data with rsync and use ZFS snapshots for keeping multiple backups of that data.

# zfs create zroot/backup/

If you run ssbt with non root user it will need permissions to run zfs snapshot and zfs destroy on that filesystem (mount is a requirement of destroy).

# zfs allow -u backup snapshot,mount,destroy zroot/backup/


A account is needed which will be used by the master to login and fetch the backups. It is recommended to create a separate account with a separate SSH certificate. This account can also be limited to only allow sftp to reduce the risk.

This example assumes that you backup to /backup/data but this can be any directory.

# adduser -d "" -D -s nologin -w no
Username: backup
Full name: 
Uid (Leave empty for default): 
Login group [backup]: 
Login group is backup. Invite backup into other groups? []: 
Login class [default]: 
Shell (sh csh tcsh nologin) [nologin]: 
Home directory [/backup]: 
Home directory permissions (Leave empty for default): 
Use password-based authentication? [no]: 
Lock out the account after creation? [no]: 
Username   : backup
Password   : <disabled>
Full Name  : 
Uid        : 1001
Class      : 
Groups     : backup 
Home       : /backup
Home Mode  : 
Shell      : /usr/sbin/nologin
Locked     : no
OK? (yes/no): yes
adduser: INFO: Successfully added (backup) to the user database.
Add another user? (yes/no): no

# mkdir -m 0755 /backup
# install -d -m 0700 -g backup -o backup /backup/.ssh
# install -d -m 0700 -g backup -o backup /backup/data

# install -m 0400 -g backup -o backup /dev/null /backup/.ssh/authorized_keys
# echo "...your-public-key-here..." > /backup/.ssh/authorized_keys

# printf "\nMatch User backup\n" >> /etc/ssh/sshd_config
# printf "\tChrootDirectory %%h\n" >> /etc/ssh/sshd_config
# printf "\tForceCommand internal-sftp\n" >> /etc/ssh/sshd_config
# printf "\tX11Forwarding no" >> /etc/ssh/sshd_config

# /etc/rc.d/sshd reload

Creating a backup

Feel free to use whatever backup script you want. The only requirement is that the filename needs to contain the date and time in the following format directly before the filename extension.

# date "+%Y%m%d%H%M"

So here is a backup script as an example:


FILE=/backup/data/`uname -n`-backup-`date "+%Y%m%d%H%M"`.tar.xz

touch ${FILE} && chmod 0600 ${FILE} && chown backup:backup ${FILE} && \
cd / && tar -cJf ${FILE} \
    boot/loader.conf \
    etc \
    root \
    usr/local/etc \
    var/cron || exit 1

exit 0


A global config file exists in /backup/.ssbt.conf and all parameters can be overwritten in a host configuration in /backup/{host}/.ssbt.conf:

rsync_flags="-av --delete"


ssbt is released under the 2-clause BSD License. Parts of the code were copied from under the 2-clause BSD License. Thanks a lot for this great code!