I am puzzled as to how I can achieve the following scenario using version 2. I have gone through the release notes several times and I just can't see how to do it.

I have an action which is presently configured to capture my home directory to an archive every hour with one or two permanent exclusions set using either the archive settings feature or the QRecall Capture Preferences. I also have a few large folders that change very infrequently, such as Pictures and Movies so it makes sense to not capture those every hour.

In QRecall v 1 I could set the action to ignore changes in these folders then have another action to capture them say, daily, to the archive.

In version 2 the ability to use the new "capture on event" schedule seems ideal using "Run when capture items change" coupled with a delay, but I can't see how I can configure things so that they aren't captured by the hourly action but can still be captured to the same archive using the "Run when capture items change" action.

I'm probably just being very dense.

I'm also seeing a lot of "unable to communicate" messages, but I am not aware of any slowdowns. The messages occur as a string over very short intervals, maybe a second or two at a time.

None that I can recall.

I have noticed one or two minor issue this evening. If I select a file in an archive and highlight it, clicking "Select existing items" in the edit menu highlights everything, and so does "invert selection" which was not what I was expecting.

If I highlight a folder, "Select Existing Items" again highlights everything, but "Invert Selection" sometimes ends up highlighting the adjacent item.

Maybe I'm not understanding something here.

Also, is it my imagination but QRecall 2 seems MUCH faster at capturing and opening archives.

I have had a few issues with the betas so I finally decide that I would uninstall it using the uninstall option and then went through the entire file system removing everything that had qrecall in the name, apart from my actions.

Voilà, QRecall beta v2.0.8 so far seems to working exactly as described.

Amazing what a really good purge can do.

I just tried double clicking an archive and QRecall opened successfully until the archive appeared, then it quit again.

Hi James

I have done a fresh install of the latest beta but it repeatedly quit on launch. I tried using activity monitor to quit qrecall monitor and it then launched successfully. I opened an upgraded archive and tried to delete the last 3 layers but QRecall did nothing. I then quit QRecall and tried to relaunch but got the same immediate quit problem. I tried a restart and quitting the monitor again but QRecall still won't launch. I can't send you a report from within QRecall for that very reason but I attach a crash report from Console.

Hi James

Yes, that's pretty much what I thought would be the case.

Thanks

I understand that version 2 changes version 1 archives irreversibly, but can version 2 still be used to verify, merge and compact version 1 archives and leave them compatible with version 1.

I ask because while I want to assist with testing the V2 beta on my iMac I wish to continue running V1 for now on my wife's Macbook but I run a weekly verify/merge/compact on her archives from my iMac. The archives are stored and a Drobo 5N NAS.

Hi James

Yes, sorry, I should have used QRecall's send report.

I am running OS X 10.10.4 in a late 2012 2012 iMac with the OS on an internal SSD and User directories on an external Promise Pegasus R4 configured as a 4-drive RAID10

Killing the QRecall Monitor seems to have fixed the problem of no progress window appearing and accessing the Window menu.

Hi James

I have installed the latest beta and my first issue is that very time I click on the "Window" menu I get the beachball. Console log is attached. I am not seeing any progress window either, but maybe that is because I can't access the Window menu!

I use QRecall to archive three Macs, all running Mountain Lion, to a Drobo FS which seems to work reasonably well, but can be excruciatingly slow if you need to repair a large archive. This is mainly the fault of the Drobo FS which suffers from relatively slow reads and writes, especially for small files. The new Drobo N is reported to have considerably better performance. As for other types of NAS I don't know, but in principle it should work fine.

I recently tried running QRecall to a firewire drive attached to my server machine, a Mac Mini, but I had all sorts of problems with the drive not showing up on other Macs, especially after waking from sleep. QRecall actions ran much faster than on the Drobo FS but I have had so many issues I have abandoned it for now. Slow and reliable is superior to fast and unreliable in my book.

I hasten to add that none of the problems were directly attributable to QRecall.

Chris Caouette wrote:Thank you for the comprehensive reply! I think I will give it a go. I have Time Machine one more go and I still am not having great success. I'll Setup Qrecall and see how it goes.
Thanks!
Chris

Chris

I abandoned Time Machine years ago due to its unreliability and total inability to put things right when they went wrong - which was often. I have been using QRecall ever since and while there are occasional hiccups they are rarely, if ever due to QRecall itself. The application is very robust and does a damned good job of looking after my data. I use a Drobo FS NAS for my archives which is not exactly a speed demon but it works well enough with QRecall.

Oh, and one more thing, you won't get better technical support anywhere else. James usually responds within hours to any request for help and he won't abandon you either.

James Bucanek wrote:

Norbert Karls wrote:Make this a paid upgrade, it will totally be worth it (to me, at least).

I'm sorry to disappoint you, but the next version of QRecall will be a free upgrade.

That proves it, James is mad, quite mad!

Thanks James, I can see it working now and what a useful feature it is. I am always learning something new about QRecall and it still wipes the floor with anything else.