Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test button should detect an existing backup at the target location #407

Closed
kenkendk opened this issue Aug 5, 2014 · 4 comments
Closed

Comments

@kenkendk
Copy link
Member

kenkendk commented Aug 5, 2014

From rst...@gmail.com on May 03, 2011 15:12:22

I have several folders on drive D:\ that are backupped with 2 jobs. One is running perfectly. The other produces an error:

The backup should access 4 folders on D:\ and create an unencrypted backup on drive z:\ which is a network share.

Both jobs (encrypted and unencrypted) are stored in the same destination. Could it be that this leads to confusion. If so, it should not be possible to create such a mess or duplicati should be able to handle such situations.

Error: Failed to download file: Der Wert darf nicht NULL sein.
Parametername: passphrase

Error: System.Exception: Failed to download file: Der Wert darf nicht NULL sein.
Parametername: passphrase ---> System.Security.Cryptography.CryptographicException: Der Wert darf nicht NULL sein.
Parametername: passphrase ---> System.ArgumentNullException: Der Wert darf nicht NULL sein.
Parametername: passphrase
bei Duplicati.Library.DynamicLoader.EncryptionLoader.EncryptionLoaderSub.GetModule(String fileExtension, String passphrase, Dictionary2 options) bei Duplicati.Library.Main.BackendWrapper.GetInternal(BackupEntryBase remote, String filename, String filehash) --- Ende der internen Ausnahmestapelüberwachung --- bei Duplicati.Library.Main.BackendWrapper.GetInternal(BackupEntryBase remote, String filename, String filehash) --- Ende der internen Ausnahmestapelüberwachung --- bei Duplicati.Library.Main.BackendWrapper.ProtectedInvoke(String methodname, Object[] arguments) bei Duplicati.Library.Main.BackendWrapper.Get(BackupEntryBase remote, String filename, String filehash) bei Duplicati.Library.Main.Interface.GetManifest(BackendWrapper backend, ManifestEntry entry) bei Duplicati.Library.Main.Interface.FindPatches(BackendWrapper backend, List1 entries, String tempfolder, Boolean allowHashFail, CommunicationStatistics stat)
bei Duplicati.Library.Main.Interface.Backup(String[] sources)
bei Duplicati.GUI.DuplicatiRunner.ExecuteTask(IDuplicityTask task)
InnerError: System.Security.Cryptography.CryptographicException: Der Wert darf nicht NULL sein.
Parametername: passphrase ---> System.ArgumentNullException: Der Wert darf nicht NULL sein.
Parametername: passphrase
bei Duplicati.Library.DynamicLoader.EncryptionLoader.EncryptionLoaderSub.GetModule(String fileExtension, String passphrase, Dictionary2 options) bei Duplicati.Library.Main.BackendWrapper.GetInternal(BackupEntryBase remote, String filename, String filehash) --- Ende der internen Ausnahmestapelüberwachung --- bei Duplicati.Library.Main.BackendWrapper.GetInternal(BackupEntryBase remote, String filename, String filehash) InnerError: System.ArgumentNullException: Der Wert darf nicht NULL sein. Parametername: passphrase bei Duplicati.Library.DynamicLoader.EncryptionLoader.EncryptionLoaderSub.GetModule(String fileExtension, String passphrase, Dictionary2 options)
bei Duplicati.Library.Main.BackendWrapper.GetInternal(BackupEntryBase remote, String filename, String filehash)
Cleanup output:

Original issue: http://code.google.com/p/duplicati/issues/detail?id=407

@kenkendk
Copy link
Member Author

kenkendk commented Aug 5, 2014

From kenneth@hexad.dk on May 03, 2011 09:24:47

Yes, you cannot store two backups in the same folder without changing the "backup-prefix". I recommend using separate folders for the backups.

I have created an entry in the FAQ that describes this: https://code.google.com/p/duplicati/wiki/FAQ#Q:_Can_I_store_multiple_backups_on_the_same_server? Let me know if this is not an acceptable answer.

Status: Done
Owner: kenneth@hexad.dk

@kenkendk
Copy link
Member Author

kenkendk commented Aug 5, 2014

From rst...@gmail.com on May 03, 2011 10:09:19

For me it is ok. Now I know it and have a work around for my problem. But I guess other users might run into the same issue too. I have thought about a few things. Here is my suggestion.

  1. Check if another backup is present before a backup is performed. This is a robust implementation in case users manually move existing backups around or fall into the same trap that I fell into.

  2. Store files in an additional, self-created sub-folder. E.g. the user defines as destination D:\backup\ and duplicati stores it in D:\backup\hash(backupname). When an existing installation is updated it needs some logic (is manifest located in folder/hash(backupname)? No-> try folder/ instead.

The only thing I do not like about this idea: If a user stored 10 backups in D:\backup\ and wants to restore a specific one from a clean installation, how can this be identified?

I'll have a look at the restore procedure tomorrow to see what can be done here...

@kenkendk
Copy link
Member Author

kenkendk commented Aug 5, 2014

From kenneth@hexad.dk on May 04, 2011 00:17:24

I prefer suggestion (1). Suggestion (2) is the same as with the backup-prefix, it moves the problem to the user who has to enter/select/know something that is not entirely obvious.

I have reopened this issue with a new title.

Summary: Test button should detect an existing backup at the target location
Status: Accepted
Labels: -Type-Defect Type-Enhancement

@kenkendk
Copy link
Member Author

kenkendk commented Aug 5, 2014

From kenneth....@gmail.com on October 01, 2011 07:55:59

This issue was updated by revision r922 .

The backends now check for existing files in the target directory,
and specially looks for any "duplicati-*" files.

Status: Fixed

@kenkendk kenkendk closed this as completed Aug 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant