, there's currently no way to do this, but we consider such a possibility for the future updates. I've added you to the list. Sorry for the inconvenience
Would the "Synchronize local repository with backup storage before plan runs" checkbox within the pre/post actions backup options do the same as a consistency check?
Reading the docs about both didn't really shone a light to me.
Essentially, yes, they use the same logic, but consistency check also performs internal comparison between the old info and the new one and adds it to the database.
So what would CloudBerry Best Practices recommends?
Scheduling consistency check (every week, month?), plus checking the synchronization of the repository on every backup plans?
What are the downsides?
I'm sorry, maybe I've missed the articles in the documentation, if you can point those to me ?
In general, running consistency check once a week is a good idea, just make sure no other plans are running at that time. This way, in case there are any problems with cloud synchronization, the software will fix them automatically.
More info on consistency check functionality can be found in our help section.
We'll implement weekly consistency check on all of our backup storages.
That being said, if understood correctly, synchronizing the repository on every backup plan (the checkbox in the pre/post action) should not be checked (as the doc you sent me is about restore plans)?
Consistency checks work per destination, not per plan. Currently they can only be created remotely, but not deployed via "remote deploy" functionality.