|
From: | Ken Bass |
Subject: | Re: [Duplicity-talk] Backup problems 0.6.17 |
Date: | Mon, 09 Jan 2012 10:32:56 -0500 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 |
On 1/9/2012 10:12 AM, Kenneth Loafman wrote:
From what I recall (I removed the data), no timestamps changed other than the timestamp of the overall 'Desktop' directory. I am not using duplicity for the windows machines for a few reasons: 1) I'm not sure how reliable using duplicity would be under windows. I wrote my own python frontend to rdiff-backup on the PC that creates VSS (volume snapshots) so that open files can be backed up reliably. Without VSS, duplicity (or anything else) will have a problem with open files. 2) rdiff-backup gives you a snapshot of all your files. Retrieving a file is instantaneous. There is no need to restore anything. This makes the occasional data recovery of a file very fast. 3) Using rdiff-backup over ssh is faster than samba. 4) For Linux machines, I'm using safekeep which is basically a centralized environment for rdiff-backup. I am using duplicity only for offsite stuff where I need encryption. My only decision with duplicity is whether I want duplicity to backup the rdiff-backup-data directory which contains the reverse deltas. Right now I am. It probably is not needed/is redundant, but might allow for better speed when restoring. After reducing my Desktop folder to a much smaller size and starting over, it appears last nights incremental worked fine. So, can you tell me where in the code, a decision is made whether to backup a file or not? I'm trying to figure out/debug why it would have backed all my Desktop files up again when it should not have. Maybe there is a bug under some scenario that I can help track down if someone can point me in the correct direction. |
[Prev in Thread] | Current Thread | [Next in Thread] |