Thanks in advance to any community members who can help! I have tried to search here on the forums, in the TrueNAS docs and on google but my search-fu is failing me. Is there some other setting I am missing? So I guess my questions are these: What does the setting "Time Machine" actually do? What samba options are changed over the default behavior? I would like to know because I don't want the share to show up as a Time Machine backup target, if possible. I also tested sparsebundle image creation using Disk Utility and it, too, exhibits this same behavior, only working when "Time Machine" is checked. If I then change the share's purpose to "No presets" (which keeps its previous settings as far as I can tell but lets me modify them) and check "Time Machine" then CCC happily creates the disk image and successfully backs up. If your needs are simple, you can get by with a simple app. I can create & delete folders and files it seems without issue on this share but when CCC tries to create the sparsebundle it seems to start (the Finder shows the image briefly) but then it fails saying that it couldn't create the image. All backup & sync requirements are not equal, and neither are all backup & sync applications. Then I created a share using "Default share parameters". Next I set permissions so my group "shareusers" has "Full Control". To reproduce this I created a new dataset with the default options and share type set to "SMB". I have also tested this behavior on my newer server running TrueNAS SCALE 22.02.4 and its behavior is identical. It has beetn failing on disk image creation and updates for a while now. That is actually the most common use case for them, as protected storage. It doesn't sound like it was reported as a bug, or opened as a case with AppleCare.I used to have CCC back up to a sparsebundle disk image which it was happy to create and update on the server years ago, iirc. It is possible that sparceimage is encrypted. (Not a very good combination in several ways, but that's how it manages to avoid full backups of the encrypted sparse bundle.)Īnd I don't think the reference to a "guy at the Genius Bar" means anybody at Apple was really looking at anything to do with this. That's how Time Machine deals with a home folder that has File Vault enabled. A sparse bundle will be backed up band-by-band, not file-by-file. Unless I'm missing something, I don't think that applies here, or is likely to be changed. Would love to see some movement on this.here's the link to the thread: I tinkered with it this morning (on 10.6.4) and it's still a problem. At one point someone indicated that Apple Engineers were "working on the issue.", but nothing seemed to come from it. There is an archived thread that describes this in detail. It used to work in 10.5, but broke in 10.6.x. So I converted my encrypted sparse image to an encrypted sparse bundle, and now I can include it along with all my other files in my ordinary backups. Your backup software only has to copy the 8 MB band(s) containing any of that file's data (often only one). As a result, assuming your backup software treats the contents of bundles as individual files, you no longer have to back up a huge disk image just because a tiny file changed. What's cool about this is that if you change something on a sparse bundle (adding or modifying a file, for instance), only the band(s) containing that data change, not the whole bundle. (To verify this, you can Control-click or right-click a sparse bundle, choose Show Package Contents from the pop-up menu, and browse through its contents.) Inside that package is a folder full of bands - files that are each 8 MB in size, as many as are needed to hold the image's data. It's a bundle (also known as a package) - a folder that Mac OS X treats as a single file, which is also true of applications. What's different is that it isn't actually a single file, as all previous disk image formats were. :Ī sparse bundle looks and acts just like a sparse image - it can grow in size, can optionally be compressed or encrypted, and so on. Sparsebundle disk image instead of a sparseimage, that shouldn't happen. And since the image is large I run out of Each time I add/modify a file inside the image, then TM marks the whole image asĬhanged and hence backs it all up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |