For clarification, TextPattern (“TXP”) doesn’t quite fit into the blog OR the CMS category because while out of the box it’s a blog, it’s designed to be flexible enough to be made into a CMS, per their FAQ.
I gripe about Wordpress security. Joomla’s had a pretty poor security history too, and both are commonly used as malware distribution points. Drupal’s had some bad ones, but they’re not as frequent as Wordpress (or even Joomla).
BackupPC (Uses SMB, SSH, etc. to remotely backup. No client installation necessary.)
Bacula (One of the grandpas- Bacula’s been around for a long while and it shows. Not very featureful, but pretty dependable. Difficult configuration.)
BoxBackup (Uses encryption for both data in-transit AND at-rest. Simple and clean, low overhead, but takes some severe finagling to play with non-GNU/Linux OSes.)
BURP (No, InfoSec nerds- not this Burp). BURP has some nice ACLs, but otherwise it serves as perhaps a slightly more user-friendly alternative to BoxBackup.)
DAR (Tarball-builder, but uses a non-tar format- it’s not proprietary, but offhand the only thing I know of that can work with DAR archive files is DAR itself. However, lets you then split this backup archive files into smaller pieces.)
Duplicity (Supports GPG encryption/signing and gzip, but basically just builds full or incremental tarball backups.)
Obnam (Simple, elegant, uses SSH for transit and allows for encryption of backups via GnuPG. Incremental backups, and allows for its archive files to be mounted via FUSE.)
rSnapshot (Doesn’t really delta or version or anything, it just copies over a file to backup if it’s been changed. It uses rsync and is pretty popular as a “Poor-Man’s Backup”, but it’s not very featureful or good for corporate settings. Similar to Jthan’s custom-brewed solution. …“Solution.”)
R1Soft (A commercial backup system for GNU/Linux and other OSes. It has some nice delta algorithms, but it sometimes eats data and requires a custom kernel module on clients.)
Unison (Unique in that it can “merge” snapshots from two different systems into one backup profile. Highly recommended for distributed environments, or git-like operations on the filesystem level/for binary data.)
…But we only mentioned ‘’‘BoxBackup’‘’ on the show. :)
We’d be remiss if we didn’t mention some offline/imaging/baremetal backup systems as well:
CloneZilla (Filesystem-aware, supports a multitude of different filesystems too. Can be used for BMR (Bare-Metal Restore) or cloning a single image across many machines. Has a LiveCD for small operations or a server implementation for larger ones.)
FSArchiver (PartImage reborn, essentially, except file-based instead of block-based. Much more flexible. Worthy to note that it doesn’t QUITE do the same job as PartImage; see their comparison.)
Mondo Rescue (This one’s pretty cool- it lets you take a BMR image from a ‘‘live, running system’‘ and lets you split to smaller archive files. It also can built a restoration LiveCD for you for BMR recovery.)
Partclone (Block-based imaging but not very network-friendly. Useful for storing “profiled” installs.)
PartImage (Mostly legacy, but offers a somewhat simpler alternative to CloneZilla- block-based. Limited filesystem support- no ext4 or btrfs, for instance.)
When I say “low regard for users”, I don’t mean as people. I mean in the nebulous sense of ID10T/PEBKAC issues, such as (l)users that tell you that you “just need to reboot the server” because that’s how they fix their Windows desktop, or ones that write their passwords down on Post-It™ notes under the keyboard- SURPRISE, EVERYONEANDTHEIRMOTHERKNOWSTHAT “TRICK”. STOPDOING IT. They continue to do things they are warned against doing multiple times or act as if they know your job better than you do without actual experience to back it up. Those are the (l)users I speak of.
In Audacity, “meter” is indeed the word I was looking for.
Jthan, it’s pronounced “Nazz” or “Nasz” or “Nass”, not “N-A-S”.