You can see from the Arq logs that Arq is spending countless hours clearing blocks that have been freed by the thinning process. I have a hypothesis that each of these blocks may be incurring a round trip from Mac to AWS to be freed. Backblaze B2 cloud storage is separate.ī2 is pay-for-what-you-use cloud storage that’s not just for backups but also for hosting files it’s comparable to Amazon S3 standard or Wasabi.īut having tens of thousands of operations execute locally on the server, rather than over a WAN, can behave much better.īackblaze used backup is unlimited storage used exclusively by their backup client software. B2 has a command-line client but it provides an API so anyone can write their own client, Arq can use it as a backup destination. Looking at your Arq logs, it takes over two hours to create a backup of /Users but your Photos drive takes only half an hour, even though it’s almost three times as much GB. That’s likely because that drive has about one-third as many files, 369K vs. 1,067K, and probably far fewer that have changed between runs. I see Arq creates an APFS snapshot of /System/Volumes/Data but it doesn’t show it being used. Just going by the logs, it shows it’s backing up the active /Users directory, not from the snapshot, meaning the backup client has to also deal with files that are locked for use by other processes. Regardless, the backup of data from your boot drive is likely involves the most disk I/O and most noticeably affects performance. I don’t really know the details of how Arq works.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |