Sorry to hear you're having problems with your migration.

Most QRecall installation problems can be resolved by performing a complete uninstall and reinstall of the application.

However, the log message you cite indicate that you currently have mis-installed components, so a simple and easy uninstall won't work. (QRecall's "Quit and Uninstall" command uses the installed components to perform the uninstall, so it's a catch-22.)

Fortunately, QRecall 3 has an embedded uninstall tool. Follow these steps to completely uninstall, and the reinstall QRecall:

1) Quit all of your other applications (the uninstall will perform a system restart, so you want to make sure you've saved your work).
2) Open the Terminal app
3) In the terminal, execute this command:
    /Applications/QRecall.app/Contents/Resources/uninstall.sh
    (This assumes your QRecall 3 app is in /Applications; if it's somewhere else, adjust this path as needed.)

This will prompt you for your administrator password, uninstall all active QRecall components, and restart your system.

4) Following the restart, trash your installed copy of the QRecall app.
5) Download a fresh copy QRecall: <https://www.qrecall.com/download>
6) Copy the QRecall app to your /Applications (or wherever) and open it.
7) Supply your admin password to install.

If that doesn't work, email a copy of your QRecall log file (~/Library/Logs/QRecall/QRecall.log) to Support. (It's a big file, so if you're not using Apple's Mail Drop service, you'll probably need to use WeTransfer or something similar.)

kananbrooks wrote:Is there a troubleshooting step i might have missed?

Start by sending a diagnostic report (QRecall app > Help > Send Report).

We have hundreds of users running QRecall 3.0 and macOS 15, so we're not aware of any macOS incompatibility at this time.

There are, however, reasons why an archive wouldn't open. Start by sending a diagnostic report (QRecall > Help > Send Report).

While that is being evaluated, try describing exactly what happens when you do try to open the archive.

Welcome!

Let me start by saying that QRecall does not store "snapshots" in the traditional sense. It stores "delta"—each layer stores only the differences between it and the previously captured version of each item. See QRecall > Help > Guide > Layers > Understanding Layers for a complete explanation.

You can focus in on a layer (or a group of layers) by adjusting the shades (top and bottom) to narrow your view of what's been captured. But if you then try to recall those items (with both upper and lower shades in place), you won't be recalling all of your items. You'll only be recalling the items that changed and were recaptured in that layer (or layers). See the warning "Recalling folders with top layer shaded" at the end of the help section QRecall > Help > Guide > Layers > Layer Shades.

james_smith wrote:I chose the right snapshot in the QRecall interface for the restore.
I made sure the incremental backup finished without any issues before I started restoring.
The file versioning looks okay for some documents, yet some files seem to be left out.

Did you "choose" your layer by adjusting the shades? If so, then recalling a folder of items would only recall the items in that folder that were recaptured by those layers. All unaltered items would excluded from the capture.

The solution is to use the shades to find the version of the items you want to recall. This is done using the bottom shade, and the bottom shade only. (Basically, you're hiding more recent version of the items to locate and earlier version of that item.) Now a recall will include all of the items.

If you want to use the top shade, remember to run the top shade back to the top before recalling a folder or package.

I was just about to post on how to manually add the QRecallHelper app to the full disk access list, but you figured it out already.

If you haven't sent a diagnostic report, do so now (in the QRecall app, choose Help > Send Report).

I received a diagnostic report that I believe is yours, but the report is anonymous. If it is yours, that means you have not installed your identity key and you didn't provide a contact email address in the report. Also, the log records in that report show no attempt to open an archive or run any actions. So I'll need some clarification on what you mean by "can't open an archive" because there are no archive access failures logged.

If you have more details, sending those to QRecall Support will likely be faster than using the forum.

Finally, opening an archive for browsing in the QRecall app shouldn't require any exemplary permissions. QRecall archives are regular documents which should be accessible to the user account that has QRecall installed, like any other spreadsheet or music file.

The QRecallHelper process, however, performs the actually capture and recall of items and often needs elevated user privileges to accomplish its work. That's why QRecallHelper is the one (and only) component that's a candidate for Full Disk Access.

Ming-Li Wang wrote:Just to make sure, by "QRecallHelper" you mean the one shown as "com.qrecall", right?

It should appear as "QRecallHelper":



The "com.qrecall" is likely the identifier of the privileged elevation service, which does not need Full Disk Access.

Ming-Li Wang wrote:Anyway, I've reinstalled QRecall and given every permission it has requested, including manually granting it full disk access

For the record, the only QRecall component it makes sense to grant "Full Access" is the QRecallHelper component. This is the executable that does all of the real work in QRecall, including capturing and recalling items.

Most of the other QRecall applications and component don't access anything beyond the archives and your preferences. Although granting "Full Access" to everything won't (likely) harm anything, the best security practice is to limit the access of applications to just what they need and nothing else.

Sorry to hear you're having difficulties.

QRecall is definitely compatible with macOS 15.0 (Sequoia). I'm running it here, and I've heard from dozens of other users who are too.

With any major upgrade, macOS can be persnickety about software that's installed at the OS level and given elevated privileges. The usually solution is to just uninstall the software and resinstall it.

Given the problems you're describing, it's likely that macOS is blocking the low-level components from executing. The side effect is that the QRecall application can't uninstall itself (since it needs those components to accomplish that—catch 22).

So you'll want to run the uninstall utility script buried inside the QRecall application bundle, like this:

Quit all of your other applications (the uninstall will perform a system restart, so you want to make sure you've saved your work).

Open the Terminal app

In the terminal, execute this command:

/Applications/QRecall.app/Contents/Resources/uninstall.sh

The command will prompt you for your administrator password, uninstall all active QRecall components, and then restart your system.
(Note: this assumes QRecall is located in your /Applications folder; if it isn't, adjust the path accordingly.)

Following the restart, launch the QRecall application and let it reinstall itself.

macOS may than ask you to authorize various QRecall components to have access to external volumes, etc., to which you should agree.

That should resolve your problems. Let us know if it doesn't.

Hello Steven,

For all kinds of reasons, QRecall components can be mis-installed, or get mis-updated, or just don't run.

The simplest solution to these kinds of problems is to completely un-install QRecall and then reinstall it from scratch.

In QRecall 3, this is most thoroughly accomplished using the "uninstall" script included in the QRecall application bundle. To do this, follow these steps:

Quit all of your other applications (the uninstall will perform a system restart, so you want to make sure you've saved your work).

Open the Terminal app

In the terminal, execute this command:

    /Applications/QRecall.app/Contents/Resources/uninstall.sh

The command will prompt you for your administrator password, uninstall all active QRecall components, and then restart your system.
(Note: this assumes QRecall is located in your /Applications folder; if it isn't, adjust the path accordingly.)

Following the restart, launch the QRecall application and let it reinstall itself.

That should resolve your problems. Let us know if it doesn't.

JoeMFox wrote:Thanks a lot, I am really impressed by the service you are providing!

Yes, the restart solved it, so it is working as expected.

That's a relief to hear!

in the older version, when creating a new archive, the "Data redundancy" by default is set to "1:8" (which I think is a good choice); but the current version, by default, redundancy is switched off.

I was encountering too many customers who had redundancy turned on for archives stored on RAID or cloud drives, which themselves provide their own error correction, which is—dare I say it?—redundant. So I made this particular feature "opt-in".

BTW: when I find some time I might test the redundancy (by "destroying" some data using a hex-editor)

Have fun! That's the way we test it here. (I even wrote a custom tool that scrambles random bits of a file so I could automate the tests.)

JoeMFox wrote:the advanced setting "QRExcludeCasheExcludesMail" (as you described) does not exist; instead there is a setting "Excluding Cache or TM excludes Mail"; I guess, this is the correct setting.

The defaults setting key is QRExcludeCasheExcludesMail—that's the value that gets set in ~/Library/Preferences/com.qrecall.helper. The "Excluding Cache or TM excludes Mail" is its human friendly description in the advanced settings panel. When you open the value for editing it will show you the equivalent defaults command.

There is, however, a long standing bug in macOS wherein a defaults setting set by one app for a different app isn't immediately visible to the second app. The easiest way to correct this is to restart the system and check the setting again. If it's still set, try the capture again.

I have done several tries:
- I also have tried "Items exclued by TimeMachine" (in this case caches are grayed out)

Time Machine exclude cashes, so one implies the other.

The easiest way to test if the setting is working is to use the command line:

qrecall capture /Path/To/Archive --deep ~/Library/Mail

I tested it here and it's working, so my suggestion is to just restart and try again.

JoeMFox wrote:why not just add another checkbox liek "ignore emails (use only for IMAP mails)" ?

I have a lot of boring reasons why I don't want to do that (just yet).

And: as you mentioned, it would be good to know, what the "Cache" checbox is doing (so any user should be able to recreate the behavior by own setting).
In general, for every checkbox which affects more than just a simple file or folder, every user should be able to fully understand what this checkbox is doing.

This answer used to be simple, but as macOS has matured it's become progressively more complicated. Right now, the short answer is there are a set of items excluded when you turn on the "Exclude caches" option:

/private/var/folders
/System/Library/Caches
/Library/Caches
~/Library/Caches
~/Library/Containers/*/Data/tmp/*
~/Library/Containers/*/Data/Library/Caches/*
~/Library/Mail/V*/*
Where ~ is every user's home folder defined in the system.

So for now, I've implemented a new advanced setting (QRExcludeCasheExcludesMail) that turns that last filter rule (Mail/V*) on or off. You can download this pre-release version of QRecall to try it out.

To capture the Mail folder with "Exclude Caches" or "Exclude Items Excluded by Time Machine" turned on, do this:

1) Go to the QRecall > Settings > Advanced
2) Edit the "Excluding Cache or Time Machine excludes Mail" setting. Click the setting until it is un-checked.
3) Save the new setting.

The next capture that captures that folder should recapture everything. But there is some weirdness when changing the ad-hoc filters between capturers because QRecall relies on the filesystem change history to determine which folders needs to be examined, and the change history doesn't reflect that fact the the filters changed. So to be absolutely sure, do this:

4) Open the capture action that captures your home folder
5) Set the "Deep Scan" option
6) Save the action (File > Save)
7) Run the action

Once the action is running, you can turn the "Deep Scan" option off and save the action again. The "deep scan" run will cause the capture to ignore the filesystem change history and iterate through every folder in the captured item.

JoeMFox wrote:I think it is a very bad idea to "hide" emails under the "cache" entry, because it is not obvious that emails belong to "Cache"!

In general, I agree with you on all points. The current mail exclusion filter is basically a hack because I couldn't really come up with a "real" solution.

As I mentioned, you could simply create a second archive for just your mail.

I could also easily add an advance settings that would disable the new ad-hoc Mail filter, restoring QRecall 3 to the behavior of QRecall 2. If that would be of interest to you, let me know here or write to support.

What I'd really like to find is a straighforward way to mark all of the data storage for IMAP mailboxes as cache and capture everything else. Maybe a shell script? Just thinking out loud.

After first (new) backup (of my user-folder) I tested restoring some files.
And I found: my emails are missing in the backup.

That is correct.

In QRecall 3.0.7 and later, if you check either the "Exclude: Cache" or the "Exclude: Items Excluded by Time Machine" option, the contents of any ~/Library/Mail/V* folder will be excluded.

This is because most of the world has migrated to IMAP, and in IMAP the contents of your mail folder are simply cached copies of what's on the server(s). Additionally, recent changes to the Mail program have made these folders immensely complicated and time consuming to capture.

If you have POP or local mailboxes that must be captured, and you do not want to turn off both of the exclude options above (which I would not recommend), then the most straightforward solution is to create a second archive just for mail. Set it up so that it does not exclude "Caches" or "Time Machine" items, and then schedule a capture to capture just the specific POP or local mailboxes you need to preserve. (Again, avoiding any IMAP accounts/mailboxes because capturing these is largely a waste of time.)

Jeffrey wrote:Looks like it is simply recapturing the next time a backup is performed. The drive is listed in the Archive Preferences Specific Items dialog box as simply

/UserName/ExcludeMeDir

This might be because your home folder is mounted on an another (not the startup) volume? This creates confusion for the bookmarks.

I deleted this so there are no entries in the Specific Items section and I'll trying entering it as a reg exp pattern now:

path
//Volumes/OtherHD/Users/UserName/ExcludeMeDir

pattern:
*

infinity: checked

Close

Absolute patterns are anchored to the root directory of each volume.

You'd actually want something like this:

/Users/UserName // ExcludeMeDir [ ] glob

To exclude the entire folder, or to be more subtle:

/Users/UserName/ExcludeMeDir // * [ ] glob

to exclude just the contents of that folder.

If you're still having problems, there are even more esoteric things to try.