![]() The quota should be at least two to three times the size of your Mac’s drive, or two to three times the amount of data to be backed up. We recommend you to set a quota to prevent Time Machine from occupying your entire storage space. If you want to encrypt your backups, use the encrypt backup option in Time Machine on your Mac instead of encrypting your shared folder. Over in the OTHER type of NAS they are having some timemachine problems as well. I would appreciate any suggestions on how to resolve this issue. The Air has only about 300GB of data on the disk, and its sparsebundle is much much smaller. The most obvious difference between the two Macs is that the sparsebundle for the Pro is very large (around 2TB there are 1.5TB of data on the computer). I configured another Mac (a MacBook Air) to back up to the same NAS, the same share, and it works with no issues. I believe that the issue is somehow unique to that specific Mac (a MacBook Pro). ![]() But killing the process, restarting the NAS or the router, or even simply unplugging the NAS from the router for a few seconds terminates the process and allows backups to resume. Restarting the Mac does not help as the process runs on the NAS. ![]() When Time Machine tries to start the next backup session, it finds that the sparsebundle cannot be accessed, because the smb process from the previous backup session is still accessing it.Īfter killing the process, Time Machine backups resume for a few cycles, until it happens all over again. It turns out there is an smb process (“smbd -D”) that continues to run on the NAS and use the sparsebundle even after Time Machine completes the backup (it’s shown as “R<” in top). I’ve been able to narrow down the source of my issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |