Some users are starting to run into warnings related to Duplicati trying to back up integrated cloud drives that use “files on-demand” (so basically a local stub points to the actual file that lives in the cloud).
Assuming this trend is likely to increase, I’m curious what people think about how to handle these. Should we ignore them, back up the stubs, pull down the on-demand file and back that up, let a setting determine which of those, or something else completely?
When considering this, keep in mind the Duplicati big picture - for example, if we back up a stub then the user deletes the file from the cloud what happens when we restore the stub (assuming the OS will even allow us to). Similarly, if we back up the cloud file itself (instead of the stub) then when we go to restore it do we overwrite the stub and let the cloud sync tool handle recreating the stub?
Your thoughts are requested, but if you just want to click buttons - here’s an informal poll.
- Ignore them (don’t back up)
- Back up the stubs
- Pull down the full file and back that up
- Use a setting so the user can determine which of the these happens on each job
- Something else