[ExchangeList] Re: Adding Additional Exchange Backend Server
- From: "Mitul Zaveri" <mitul@xxxxxxxxxxxxxxxxxxxxx>
- To: <exchangelist@xxxxxxxxxxxxx>
- Date: Tue, 18 Mar 2008 12:37:25 +0530
Hi All:
We have added a new Exchange backend server in the current setup and tried
moving a test user mailbox using ESM. The process was completed
successfully. However when we are trying to check the same using OWA it is
giving "HTTP/1.1 503 Service Unavailable". Please help me on this.
Thanks & Regards
Mitul Zaveri
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jason Sherry
Sent: Monday, March 17, 2008 10:59 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Adding Additional Exchange Backend Server
1. Make the new server Exchange 2007
. Read:
http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchang
e-Server-2007-Part1.html or similar articles that cover migrating to E2k7
and retiring your E2k7 servers
. Recommend going with a CCR cluster, which requires at least 3 E2k7
server (CCR node 1, CCR node 2, HUB & CAS server)
o If you call all-in-one then HUB, CAS, & MBX roles can be on one system
. If you don't go CCR then at least setup LCR
. If you do goto E2k7, you will need to replace your FE with a E2k7
CAS server before you move mailboxes to E2k7
2. Recommend adding at least one addition DC.
Jason Sherry - Technology Strategist, MCSE: M, Microsoft MVP
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Kamuni, Prabhakar
Sent: Monday, March 17, 2008 3:05 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Adding Additional Exchange Backend Server
Since there is only 1000 Mailboxes in the Organization, new Back end server
should be a well versed solution.
I will recommend you to distribute the mailboxes, so everything should go
ok.
Thanks and Regards
PRABHAKAR KAMUNI | System Analyst| Enterprise Computing Group
Unisys Global Services India | 135/1 Residency Road | Bangalore |
Business Phone +91 4159 4828|Net 7594828
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
_____
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of James Chong
Sent: Monday, March 17, 2008 9:43 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Adding Additional Exchange Backend Server
No cons really; this is the correct step. The only con is probably to
considering migrating to 07 which will give you a that significant IO
reduction via incremental memory.
James Chong
Sr. Systems Engineer
Simplexity, LLC.
11130 Sunrise Valley Drive, Suite 300
Reston, VA 20191
O (703) 657-4612
C (703) 863-1483
_____
From: exchangelist-bounce@xxxxxxxxxxxxx [exchangelist-bounce@xxxxxxxxxxxxx]
On Behalf Of Mitul Zaveri [mitul@xxxxxxxxxxxxxxxxxxxxx]
Sent: Saturday, March 15, 2008 7:23 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Adding Additional Exchange Backend Server
Hi All:
The Current Exchange Setup is as follows:
# Frontend - Backend Setup
# 1 Frontend Server (with RPC over HTTPs proxy) + 1 Backend Server (1000
mailboxes) + 1 Domain Controller
# Windows 2003 Enterprise Server (SP2) + Exchange 2003 Enterprise Server
(SP2).
We are planning to add an additional backend server with higher disk and I/O
capacity and move the mailboxes on the new server.
The steps are broadly outlined as below:
1. Additional Server joining the Existing windows domain
2. Installing Exchange server joining the Existing Exchange Organization.
3. Creating Multiple Mailbox Stores to distribute Mailboxes between stores.
4. Moving mailboxes to a New Exchange Server
Can somebody please guide me through the pros/cons of this setup or
pre-defined checklist that one needs to take care of in this kind of
migration.
Thanks & Regards
Mitul
--
**************** CAUTION - Disclaimer ***************** This e-mail contains
PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the
addressee(s). If you are not the intended recipient, please notify the
sender by e-mail and delete the original message. Further, you are not to
copy, disclose, or distribute this e-mail or its contents to any other
person and any such actions are unlawful. This e-mail may contain viruses.
NetMagic Solutions Pvt. Ltd. has taken every reasonable precaution to
minimize this risk, but is not liable for any damage you may sustain as a
result of any virus in this e-mail. You should carry out your own virus
checks before opening the e-mail or attachment. NetMagic Solutions Pvt. Ltd.
reserves the right to monitor and review the content of all messages sent to
or from this e-mail address. Messages sent to or from this e-mail address
may be stored on the NetMagic Solutions Pvt. Ltd.'s e-mail system.
***************** End of Disclaimer *******************
--
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are
not to copy, disclose, or distribute this e-mail or its contents to any other
person and any such actions are unlawful. This e-mail may contain viruses.
NetMagic Solutions Pvt. Ltd. has taken every reasonable precaution to minimize
this risk, but is not liable for any damage you may sustain as a result of any
virus in this e-mail. You should carry out your own virus checks before
opening the e-mail or attachment. NetMagic Solutions Pvt. Ltd. reserves the
right to monitor and review the content of all messages sent to or from this
e-mail address.
Messages sent to or from this e-mail address may be stored on the NetMagic
Solutions Pvt. Ltd.'s e-mail system.
***************** End of Disclaimer *******************
Other related posts:
