|
From: <di...@us...> - 2008-02-25 00:57:49
|
Revision: 577
http://safekeep.svn.sourceforge.net/safekeep/?rev=577&view=rev
Author: dimi
Date: 2008-02-24 16:57:47 -0800 (Sun, 24 Feb 2008)
Log Message:
-----------
Clarify snapshot usage.
Modified Paths:
--------------
safekeep/trunk/TODO
safekeep/trunk/doc/safekeep.backup.txt
Modified: safekeep/trunk/TODO
===================================================================
--- safekeep/trunk/TODO 2008-02-24 16:53:23 UTC (rev 576)
+++ safekeep/trunk/TODO 2008-02-25 00:57:47 UTC (rev 577)
@@ -4,7 +4,6 @@
* Add tests db dumps
* Avoid snapshotting snapshots
* Don't snapshot a device if a snapshot is already present
- * Clarify snapshot usage in docs
* local backup to bypass ssh
Feedback from users:
Modified: safekeep/trunk/doc/safekeep.backup.txt
===================================================================
--- safekeep/trunk/doc/safekeep.backup.txt 2008-02-24 16:53:23 UTC (rev 576)
+++ safekeep/trunk/doc/safekeep.backup.txt 2008-02-25 00:57:47 UTC (rev 577)
@@ -179,9 +179,11 @@
Optional, defaults to "false".
/backup/setup/snapshot/@device::
- The path (device location) to the LVM volume to snapshot
- before the backup commences. It is recommended.
- Multiple snapshots may be specified, in which case the
+ The path (device location) to the client LVM volume to snapshot
+ before the backup commences. Note that the snapshot happens
+ on the client machines, and it ensures that the data that is
+ being backed-up is in a consistent state throughout the backup
+ process. Multiple snapshots may be specified, in which case the
order is important, the associated filesystems are mounted
in the order given.
Please note that using this feature requires that `safekeep(1)`
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|