Prune command details

  • Remove -exhaustive flag.
  • reverse order of -keep flags.

Thank you. After running prune I see ā€œMissing Chunksā€ under the check process status. Alos, the storage size was not updated on the graph. What can I run to reconcile?

Run check -fossils - see if it’s the same.

That worked, thank you. But my storage size should have been reduce by 50% based on my revised prune policy above. Now that the check went through I see only a small decrease in size. What am i missing?

Pruning happens in a two-step process - marking then deleting files. But you need to run backups for all IDs between these steps. So chunks will eventually be deleted after you backup then run another prune.

You can speed this up but using prune -exclusive but you need to make sure no other operations are running on your storage.

Also, if that -fossils worked, you may want to run it again with -fossils -resurrect before you do any clean-up.

1 Like

Thank you. What would be a boilerplate daily job then?

  1. Backup
  2. Prune
  3. Check

Is that more or less the routine?? Special commands?

Thx for your help.

Yep that’s usual. No special commands. You don’t always have to run prunes or checks daily though. Weekly prunes are fine too.

Hi everyone,

I only have space for 1 backup on my google drive.

So I want tonight to have a backup. Tomorrow it should delete that backup and take a new one.

I’m using: -keep 1:1 -keep 1:2 -a

But it’s not deleting anything. Can anyone help?

I ran this policy and what i see in my restore files are:

Daily for the last month
Weekly for 6 months after that (until mid april)
Monthly for two months after that (mid march, feb)

Very different from the stated goal. Any ideas?

  1. Backup are incremental and deduplicated. If you take backup today and it transferred 10GB of data, and then you add 1MB of new unique data and take backup tomorrow — your storage will grow by 1MB, give or take. There is no need to keep aggressively deleting old backups.

This needs to be sorted by time:

: -keep 1:2 -keep 1:1 -a

This would mean: for snapshots older than 2 days keep one snapshot every dat. For snapshots older than 1 day keep snapshot every day. Quote a pointless redundant policy.

Also prune will not delete the last remaining backup.

My suggestion: do -keep 0:10 -a: this will keep rolling history of 10 days worth of backups.

Again, remember, backups are incremental.

I’m still wondering why a policy of…

-keep 0:270 -keep 30:60 -keep 7:7

Produces:
Daily for the last month
Weekly for 6 months after that (until mid april)
Monthly for two months after that (mid march, feb)

?

The only part that seems consistent is the 0:270

See:

It does not.

Your policy as written will yield

no revisions older than 270 days,
one revision every month between two months and 270 days
one weekly revision starting from week two until two months
every revision for a week.

you can use -dry-run parameter to see what prune will be doing without actually doing it.

That’s also what I expected. But after running that exact policy, as you can see, it did not produce those results. These are all my restore files, which reflect a different policy of:

Daily for days 1-30
Weekly for days 30 - 180
Monthly for days 180 - 300