Isn't the easiest route to install the old data drive in the new server and
copy the data drive to drive?
The route I used was to install my SBS 2K from scratch/clean. Apply all the
updates (saving them on the server in case needed later)
Create a few accounts for test.
Then one night I moved the data drive from the server and copied all the
data to the new machine.
I then did a full backup of the new server.
Data drive went back to old server and was available next day for normal
In the mean time I had the new server running with 2 test workstations on
it's own mini LAN.
Made sure everything was running ok, Did more backups etc. Tested AV
software left server running for a week or so to make sure any parts that
were going to fail would be spotted.
Then when I was ready I restored back to my first good SBS2K tape backup and
re did the whole process for real.
Kept the old server on standby incase there was a problem. When all was ok
after a day or 2 the old server was pulled.
> We're just looking in to this at the moment - we were hoping to do it
> the three day plan since this seems reasonable.
> Most of the plans I've seen don't account for downloading updates to the
> (No point in installing ashiny new server without all those important
> security updates), testing of the configuration (IMHO an absolute must) or
> the amount of data to be moved.
> Unfortunately we're only on an ISDN line (and down to single channel half
> the time due to an ISP problem) so updates can take 3-4 hours.
> A test copy of about 20 Gb (25%) of our data took about 2 hours so there
> goes a day on the data move alone. We're currently looking for software
> that can reliably copy the data overnight (i.e. will report any errors in
> log, but continue to process the rest). We've been looking at
> synchronisation software since backup doesn't seem to do what we want.
> If anyone has recommendations on these areas I'd love to hear them.
> > About 16 working hours is a fair estimate ASSUMING your
> > SBS 4.5 installation is working perfectly. No errors or
> > problems. The hardest part is the Exchange 5.5 to 2k
> > migration. This also assumes migrating the server only,
> > no client migration/setup work (that could take longer
> > depending on number of and type of clients). Also, 24
> > working hours is not too far fetched either, it could end
> > up taking that long if problems arise. This is the reason
> > why I try to follow the advice of many others here and
> > only do fresh, clean installs if at all possible. Hope
> > this helps.
> > >-----Original Message-----
> > >I just got a few quotes for that exact process.
> > Dell/Techsolve estimated 24
> > >hours, with no attention to the clients at all. Another
> > local, reliable,
> > >and experienced IT company estimated 16 hours. I posted
> > a similar thread a
> > >while back, and got one response of 15 hours, and one of
> > 4 hours (I liked
> > >the 4 hour one, but I would have had to fly them in from
> > England, so the
> > >cost was more or less equal).
> > >From the responses I got, and the responses you got, it
> > seems like two work
> > >days (16 Hours) is how long it should take, and anyone
> > quoting 24 is either
> > >not experienced, or padding their quote, or providing
> > some additional
> > >service.
> > >> Approximately, How long does it take to do a migration
> > upgrade from SBS
> > >4.5
> > >> (22 clients)
> > >> onto a new server to SBS 2000?????
> > >> I'm thinking of doing it on a weekend, my service
> > provider gave me
> > >estimate
> > >> of 3 days or 24 hours???
> > >> Any tips? Comments? Suggestions???
> > >> Thanks.
> > >.