![]() ![]() I have a 3 TB AirPort Time Capsule (TC) and run backups exclusively through Time Machine (TM). I'm currently running a single 2013 27" iMac running Catalina 10.15.7. (Please be patient, I promise I'm going somewhere with this long post.) I know I'm way late to join this conversation, so please forgive anything that might seem like it was already covered or perhaps novice. As far as I can determine, "APFS sparsebundle on a NAS" is the only common factor that consistently causes slow incremental backups for me and allegedly many others, but not all. The behavior is the same with MBP16 and M1 Air. But I don't think there are any reliable references to back up that statement/opinion. ![]() After a few weeks, I could only produce one backup a day. If "there is a reason why APFS has to be used", it better be good, because if I use APFS on NAS boxes, it just doesn't work very long. If that bundle is HFS+, the speed stays constant over the weeks. If that bundle is APFS, backups get slower over a week, becoming unusably slow. The backup target must be a sparsebundle. The host disk could be formatted into anything that the Pi supports, as long as it's served over SMB/AFP. There's no mechanism for it to make a difference.įurthermore, the behavior is exactly the same with a Raspberry Pi as a backup target. ![]() That is to say, this probably has nothing to do with Time Capsule. MacOS does all the work of converting those bits into an APFS file system, mounted in /Volumes. It's just serving the bands over the wire. But the Time Capsule has no way of knowing what the internal format of the bundle is. Inside the host disk, there's a sparsebundle, which is indeed APFS by default in Big Sur. It's dealing with an HFS+ disk that it creates. Click to expand.In the default setup that Big Sur produces, Time Capsule itself is not dealing with APFS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |