I am (too) looking for an crashplan replacement. I am trying duplicati and so far it look really good. Awesome job guys
I am using win and linux machines.
With some (linux) machines I would like to start backups manually, because my “exclusions” are dependent on what mounts are currently active. Getting the command line string to start the backup is really easy thanks to the “export” function.
When I start a backup manually, I think it would be great if:
the current progress be shown in the WebUI
the Information on the “Last successful run” as well the Backup Information (size and no of Version)
would be updated in the Home view.
Could this even be considered a bug? It seems the WebUI does not know of the job started via command line. So if I start an operation there, would that get queued or would things get messed up because two jobs would try to run simultaneously?
ok. I understand. We are looking at two independent applications by design.
Maybe it is not feasible to show the progress of any currently running job in the WebUI, but might it not be a good idea to (optionally) let the command line app update the servers metadata (Duplicati-server.sqlite)?
I found this thread because I was wondering if anyone had had the same thoughts.
I’ve got Duplicati set up to remotely initiate backup of my data whenever the destination PC is powered on. Which is handy, but I made it work by calling a script that starts Duplicati by command line. Then I noticed that the webUI doesn’t count the command line backups.
So il support any efforts to tie the two together, or am intrested to know if I could do it myself.
The metadata is updated after running a backup, so just updating the local database does not update the metadata (in the Duplicati-server.sqlite database).
It would perhaps be possible to read the operation results from the local database, and update the metadata, but the data is stored in “human readable” format, not always easy to parse reliably, but it could be done.