TimeMachine Backups Stop With Error

DEVONthink
1

I’m using DT3 since years. Last week I installed DT4beta for testing on the same MacBookAir (M2, Sequoia 15.5).

Since then TimeMachine backups stop with an error:
“Backup of /Users/myUserName/Library/Application Support/DEVONthink/Inbox.dtBase2/Files.noindex could not be created”.

The file names in the error messages may vary. I also saw “inbox.dtBase2/Files.noindex/rtf”

I know that installing the beta created a link in ~/Library/Application Support/DEVONthink 3 :
Inbox.dtBase2 → /Users/myUserName/Library/Application Support/DEVONthink/Inbox.dtBase2

Any ideas to get TimeMachine doing backups again? Installing Devonthink 4.0.1 didn’t help.

2

Welcome @tcfos
That is an Apple question. We don’t control Time Machine and its behavior.
Have you rebooted the Mac?

3

A screenshot of the filenames would be useful. Maybe the filenames are too long or contain characters not supported by the Time Machine volume.

4

Yes, I did. Unfortunately reboot didn’t help.

5

Nothing unusual with the filename, I guess.

TerminalScreenshot
TerminalScreenshot845×611 89.7 KB

BTW, “ll” is an alias for “ls -la”.

I understand that this is an Apple problem. I just thought that I might be not the only one with this kind of issue. Maybe I’ll delete my TimeMachine backup and start a new one from scratch.

6

It’s the only report I’ve seen.

7

Summary: there was an issue with my TimeMachine backup destination.

I used the following shell script to display the TM log:

#!/bin/bash
# delete terminal scrollback
printf '\e[3J'

# show logs: time machine, last 6 hours, filtered
log show \
  --predicate 'subsystem == "com.apple.TimeMachine"' \
  --info \
  --last 6h \
| grep -F 'eMac' \
| grep -Fv 'etat' \
| awk -F']' '{print substr($0,1,19), $NF}'

There I found this message:
Copy failed because of a problem on destination, error: 100018

So I had to delete the TM backup by erasing the volume. Then I started TM again and the backup finished w/out errors.

Sorry for bothering you with this off topic issue. Thank you for your support.

8

No real bother and we’re glad to hear you found the core issue! :slight_smile: