Romex Software Forum

I noticed that my hit rates were falling dramatically during backups, despite using the "rxpcc pause -a -s" command before starting them. Doing a little investigation, I found that the -a switch didn't pause the cache task, only it's assigned volumes. The cache task keeps running, and hit rate keeps falling during backups (verified by kicking off a manual and watching it). It is a steady and large decline in hit rate immediately following a kick-off of the backup.

Note that you can get the Cache tasks in Primocache to pause by selecting it in the GUI, and pressing the pause button. The results from using the command line "pause -a" do not pause a Cache Task, only it's volumes. This may or may not be a bug, which is why I'm posting here.

I'm using Macrium Reflect for the actual backups, and kicking all commands off sequentially using a .bat file: Here's what Primocache looks like after issuing the "rxpcc pause -a -s" command. These are *not* before/after images, they are both after using the "pause -a" command:






Is there some other method for preserving hit rate during backups? Or is there possibly a bug with the "pause -a" command line options that should be pausing the cache task in addition to it's volumes?

It's by design in order to monitor the correct "Total Read" value. But just the hit rate changes, and it does not affect any cache content and space.

The command and the gui are correct. Cache task item always shows active when the task is correctly created.

Okay, thanks for the feedback Support. I figured the cache contents didn't change when it was inactive, and it's good to hear there's no bug for pausing cache tasks themselves.

Would have been nice to preserve hit rate when paused, but it's ultimately a non-issue. I just like to know if the cache is working efficiently. I'll force reboots immediately following Full/Differential backups to reset the hit rate counter from now on.

You may use the following command to reset statistics including the hit rate.

rxpcc perf -a -r -s

Alternatively, right click on the statistics panel in the GUI, and choose "Reset" in the pop-up menu.

Good to know about those command line switches. Will help with less restarts on the hardware. Cheers.

Backup is good, I think right.