I don't know if this is relevant but there are issues with the way Finder reports disk space on APFS volumes. There is quite a lot about it here

https://macintouch.com/community/index.php?threads/apfs-file-systems.1489/page-4

I should add that while I was having the problem the "Show when actions start" and Hide when actions complete" check boxes were empty. I have just unchecked them and with your work around the monitor is showing correctly in the dock on my iMac.

Hi James

Thanks for the fix which seems to have worked. I note that the "Show in dock" preference window is now blank and I have left it like this.

As it happens I am also seeing this on my wife's Macbook Pro

Adrian

Hi James

The preference "Always show monitor in dock" worked fine under version 2.1.11 but under version 2.1.12 the preference always reverts to "When active". I have tried uninstalling and reinstalling QRecall but the issue is still there.

Any ideas?

James Bucanek wrote:
But if your folder is very targeted (~/Documents/Projects/Hot) then consider the "When source items change" event schedule. QRecall will monitor that folder for changes and immediately start a capture only when it does. It's more timely than waiting for the hourly capture, and it can be more efficient because the action only runs when there's something to capture. You just don't want this kind of schedule on a folder that changes all the time (like your home folder, which change every few minutes).

I use "When source items change" on my Pictures folder because I tend to work on photographs relatively infrequently so there is no point including it in my regular, 2 hourly backups.

However. while I don't want to lose any changes while I am working on photographs I don't see any point in capturing every minor edit so I delay the capture for 15 minutes. If I feel the need I can, of course, always initiate a manual capture at any time.

James

Qrecall has never mounted the volumes automatically, I have always had to mount them manually or by an application such as Mountain. I usually have three NAS volumes mounted, one of which is used for Qrecall.

I am running OSX 10.11.5 but it has occurred in recent versions.

The NAS volume are mounted from Finder, more recently using an application called Mountain rather than the NAS mounting the volume itself.

Report on its way to you.

I archive to a NAS from my iMac over ethernet and mount my NAS volumes using smb, the Qrecall actions point to these archives on the NAS volume. Everything works fine normally but occasionally, for some reason that I have yet to discover, and unrelated to Qrecall, the NAS volume will mount using afp. I even have the same volume mounted with both afp and smb at times.

If I don't notice this and Qrecall tries to run a capture it will fail and I have to repair the archive. I don't understand why the network protocol should have any bearing on the capture action but it clearly does and it is annoying when I have to repair the archive, which takes several hours.

Ideally, I'd like to know why the NAS volume mounts as afp anyway and I'd like to find a way to tell the OS not to mount any volume as afp under any circumstances, but so far that has defeated me.

Any ideas James?

Thanks James, I thought you might say something like that but I thought it best to check.

Adrian

James

Please can you clarify the value, or otherwise of using QRecall's redundancy feature if the archive is stored in a RAID 5 array or a ZFS Mirror.

Thanks
Adrian

James

James Bucanek wrote:Can you clarify a few things? Are you capturing to the same archive on the NAS, or separate archives for the iMac and Macbook?

Each computer has its own pair of archives, one each for the system volume and the Users Volume.

James Bucanek wrote:Is the status message you're talking about the one on the Macbook or the iMac?

It is the status message on the iMac

James Bucanek wrote:Does the iMac and Macbook show different status message for the same archive?

I can't remember off hand, I'll check next time it happens

James Bucanek wrote:Is the NAS connected to the Macbook all of the time, or only during the capture?

The NAS is connected wirelessly via the router so unless the Macbook drops the connection, which is rare, but not unheard of, it is connected all the time. The NAS always reappears after sleep too.

James Bucanek wrote:Does the Macbook capture occur when it's logged in or out?

Captures only occur while logged in.

James Bucanek wrote:When archives are shared across networks, keeping the status information up-to-date across all participants gets a little tricky.

I can appreciate that, which is why it isn't a big issue for me.

Adrian

I see this quite frequently. I archive from my iMac and my wife's Macbook. The iMac is ethernet connect to a NAS, the Macbook connects wirelessly to the NAS via my router.

It is always a Macbook archive that shows up as not being run for x days, but when I check the actions have been running correctly. I should add that all my verify, merge and compact actions run from my iMac.

James

Thanks for your clarification. My understanding was more or less correct up to a point, but I have now got my mind round the whole thing.

Regards
Adrian

James

I have weekly rolling merge actions set as follows:

Keep most recent: 7 Days
Followed by:
90 Day Layers
52 Week Layers
12 Month Layers
2 Year Layers

If my understanding is correct all layers beyond 2 years will be merged into a single layer but I have archives with year layers dating back to 2011 and 2012.

Is this how it is supposed to function or have I misunderstood something.

Adrian

Yes I am/was being dense. What you say is obvious in hindsight.

On the whole I am finding Version 2 works very well for me.

Thanks