RE: Stand-by servers
Thanks for the feedback. I suspect that this will get too complicated for e-mail very quickly... We already use the idea of minimum and maximum cost X.400 connectors to different servers in two physical locations (but in the same Exchange Site); and this works well. We now want a third location, just in case both of the first two disappear! As this third location is on a different companies premises, and we can not manage and operate the servers on a day to day basis as though they are ours, we were looking for alternate ideas for a rapid restore of the central hub routing site capabilities. The present plan is to build the servers as exact replicas on their own separate network, and restore the Exchange system from the live environment to these servers on a regular (probably monthly) basis. These servers will then sit there doing nothing, until the original servers disappear in a massive puff of smoke. When that happens we link up the spare servers to the network, and the ends of the spokes don't realise that they are different servers. Cheers, Chris -Original Message- From: Ed Crowley [mailto:[EMAIL PROTECTED]] Sent: 02 June 2002 00:56 To: Exchange Discussions Subject: RE: Stand-by servers I think you should build these servers with new names and create new X.400 connectors to each of the hub sites but with higher costs than the X.400 connectors to the primary hub site. Leave them online all the time. Then if the primary hub site goes away, Exchange will automatically reroute via the secondary site with no effort on your part whatsoever. If you want a BDC or two at the secondary site, then build them, but don't follow your idea of promoting and taking offline. You can always promote any BDC to PDC at any time if the PDC goes away; just promote one of your BDCs to PDC if the need arises. Ed Crowley MCSE+Internet MVP kcCC+I Tech Consultant hp Services Protecting the world from PSTs and Bricked Backups! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Chris Jordan Sent: Thursday, May 30, 2002 6:45 AM To: Exchange Discussions Subject: Stand-by servers We have a hub and spoke network of 150 Exchange 5.5 Sites. The centre Site of the hub is just a routing Site with 2 servers (no user mailboxes). All spoke Sites are connected to the hub Site with X.400 connectors (to one or other of the servers). We now need a Business Continuity / Disaster Recovery environment for the Hub. We want to build 2 spare servers in another location, and have these servers take over the role of the routing hub in as short a time as possible. Our plan is to build these spare servers as copies of the live servers (same NT name, same IP address, same Exchange configuration). They will be kept off the network until the central hub is no more, and then the network will be switched, and these servers will become live. How should we build the server?? One idea is: Build a BDC in the normal domain. Then disconnect the BDC from the network, and promote it to a PDC. Then the new (member server) Exchange server can be built off the network and connected into the stand-alone domain using the new PDC. The Exchange server and configuration can then be restored, probably on a monthly basis to maintain it in (approximate) step with the live environment. Anyone know whether these ideas will work? Anyone got other ideas that we should explore? At the present time we are less worried about the spoke Sites, which is where the users reside. Thanks, Chris _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Stand-by servers
Wow 150 sites... I remember when Merrill Lynch reached 212 sites and Directory Replication stopped working. Turned out that 212 was a design limit. Of course Microsoft fixed it since. -Original Message- From: Chris Jordan [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 30, 2002 9:45 AM To: Exchange Discussions Subject: Stand-by servers We have a hub and spoke network of 150 Exchange 5.5 Sites. The centre Site of the hub is just a routing Site with 2 servers (no user mailboxes). All spoke Sites are connected to the hub Site with X.400 connectors (to one or other of the servers). We now need a Business Continuity / Disaster Recovery environment for the Hub. We want to build 2 spare servers in another location, and have these servers take over the role of the routing hub in as short a time as possible. Our plan is to build these spare servers as copies of the live servers (same NT name, same IP address, same Exchange configuration). They will be kept off the network until the central hub is no more, and then the network will be switched, and these servers will become live. How should we build the server?? One idea is: Build a BDC in the normal domain. Then disconnect the BDC from the network, and promote it to a PDC. Then the new (member server) Exchange server can be built off the network and connected into the stand-alone domain using the new PDC. The Exchange server and configuration can then be restored, probably on a monthly basis to maintain it in (approximate) step with the live environment. Anyone know whether these ideas will work? Anyone got other ideas that we should explore? At the present time we are less worried about the spoke Sites, which is where the users reside. Thanks, Chris _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
Re: Stand-by servers
Never had to do this but my guess would be to do the following. Build the servers in another location with X.400 connectors as the same as your main routing site, but make the cost of the connectors higher say 100. If the main site goes down the backup routing site should take over automatically. - Original Message - From: Andrey Fyodorov [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, June 13, 2002 12:44 PM Subject: RE: Stand-by servers Wow 150 sites... I remember when Merrill Lynch reached 212 sites and Directory Replication stopped working. Turned out that 212 was a design limit. Of course Microsoft fixed it since. -Original Message- From: Chris Jordan [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 30, 2002 9:45 AM To: Exchange Discussions Subject: Stand-by servers We have a hub and spoke network of 150 Exchange 5.5 Sites. The centre Site of the hub is just a routing Site with 2 servers (no user mailboxes). All spoke Sites are connected to the hub Site with X.400 connectors (to one or other of the servers). We now need a Business Continuity / Disaster Recovery environment for the Hub. We want to build 2 spare servers in another location, and have these servers take over the role of the routing hub in as short a time as possible. Our plan is to build these spare servers as copies of the live servers (same NT name, same IP address, same Exchange configuration). They will be kept off the network until the central hub is no more, and then the network will be switched, and these servers will become live. How should we build the server?? One idea is: Build a BDC in the normal domain. Then disconnect the BDC from the network, and promote it to a PDC. Then the new (member server) Exchange server can be built off the network and connected into the stand-alone domain using the new PDC. The Exchange server and configuration can then be restored, probably on a monthly basis to maintain it in (approximate) step with the live environment. Anyone know whether these ideas will work? Anyone got other ideas that we should explore? At the present time we are less worried about the spoke Sites, which is where the users reside. Thanks, Chris _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Stand-by servers
Perhaps configure them into the network with a full set of connectors identical to the the existing hub, but set the cost on the new connections to 100 (use when the other connectors are not availalbe)? -Original Message- From: Chris Jordan [mailto:[EMAIL PROTECTED]] Sent: Thursday, 30 May 2002 11:45 PM To: Exchange Discussions Subject: Stand-by servers We have a hub and spoke network of 150 Exchange 5.5 Sites. The centre Site of the hub is just a routing Site with 2 servers (no user mailboxes). All spoke Sites are connected to the hub Site with X.400 connectors (to one or other of the servers). We now need a Business Continuity / Disaster Recovery environment for the Hub. We want to build 2 spare servers in another location, and have these servers take over the role of the routing hub in as short a time as possible. Our plan is to build these spare servers as copies of the live servers (same NT name, same IP address, same Exchange configuration). They will be kept off the network until the central hub is no more, and then the network will be switched, and these servers will become live. How should we build the server?? One idea is: Build a BDC in the normal domain. Then disconnect the BDC from the network, and promote it to a PDC. Then the new (member server) Exchange server can be built off the network and connected into the stand-alone domain using the new PDC. The Exchange server and configuration can then be restored, probably on a monthly basis to maintain it in (approximate) step with the live environment. Anyone know whether these ideas will work? Anyone got other ideas that we should explore? At the present time we are less worried about the spoke Sites, which is where the users reside. Thanks, Chris _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] Important Message: [This transmission or any part of it is intended solely for the named addressee. It is confidential. The copying or distribution of this transmission or any information it contains, by anyone other than the addressee, is prohibited. If you have received this transmission in error, please let us know by telephone 61 7 3860 2111 or by reply email to the sender. If you are not the named addressee, you must destroy the original transmission and its contents. You may not rely on electronically transmitted material unless the transmission is subsequently confirmed by fax or letter. Material transmitted to you should also be checked by reference to a hard copy of that material printed directly from our word processing system.] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Stand-by servers
I think you should build these servers with new names and create new X.400 connectors to each of the hub sites but with higher costs than the X.400 connectors to the primary hub site. Leave them online all the time. Then if the primary hub site goes away, Exchange will automatically reroute via the secondary site with no effort on your part whatsoever. If you want a BDC or two at the secondary site, then build them, but don't follow your idea of promoting and taking offline. You can always promote any BDC to PDC at any time if the PDC goes away; just promote one of your BDCs to PDC if the need arises. Ed Crowley MCSE+Internet MVP kcCC+I Tech Consultant hp Services Protecting the world from PSTs and Bricked Backups! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Chris Jordan Sent: Thursday, May 30, 2002 6:45 AM To: Exchange Discussions Subject: Stand-by servers We have a hub and spoke network of 150 Exchange 5.5 Sites. The centre Site of the hub is just a routing Site with 2 servers (no user mailboxes). All spoke Sites are connected to the hub Site with X.400 connectors (to one or other of the servers). We now need a Business Continuity / Disaster Recovery environment for the Hub. We want to build 2 spare servers in another location, and have these servers take over the role of the routing hub in as short a time as possible. Our plan is to build these spare servers as copies of the live servers (same NT name, same IP address, same Exchange configuration). They will be kept off the network until the central hub is no more, and then the network will be switched, and these servers will become live. How should we build the server?? One idea is: Build a BDC in the normal domain. Then disconnect the BDC from the network, and promote it to a PDC. Then the new (member server) Exchange server can be built off the network and connected into the stand-alone domain using the new PDC. The Exchange server and configuration can then be restored, probably on a monthly basis to maintain it in (approximate) step with the live environment. Anyone know whether these ideas will work? Anyone got other ideas that we should explore? At the present time we are less worried about the spoke Sites, which is where the users reside. Thanks, Chris _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
Stand-by servers
We have a hub and spoke network of 150 Exchange 5.5 Sites. The centre Site of the hub is just a routing Site with 2 servers (no user mailboxes). All spoke Sites are connected to the hub Site with X.400 connectors (to one or other of the servers). We now need a Business Continuity / Disaster Recovery environment for the Hub. We want to build 2 spare servers in another location, and have these servers take over the role of the routing hub in as short a time as possible. Our plan is to build these spare servers as copies of the live servers (same NT name, same IP address, same Exchange configuration). They will be kept off the network until the central hub is no more, and then the network will be switched, and these servers will become live. How should we build the server?? One idea is: Build a BDC in the normal domain. Then disconnect the BDC from the network, and promote it to a PDC. Then the new (member server) Exchange server can be built off the network and connected into the stand-alone domain using the new PDC. The Exchange server and configuration can then be restored, probably on a monthly basis to maintain it in (approximate) step with the live environment. Anyone know whether these ideas will work? Anyone got other ideas that we should explore? At the present time we are less worried about the spoke Sites, which is where the users reside. Thanks, Chris _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
