Some thoughts to the WebUI

Drive letter:
so this means, duplicacy will orientate itself on the drive letter? Very bad idea. If a user does not uses this tool you mention things may go wrong. Duplicati has an easy solution for this:

You can just place an emtpy file with a random name on the drive. Duplicati will then use this file to get the backup medium right. Simple and reliable.

I just saw that a check can be scheduled. This can be done once a weak and would nearly met my criteria but the pc has to be running at the time there I scheduled it.
This brings me back to the catch up of the missed backups :slight_smile:

A storage has a special structure:


So when :d: tries to connect to your storage (on the usb drive) if it won’t find the config file, then it will error out. I believe this to be enough.

There is ofc one case where even this may fail: if you have multiple external HDDs, and they all have the same storage init-ed at the same location. In that case i honestly blame it on you though :stuck_out_tongue:

1 Like

You can also use windows scheduler to run duplicacy. This gives you options to run missed backups/checks as soon as the computer is turned on.

Regarding the drive letters: I had missed that you were talking about storage. I thought you wanted to backup those external drives. When it comes to storage, there is no problem as TheBestPessimist mentioned above.

Will it search through all connected drives? So in case of a letter swap, will it find the correct drive? Will the user be informed in case of error?

This makes the usage very complicated. in this case I could also use the cli version which is free for personal use. The webui should target users who want an easy to configure backup solution. The webui is very very close to it and it would be sad if it will fail only because missed backups can not be addressed.

idk :-/ (i wouldn’t expect it to, though)

I hope so. (idk either)

I’m not a web-ui user, so all i’m saying here is from what i read in other posts and what i know from my cli usage.

I only see a notification option via mail but only in scheduled jobs. I do not want to be informed every hour about an successful backup.
perhaps @gchen can comment on this :slight_smile:

edit: Video finished:

No, of course not (@gchen, correct me if I’m wrong). It only looks at the storage path, i.e. only the drive letter under which the drive was originally registered. If the path doesn’t exist or if it doesn’t find the config file, I suppose ot will exit with an error, just like it will if your trying to backup to any other unavailable destination.

Great! Would you like to post it in a separate topic?

Since we’re pinging Gilbert anyway, I’d like him to confirm how duplicacy is supposed to be pronounced according to him. In my mind, the - acy is pronounced as in privacy. So that would put the emphasis on the syllable pli in duplicacy, but in some versions of English perhaps it’s also possible to ephasize the du. I’m not a native speaker…

my speaker used both versions in the video :smiley:
But me and the speaker are also not native (as you may have already guessed :wink: )
Would be nice to get the hint from @gchen

yes give me a second


feel free to change the category if I got it wrong

Yes, the email after each completed schedule is the only notification.

That is correct.

I’m not a native speaker either, so I really don’t know which syllable should be stressed. Maybe someone here can recommend an official pronunciation?

Did you mean ? Without the ‘s’ it takes you to a domain reseller. However this is a cool idea! I was thinking of using email filters and maybe IFTTT, but that wouldn’t really help with missed backups. The Crashplan service has a tendency to stop working or not restart occasionally and it takes the “no backup” email for X days before I realize it.

Yes, sorry, fixed it.

This would make it a show stopper for me for windows.
Users must be informed if something is going wrong :wink:

Why not using the same methoed as duplicati does? Drive letter is really a bad idea in windows and if the user does not gets informed in case of an error… this is a receipe for desaster :scream:

1 Like

This is not as easy as it sounds.

In fact, literally just this second, I checked the Duplicacy web edition icon in the tray next to the clock. Hovered over the icon and it disappeared. Duplicacy, was in fact, not running.

This is an issue I’ve been seeing for the past several weeks but am unable to put a finger on it. My PC is on 24/7 and I leave it logged in. Once a week or two I’ll notice Duplicacy isn’t running. Why? I have no idea! The Windows event logs don’t show any crashes. My last successful backup today was at 12:15 but the 14:15 (and 16:15 & 18:15) backup didn’t run according to the dashboard. Sometimes a day or two will pass before I notice it isn’t running. Luckily, today I only missed a few hours.

Anyway, the point I’m trying to make… Duplicacy itself can’t tell you if something like that goes wrong, if it isn’t even running. :slight_smile:

Hence the purpose of an external service like I recently set up an alert for a customer’s system running Vertical Backup (Duplicacy’s brother for ESXi hosts) and set up a pre-script to ping a given URL. If it doesn’t run, I get an email notification. I may have to do the same on my personal machine.


This is not my point. If a program crashes it can not alert the user this is clear. But if the backup medium is missing the user should be alerted. There is an easy solution to this. What do you think of a threshold which can be user defined. This threshold should check for the last successful backup and measure the time which has past since then. If the value is too high it should send a mail.
This would also help if duplicacy crashes entirely. At the next start a mail could be triggered that the last Backup is too old.

1 Like

I like this idea and I definitely think notifications could be more finer grained.

1 Like

I could try to write a script but for that I would need a time stamp format which can be set in relation to the actual time. Any ideas how to do this?

Normally when the web GUI crashes it will leave the stack trace in the ~/.duplicacy-web/logs/duplicacy_web.log. If you can’t find anything there maybe you can try ProcDump? This page has instructions on how to do that for a Windows service but it should work the same way for the web GUI:

2 posts were merged into an existing topic: How to pronounce duplicacy?

Thanks for that.

Looks like I’ll give ProcDump a go.

The duplicacy_web.log doesn’t show anything untoward, but the last section of the log when I last saw Duplicacy had crashed, only showed this:

2019/06/11 12:16:23 Schedule Regular next run time: 2019-0611 14:15
2019/06/11 14:15:01 Starting schedule Regular at scheduled time 2019-0611 14:15
2019/06/11 14:15:01 Created log file C:\Users\Droolio/.duplicacy-web/logs/backup-20190611-141501.log
2019/06/11 14:15:01 Running C:\Users\Droolio/.duplicacy-web/bin/duplicacy_win_x64_2.2.1.exe [-log backup -storage NAS -vss -stats]
2019/06/11 14:15:01 Set current working directory to C:\Users\Droolio/.duplicacy-web/repositories/localhost/0
2019/06/11 18:53:38 Duplicacy CLI 2.2.1

So it’s missing the ‘Created log file’, ‘Running’, ‘Set current working directory’ for repo ‘0’, plus the same for repo’s 1, 2 and 3 plus a final ‘Schedule Regular next run time’ - all missing. Seems to be crashing when trying to run the first job in the schedule.

I’ll try out ProcDump.

Instead of having to deal with it would be great if this was a service that Duplicacy offered as part of the yearly license fee. If Duplicacy has not received a backup ping in 1-3 days they would send you an email. It wouldn’t need to support the CLI version since that is free, but it should be supported out of the box for Web.