Re: New Hardware and Setup Advice



I have no problems with your plan. Your plan should be what you are
comfortable doing and you should practice/test it. Sometimes when you
restore it will kick off you have 30 days to reactivate.

Just for kicks look at
http://www.usb-ware.com/sata-hot-swap-internal-drive-kit.htm as another
idea. So if your drives were in trays and the power supply died, swap em to
your spare box and plug it in :)

--

Grey
SBS Rocks !!!
Join the worlds largest SBS User Group
http://groups.yahoo.com/group/sbs2k/


"Richard Wagstaff" <rwagstaff@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23V1jO4KgGHA.3860@xxxxxxxxxxxxxxxxxxxxxxx
We are a small family-owned company who are about to move into a new
location and I'm looking to start from scratch. The problem is that we
don't have the budget to bring in outside experts and I'm certainly no
expert (although I've been watching over our current SBS 2003 network for
some years).

These are my thoughts as to how to proceed and I'd be really grateful if
some kind should could give me their thoughts.

Currently our server (SBS 2003 Standard) has only two HDD's. Disk 0 is
split into C & D - C has the operating system and D has Exchange. Drive 1
has the data. We back up Drive 1 & Exchange every day using Backup Exec
10 (SBS) and each week an image is taken on C & D using Powerquest's V2i
Protector.

We have 8 workstations all running XP Pro SP2

My thoughts are to buy two identical servers (something like Dell's
Poweredge 830) so if one server dies I can copy the drive image to the
"spare" C & D drives, restore the data to the second disk and be up and
running again with the minimum delay. I'm thinking of sticking with SBS
2003 Standard.

We also have an old accounts/software package that is a Btrieve based
package. This is getting very long in the tooth now so I'm planning to
put this onto another server box running Windows Server 2000. By doing
this I'm hoping that future "improvements" to SBS 2003 will not trash our
accounts package.

We will also need a new network switch and I'm guessing that we will only
need a basic unmanaged switch (we're currently using a Netgear FS 524. At
present out firewall a is taken care of by a Netgear FVS 328.

Does this plan sound feasible or I'm I totally off the mark here? I'm
really looking for a fairly sound system that can be recovered as quickly
as possible in the event of a major hardware failure in the server.

Many thanks

Richard



.



Relevant Pages

  • Re: slow disk response
    ... Same for the SBS CALs. ... once i have the new server up i will add a note to this ... great with PATA HD and mobo driver is unlikely to improve things much. ... drives passed. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Determin drive letter using DeviceHarddiskVolume##
    ... drives in the RAID array. ... replaced during the time they were bringing the server back up. ... On a workstation of the SBS domain, Event ID 55 is recorded that indicates ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Moving computer and user accounts over to a new server
    ... If we are all familiar with the idea that you can mirror a pair of drives, ... Now you build a different server as you described, ... Essentially that is the core of a process that I've written a migration ... I would say that 1 in 50 SBS techs at most would find the entire ...
    (microsoft.public.windows.server.sbs)
  • Re: Rebuilding SBS Server 2003 SP2
    ... As a way of keeping things easy, I name all my SBS installations as ... to the WAN IP of the client's SBS server. ... or mirroring with two drives. ... Just stick in one drive for the OS and partition for the OS and data, ...
    (microsoft.public.windows.server.sbs)
  • Re: Need to rebuild my SBS 2003 Premium Server
    ... image your existing drives. ... would then be your production server, and then one back to the repaired PE. ... that you're left with a clean install of SBS. ... So I figured that the drive couldn't rebuild due to ...
    (microsoft.public.windows.server.sbs)