Changed the non-streaming file-backend interface to use sytem copy calls rather than
manual stream copy.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@654 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
There were some issues with namespaces and signing of the files,
which caused the translations to not load.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@649 59da171f-624f-0410-aa54-27559c288bec
Update issue #323
Status: Fixed
I see the problem, in SSHUI.cs line 107, the keyfile option is always set, even if it is empty.
I have added checks to detect the empty string in the UI and the backend itself.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@639 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
There is now a Tahoe-LAFS backend option.
It is quite new, so obviously it is fairly untested in real life.
It passes all unittests, and is largely based on the WEBDAV backend which as seen some action.
I will put up a preview build with Tahoe-LAFS support soon.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@623 59da171f-624f-0410-aa54-27559c288bec
I have now added preliminary support for keyfiles under SSH.
For the time being it only supports OpenSSH private key files, and only unencrypted or tripple-DES encrypted ones.
This is a limitation of the SharpSSH library, which is based on an old JSCH implementation with this limitation.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@622 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
I found the error in the USN handling code.
The problem was that the filename was compared case insensitive, when doing USN file listing.
This caused all my tests to pass (as the folders have the correct case).
I managed to type it with the incorrect case in a test setup and found the error.
I will put up a new preview soon with the fix.
I would recommend that you use that version instead and delete the usn-policy setting from the backup.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@605 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
Now allows 1% (max 1 hour) slack in the time difference.
Can be disabled with the --disable-time-tolerance flag.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@595 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
Yes, nicely spotted, thanks for reporting.
It seems that the settings was actually saved and applied,
but just didn't show up, so a re-save would clear it.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@594 59da171f-624f-0410-aa54-27559c288bec
I certainly don't mind fixing minor issues.
Spelling errors have a tendency to make the product look
incomplete, so I appreciate spelling error reports.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@590 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
The implementation is a mix of the the three mentioned methods (issue #247).
There is a commandline option called --open-file-policy, which can be set to
"ignore", "snapshot" or "copy".
The "ignore" setting does the same as previous version, simply exclude the file from the
backup set.
If the setting is either "snapshot" or "copy", and the file it locked, it is opened in non-excusive read mode.
Once open, a in-memory signature file is generated. This is compared to the previous signature to detect changes,
just as the normal operation. If the file has not changed, the file is skipped as it would normally be.
If the file has changed and the policy is "snapshot", the file will be processed as normal,
but during the file read, a new signature is generated. This new signature is stored
in the signature archives. When writing the new signature, it is compared to the original signature.
If the file has changed during the backup operation, a warning is written to the output log.
If the policy was set to "copy", the modified file is copied to a temporary location,
while a new signature is generated. If the copy fails due to a file change, the file
is omitted from the backup set. If the copy succeeds, the file is known to not have changed
during the first access and the copy, which gives some assurance that the file is not
actively being written, at the expense of a copy operation.
The default setting is "snapshot", because this is likely to work in most scenarios,
and potentially produces a broken file rather than guarantee a missing file (by "ignore").
Note that when reading an open file, there is always a chance that the file is being written,
so you may end up with a broken file in the backup. This is also true for the VSS and LVM snapshots,
except for VSS-aware applications.
The "copy" method is meant to minimize this risk, but there is no guarantee that the file is in an
acceptable state, just because it has not been written for any period.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@588 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
USN is now activated by default on windows, but requires Administrative privileges.
If it fails to activate, it is silently ignored, and normal filesystem enumeration is used.
Set --usn-policy to:
"on" to get a warning if it fails,
"required" to abort the backup if it fails
"off" to disable USN
"auto" to silently ignore a fail
git-svn-id: https://duplicati.googlecode.com/svn/trunk@584 59da171f-624f-0410-aa54-27559c288bec
Added the --vss-exclude-writers option.
Update issue #260
Status: Fixed
I have now added a --vss-exclude-writers commandline option.
I had another look at the other supported options, and I consider this the most important.
I made the simplest possible version, so it only supports class guids, not component names
or writer instance ids.
If you need any of the other switches or the component names, please let me know.
I would also be interested in hearing that it actually works (I get no errors, but thats no proof).
You can specify multiple writers with a semicolon: --vss-exclude-writers="{d61d61c8-d73a-4eee-8cdd-f6f9786b7124};{0bada1de-01a9-4625-8278-69e735f39dd2}"
If you need the guids, you can get them with the following command in a command prompt:
vssadmin list writers
git-svn-id: https://duplicati.googlecode.com/svn/trunk@574 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
The logic was attempting to prevent a case where the backup was scheduled to run and "Run backup now" was checked.
In this special case, the "Run backup now" does nothing because the backup will run twice otherwise.
The logic was a bit flawed, so based on some various settings it would detect that it was scheduled to run,
while it was not.
Thanks to your fine description, I was able to reproduce easily and fix it.
With the regards to the other error message, I have reproduced it by doing the following without restarting:
1) create the backup
2) edit the backup
3) delete the backup
I will create a new issue for it, but the bug is deep in the database abstraction layer,
so it is pretty hard to debug.
Update issue #227
Status: Fixed
Now correctly removes the deleted task from the scheduler and updates the display.
I also managed to get a slight speedup on the display update.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@572 59da171f-624f-0410-aa54-27559c288bec
After a fix with source folder filters, the internal file "added_folders.txt"
contains the root folder entry, but not suffixed with a slash/backslash,
which caused an "index of of bounds" error when attempting to restore.
Update issue #295
Status: Fixed
I found 3 situations where an opened file was not closed.
Strange thing is that it should have been that way since the multivolume stuff was introduced.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@569 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
Added a find-last-version command to the commandline version,
it takes the same input as a restore operation, so
use --file-to-restore to supply a list of files to search for.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@559 59da171f-624f-0410-aa54-27559c288bec
Previously some backends autocreated a missing folder, and some threw an exception.
The new standard is that all backends throw the FolderMissingException on all access (except delete).
This means that the Test() and List() methods are now the same for all stock backends.
Third-party applications that use the backends should implement custom logic to auto-create the folders,
when the FolderMissingException is encountered.
Duplicati auto-creates missing folders, but this can be toggled through the new flag --disable-autocreate-folders.
In case the auto-create fails to detect a missing folder, there is now a "create-folder" action in the commandline version.
Update issue #102
Status: Fixed
The IBackend_v2 interface has the CreateFolder and Test methods.
The CreateFolder is exposed to the commandline interface with the action create-folder.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@558 59da171f-624f-0410-aa54-27559c288bec
I have now fixed the issue, and tested it on the file provided.
It seems to compress better now, although the file contains sporadic changes,
even if only a single line was added. The restore also works as expected,
and the update works on my unittest.
Could you please try the updated version and see if it works as expected for you as well?
With regards to the "no else statement" (comment 7), I think that you discovered another
bug, which I have also fixed. The else statement is there to ensure that the buffer is completely filled,
so long chains of unmatched data gets written with as few commands as possible. So, on the first entry,
the copy command is flushed and the force_buffer_refill is set, causing the buffer to refill.
The bug was that IF the buffer was already full, the stream would read 0 bytes, and return a count of 0.
This was then interpreted as if the stream was empty (it returns zero when empty). I have now fixed that
with a check for this special case.
I have also included an update to the ChecksumFileReader that splits the previous m_weakTable into two
separate arrays, as that gives a faster lookup, than using a custom comparer. I also added support for
very large files (files larger than blocksize * int.MaxValue, appx. 4TB).
git-svn-id: https://duplicati.googlecode.com/svn/trunk@548 59da171f-624f-0410-aa54-27559c288bec
Added name support in GUI and commandline version.
When restoring from commandline, subfolders will now be named like the source folders, if only one source folder is given.
When restoring from GUI, the names will be suggested like in the commandline.
It is no longer required that the unused folders exists when restoring a multi-source backup from the GUI.
Added size tooltips to the restore GUI window with the list of backup chains.
Now correctly deletes old signature cache files, even if they use the old names.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@542 59da171f-624f-0410-aa54-27559c288bec
Update issue #235
I have now added a simple version of the collection-status command,
which shows Type, Time, Volume count and Size for each backup set,
with the incrementals listed under the full's they belong to.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@540 59da171f-624f-0410-aa54-27559c288bec
Status: Fixed
The new strategy is to provide general assembly redirects.
These are generated during the build procedure and added to the output.
Using these redirects it is possible to load a new/old version of a backend
(or other module) into Duplicati.
To ease testing, it is now also possible to place a dll for a backend in
a subfolder named "backends" and it will override the normal backend.
To remove the test backend, simply stop Duplicati and delete the "backends" folder.
The same works for compression, encryption, generic modules, and settingcontrols
with the folders "compression", "encryption", "modules", and "settingcontrols"
respectively.
git-svn-id: https://duplicati.googlecode.com/svn/trunk@536 59da171f-624f-0410-aa54-27559c288bec
