Scheduled pruning appears hung on "prune in progress"

Support
#1

Hi,

I have a ton of backups, with over 4 million chunks in one of my storage locations. This storage uses sftp.

Many of the prune jobs I have in my schedule get hung on “prune in progress”:

Screenshot
Screenshot960×1697 138 KB

I can’t click on “prune in progress” whenever this happens. Also, once this happens, not even a reboot gets it to reset.

Any ideas as to how I can fix this?

Thanks in advance!

#2
  1. Is the prune actually stuck? Do you see traffic on your SFTP server? What is in the prune log? Prune is very IO intensive, it can take ages.
  2. Your prune “keep” policy is wrong.
  3. Backup with 14 threads to SFTP server makes little sense, unless your SFTP server is flash based.
  4. Interrupted prune can leave ghost snapshots in the storage. You will need to clean them up eventually, otherwise “check” will be reporting bogus failures.
#3

Hi, sorry for the delay. To answer your question about the prune actually being stuck, no, there is no traffic to my destination. Even after reboots, it doesn’t go away.

It could be due to the prune keep policy being incorrect, can you explain more about it being wrong?

Also, check is actually reporting healthy, it’s just the prunes that seemingly get “stuck” even though no traffic is going over the network.

Thanks again.

#4

Can you elaborate on this? What are you rebooting? The server or the client?

How does the disk IO look like on the destination? When prune appears “stuck” its’ enumerating files. If there are a lot of files – it may take signinficant amount of time with no traffic if metadata is not cached on the server.

Duplicacy applies every prune argument in order to every file it tests. Your first argument will apply to filels older than 7 days. Therefore all subsequent argumetns won’t have any effect. See more here: prune · gilbertchen/duplicacy Wiki · GitHub

First, you need to decide between -keep 180:7 and -keep 1:7: for filles older than 7 days, do you want to keep one every half a year or every day? Proably the latter.

So you would want to transform your prune command into

prune -keep 1095:90 -keep 365:30 -keep 1:7 -keep 30:1 ...

Still quite a weird, and contradictory prune schedule.

For example, you want to keep a file every month for files from last week, but keep one every day for files older than 1 week? That woudl be impossible to acomplish.

Maybe explain in words what are you trying to acomplish?