Update failed to install.
What do you do next? Just try to download it again? What if you’re running a local Content Caching server?
Content Caching
The macOS 12.1 update is the smallest x.1 update since High Sierra 10.13.1 in October 2017, over four years ago. How come it has bucked the trend in Big Sur?
Content Caching server originated in 2005, as a feature in Mac OS X Server, which sold Xserves. Time Machine came in 2007, to support Time Capsules. Those legacies are so different, though.
Details of how the Content Caching server handles a cache macOS security data update, and both client and server handle an App Store update.
Using Activity Monitor and command tools to assess performance of a content caching server, and diagnosing problems from the log.
Big Sur updates have far exceeded those of Mojave or Catalina, and are set to total well over 40 GB. Prospects for security updates are no better, with a high carbon footprint.
Those who are cautious and like to wait before updating are in a quandary: it is better to risk updating now, or your Mac falling victim to malware?
macOS 11.2, 11.2.1 and 11.2.2 have come in quick succession. What do they tell us about how difficult it is to update Big Sur’s sealed System volume? Is this the way to go?
Although updating each M1 Mac requires 1 GB of direct download from Apple, there are great economies in running your own Content Caching Server. And why Apple doesn’t want to offer standalone Big Sur updates.
Can you use Big Sur’s Content Caching Server to save and retain updates which can substitute for ‘delta’ and Combo standalone update packages?
The Eclectic Light Company 