Here’s another build, this time peppered with logging messages throughout the ClientConnector::replaceSettings function. Please try with this version and do the same thing, and post the outcome here again - this will help narrow down exactly where the failure is happening.
the context menu of the urbackup client taskbar icon only shows “Access Backups”, “About…”, “Status” and “Uninstall”
trying to debug it I get the following error: macOSTaskPolicy: (com.apple.debugserver) may not get the taskport of (urbackupclientba) (pid: 15628): (urbackupclientba) is hardened, (urbackupclientba) doesn’t have get-task-allow, (com.apple.debugserver) is a declared debugger
With the previous version provided by @Moisie debugging was possible and also I was able to see “Settings” in the context menu.
thank you very much for that hint. In deed your version runs fine in the debugger, but the problem I described with uroni’s version remains the same. After installation the icon of the application stays white for quite some time (1-2 minutes), then finally turns red. But in both cases the context menu only shows the options mentioned above (“Access Backups”, “About…”, “Status” and “Uninstall”). Your previous version worked better
Sorry for the delay on this. If you’re happy to keep testing a few builds, then I’m happy to try and narrow it down further! It might take a little while, but I’m happy to persist if you are…
Perhaps we should take this into DMs, rather than contaminate this thread further?
I have installed the “MacOS client 2021 - #75 by Moisie” (from the link above) and configured /Users as a backupdir. (Using sudo to run the urbackupclientctl command).
Are there other directories that are recommended to backup on the Mac version?
Thanks for giving this a try - please feed back with your experiences on the macOS client!
The /Users directory is likely the most important for any individual; however, you might consider backing up the entire system drive in order to catch your applications and their supporting data too.
Even though you won’t be able to fully restore a working system drive from such a backup, it can be a useful reference for - e.g. - reverting to a previous version of an application, should an update break functionality.
This isn’t currently noted anywhere, but you likely need to grant the Urbackup application Full Disk Access:
Go into System Preferences > Security & Privacy > Privacy, and select Full Disk Access in the column on the left-hand side. Then drag the Urbackup application into the table on the right-hand side, and ensure it’s ticked. You might need to unlock the padlock at the bottom of the screen for this.
AHA! Yes, that was exactly it. I found that the UrBackup Client.app was in the list (but not checked). After checking it and rebooting the iMac, a full backup is running and moving data (it failed in just building the list before).
I am again getting errors that indicate the UrBackup client does not really have full disk access. However; I have told it to protect /Applications and two accounts in /Users, but it is getting upset about “Error while listing files in folder “/System/Volumes/Data/private/var/db/ConfigurationProfiles”. User may not have permissions to access this folder. Errno is 0”
I have confirmed that UrBackupClient still has Full Disk Access.
I am confused about why UrBackupClient is down that path to begin with. I can’t see any reason for it in the other messages that came out (about symlinks going off to places and needing to be verified).
Thanks for the feedback. The error you’re seeing is different from the ‘Full Disk Access’ Privacy permission, and is an area I’m working on at the moment - better removal of unreadable (or unbackupable, or unrestorable) system files - so in due course, this error will be handled better.
As to why the client is going down this path: I suspect you may have an alias to Macintosh HD somewhere inside /Applications or your two user accounts, which will lead the client here. The client will then be looking inside the folder to see what files it has, and whether they should be included in the backup - at which point the OS doesn’t give it permission.
Assuming you can’t easily find the alias to Macintosh HD in those places, you might want to try adding /System to the list of excluded folders, in the hope that the client will be prevented from delving too deep inside there; TBH I don’t know if this will work or not - but it’s easy to try!