macOS will delay disk and other input/output operations for background tasks like backing up. Is there any point in disabling that in an Apple silicon Mac to make backups faster?
Time Machine
How to browse log entries for an event that occurred many days after its entries have been removed from the active log, by discovering its exact time and the processes involved.
After logging in, macOS may check for system software updates, run an initial Time Machine backup, and run XProtect Remediator scans. This is how those happen.
If you’ve upgraded to Tahoe, your Time Capsule should still back up normally. But erase it to start new backups, and Time Machine refuses to back up to it any more.
As Time Machine has changed, first to back up APFS volumes, then to create backups as snapshots, its needs have changed. This makes it complicated to decide which local snapshots you can delete without affecting its backups.
Fundamentally simple: a preserved copy of a volume at a moment in time. How its size can only increase with time, how they’re managed, what they’re used for, and the tools for using them.
In a quest to reduce the number of processes running in macOS Tahoe, consider the example of Time Machine backups, which can easily be replaced by 3rd party alternatives.
When I started my Mac up, its external backup storage was present as expected, but couldn’t be opened. It turned out that Time Machine had stopped backing up after 12:35 the previous day, but hadn’t reported the problem.
T2M2 is nearly 9 years old. Here’s a walk through its summary reports on Time Machine backups. and an outline of what you’ll see in its log extracts.
How to exclude folders and files from these services, with new problems apparent in macOS Tahoe over exclusions from Time Machine backups.
The Eclectic Light Company 