WIndows Server 2003 - Exchange 2003 & iSCSI

afking8268 used Ask the Experts™
We have implemented a lefthand iscsi san and successfully move information stores to it.  The SAN is functioning properly, but when I restart the mail server the nic assigned to the SAN doesn't start in time for the Exchange information store to be mounted, so it the service needs to be started manually.  Is there a way to have the NIC assigned to the SAN load up first?  Or is there another solution?
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I woudl first test, but try to set the MSExchangeIS service to be dependent upon the iSCSI Initiator.  Similar to what's being discussed here, using
>sc.exe config MSExchangeIS depend= MSiSCSI   (you're probably forever setting other services to depend on the iSCSI initiator already, or you will be.)

How are you connecting to the SAN? Are you using the MS iSCSI Initiator?

Not sure what you mean that the NIC doesn't start up in time. My guess is that Exchange is starting before the iSCSI Initiator Service.

I would create dependencies on iSCSI for the Server and MSExchangeIS services.

Set Server service dependency so that file shares are created: sc \\computer_name config LanManServer depend= MSiSCSI
Set MSExchange Information Store service dependency: sc \\computer_name config MSExchangeIS depend= MSiSCSI

See also -

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial