Pretty much, although I personally don’t run those exactly in that sequence - the basic gist is; backup as many times as you want, prune before copy to cloud. Check and prune can be run semi-regularly, like once a day or week.
I run mine mine once a day, directly from the NAS. You can run it less often like weekly, but if your NAS isn’t taxed for resources, why not keep it daily? Totally up to you. When do you want to learn there was a chunk missing?
Yes, always. And manually test your backups - say once a month or two - either through partial/full restore or through
An important question. You can opt not to prune your cloud storage at all, but if you decide to do so, you probably want to use the exact same retention settings (
-keep) as your local NAS storage, and run them on the same day as each other i.e. local and then immediately cloud.
Why? Because the way that revisions are removed depend on when you run them and you have to remember there is no fixed epoc for when the ‘monthly’ and ‘weekly’ revisions start and end.
So if you don’t adopt the same retention numbers, what happens is you’ll prune revisions that don’t match between the two storages, and then
copy ends up re-copying missing revisions and the cloud prune removes them again. This wasteful cycle repeats. Had this issue recently myself and the fix was once to copy storages both ways and then make sure the prune of local and cloud was done exactly the same.