Aubrey Grey wrote:I tried to read the value by using: defaults read com.qrecall.client QRAuditFileSystemHistoryDays, but it reports it does not exist.
If this value is not set in the preferences, QRecall uses the default value of 6.9 days.
Related: is the 6.9 days since last backup or since last full backup?
Neither. It's the amount of time that QRecall has been trusting the file system change events to tell it which directories have changed.
Here's an example. Let's say that you've set up QRecall to capture your Documents folder once a day. On Monday you capture the entire Documents folder for the first time. On Tuesday, QRecall will query the file system change history to determine which folders changed between Monday and Tuesday. QRecall has now been depending on the accuracy of the change history for 1 full day. On Wednesday, it's now been depending on the change history for 2 days, and so on.
When the capture starts the following Monday, QRecall will have been depending on the accuracy of the file system change history for 7 days. That exceeds the default limit. It ignores the change history and exhaustively recaptures the entire Documents folder again. On Tuesday, it will only be using the past 24 hours of change history to locate changes, and the whole thing starts over.
So it's not the time from your last capture. It's the amount of time since the last capture that
did not rely on the file system change history.
I read about QRecall using as much memory as it can... I read that with systems over (was it 10GB) it uses 8G of memory. Is that parameter adjustable to reduce the interference with other work especially if it is going to take all day to do it's backup.
Yes. QRecall definitely assumes VM is turned on, and if you turn it off you'll want to "dial back" QRecall's use of memory. Advanced settings can be found on the
advanced settings page.
The setting you're interested in is
QRPhysicalMemoryMB. Set it to a value (in megabytes) less than the amount of physical RAM you have, say something between 3072 and 4096. QRecall will try to keep it's index and lookup memory footprint within that limit. Caution: lowering this value might reduce QRecall's ability to cache index data, and thus slows the capture process. But that's a reasonable trade off if it means you can still use your computer.