Re: Breaking the rules?

From: Al Mulnick (amulnick_No_SPAM_at_ncDOTrr.com)
Date: 06/30/04


Date: Wed, 30 Jun 2004 18:25:27 -0400

I wonder why I never get consulting gigs like this one :)
Yikes. What a PITA.
IMHO, log files are much more important than EDB's. Protect them at a cost
commensurate with your risk.

Depending on size and density of the server, you may not need to put
everything on separate RAID drives, but having RAID configuration is a best
practice you'll be glad you followed. Disk drives are moving parts and as
such have a lower MTBF compared to other components. Backups are a funny
thing: if you don't practice putting them back, they tend to not work when
you need them. Since no RAID would mean you'd be susceptible to many
failures, that may be a problem that takes care of itself. :)

As for the other item, that is something you have to figure out. You can
run Exchange on a single server along with DHCP, DC, GC, F/P, etc.
Microsoft has a product just for that called SBS. The difference is that
you won't be using SBS so you'll have to figure out how to balance all of
that on a single machine. That just translates to more work in the
development side. 20 users? You *might* get away with putting their
mailboxes on the other side of a WAN, but that totally depends on your other
infrastructure and other variables. There's a lot to consider when figuring
out which is best. Your risk is probably divided into several parts: the
user perception, the WAN link (saturation, reliability, etc), local
backup/support (central vs decentralized), development time, etc. You'll
have to decide what you're willing to risk or not and only you can put a
price on that risk. That's what a consultant can help you do....

Al

"admin too" <nguser2u@no.spam.AOL.com> wrote in message
news:10e6bbghic1as14@news.supernews.com...
> We are going from 5.5 to Exchange 2003 and outsourcing the labor. Vendor
#1
> has said you need to have two RAID setups for OS and logs and EDB because
> that is what Microsoft recommends. Vendor #2 has said there is no
advantage
> because if you lose either the logs or the EDB, you are restoring anyway!
>
> Another issue is, #1 said even for a very small (20 users) location we
must
> setup a separate Exchange server from the DC which is doing File and print
> and DHCP). We lived for five years with everything on one DC in that
> location. He said, just have a DC locally and have them connect across our
> VPN to the single exchange server. The second vendor said ' Hogwash, for
20
> users you can put everything on one nice new server with plenty of RAM and
a
> new Xeon CPU.
>
> I can save some big bucks using #2 but how big is the risk?
>
>



Relevant Pages

  • Advice on RAID crash
    ... Event Source: Disk ... This RAID array contains some data and the exchange and SQL databases. ... Other drives are on another separate RAID mirror, so the server continued to ... The strange thing is I checked the Adaptec Storage Manager logs and it shows ...
    (microsoft.public.windows.server.sbs)
  • NTDS.dit and logs on same disk- actual real-world performance
    ... preferably two Raid 1 arrays. ... 36GB for OS, NTDS.dit, logs, SYSVOL, and pagefile. ... these server are dual 3.2 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Problem Configurating Firewall
    ... De Server has 1 NIC, connected to the internet thru a router. ... the logs? ... The os is installed on 1 raid 1, the data on the other raid 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Hardware + Exchange 2003
    ... One problem is that you're not isolating the logs. ... RAID type you've chosen for the stores. ... the server, I would avoid using server assist. ... I am planning an Exchange 2003 move. ...
    (microsoft.public.exchange.setup)
  • RE: isa 2004 & external website access issue
    ... emailed the logs to you as requested. ... each web server has its own public IP ... > headers in ISA Server ... > 'Microsoft Firewall' service. ...
    (microsoft.public.windows.server.sbs)