We are looking at this heavily right now. Each year at budget time (now) I am asked to put together my view of what our infrastructure should look like, without regard to cost. So each year I spend a little time with Visio and knock something out. My drawing this year shows lots of blades connected to our SAN. Now, when the costs are all flushed out of this, we may find that connecting them to the SAN this year is not cost effective. There are not a lot of reasons to connect a Citrix server to a SAN today. Just my opinion. But, the main reason I did show them connected to our SAN is for disaster recovery. My intention is to get to a blade environment that does Boot From SAN. The SAN will then be split across 2 locations / cities. If the funding doesn't work out for attaching the blades to the SAN this year, we will at least be in a position where we can move blades to the SAN slowly over time as the Business requirements justify that "live" disaster recovery design. By the time the drawing becomes reality I expect to have a couple racks of blades (replacing 10-17 racks of equipment today) and a large VMWare farm. I expect to have just a few "regular" servers for SQL and Exchange clustering, although we are keeping our eyes on IBM's quad processor blades as well. That could eliminate the "regular" clusters. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Grecsek Sent: Wednesday, June 16, 2004 5:31 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Hardware - Blades, SAN? We're trying to determine which way to go with our backend hardware for our Citrix farm...I've been hearing a lot about these blade servers and was wondering if we should setup our farm on a slew of blades and tie it into a SAN? Seems like the optimal configuration for a ton of users running basic apps like Office, IE, Acrobat, etc. Was wondering if anyone had any feedback regarding a setup like this - have you done it, advisable, not really, pro/cons, etc. Email Confidentiality Notice: The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act (HIPAA). The message is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.