Question on syncing a TM or CCC backup to the cloud
Now TM uses APFS and does not use hard links. The size increase mentioned above may not occur. Should this be the case, Is it possible to sync (not backup) the external SSD doing TM (or CCC) backup to the cloud? On the event of catastrophe, one could download the cloud copy. Even though it may take a long time, but in theory, it could be downloaded and could work. Yes?
One difficulty is "what would you sync?" TM and, by default, CCC create an APFS volume and in that volume make a snapshot for each backup. So you would, presumably, sync the latest snapshot. By the time that is finished (some days/weeks later) there would be many more snapshots - would you skip them? And some deleted (thinned) from 1 per hour to 1 per day to 1 per week - would you want to delete them? It kind of gets messy to even decide what you want to do.
And would it be useful for recovery? Not, I think, for a Migration Assistant recovery. Yes, for a folder and file recovery.
But for a file and folder recovery it would have been easier to have used Arq (or Backblaze, Crashplan, etc.) which can recover particular folders, etc. without any need to restore the whole backup.
Question on snapshots
When the external TM disk is not plugged in, I understand that TM stores the hourly snapshots on the Macintosh HD (or Macintosh HD-data, not sure which), yes? But later when the external TM disk is plugged in, TM does its normal hourly backup, that is it does not create hourly snapshots, yes? What happens to the snapshots created previously? Nothing happens to them, yes?
Snapshots are of the Macintosh HD-data (since that is the only varying volume). The "local" snapshots are removed after 24 hours. The new snapshots on the external TM disk, would be deleted according to TM's internal rules about thinning. Note, I have not tested this - on my MacBook I run TM manually whenever I connect the external disk. The snapshots on the external get thinned as expected to 1 per day and then 1 per week as best it can.
Question on how to do CCC backup when backup contains snapshots
I read that CCC creates a snapshot on the destination drive before each backup. For daily backup, after one week, I will have 7 snapshots on the destination backup disk. Now the Macintosh HD fails. I use CCC to clone the CCC backup to the Macintosh. So the 7 snapshots previously on the CCC backup are also cloned to the Macintosh HD. This is OK because as far as snapshot goes, whether it is created by CCC or TM does not matter because they are the same, yes?
With CCC you can configure how it does the thinning.
By default (and unsupported) CCC does not make bootable clones. I would avoid that path. Just configure CCC to make backups (with snapshots) which are Migration Assistant compatible.
Also "cloning" (as per CCC) clones the current snapshots, not past ones. So if you cloned back from external to internal you would only get the most recent snapshot.
Much depends on your Mac hardware...
Question if it is useful for backup to be bootable
I also read that for Macs that have the apple silicon chip, a bootable backup is not necessary because when the Macintosh HD fails, it couldn’t be booted by an external disk. So it is better off just backup only the Macintosh HD-data because it is less complex to do and save disk space, yes?
There are those who like bootable clones. I am amongst those who don't for recent Macs.
With older Intel Macs you can boot directly from an external drive and this provided fast recovery following failure of the internal disk. As you know, this is not true for an Mx Mac. The initial boot for an Mx Mac is to boot from a hidden partition on the internal disk. This then loads macOS from the Macintosh HD from either internal or (if you allow it) external. So the only value of a clone is for protection in case you make your internal macOS so corrupt it won't start - that is no protection from hardware failure.
Finally, a dump question. Using APFS, is there any fundamental reason that prevents apple to offer Time Machine backup to the cloud?
Yes, network speed.
Time Machine without major redesign would be very network intensive.
For backup, it is bad enough when the TM destination is on a local network share - it would grind to a halt if the destination were over the internet. Backup performance could be alleviated if TM kept a local index of the TM cloud copy. Just like Arq, etc. do.
Apple could offer to synchronise the TM volume (and its snapshots) to iCloud in the background (for those with adequate connectivity). Apple would then need to provide a web based recovery tool for individual files and folders (like Backblaze) or another app (e.g. like Arq's recovery).
Full system recovery becomes problematic except to a Mac which has ~1Gb/s network throughput all the way from a Mac to Apple's servers.