I’m currently using the web GUI to back up my repository up to local storage and then running a copy job to update offsite storage with the newly created nightly backup.
In order to decrease the capacity requirements for the remote storage pool, I’d like to change its retention policy so that fewer revisions are maintained while still keeping a greater number of revisions locally.
The problem, of course, is the current copy job as configured (no ‘-r’ option) will replace all the “missing” revisions in the pruned remote storage and negate the updated retention policy.
Is there a way, using the web GUI, to somehow have Duplicacy only copy the most current revision to the remote storage pool? I suspect I’ll need to go back to scripts, and dig relevant information out of the logs for use in a customized copy script. But I thought I might pose the question before going down that rabbit hole.