The number of methods required by the ICompression interface is now reduce and all handling of path conversion and text encoding is now done in the CompressionWrapper class. This should make it easier to implement a new compression module, and reduce the number of errors that occur because of filename/encoding issues.
This commit also contains a fix for reporting a sane error message if the compression module is not found/loaded.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@1417 59da171f-624f-0410-aa54-27559c288bec
There is now an option called "vss-use-mapping" that activates DefineDosDevice and uses short DOS like paths.
I also find a little place that could be a performance problem, so maybe this fixes the issue even without the mapping.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@1413 59da171f-624f-0410-aa54-27559c288bec
This fixes issues #144, #577 and #320.
This update introduces a new options called "symlink-policy" that can be set to "store", "ignore" or "follow".
The default setting "store" means all symlinks are recorded as symlinks and recreated as symlinks on restore. This is chosen as default because it is the best replication of the actual disk contents.
Setting it to "ignore" simply means that no information is recorded about any symlinks.
And lastly, setting it to "follow" reverts to the previous default of treating symlinks as if they are normal files/folders.
Caveat: On Windows, you need Administrator privileges to create symlinks (when restoring), but not for reading them (on backup).
Since this change meant that the file attributes must be read, I also added support for the option "exclude-files-attributes", that can be used to ignore/exclude files with certain attributes, such as "hidden", "archive" or "encrypted".
Since I had to much about so much with getting the symlinks supported on Windows, I also added some extra logic to the Windows file handler, so it can now handle files and folders with up to 32k chars in the path. The logic is done so that the normal System.IO operations are used for paths with less than 260 characters (MAX_PATH), and on error or longer paths, the Win32 Unicode API is invoked. This should give maximal backwards compatibility and still allow backup and restore of files with long paths.
This commit also includes a BlockingQueue implementation that is supposed to make file/folder enumeration faster, but this has not been implemented because Duplicati depends on having a "whole world" view of the files and folders before running the backup (i.e. deeper changes required for this).
git-svn-id: https://duplicati.googlecode.com/svn/trunk@1381 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
The problem is that the the file-based backend returns "Directory not found" when asking for the not-yet-mounted folder.
Duplicati assumed that this error means that the folder will be created later, and thus returned an empty list,
as the folder would be empty when created. This means that the retry logic was not used.
Backing up to an empty folder will then result in a full backup being made.
But once the files started uploading, the folder is there and the folder is not created, but it is still a full backup.
This commit changes the logic a bit, so the list operation will not return until successful and a missing folder will be created during the list operation.
This ensures that the backup does not start before there has been a successful listing of the folder. If it fails, there is the normal retry delay, which should be enough to ensure that the folder is re-mounted. There may be warnings in the log, that the auto create failed. I have removed the logic that will auto create the folder during upload, as it should no longer be possible to get to the upload stage without verifying that the folder exists.
I have also changed the logic of the --disable-autocreate-folder option, so default value is "false" if it is a backup, and "true" for any other operation, so simply issuing a "list" or "cleanup" will not create folders (it did not do that before either).
git-svn-id: https://duplicati.googlecode.com/svn/trunk@1259 59da171f-624f-0410-aa54-27559c288bec
Update issue #296
I found and fixed a situation where a single file could be left open if the backup was stopped/aborted.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@1173 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
I found the problem, it was because Duplicati was trying to read the size of the file AFTER it was moved.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@1166 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
Duplicati now defaults to not upload a backup if nothing has changed.
This is indicated by a light-green check mark in the status window.
The option --upload-unchanged-backups can be set to revert to the previous way of working.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@958 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
There is now a delete transaction file being written, which should prevent cases where a large number of orphan files are detected.
If a large number of orphan files are detected, this should now be considered a real error.
I chose not to put in the cleanup button, because it would take too long for me to fit it in there, and I would rather focus on getting 2.0 ready, which will have a new UI anyway.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@957 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
Found and fixed a "slash vs. backslash" problem with files that span multiple volumes.
This will be included in the next preview release.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@950 59da171f-624f-0410-aa54-27559c288bec
kenneth@hexad.dk