My trial license expired at some point and my backups (understandably) started to fail. However, this was essentially a silent failure as the only place this is visible is in the Schedule tab.
Furthermore, my prune job was continuing to run successfully! So duplicacy was slowly pruning away all my old backups without adding any new ones. I don’t have these jobs set to run in parallel so I would have expected the prune job to fail if the backup job failed.
I have since purchased a license, so this is no longer an immediate issue for me, but I’m concerned about what’s going to happen when my license expires again down the road.
Backups expire according to rules you set and those rules generally leave the most recent backups alone until a very long time passes - i.e. what gets pruned are backups that would normally have been pruned anyway.
All non-backup jobs - pruning, copying, checking etc. - are allowed without a licence. Just make sure there’s a licence if you want to continue backups.
So, the reason that I think this is dangerous is the combination of:
It wasn’t immediately clear to me that my backups were failing, AND
All of my backups were deleted
This left me with no off-site backups by the time I realized what was happening. My suggestions for these are:
Promote job errors to the dashboard in some way. Maybe it’s just putting an on the Schedule item in the left bar? As a new user I wasn’t aware that I needed to click into Schedule to check for errors.
Allow me to specify that a job failure within a schedule aborts the subsequent (non-parallel) jobs. Ex: if backup fails, do not run prune. This means that I will never be in a position where all my backups get deleted.
Hmm, you’re probably correct then about there being one backup remaining. My successful backup after entering the license was the only one I saw so I assumed it had been empty, but the storage history indicates otherwise. I’m glad to know that safety net exists!