#OPENZFS ON MAC MAC#
I've been testing this and the performance I get from iSCSI disk attached to a MAC VM is substantially better than using SMB1 on 10.9.5 to alleviate the permissions and open handle issues. Also for your test - if VHDX containts lots of over provisioned junk you'll cheat yourself on a numbers :) Reason? Issue with chunk datastore and whole volume is trashed.
#OPENZFS ON MAC HOW TO#
Also make sure you run a good backup for deduped volume (some backups know how to move MSFT data dehydrated AFAIK DPM does it). Reason? Dedupe chunks would move to and from sealed containers killing performance. If you do a lot of writes then you probably don't want to use per-volume deduplication. MSFT dedupe works well for read-intensive workloads (for some reason MSFT keeps calling them "VDI" which leads to tons of confusion). I don't have an internal person to bounce these ideas off, so the spiceworks sanity check is always nice. We'll see after some stress on the system though.Įither way, all input has been greatly appreciated. If I have no issues with backups, integrity, or performance, I see no reason NOT to dedupe. Other than that, I'm really testing backups and data integrity. The iSCSI target VHDX is deduped between 50-60% depending on the data I move to it, and the most taxing thing is CPU during dedupe, and network during transfers. I'm running tests on a Server 2012 R2 iSCSI target, which ESXi has mounted as a datastore, and Mac 10.9.5 running on ESXi as guest OS. Worst case, they have terrible performance or are unreliable, and I go back to plain old RAID. I'd feel foolish if I didn't at least test them out. I understand the cost of disk is coming down, but the options for dedupe are also growing.
#OPENZFS ON MAC WINDOWS#
Some things - directly from MacOS X, some - thru Windows 7/8 running VMs under VMware Fusion. Hosted Exchange, file shares etc - everything works. That's what we use here: company is 80% Windows (hypervisors are VMware vSphere and some Hyper-V and file servers are all Windows Server 2012 R2) and some 20% guys (including myself) are on Mac. However for VM you don't really need ZFS inside (how are you going to pass-thru disks to it)? I'd either configure Windows Server 2012 R2 roll-your-own VM exposing shares (SMB3? NFSv4?) you like. I've looked at openzfs to see if this will work.Īny suggestions whether it is best to mount a LUN from the mac through ISCSI and put openzfs on the mac directly, or a linux based VM with openzfs and then mount the volume served up by the VM to share? I'm looking into a suitable plan to move it back to a mac but keep the data deduplicated and on the SAN. We obviously ran into some issues with permissions and file locks accessing windows shares from a mac.
We purchased SAN disks to add to our existing infrastructure to move our mac fileserver to server 2012 and take advantage of deduplication since the data has become quite large.
0 kommentar(er)
