![]() I think most or all of this is fixed, so some retesting would be in order. A new backup should be created clean, and for that the configuration should have no history stored, lest becomes impossible to repurpose the same configuration file for a new backup altogether. The issue I'm reporting, then, is a usability issue with the config files. I don't know how Duplicati will handle the situation, I guess it will start over regardless and the information is just a harmless residue from reconfiguring the same backup, but it does give the impression that the same backup cannot be started over. Since I had changed to a new backend, having the transient data from the previous backup displayed on reimporting gave the impression that Duplicati will continue the backup from the position it last stopped in the previous backend, which is impossible and suggests the backup is bound to fail. These values are not part of the configuration proper, but a kind of history of the backup. My presumption was that, if I recreate a backup I deleted, by importing it's configuration, it should not remember properties like "Last successful run", number of versions and size. The database seems to be deleted properly, The only way I found to erase the history is to export as a json file and delete the relevant entries before importing. I noticed that changing the name won't help. Create a new backup with the same name.Īctual result: The deleted backup will resurrect with the full history as if it had not been deleted.Įxpected result: There should be a way of "resetting" a backup and starting it over, or at least the deletion of a backup should be complete and persistent, so you can recreate it.If I try to see the logs, for instance, I get the following error: Failed to connect: SQLite error no such table: LogData Steps to reproduce The recreated backup also seems to be left in an inconsistent state, as if part of it's data has in fact been deleted. It seems the only way to achieve this is to create a backup with a new name. Even if I export the configuration, delete the backup, and recreate it, it still remembers the history of the previous one. I decided to change the backend for my backups from ACD to Jottacloud, but I'm unable to make the backup "start over", that is, forget the history and begin from version 1 with the new backend. searched open and closed issues for duplicates.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |