[Box Backup-commit] COMMIT r2309 - box/boxbackup-web

Wed Oct 1 14:42:18 BST 2008

Author: jamesog
Date: 2008-10-01 14:42:17 +0100 (Wed, 01 Oct 2008)
New Revision: 2309

Modified:
   box/boxbackup-web/comparison.html
Log:
Update comparison page, as requested by the Bacula folks (via Ben).


Modified: box/boxbackup-web/comparison.html
===================================================================

--- box/boxbackup-web/comparison.html	2008-10-01 12:37:21 UTC (rev 2308)
+++ box/boxbackup-web/comparison.html	2008-10-01 13:42:17 UTC (rev 2309)
@@ -1,186 +1,199 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Comparisons to other backup systems</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<div id="header">
-<div id="logo">
-<img src="images/bblogo.png" alt="logo" height="65" width="331" border="0" vspace="5" align="middle" /> <img src="images/stepahead.png" alt="a step ahead in data security" width="182" height="11" hspace="10" vspace="20" border="0" align="middle" /></div>
-</div>
-<div id="page">
-
-<h1>Comparisons to other backup systems</h1>
-
-<p>Within this document, <i>encrypted</i> and <i>on-line</i> are used in very specific ways to describe backup systems.</p>
-
-<dl>
-<dt>encrypted</dt>
-<dd>The data to be 
 backed up is transmitted and stored on the server so that the data can only be recovered if secret encryption keys are available.</dd>
-
-<dt>on-line</dt>
-<dd>The backup server does not use tape or any other removable archive media. All data is stored within the server file system on conventional hard discs, and every (current) file is always available.</dd>
-</dl>
-
-<p>Only backup systems which are both encrypted and on-line are compared in depth. Other systems have brief notes at the end of this document.</p>
-
-<p>Please email me with any systems I have missed, or corrections to my analysis. This is not intended to promote Box Backup, but as an objective comparison to allow you to decide which system to adopt.</p>
-
-<h2>Encrypted, on-line systems</h2>
-
-<table border="0" cellspacing="4" cellpadding="1">
-<tr><td></td><td><b>Box Backup</b></td>
-<td><b><a href="http://www.nongnu.org/duplicity/">duplicity</a></b></td>
-<td><b><a href="http://miek.nl/projects/hdup16/hdup
 16.html">hdup</a></b></td>
-</tr>
-
-<tr><td>Development status
-</td><td>stable, under development, not feature complete</td>
-<td>"not stable yet" <a href="http://www.nongnu.org/duplicity/#ToC4">(details)</a></td>
-<td>stable, maintainance only</td>
-</tr>
-
-<tr><td>Changes only when uploading new versions of existing files (like rsync)
-</td><td>yes</td>
-<td>yes</td>
-<td>no</td>
-</tr>
-
-<tr><td>Connects to server using
-</td><td>TLS (SSL)</td>
-<td>ssh/scp, local file access, rsync, ftp</td>
-<td>ssh, local files</td>
-</tr>
-
-<tr><td>Authentication
-</td><td>SSL certificates (client and server)</td>
-<td>Traditional file storage accounts on server (eg unix username,
-virtual FTP etc)</td>
-<td>Traditional file storage accounts on server (eg unix username,
-virtual FTP etc)</td>
-</tr>
-
-<tr><td>Dependencies
-</td><td>OpenSSL</td>
-<td>Python installation, librsync, GnuPG, remote shell</td>
-<td>ssh, mcrypt/GPG, GNU tar</td>
-</tr>
-
-<tr><td>Signed data storage
-<
 /td><td>Implicit</td>
-<td>Explicit with GnuPG</td>
-<td>Implicit/Explicit with GnuPG</td>
-</tr>
-
-<tr><td>Scheduling
-</td><td>Self-contained with randomised element to avoid cyclic server loading, or cron job</td>
-<td>cron job</td>
-<td>cron job</td>
-</tr>
-
-<tr><td>Continuous backup
-</td><td>Yes -- backs up files a configured time after being changed, or...<br>No -- in snapshot mode</td>
-<td>No -- takes a snapshot of the filesystem when it is run</td>
-<td>No -- takes a snapshot of the filesystem when it is run</td>
-</tr>
-
-<tr><td>Handling of old versions and deleted files
-</td><td>Old and deleted files remain on server until store reaches a set limit, after which they are removed. No particular limits on availiability apart from this size limit.</td>
-<td>Full and incremental backups, deletion by user scripts</td>
-<td>Monthly full backups, weekly and daily incremental, deletion of archives by user scripts</td>
-</tr>
-
-<tr><td>Resources used on client
-</td>
 <td>Few Mb of memory, very small amount of disc space</td>
-<td>Status and checksums for all files backed up, plus potentially large temporary files. (however, disc space is cheap, so this is not an issue unless the clients are older machines with small hard drives)</td>
-<td>Minimal (latest versions can stream archives directly to server)</td>
-</tr>
-
-<tr><td>Resources used on server
-</td><td>Disc space</td>
-<td>Disc space, remote shell server, UNIX accounts</td>
-<td>Disc space, ssh, UNIX accounts</td>
-</tr>
-
-<tr><td>Redundant storage on server
-</td><td>Optional built in userland RAID storage</td>
-<td>Relies on OS to provide RAID</td>
-<td>Relies on OS to provide RAID</td>
-</tr>
-
-<tr><td>Restore
-</td><td>FTP-like client, or simple command to restore entire directories</td>
-<td>Simple command to restore entire directories, fetch files or directories by name.</td>
-<td>Simple command to restore entire directories, fetch files or directories by name, will fetch 
 entire archives for single files.</td>
-</tr>
-
-</table>
-
-
-<h2>Other systems</h2>
-
-<table border="0" cellspacing="4" cellpadding="1">
-
-<tr><td></td><td>Encrypted?</td><td>On-line?</td><td>Network</td><td>Notes</td></tr>
-
-<tr><td><a href="http://www.amanda.org/">Amanda</a></td>
-<td>no</td>
-<td>no</td>
-<td>LAN</td>
-<td>The classic network backup system</td>
-</tr>
-
-<tr><td><a href="http://www.bacula.org/">Bacula</a></td>
-<td>no</td>
-<td>yes</td>
-<td>LAN</td>
-<td>Comprehensive job control. Stores lists of backed up files in a database for faster retrieval.
-Can backup to disk as well as tape. Supports encrypted transfer, but not storage.</td>
-</tr>
-
-<tr><td><a href="http://rdiff-backup.stanford.edu/">rdiff-backup</a></td>
-<td>no</td>
-<td>yes</td>
-<td>Remote</td>
-<td>"The idea is to combine the best features of a mirror and an incremental backup."</td>
-</tr>
-
-<tr><td><a href="http://www.rsnapshot.org/">rsnapshot</a></td>
-<td>no</td>
-<td>yes</td>
-
 <td>Remote</td>
-<td>Perl script. Pulls files over ssh from the source server to the backup server. Creates efficient
-snapshots of the source filesystem.</td>
-</tr>
-
-<tr><td><a href="http://samba.anu.edu.au/rsync/">rsync</a></td>
-<td>no</td>
-<td>yes</td>
-<td>Remote</td>
-<td>Requires extra scripts for automatic scheduling and old version archival. May be less efficient than Box Backup, as it needs to check for existence of every file on the remote side, whereas Box Backup keeps an efficient record.</td>
-</tr>
-
-<tr><td><a href="http://www.mondorescue.org/">Mondo Rescue</a></td>
-<td>no</td>
-<td>no</td>
-<td>n/a</td>
-<td>Backup to local media, aimed at full system recovery.</td>
-</tr>
-
-
-</table>
-
-<p>"Network" is marked as LAN if the system uses so much bandwidth it can only be used on a LAN, Remote if it uses bandwidth conservation techniques which make it suitable for use over an internet connection.</p>
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p
 >
-<p> </p>
-</div>
-</div>
-</body>
-</html>
-
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
+<title>Comparisons to other backup systems</title>
+<link rel="stylesheet" href="bbstyles.css" type="text/css" />
+</head>
+<body>
+<div align="center">
+<div id="header">
+<div id="logo">
+<img src="images/bblogo.png" alt="logo" height="65" width="331" border="0" vspace="5" align="middle" /> <img src="images/stepahead.png" alt="a step ahead in data security" width="182" height="11" hspace="10" vspace="20" border="0" align="middle" /></div>
+</div>
+<div id="page">
+
+<h1>Comparisons to other backup systems</h1>
+
+<p>Within this document, <i>encrypted</i> and <i>on-line</i> are used in very specific ways to describe backup systems.</p>
+
+<dl>
+<dt>encrypted</dt>
+<dd>The data to be backed up is transmitted and stored on the server so that the data can only be recovered if secret encryption keys are available.</dd>
+
+<dt>on-line</dt>
+<dd>The backup server does not use tape or any other removable archive media. All data is stored within the server file system on conventional hard discs, and every (current) file is always available.</dd>
+</dl>
+
+<p>Only backup systems which are both encrypted and on-line are compared in depth. Other systems have brief notes at the end of this document.</p>
+
+<p>Please email me with any systems I have missed, or corrections to my analysis. This is not intended to promote Box Backup, but as an objective comparison to allow you to decide which system to adopt.</p>
+
+<h2>Encrypted, on-line systems</h2>
+
+<table border="0" cellspacing="4" cellpadding="1">
+<tr><td></td><td><b>Box Backup</b></td>
+<td><b><a href="http://www.nongnu.org/duplicity/">duplicity</a></b></td>
+<td><b><a href="http://miek.nl/projects/hdup16/hdup16.html">hdup</a></b></td>
+<td><b><a href="http://www.bacula.org">Bacula</a></b></td>
+</tr>
+
+<tr><td>Development status
+</td><td>stable, under development, not feature complete</td>
+<td>"not stable yet" <a href="http://www.nongnu.org/duplicity/#ToC4">(details)</a></td>
+<td>stable, maintainance only</td>
+<td>stable, under development, adding high end features</td>
+</tr>
+
+<tr><td>Changes only when uploading new versions of existing files (like rsync)
+</td><td>yes</td>
+<td>yes</td>
+<td>no</td>
+<td>yes</td>
+</tr>
+
+<tr><td>Connects to server using
+</td><td>TLS (SSL)</td>
+<td>ssh/scp, local file access, rsync, ftp</td>
+<td>ssh, local files</td>
+<td>TLS (SSL) if configured</td>
+</tr>
+
+<tr><td>Authentication
+</td><td>SSL certificates (client and server)</td>
+<td>Traditional file storage accounts on server (eg unix username,
+virtual FTP etc)</td>
+<td>Traditional file storage accounts on server (eg unix username,
+virtual FTP etc)</td>
+<td>CRAM-MD5 (default) plus SSL certificates (all components) if configured</td>
+</tr>
+
+<tr><td>Dependencies
+</td><td>OpenSSL</td>
+<td>Python installation, librsync, GnuPG, remote shell</td>
+<td>ssh, mcrypt/GPG, GNU tar</td>
+<td>None after building</td>
+</tr>
+
+<tr><td>Signed data storage
+</td><td>Implicit</td>
+<td>Explicit with GnuPG</td>
+<td>Implicit/Explicit with GnuPG</td>
+<td>With OpenSSL PKI if configured</td>
+</tr>
+
+<tr><td>Scheduling
+</td><td>Self-contained with randomised element to avoid cyclic server loading, or cron job</td>
+<td>cron job</td>
+<td>cron job</td>
+<td>Built-in scheduler</td>
+</tr>
+
+<tr><td>Continuous backup
+</td><td>Yes -- backs up files a configured time after being changed, or...<br>No -- in snapshot mode</td>
+<td>No -- takes a snapshot of the filesystem when it is run</td>
+<td>No -- takes a snapshot of the filesystem when it is run</td>
+<td>No -- takes a snapshot of your defined FileSet when it is run</td>
+</tr>
+
+<tr><td>Handling of old versions and deleted files
+</td><td>Old and deleted files remain on server until store reaches a set limit, after which they are removed. No particular limits on availiability apart from this size limit.</td>
+<td>Full and incremental backups, deletion by user scripts</td>
+<td>Monthly full backups, weekly and daily incremental, deletion of archives by user scripts</td>
+<td>Automatic pruning of catalog, Volumes recycled when needed</td>
+</tr>
+
+<tr><td>Resources used on client
+</td><td>Few Mb of memory, very small amount of disc space</td>
+<td>Status and checksums for all files backed up, plus potentially large temporary files. (however, disc space is cheap, so this is not an issue unless the clients are older machines with small hard drives)</td>
+<td>Minimal (latest versions can stream archives directly to server)</td>
+<td>Minimal -- runs as a daemon</td>
+</tr>
+
+<tr><td>Resources used on server
+</td><td>Disc space</td>
+<td>Disc space, remote shell server, UNIX accounts</td>
+<td>Disc space, ssh, UNIX accounts</td>
+<td>Minimal -- unless local disks used as Volumes</td>
+</tr>
+
+<tr><td>Redundant storage on server
+</td><td>Optional built in userland RAID storage</td>
+<td>Relies on OS to provide RAID</td>
+<td>Relies on OS to provide RAID</td>
+<td>Relies on OS to provide RAID, uses tape</td>
+</tr>
+
+<tr><td>Restore
+</td><td>FTP-like client, or simple command to restore entire directories</td>
+<td>Simple command to restore entire directories, fetch files or directories by name.</td>
+<td>Simple command to restore entire directories, fetch files or directories by name, will fetch entire archives for single files.</td>
+<td>Simple command to restore entire directories, fetch files or directories by name, will fetch entire archives for single files.</td>
+</tr>
+
+</table>
+
+
+<h2>Other systems</h2>
+
+<table border="0" cellspacing="4" cellpadding="1">
+
+<tr><td></td><td>Encrypted?</td><td>On-line?</td><td>Network</td><td>Notes</td></tr>
+
+<tr><td><a href="http://www.amanda.org/">Amanda</a></td>
+<td>no</td>
+<td>no</td>
+<td>LAN</td>
+<td>The classic network backup system</td>
+</tr>
+
+<tr><td><a href="http://www.bacula.org/">Bacula</a></td>
+<td>yes</td>
+<td>yes</td>
+<td>LAN</td>
+<td>Comprehensive job control. Stores lists of backed up files in a database for faster retrieval.
+Can backup to disk, DVD, and tape. Supports encrypted transfer and encrypted storage.</td>
+</tr>
+
+<tr><td><a href="http://rdiff-backup.stanford.edu/">rdiff-backup</a></td>
+<td>no</td>
+<td>yes</td>
+<td>Remote</td>
+<td>"The idea is to combine the best features of a mirror and an incremental backup."</td>
+</tr>
+
+<tr><td><a href="http://www.rsnapshot.org/">rsnapshot</a></td>
+<td>no</td>
+<td>yes</td>
+<td>Remote</td>
+<td>Perl script. Pulls files over ssh from the source server to the backup server. Creates efficient
+snapshots of the source filesystem.</td>
+</tr>
+
+<tr><td><a href="http://samba.anu.edu.au/rsync/">rsync</a></td>
+<td>no</td>
+<td>yes</td>
+<td>Remote</td>
+<td>Requires extra scripts for automatic scheduling and old version archival. May be less efficient than Box Backup, as it needs to check for existence of every file on the remote side, whereas Box Backup keeps an efficient record.</td>
+</tr>
+
+<tr><td><a href="http://www.mondorescue.org/">Mondo Rescue</a></td>
+<td>no</td>
+<td>no</td>
+<td>n/a</td>
+<td>Backup to local media, aimed at full system recovery.</td>
+</tr>
+
+
+</table>
+
+<p>"Network" is marked as LAN if the system uses so much bandwidth it can only be used on a LAN, Remote if it uses bandwidth conservation techniques which make it suitable for use over an internet connection.</p>
+
+<p> </p>
+<p>© Ben Summers and contributors, 2003-2008</p>
+<p> </p>
+</div>
+</div>
+</body>
+</html>


