“Has anyone seen this problem before?”
I have, and from what I have heard from reading forums over the years, it sounds like a very common problem with Time Machine: every once in awhile, it says “I need to delete your backup and start over.”
Or it says “I can’t backup because your backup device is full” (even though Time Machine is supposed to prune itself ...
Yes. Setup is easy.
Connect the drive to the first Mac directly (USB or whatever is fastest)
Add the drive in Time Machine Preferences
Use System Preferences, the menu bar or tmutil to make a backup.
Eject the drive from the first Mac once you have a couple backups completed.
Repeat the above steps for the second Mac.
Now when each Mac tries an hourly ...
I have Time Capsule and Time Machine setup on my MacBook Pro.
The Time Capsule is always available at home. The Time Machine is only available sometimes.
macOS never complains about the Time Machine drive being unavailable, unless it's been like 7 days (which almost never happens).
You can try starting in Safe Mode. Restart your Mac and immediately after your Mac starts (some Mac computers play a startup sound), press and hold the Shift key. Release the Shift key when you see the progress indicator. See if this works. If so edit your question mentioning that it works in safe mode, and leave a comment here.
Finder knows how to do this, almost nothing else does.
Hard links &/or permissions are the downfall usually.
Don't attempt to manually trim it as part of the copy process, just copy the whole lot. If you need to trim by size or date, do it separately.
Apple guide on copying - Transfer Time Machine backups from one backup disk to another
You can try this method. it has worked in the past. Open your Time Machine backup disk and then Enter Time Machine using the Time Machine icon in the menu bar. Now you should be in Time Machine with a list of the backups. Select one of the backups and then look for a gear icon near the header of the backup you selected. Click on this gear icon and it should ...
Great details - since you are in the command line already we should be able to get some very critical details sorted and help you understand how the system works, validate it’s configured and perhaps let you solve this.
The three big commands are tmutil isexcluded and tmutil startbackup --block and tmutil compare
You should be able to check at any time if ...
With TMNotifier you can send yourself an email when a backup is completed. It also notifies you when a Time Machine error occurs.
The only disadvantage: TMNotifier is not free.
However, there is a free version, but you can only do limited things there... But the small price that has to be paid, it's worth it!
Your situation doesn't entirely makes sense to me (but maybe I'm reading too much into it). You need zero space and zero functioning drive to boot to Internet recovery. Since you mentioned reformatting as a solution. I wanted to share the official steps for an erase install (for the curious)
The answer to your question is No.
There have been various attempts. I seem to remember a company which attempted to offer this several years ago as a commercial product (not even to iCloud, but Time Machine to "the cloud"), but I believe they discontinued it, and it was never particularly well-regarded in practice.
There have been lots of people ...
iCloud is not a backup solution, it is a sync solution.
It will hold phone/pad backups, but not computer.
You cannot use it to store data that is not also present on your devices, other than such as offloading full-resolution photos or documents in low-space situations locally.
For true off-site backup you need to be looking at such as Backblaze.
The estimates are often off to be conservative, make sure enough space is there to not run out if the estimate is not perfect. Just exclude every folder and allow a token empty one to back up. After several intervals, the estimate will be better and you can add documents back by removing it from the exclusion list.
Timemachine has changed a lot between different OSX versions. Some settings were still linked to an old version.
The root cause appears in the Console logs. You can filter Timemachine error in Console.app by searching backupd.
In this particular case, we've figure out the error was: Illegal permissions or ownership discovered on local snapshot directory !
Keeping an external drive connected cleans up snapshots in 24 hours. There’s no real need to disable things in my experience, other than let the hourly backups run and prune.
I would also upgrade to 10.15.7 and then report if you have some specific issue once a day passes on the new system build.
With APFS on SSD I can’t measure any performance issue since ...
In Terminal, enter the following command to list all backup snapshots:
tmutil listlocalsnapshots /
You will get a list of all the snapshots in the root directory (/).
Delete each snapshot by entering the following command + date of the corresponding snapshot:
sudo tmutil deletelocalsnapshots <snapshot_date>
sudo tmutil ...