I have a doubt. I made some settings that I’m testing, in one of them is one that apparently deletes the files that were removed locally as well. Today I have a paid software that allows me to set a time for the remote files to be removed when the locations are also, this is possible here or it just works the way I tested it, when deleting the location it already erases in the backup. Another thing, I did a Full backup, put it to keep the last 5 backups, when he goes to do the sixth, he deletes the oldest one that would be Full, how does it work?
I went to restore the most recent backup and it brought me only what was changed on the date, that’s cool, but what if I need Full, The first backup should never be removed.
With Duplicati, every backup is effectively a “full” backup from a restore perspective. You can restore any file that was present at the time a backup was taken, even if that file is old. Duplicati is also an “incremental forever” type of backup in that it only processes new and changed files each backup job.
These terms carry a lot of baggage and it can cause confusion because backup products use the terms differently. Rest assured, there is no problem with deleting the first backup because with Duplicati there is no dependency chain among backup versions.
Cool, I’m time to use the tool, trying to learn a little more with some problems I had. One was that he lost his source mapping that was mapped in Linux and with that lost the count of the data. Other thing, has some configuration that makes it felt faster? I found it a bit slow about some other software.
Does this actually work for you? It’s supposed to be a file list supplied by your filesystem watcher.
When I just hardcode 1 there, it gets upset because there’s no such file for it to put in the backup:
What does this mean? Yours was completely ignored? Mine broke my backup, because it’s wrong.
The original post had it in use. I especially worried about the “source mapping” issue you mention.
I’m afraid the language there is vague enough that I don’t follow it, so I mention the suspect option.
Generally (especially when starting out), sticking close to the defaults is likely to invite less trouble.
The –changed-files option is missing some key information on its use, which you can find in forum:
It would be nice if someone could confirm this, enhance the help text, then get the manual updated.
Possibly a GitHub issue will be needed to get it in the queue for a developer. Sometimes that’s so…
–snapshot-policy=Auto is (on Windows) only useful if running as a Windows service (special install), or running as a user with Administrator privilege that is actually using them. It’s used to backup open files.
For the --send-mail-* options, there’s usually more needed. –send-mail-url is probably always needed. Unless this is your private server, your ISP may need –send-mail-username and –send-mail-password however possibly you just didn’t post those (instead of posting them and redacting the personal parts).
Well, you could certainly hardcode the file lists, but most people would need the file monitoring service.
Yeah this is almost certainly unnecessary. The idea behind this interval option is to keep it from running vacuum too frequently. Are your backups scheduled for every 10 minutes? If so you can just leave the option off if you want it to vacuum each time.
On my system I back up every 4 hours and have the vacuum interval set to 1W (one week). I only want to vacuum once a week.