I have a local and remote storage. The storage was added using add -copy
.
My backup/prune commands look like this (encryption/password related stuff omitted for brevity):
duplicacy-wrapper backup
duplicacy-wrapper prune -a -keep 0:365 -keep 30:30 -keep 7:7 -keep 1:1
duplicacy-wrapper prune -a -exclusive
duplicacy-wrapper copy -from default -to b2
duplicacy-wrapper prune -a -storage b2 -keep 0:365 -keep 30:30 -keep 7:7 -keep 1:1
duplicacy-wrapper prune -a -storage b2 -exclusive
duplicacy-wrapper check -a
duplicacy-wrapper check -a -storage b2
And this is a log showing the prune for each storage respectively:
Keep no snapshots older than 365 days
Keep 1 snapshot every 30 day(s) if older than 30 day(s)
Keep 1 snapshot every 7 day(s) if older than 7 day(s)
Keep 1 snapshot every 1 day(s) if older than 1 day(s)
Deleting snapshot backup at revision 22
Fossil collection 1 saved
The snapshot backup at revision 22 has been removed
Keep 1 snapshot every 30 day(s) if older than 30 day(s)
Keep 1 snapshot every 7 day(s) if older than 7 day(s)
Keep 1 snapshot every 1 day(s) if older than 1 day(s)
Deleting snapshot backup at revision 21
Deleting snapshot backup at revision 22
Deleting snapshot backup at revision 26
No snapshot to delete
As you can see, it doesn’t appear that the prune for two-step fossil collection runs for the remote storage. I have to manually run the command later for it work. I also tried using the -exhaustive
flag to no effect. I have two questions:
-
How do I effectively use the
copy
/prune
command so that I don’t need to runprune
on the remote storage? -
What am I doing wrong w.r.t. the two-step fossil collection prune not running for the remote storage?