apt-get install librsync-dev libz-dev libssl-dev uthash-dev make g++ bzip2 libncurses5-dev
After that you can download source in source in /usr/src
cd /usr/src tar -jxvf burp-1.4.40.tar.bz2 cd burp ./configure make make install
After that it is possibile start the burp server with this command
burp -c /etc/burp/burp-server.conf
Real-case config file server-side
password = <real strong password> timer_arg = 24h timer_arg = Tue,Wed,Thu,Fri,Sat,Sun,00,01,02,03,04,05,06,19,20,21,22,23 include = <path 1 to backup> include = <path 2 to backup> ..... exclude=<path to exclude> exclude=T:/BKSqlServer/model ratelimit=0.4 compression=2 . incexc/example keep = 7 notify_failure_script = /etc/burp/notify_script_wrapper notify_failure_arg = sendmail -t notify_failure_arg = To: <mail 1 to send backup error notifications> notify_failure_arg = To: <mail 2 to send backup error notifications> notify_failure_arg = From: <mail from to backup error notifications> notify_failure_arg = Subject: <Subject for backup error notifications> - %c %w
client="$1" backup_file="/mnt/nfs/$client/backup" touch "$backup_file" /etc/burp/notify_script "$@"
The usual case is that the client is running the ‘burp -a t’ command regularly (via cron or the Windows scheduler) and will contact the burp-server.
The server-side will then decide whether or not it needs a backup of the client at that moment, and will accept or reject the request as appropriate.
Using notify_script_wrapper an interrupted backup will be reattempted promptly.