Exchange Server

taco · Guest

Hi...

I have the following setup...

2 HP DL320 G3 servers, 2x72 GB HDD
1 MSA 1000, 3x146 GB

I have divided the SAN for the Exchange 2003 cluster (fresh setup) as follows

1 GB Quorum - drive Q
1 GB MSDTC - drive M
10 GB Logs - drive L
250 GB Data - drive I

When I reach to the System Attendant resource creation stage, and add disk I
and name resource dependencies,I get 'error: cannot find path' or something
like that.

I tried several times but was finally able to get it up usiing IP address
resource as a dependency instead of network name.

I want to know if this setup is ok or what error have I done during my setup

Thanx.

Rodney R. Fournier [MVP] · Guest

From the Deployment guide http://www.microsoft.com/downloads/details.aspx?familyid=77B6D819-C7B3-42D1-8FBB-FE6339FFA1ED&displaylang=en (Pages 134-135):
To create an Exchange 2003 System Attendant resource

1. In Cluster Administrator, in the console tree, right-click the Exchange Virtual Server, and then click Bring Online.

2. Right-click the Exchange Virtual Server, point to New, and then click Resource.

3. The New Resource Wizard starts. In the Name box, type Exchange System Attendant - (<EVSName>), where EVSName is the name of your Exchange Virtual Server.

4. In the Resource type list, select Microsoft Exchange System Attendant. Verify that the Group box contains the name of your Exchange Virtual Server, and then click Next.

5. In Possible Owners, under Possible owners, verify that all nodes that are running Exchange 2003 are listed, and then click Next.

6. In Dependencies, under Available resources, select the Network Name resource and all of the Physical Disk resources for this Exchange Virtual Server, and then click Add. Click Next.

7. In Exchange Administrative Group, in the Name of administrative group list, select the location in the Windows directory where you want to create the Exchange Virtual Server, and then click Next.

Note
This option is available only when you create the first Exchange Virtual Server in a cluster. All Exchange Virtual Servers must reside in the same administrative group.

8. In Exchange Routing Group, in the Name of routing group list, select the routing group in which you want the Exchange Virtual Server created, and then click Next.

Note
This option is available only when you create the first Exchange Virtual Server in a cluster. All Exchange Virtual Servers must reside in the same routing group.

9. In Data Directory, in the Enter path to the data directory box, verify the data directory location. You must verify that this location points to the shared physical disk resource assigned to this Exchange Virtual Server. Exchange will use the drive you select in this step to store the transaction log files, the default public store files, and the mailbox store files (pub1.edb, pub1.stm, priv1.edb, and priv1.stm). Click Next.

10. In Summary, read the summary of the action you are about to perform. Click Finish to create the Exchange Virtual Server.

Important
After you create an Exchange Virtual Server, you cannot rename it. If you want to rename an Exchange Virtual Server after it has been created, you must remove it and then re-create it with another name. For information about how to remove an Exchange Virtual Server from a cluster, see "Removing an Exchange Virtual Server" in the Exchange Server 2003 Administration Guide (http://go.microsoft.com/fwlink/?linkid=21769).

11. If the operation was successful, a dialog box appears indicating that you have successfully created the Exchange Virtual Server. The Exchange Virtual Server you created will now appear in Exchange System Manager.

However, if the operation was not successful, a dialog box appears indicating why the process failed. The New Resource Wizard remains open, so it is possible to go back in the wizard, remedy any problems, and then click Finish again.

12. After the Exchange Virtual Server is created, in Cluster Administrator, right-click the new Exchange Virtual Server, and then click Bring Online.

Note
Due to directory replication latency, all resources may not come online in your first attempt. In this case, wait for replication to occur, and then bring the resources online again. To add resources to the dependencies list when creating the Exchange System Attendant resource, first ensure that the resources you want to add are online.

Notice step 6 :) You did fine.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"taco" <taco@discussions.microsoft.com> wrote in message news:207F8398-1D94-442F-B7B2-6B00A9463E1E@microsoft.com...

Shon Shah [MSFT] · Guest

Are you able to bring the system attendant resource online? System attendant
resource's dependency on a resource of type network name is a 'required'
dependency and the resource should not come online if this dependency does
not exist.

If you are using Cluster Administrator to create the system attendant
resource, it should not succeed in creating the resource unless the
dependency on a resource of type network name is specified. If the
dependency is not specified, you should see an error like "A dependency is
required on a resource of type Network Name".

Not sure how you were able to create the system attendant resource without
specifying this dependency. Or am I missing something here? Some of the
errors logged while creating system attendant resource can be checked in
file "%SystemDrive%\Exchange Server Setup Progress.log".

Lastly, assuming that you have a system attendant resource in online state
that is not dependent on a resource of type network name, I would say the
setup is not ok since email clients might not be able to access the exchange
server using that network name.

Hope this helps.

--
Regards,
Shon Shah
Software Design Engineer/Test
Microsoft Cluster Server

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples, if any, are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"taco" <taco@discussions.microsoft.com> wrote in message
news:207F8398-1D94-442F-B7B2-6B00A9463E1E@microsoft.com...

taco · Guest

I found the error. The public and private adapter order was not right. It
should be public then private. I only new this would affect the cluster while
upgrading to sp1

For SA, I added both name and IP resources.

One question though. during SA setup the srver name should be written in
this form (<server>) or (server)

Thanx

"Shon Shah [MSFT]" wrote:

Gerald Aigenbauer · Guest

hi taco!

you will need the proper priority in binding not only during sp1 setup. you
will find some more issues with wrong bindings. and you should disable
netbios on the heartbeat lan too...

gerald aigenbauer.

"taco" <taco@discussions.microsoft.com> schrieb im Newsbeitrag
news:5D7EFD2C-56B1-4873-B559-A2F590C2AD04@microsoft.com...

	Exchange Server Forum Index -> Connectivity	All times are GMT
Page 1 of 1