[Zodb-checkins] CVS: ZODB3/Doc - storages.html:1.6

[Toby Dickenson]

Update of /cvs-repository/ZODB3/Doc
In directory cvs.zope.org:/tmp/cvs-serv6066/Doc

Modified Files:
	storages.html 
Log Message:
more detailed comparison of incremental backup tools. Thanks to Barry.

=== ZODB3/Doc/storages.html 1.5 => 1.6 ===
--- ZODB3/Doc/storages.html:1.5	Tue Jun 17 05:34:29 2003
+++ ZODB3/Doc/storages.html	Tue Jun 17 10:21:51 2003
@@ -400,10 +400,17 @@
 
 <tr>
 <td class="filestorage">
-Yes, using repozo.py.
+Yes, using repozo.py, full and incremental backups. Incremental backups
+write a file that only contains the changes, but it has to read the whole storage
+into memory before producing it. (or a third option saves the IO cost, but exposes
+some risk of corrupt backups)
 </td>
 <td class="dirstorage">
-Yes, using a standard script with a tar backend.
+Yes, using backup.py script, full and incremental. Incremental backups
+write a file that contains the changes, and it only needs to read the changed files
+while creating it.
+Backups events are transactional; you will not be left with a half-complete backup
+file if power is lost during or after the backup process.
 </td>
 <td class="bdbstorage">
 Yes, as BerkeleyDB.
@@ -421,7 +428,7 @@
 </td>
 <td class="dirstorage">
 Yes, A standard script to replicate changes into an identical storage directory
-on another machine.
+on another machine. Efficient and transactional.
 </td>
 <td class="bdbstorage">
 No.