* Package name : bung Version : 3.0.3 Upstream Author : Charles Atkinson <bung@charlesmatkinson.org> * URL : https://redmine.auroville.org.in/projects/bung/files * License : GPLv2 Programming Lang: bash Description : Backup next generation (bung) bung has been developed over eight years as a campus backup utility, running on Debian and a few Ubuntu systems. It is known to be used on more than 100 computers Documentation includes man pages and user and programmer guides. The guides' primary format is .odt. The package includes .pdf and .html Guides are available from https://redmine.auroville.org.in/projects/bung/documents Selected text from https://redmine.auroville.org.in/projects/bung/wiki/Bung_technology follows bung is a set of wrapper scripts for several backup utilities: * OpenLDAP (slapcat and tar) * mysqldump * pgdump * rsync bung also has: * A "sysinfo" facility to generate system information reports * Templated backups allowing custom backup commands. Example templates are provided for Cisco switches and MikroTik routers bung features: * Automated backup to hotplug devices when they are plugged in with on-screen notifications to both character terminals and X displays * Backup to remote file systems via ssh * Custom commands (hooks) to run before and after the backup itself * File system hierarchy standard (FHS) compliant * GPLv2 * Logging designed to ease production support * LVM snapshots * man pages * Mounting and unmounting local file systems * Remote ssh command validation Best Charles Atkinson
Hi Charles That reminded me a lot to some tool I wrote 20 years ago or so for Solaris, later adapted also for Linux and FreeBSD: https://github.com/alexmyczko/ibackup including the sysinfo part, which I have in an up to date version, modernized a lot for todays need, I should release/update on that same page someday. Thoughts or parts you could profit from?
Hi Gürkan Yes, there are many similarities between bung and ibackup Regards "Thoughts or parts you could profit from?" ... Encryption. Bung would be better for having an encryption feature. Not yet implemented because a) increased risk of losing data by loss of decryption keys b) encrypted backups are harder to search for files wanted for restore I plan a simple form of encryption by using encrypted file systems on hotplug devices,. The backup user would need the key each time the file system was mounted so the key would be in regular use so harder to lose unless the user was incapacitated, un-co-operative etc. Once mounted, the file system could easily be searched for files wanted for restore Compression. Bung would be better for having an compression feature. Not yet implemented for the same reasons (except for key loss) that encryption has not been implemented Tarballs. tarballs are great for a point in time snapshot of a set of files. Bung's rsync wrapper creates a "rolling full" backup so the backup looks just like the source except for having a "Changed and deleted files" tree. That's important for ease of use and avoids the high backup volume of doing a full backup every time or periodically. OTOH restoring to an old point in time is difficult to approximate and impossible to do accurately ibackup has features to save conffiles for individual services such as bind. Bung does not because a) we use bung to backup all files except for exclusions (safest approach) so those files are already backed up and b) there are many such individual services and c) bung can be conffed to back up individual services conffiles/conftrees if required sysinfo. ibackup's uptime feature is nice. There are probably better (= less maintenance work) ways of generating sysinfo now than when than bung's sysinfo was developed.