So I deleted it and created another one and was very careful to NOT select APFS. In frustration I did a Get Info on the mounted sparseimage bundle and it showed as an APFS volume. I had assumed that disk utility was creating an HFS+ formatted sparsebundle because I had selected that option when creating the image, as shown in the screencap above. I created a few of these (just to be sure) and each one failed as a Time machine Destination.Īs pointed out in his comment Time Machine relies on a feature of HFS+ to do it's job and will not work on one formatted as APFS. It turns out that when you create a sparse bundle disk image that resides on an APFS volume that it is ALWAYS formatted as APFS even if you specify the the format as HFS+ like this: I tried the suggestion, "sudo tmutil setdestination -p instead, and allow tmutil to create it's own sparsebundle on the server." which returned an error. Wondering if anyone has any experience with this? And once it is mounted on the desktop on the Mac I can put files into the sparse bundle, so it is writable. I tried both HFS+ and APFS format on the sparsebundle. Pretty sure I have the correct options for the sparse bundle selected. Sudo tmutil setdestination /Volumes/MBAirĪnd I get an error The backup destination could not be setĪfter much Googling where a lot of answers pop up from AskDifferent none of them seem to have this particular issue using macOS Mojave.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |