From 424855bd963bba733116da45597db82ce067d5be Mon Sep 17 00:00:00 2001 From: mainboarder Date: Thu, 12 Mar 2015 08:32:56 +0100 Subject: [PATCH] Explanation for recovery --- README.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4adffab..e7aadc2 100644 --- a/README.md +++ b/README.md @@ -11,4 +11,16 @@ Works for all versions. 3. Let the magic happen You can restore your data with -`duplicity --file-to-restore neddedFile $EXTERNALPATH/TO//media/mount/duplicity/path/to/file/ /where/to/save/now` +`duplicity -t nD --file-to-restore relative/neddedFile $EXTERNALPATH/TO//media/mount/duplicity/ /where/to/save/now` + +| Parameter | Description| +| ------------- | ------------- | +| `-t nD` | The version from how much days in the past should be recovered? | +| `relative/neddedFile` | Where, relative from the next parameter is the file in the backup? | +| `$EXTERNALPATH/TO//media/mount/duplicity/` | Where are the duplicity-files stored on the external storage? | +| `/where/to/save/now` | Where should the recovered file saved to (must not exist)? | + +Example: +`duplicity -t 8D --file-to-restore apache2/sites-available/site.conf ssh://backup@hostname2.domain.tld//home/hostname1/etc /home/user/site.conf` + +If you execute this on the machine where you want to restore an eight days old `/etc/apache2/sites-available/site.conf` from the external machine `hostname2.domain.tld`, then the recovered file will be saved in `/home/user/site.conf`