> I have both the sparsebundle size and the ZFS FS set. So the FS was created > with a quota of 300GB and the sparsebundle then created in there with > 300GB. >
OK, thanks for the tip. I'll give it a go. > Unless you're backing up multiple Macs, don't use dedup, the performance > hit you'll take will be huge after a few months unless you've got an > obscene amount of RAM, like 64+GB I don't use dedup for everythings, but for TimeMachine I think it may write more or less the same data quite often so there I have it enabled. Performance for time machine doesn't really matter too much. Besides, my NAS (5GB RAM) is only connected with single GBit, so I don't need faster than that. > Dedup and compression give you more free space, and that's what time > machine sees. > > Works great for me. I'm backing up 5 macs. Cool thanks! Jaco >> >> To limit TM disk-usage I have found at least 5 different options: >> 1) Use "zfs quota" to limit the size of the filesystem. >> 2) Use "zfs refquota" to limit the referenced amount of data in the fs. >> 3) Use netatalk feature "volsizelimit" >> 4) give the sparsebundle that TM uses a maximum size (hdiutil -resize 100g) >> 5) Limit Timemachine at application level (defaults write >> /Library/Preferences/com.apple.TimeMachine MaxSize -integer XXXX ) >> >> What are you all using and how does it work out for you? What would you >> recommend? >> >> Best regards, >> >> Jaco _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
