BTW, for all of this I am using the Duplicacy Web interface.
Question 1: This is more of a high level conceptual question. While I think I have come close to setting this up right, I want to double check. I am looking to perform a daily backup for each day of the week from one local internal hard drive to another local internal hard drive. I am also trying to keep weekly backups for anything older than 7 days. Finally I have setup cloud backup (Google Drive) that is supposed to run as follows: keep one backup each week for 4 weeks and keep no backups after that.
Subquestion 1a. Is this a reasonable configuration for a personal home business (i.e. not mission critical but annoying if a major crash happened and we needed to rebuild)?
Subquestion 1b. What would be the right backup and prune configs to make this happen?
Current config:
a) Backup from local HD1 to local HD2 every day at midnight
b) Backup from local HD2 to Cloud every Sunday at 3am
c) Prune runs every Sunday at 6am to clean up both the local and cloud repos
Question 2: My cloud storage seems to be growing out of control. I would have expected it to grow for the first 4-5 weeks but then be pretty steady after that. I am now running out of space and wonder if I have set something up improperly.
Subquestion 2a. Is there a way to use Duplicacy to empty out the cloud storage so I can start over? If so, what precise web I/F steps do I take to accomplish this? I could just delete the files on the Google Drive but I am worried that will leave Duplicacy in some befuddled state and make matters worse.
Subquestion 2b. As I mentioned above, I would have expected the cloud storage growth rate to stabilize after 4-5 weeks, with minor growth from new files being created under normal use (note the rate of new file creation is pretty low; there is lots of editing of existing files though). But that does not seem to be the case as we seem to be generating several GBytes of growth each week. Am I missing something in the setup or in my logic?