"File Not Found (-43)"

[bayswater]

…
Does that mean, as far as you know, macOS 12.6 will record snapshots on other volumes on the same disk? E.g., if you have a 10.14 and at 12.6 startup volume on one internal SSD, when 12.6 is running it will create snapshots of the 10.14 volume?

I finally have an answer.
——
I have not tried a System Restore but I now know that it can be done.

Thanks Mike. That’s pretty much the setup I want, but using 12.6 for newer apps (still too much that won’t run on Venture) and keeping 10.14 going for older apps I have to keep using. At this point, only the Mojave startup uses TimeMachine and I manually copy any documents to the backup drive.

The next puzzle is what happens if I tell the 12.6 partition to use my 8T spinner backup drive for TM. My understanding is that 12.6, unlike 10.14 will not give the option to leave the backup drive as HFS and will force it to APS. From what I’ve read, this drive will not perform well if formatted as APS.

[mikehalloran]

…
Does that mean, as far as you know, macOS 12.6 will record snapshots on other volumes on the same disk? E.g., if you have a 10.14 and at 12.6 startup volume on one internal SSD, when 12.6 is running it will create snapshots of the 10.14 volume?

I finally have an answer.
——
I have not tried a System Restore but I now know that it can be done.

Thanks Mike. That’s pretty much the setup I want, but using 12.6 for newer apps (still too much that won’t run on Venture) and keeping 10.14 going for older apps I have to keep using. At this point, only the Mojave startup uses TimeMachine and I manually copy any documents to the backup drive.

The next puzzle is what happens if I tell the 12.6 partition to use my 8T spinner backup drive for TM. My understanding is that 12.6, unlike 10.14 will not give the option to leave the backup drive as HFS and will force it to APS. From what I’ve read, this drive will not perform well if formatted as APS.

TM drives since Monterey are APFS. Apple recommends HDDs and I'm have no problem with any of mine ranging from 6–14TB.

I'm lousy with 2012 MBPs around here at the moment. Mine is running Catalina and one of the ones I'm working on is over Monterey — both are backed up to one of my drives. The one running Monterey only uses half of the 128GB drive I installed so I did a full System Restore (not APFS Snapshot) just to test this — worked great. This MBP is one of the ones I'm incorporating into the newer one running Ventura.

After I get my new AS Mac, I'll probably reformat the 2T SSD in my MBP to Mojave for the rare occasions I need to use Encore. I am not going to keep my iMac Pro for that one use and have lost confidence that Don Williams's planned upgrade to Encore 6 will ever happen.

[daniel.sneed]

I just set a new 4Tb HD for Time Machine and boot drive clone.
This new HD is APFS for both volumes.
The previous was APFS for TM only (the boot drive clone was not).
Now, when DP is running, no more “File not found (-43)“ when TM is backing up.
Back to work!

[mikehalloran]

I just set a new 4Tb HD for Time Machine and boot drive clone.
This new HD is APFS for both volumes.
The previous was APFS for TM only (the boot drive clone was not).
Now, when DP is running, no more “File not found (-43)“ when TM is backing up.
Back to work!

None of that explains why I was getting it since everything has been APFS since Monterey. OTOH, it was a much bigger issue for me in DP 10 and it’s been a few months since I’ve seen it in DP 11.

[Rick Cornish]

FWIW: Since this original post, I have turned off automatic Time Machine backups on my studio Mac and have gotten in the habit of starting a TM backup after I finish for the day.

The other day, I started a TM backup and then re-opened a DP project to check something… same behavior: when I went to save (and NOT "Save As…) it would not save in the original project. The only way to save my work was to create a new DP project.

So, in my experience, this is still an issue.

[mikehalloran]

FWIW: Since this original post, I have turned off automatic Time Machine backups on my studio Mac and have gotten in the habit of starting a TM backup after I finish for the day.

The other day, I started a TM backup and then re-opened a DP project to check something… same behavior: when I went to save (and NOT "Save As…) it would not save in the original project. The only way to save my work was to create a new DP project.

So, in my experience, this is still an issue.

Did you check the box Copy Audio? If so, it should have cautioned you that it would overwrite when you navigated back to the Project directory. Click Yes and it will overwrite and you will not lose any work.

AutoSave is the culprit—I have been able to demonstrate this to MOTU who told me that it was Time Machine based on your comments. If that was true, it would affect everyone but it doesn't.

Unfortunately, now that I have Activity Monitor on whenever DP is running, I've not experienced this again. I have no doubt it's a conflict. I'd love to find out with what but it has to act up when I'm looking.

[Rick Cornish]

FWIW: Since this original post, I have turned off automatic Time Machine backups on my studio Mac and have gotten in the habit of starting a TM backup after I finish for the day.

The other day, I started a TM backup and then re-opened a DP project to check something… same behavior: when I went to save (and NOT "Save As…) it would not save in the original project. The only way to save my work was to create a new DP project.

So, in my experience, this is still an issue.

Did you check the box Copy Audio? If so, it should have cautioned you that it would overwrite when you navigated back to the Project directory. Click Yes and it will overwrite and you will not lose any work.

AutoSave is the culprit—I have been able to demonstrate this to MOTU who told me that it was Time Machine based on your comments. If that was true, it would affect everyone but it doesn't.

Unfortunately, now that I have Activity Monitor on whenever DP is running, I've not experienced this again. I have no doubt it's a conflict. I'd love to find out with what but it has to act up when I'm looking.

Thanks, Mike. Interesting to know that I'm now famous with MOTU tech support!

I'm too nervous about losing a track to overwrite a project that way. For now, I'm OK with limping along the way I've been doing it. Hopefully, it'll get fixed somewhere along the line one way or the other (like when I migrate to an AS machine).

[EMRR]

Happened a lot this weekend, multiple times a complete freeze requiring force quit, wouldn't save. Occasionally it went away and I could continue.

Every time I had a look and it was always at the end of an automatic time machine backup. TM is a USB3 Samsung T7 APFS volume. Maybe not related, but.....

ALSO - my working audio project folder is EXCLUDED from TM backups, and is on the internal Studio drive.

Corresponding PITA: autosave has been intermittent for me in dp11. It's semi-random, and sometimes it just stops saving altogether. I've got it set for 1 minute, and if I toggle it on/off it'll do 1 minute again for a short while.

[EMRR]

2 months later, still doing manual TM backups, not one (-43) since.

[Rick Cornish]

FWIW: I just wanted to post that this issue—which had led me to do manual Time Machine backups on my Intel system—has not appeared since migrating to DP11.3 on Sonoma on my new Mac Studio.

EDIT:
OK—hold on, this may be back.