We have a virtualized environment of T-Series where each host has either zones or LDoms. All of the virtual systems will have their own dedicated storage on ZFS (and some may also get raw LUNs). All the SAN storage is delivered in fixed sized 33GB LUNs.
The question I have to the community is whether it would be better to have a pool per virtual system, or create a large pool and carve out ZFS file systems per virtual system? The trade-offs are with the one large pool, you'll be able to take advantage of dedup when it becomes available in Solaris, however you then have all your eggs in one basket. It was originally thought that if we have a pool per virtual host, then when you migrate a host, you could migrate the storage too, but that's not looking feasible in this environment. What is probability of corruption with ZFS in Solaris 10 U6 and up in a SAN environment? Have people successfully recovered? In this environment the redundancy is performed at the hardware level, not at the host. So there's no chance of self-healing here. Yes, its been discussed, but because of the legacy storage environment thats shared with other non-ZFS systems, they require redundancy at the hardware level, and they won't budge on that and won't do additional redundancy at the ZFS level. So given the environment, would it be better for lots of small pools, or a large shared pool? Thanks, Brian _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
