http://www.msexchange.org
-------------------------------------------------------I agree.
I just barely built our new Exchange server on a NetApp FAS270 SAN
with fibre channel (McData switch, Qlogic 2340 HBA), and everything
works very good.
The other benefits that I can see from boot from SAN are:
1. Easier to do disaster recovery.
When I snapshot the volume where the LUNs for the Exchange servers
located, I snapshot practically the entire server. In case our
Exchange server is stolen or destroyed, I can always redirect this
snapshot to a different server with similar specs and brand, and boot
the server.
From the server standpoint, it will think that power just went off,
(unclean shutdown) and Exchange should start doing soft-recovery.
2. Before I install Windows service pack, or anti-virus, new driver,
or some application on the server, I can snapshot the server. So, in
case the service pack, or program breaks something, I can always
restore the point of snapshot.
Granted this doesn't work with Active Directory, and that's why I
don't boot from SAN for our AD server, but this should work with
Exchange.
Of course one should test this first in a lab, but not everybody has a
lab they can play with.
On 4/11/06, Michael B. Smithwrote:
>
>
>
> Dunno your hardware configuration.
>
>
>
> Those points are somewhat valid, but replacing an HBA is no harder than
> replacing a NIC. How often do you do it? I don't think I've ever replaced an
> HBA (although I don't buy cheap ones, either) and if you are meshed, then
> that argument is COMPLETELY specious.
>
>
>
> Replacing a server is replacing a server. Easier with boot-from-LAN ?
> nothing to configure. J
>
>
>
> If you've got LUNs, then use them. Word. What on earth are you paying for?
> It to look pretty standing there?
>
>
>
> A valid argument from them would be something that would cause you: a)
> performance degradation, or b) downtime.
>
>
>
> SANs are for storage consolidation and performance improvement. Why pay the
> cost for a RAID controller plus at least two disks in the server to boot
> with, when you've got the space, capacity, and performance on the SAN?
>
>
>
> IMHO. YMMV.
>
>
> ________________________________
>
>
> From: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Tom
> Kern
> Sent: Tuesday, April 11, 2006 2:52 PM
> To: exchangelist@xxxxxxxxxxxxx
> Subject: [ExchangeList] Re: SAN Boot
>
>
>
>
>
> EMC told me they support it but were trying to sway us away from it.
>
>
>
>
>
> We have an unmanaged datacenter, so they felt replacing a failed server or
> HBA would add a layer of complexity for a level 1 tech to achieve.
>
>
>
>
>
> Also, they mentioned something about wasting LUN's for swap files for the
> OS.
>
>
>
>
>
>
>
>
> make any sense?
>
>
>
>
>
> Thanks
>
>
>
>
> On 4/11/06, Michael B. Smithwrote:
>
>
>
> Works fine for me with HP SANs (the little MSA's) and EMC SANs.
>
>
> ________________________________
>
>
> From: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Tom
> Kern
> Sent: Tuesday, April 11, 2006 2:23 PM
> To: ExchangeList
> Subject: [ExchangeList] SAN Boot
>
>
>
>
>
> Anyone have any pro or con for SAN booting win2k3 with Exchange 2k3?
>
>
>
>
>
> I know its supported by MS but I'm not sure if we should go that route.
>
>
>
>
>
> My manager is pushing for it.
>
>
>
>
>
> We are about to purchase an EMC Clarion to put Exchange 2k3 on(which
> obviously i have no problem with) and SAN boot the OS(unsure about that).
>
>
>
>
>
>
>
>
> Thanks
>
>
>
-------------------------------------------------------
List Archives: //www.freelists.org/archives/exchangelist/
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp
MSExchange Articles and Tutorials: http://www.msexchange.org/articles_tutorials/
MSExchange Blogs: http://blogs.msexchange.org/
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx