3

Time Machine is not accessing the internet. Your ISP or your modem are incorrectly categorizing the traffic as network traffic. Time Machine operates entirely between your computer and the drive itself (necessarily communicating to the device the drive is plugged into). There's no intermediary servers. You will need to pursue solutions specific to your modem ...


3

Time Machine in Catalina only supports HFS+ as a destination volume. The first macOS that supports APFS as a destination volume is Big Sur. ref: https://support.apple.com/guide/mac-help/types-of-disks-you-can-use-with-time-machine-mh15139/10.15/mac/10.15 vs: https://support.apple.com/guide/mac-help/types-of-disks-you-can-use-with-time-machine-mh15139/11.0/...


3

As of macOS Big Sur - and according to the updated man tmutil - you need to provide the date and time of each backup using -d and -t flags, respectively. So the following tweak is needed for the accepted answer: latest=$(sudo tmutil latestbackup) sudo tmutil listbackups | while read backup; do if [[ "$backup" != "$(basename $latest)" ...


2

Regarding your first question: It is the operating system that automatically resizes sparse bundles as necessary when you add data to them. This is done transparently underneath Time Machine, so it is not something that Time Machine explicitly handles. The sparse bundle itself can have a maximum capacity that exceeds the available space on your drive, as it ...


1

Starting from January 2020, CCC is not allowing clone tasks for Time Machine volumes, see this official docs: https://bombich.com/kb/ccc5/can-i-use-carbon-copy-cloner-clone-time-machine-backup However another application SuperDuper! does the trick. It's free for tasks like a simple clone. Make sure to select "Backup - all files" option after ...


1

It’s going to be hard to offer blanket advice since if your hardware has failed, your backup is suspect, no amount of correct process will help. This would be a data recovery project which is very different than trying to recover from a lost password, admin database corruption. Reinstalling the current OS from recovery should fix the machine enough to ...


1

Solved: I had to uninstall Mac Server from the Mac Mini!


1

Yes, you can just use Migration Assistant to transfer your files from the old computer to the new. There's no need to create a Time Machine backup first in order to migrate data and settings. It does not matter that one is a Mac Mini and the other is a Mac Pro. Migration Assistant will be default allow you to transfer the data over the network. Both ...


1

Best guess is the drive is the wrong format. Time Machine won't back up NTFS, FAT or ExFAT. APFS should work, but 'safest' is HFS+ [MacOS Extended, Journaled] using GUID, not MBR. These options are available in Disk Utility. You will not be able to change the format "live," you will need to copy this data elsewhere, then erase the drive & then ...


1

Converting "forward" means that direction is from not encrypted -> encrypted. I.e. you started with a blank disk and enabled encryption. It is possible to do a conversion in the opposite direction if you later decide you do no want your disk to be encrypted. Your backup was encrypted - it is not stored in the clear when encryption is enabled. ...


1

You can't delete individual files or folders from Big Sur's Time Machine. And using the command line tmutil does not help. Big Sur uses the new Time Machine to APFS (TMA). TMA is very different to the old TMH (TM to HFS+). TMH used hard linked folders to avoid storing the same folder and its files many times. These hard links were the main cause of ...


1

Many thanks @Joy Jin. I have improved the solution by decreasing the interval from 10 seconds to 1 second to prevent cleaning backups better: #!/usr/local/bin/fish while test 0=0 if tmutil status | grep -q "BackupPhase = ThinningPostBackup" tmutil status tmutil stopbackup echo '!' say "Prevented cleaning Time Machine backups&...


Only top voted, non community-wiki answers of a minimum length are eligible