Some questions/issues regarding deleting backup and permission

Support
#1

Hello Duplicacy Community,

I’ve been a Duplicacy user for over a year and have a few questions and issues I’m hoping someone can help me with.

  1. Managing Backup Destinations, Folder Sets, and Reclaiming Space:
    I initially configured a backup task (let’s call it “Backup Job A”) to back up folders a, b, c, d, and e to Cloud Drive A. I’ve recently added a new backup destination, Cloud Drive B.

    My new goal is to:

    • Back up only folders a and b to Cloud Drive A.
    • Back up folders c, d, and e exclusively to Cloud Drive B.

    More importantly, once folders c, d, and e are no longer being backed up to Cloud Drive A, how can I remove their previously backed-up data from Cloud Drive A to free up the storage space they currently occupy there? Do i just excluding them from future backups to Drive A? Will that automatically delete the old data?

  2. Resolving “Permission Denied” Errors on Unraid: I’m consistently encountering “permission denied” errors when Duplicacy attempts to back up my Unraid server. An example of the error log is:

    2024-04-16 01:36:45.003 WARN OPEN_FAILURE Failed to open file for reading: open /backuproot/appdata/speedtest-tracker/keys/cert.key: permission denied
2024-04-16 01:36:45.004 WARN OPEN_FAILURE Failed to open file for reading: open /backuproot/appdata/speedtest-tracker-1/keys/cert.key: permission denied

    I’ve checked the Docker container settings for duplicacy, and they are configured with user ID 99 and group ID 100. I’m unsure how to resolve these permission conflicts.

  3. Scrolling in Web GUI Activities Section: In the Duplicacy web GUI dashboard, under the “Activities” section, I’m unable to scroll horizontally to view backup activities from more than a few days prior (specifically, I can’t seem to go back further than 7 days). Is there a way to scroll further to the left to see older activity logs, or is there a known limitation or setting I might be missing?

Thank you in advance for your assistance!

#2

If you were starting from scratch (and I realize you are not, see below) then the easiest way to do this would be as follows:

  • Put folders a and b into Dir1
  • From Dir1 init a repo to Storage A
  • Put folders c d and e into Dir2
  • From Dir2 init a repo to Storage B

Now you have two separate repos, each backing up to separate and designated storages.

If you simply start excluding c d and e now, that will not be enough, because the old backups of c d and e folders are still going to be present on storage A. Changing what you back up in the future does not delete anything from a storage.

To delete stuff, you will need to run prune commands to eliminate all the old snapshots prior to when you started excluding those folders. So if you starting running new backups on May 1st that contain only the folders you want, you could prune and forget everything prior to May 1st. But BE CAREFUL: this will obviously eliminate not only the c d and e folders but also anything old that used to be in the a and b folders but is no longer in them now. I am not aware of a way to remove the old folders (that you are not currently backing up) while keeping the old versions of the folders you are still backing up. There might be a way! I just don’t know it.