Upgrade from Win2k to Win 2003 including Hardware

Discussion in 'Server Migration' started by Tarran Walker, Oct 11, 2004.

  1. Hello All,

    We are planing a upgrade of our servers from win2k to win 2003 however we
    want to purchase new servers for this to go onto.

    Server One (Win 2k):
    - ROOT DC
    - DHCP
    - DNS
    - WINS
    - File Server
    - Print Server
    - Client AntiVirus Server

    Server Two (Win 2k):
    - Exchange 2000 (Upgrade to Win 2003)
    - Exchange Virus Software
    - IIS
    - MS SQL SERVER

    Does anyone have any advice on doing this? Any precautions? Best steps to
    take? Improvement ideas on structure? Whitepapers or resources?

    Hardware side of things:

    We are currently using two Compaq Proliant 1850R Servers with three drives
    (RAID-5 Config) and a forth drive as cache drive. Each server contains:
    CDROM, FLOPPY and Backup TAPE Drives.

    I am looking for servers like this (maybe exclude the cache drive and use
    the forth in the RAID-5 config) but with higher specs, anyone have any
    suggestions on decently priced servers along these lines?

    Any better suggestion on the Server config is welcome.

    Thanks in advance,

    As always any help is much appreciated,

    Kind Regards,
    Tarran Walker
     
    Tarran Walker, Oct 11, 2004
    #1
    1. Advertisements

  2. Tarran Walker

    Herb Martin Guest

    Why? In most domains DCs are actually overpowered if they perform
    no other service (except perhaps name resolution.)

    It's likely an artificial limitation you are imposing as Windows is
    designed to be upgraded and does so quite nicely. You can certainly
    add new hardware and retire old hardware as necessary but do it
    for reasons you can clearly identify.

    If you are running multiple services (especially file servers, SQL,
    and Exchange) on your DCs, or if you are running with only ONE
    DC then you would probably be better served by using multiple
    (even old,slow) DCs and using the newer faster servers for to
    separate the Exchange, SQL, and File services depending on
    load.
    Likely the above is a DC (perhaps in the Root domain of a multidomain
    forest but then all other DCs in that domain would be "root" too.)
    Multiple domain controllers -- splitting the "big services" to multiple
    newer, faster machines IF you have a performance issue.
    It is common for READ-mostly databases to actually SUFFER
    from RAID-5 (depending on how well your controller handles this)
    and Active Directory and Exchange are very frequently READ-mostly
    databases. This is also somewhat common for even SQL but the data
    access patterns on SQL are much less likely to be predictable outside
    of your organization.

    You might do better adding separate drives for such databases (perhaps
    Mirrored/Duplexed rather than RAID-5.)

    All of this presumes you have SOME sort of performance concerns,
    such as a large user base, which you imply by the desire for "new
    hardware."
    First identify you peformance and fault tolerance requirements and
    current issues.

    You cannot optimize or effectively and economically improve your
    performance unless you know your baseline and know your goals
    very explicitly.
     
    Herb Martin, Oct 11, 2004
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.