Hi
Another question I had
Why does SAN booting seemed to be frowned upon and not good practice from VMware and the likes?
Some blades are good to boot from the SAN but look at the cost of SAN disks and a pair of mirrored drives.
from my personal experiences the main concern raised with booting from SAN is the fact that all your commands are sent across the fibre, I haven't seen any performance impact but theoretically if you have your swap on the SAN and your serviceconsole and your VMs all going down (potentially) 1 pipe there could be some performance impact.
More to configure, more to troubleshoot, more headaches, more money, very little gain..
Stick to booting from local drives, SWAPPING to local drives, and keeping the 'live data' on the SAN.
I would say that if the SAN crashes you've lost everything anyway. From my viewpoint it seems that for the most part people are just being resistant to doing things in a new way. I know a large bank locally that recently removed all of it's local hard drives from it's ESX servers (over 50 of them) because the only disk related failures they have experienced in the last 12 months have been related to local disk. The SAN has been the far more fault tolerant than any local disks could ever hope to be. And with dual fiber paths into the SAN your better off than having an array controller that can go bad.
Just my opinion, but I think you guys should re-evaluate your position on not booting from the SAN.
In the design that my team and I put together, we chose to go with local disks for all of our ESX Hosts, using the SAN strictly for VMFS volumes. We weighed the cost of hosting boot volumes on the SAN vs. using internal disks, making sure to research the potential technical risk on either side, and determined that it was the safer approach..
I may be wrong here, but if I recall correctly... boot-from-san is only currently supported under certain situations (i.e. with certain HBA's attaching to certain arrays), and there currently isn't support for redundant paths... so, if you lose the HBA that's got the LUN for the boot volume (but not the redundant HBA you should have in there!)... eep.
We tested the multipath ability by pulling out the fiber while things were running with multiple VM's perfoming tasks. Everything worked flawlessly. We put the fiber back in and it all moved back. We pulled the other fiber and again all worked as designed. We are using an EMC Symetrix and an HP blade center with dual port Qlogic cards. Perhaps that is why ours works so well. We haven't tested it on a normal server so I can not say for sure what would happen there. I just assumed that if it worked on one platform it would work on all. Can't say for sure. We will test it when wee get a chance.
Just don't be in too much of a hurry to poo poo the idea on conjecture that it might not work.
Also as to the cost of hosting the OS on the SAN, we feel that it is a minor expense when compared to the nearly 30 TB of storage we are currently using for data.