Exchange and the SAN

[xmario2013]

Hi All:
We are thinking about putting Exchange data file onto a SAN which the storage will be separated from the server itself, is it better to setup like that anyway ?

Also we need to setup replication and fail over between two sites , the SAN vendor can offer replication software to snapshot or just hot-replicate the data, I am assuming we need a second Exchange server to handle the replication and failed over data to redirect user and ensure up time.

so we need to install Exchange 2000 on the second server and create/restore the same site name ?

(ie. we are using Win 2000 server, EXG 2000 Entprise edition and we dont have OS-based Cluster)

does anybody have experience in doing this ?
how we should go about and do that ?

Thanks
XM

 

[DestinysDream]

It is better to use a SAN for obvious reasons: Faster backups and storage space. You could have a secondary exchange server but I don't think it is absolutely necessary to do that. Replication and failed over data should be able to be handled by the one Exchange server.

If anyone calls and says "I know a little something about computers" just tell them to reformat it.

 

[xmario2013]

but what if the Exchange server itself failed ? is that safer for it to failed over the a second box so client connection is uninterrpted ?

There are two software we are looking at right now that can do that, since we dont have Microsoft clustered

Legato Co-Standby Server AAdvanced For Microsoft Exchange
XOSoft WANSync HA 10K for Oracle and 8K for Exchange

Do you have experience using these ?

thanks

 

[DestinysDream]

I have no experience using those software items because we never had it set up where if one server failed the other could access the priv.edb. Sorry I can not help with that. It would be wonderful to have something like that. Where did you get it?

If anyone calls and says "I know a little something about computers" just tell them to reformat it.

 

[Marcs41]

No experience with those products either, and frankly, I would not want to.
Stick to 'normal' procedures like clustering or even a spare server with (again) 'normal' backup procedures.

In case of disaster, you would find loads and loads of support, where if you opt for a third party product like these, however good they may be, you are basically depending on them.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
How Do You Get Great Answers To my Tek-Tips Questions? [/sub]See faq222-2244

 

[DestinysDream]

Since you are going to put your important files like priv.edb and pub.edb on the SAN a Exchange failure would be insignificant in the grand scheme of things since all you have to do is reload it.

If anyone calls and says "I know a little something about computers" just tell them to reformat it.

 

[xmario2013]

but how much time will it take to reload the operating system, the Exchange and reconfig it ? assuming our server gets smoked

There is a lot storage,DR, down time related considerations we are looking into , alots info out there in various storage site like
searchstorage.com

http://www.networkcomputing.com/channels/storage.jhtml

http://informationweek.storagepipeline.com/

http://www.enterprisestorageforum.com

Hi Marc:
How would you prepare for a spare Exchange server if our OS is not clustered ? do we have to buy a mirrored set of license (ie. Microsoft Exchange and the CALs) if we are to install one ? maybe that is a second layer we can look in to do. if I only install the Exchange and setup in the spare server with the identifical setting (ie. Exchange settings, IP address, computer name etc.) and keep the data files on the SAN, will this work ?

XM

 

[DestinysDream]

I can uninstall and reinstall Exchange with no errors in about 45 minutes.

If anyone calls and says "I know a little something about computers" just tell them to reformat it.

 

[Marcs41]

Mario,

even with your setup idea, you would need a spare server, so that part does not change a thing, costwise.

Some use an imaging tool to 'ghost' the server, but that is ussually a heavy load because of the data. Now, in your case, with a SAN, that could be easier, since the data is not part of the image.

"nicer' is a second server (and Server License) on standby.
If the config is the same, all you need to do is connect to the SAN when #1 goes down.
You can use parts of :

http://support.microsoft.com/default.aspx?scid=kb;en-us;297289

WITHOUT of course:
Take the existing server offline.
Reset the machine account for the Exchange 2000 server: a. Start Active Directory Users and Computers.
b. Locate the Exchange 2000 server machine account, right-click the machine account, and then click Reset Account.

Your next problem is the IP address. If they are both live, you need different IP addresses of course, but that is not an issue since #2 is not doing anything, it is just a ghost of #1. One #1 goes down, change the IP of #2.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
How Do You Get Great Answers To my Tek-Tips Questions? [/sub]See faq222-2244

 

[novachild]

What would you recommend for an SBS 2000 user who is limited to one server and a couple of workstations that aren't being used?

I'm looking for a way to replicate my Exchange data in case the DC fails again. Doubletake has been recommended by friends, but will it work on a SBS 2K network? Also, it's a tad expensive for a small business having to buy two additional licenses for everything.

I'm trying to avoid having to send my data off to be converted to PSTs in case of an extreme hardware failure. I know I can export individual mailboxes as PSTs as a safety measure, but there's got to be an easier way.