Re: Move mailbox process experience



"Mark Arnold [MVP]" wrote:

> On Tue, 9 Aug 2005 10:19:02 -0700, "BvdB"
> <BvdB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >
> >
> >"Mark Arnold [MVP]" wrote:
> >
> >> On Tue, 9 Aug 2005 06:48:06 -0700, "BvdB"
> >> <BvdB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> >Hello All
> >> >
> >> >Situation:
> >> >Old exchange 2000 mailboxes have to move to a new exchange 2003 server with
> >> >new hardware. The average mailbox is about 22 MB with 350 items.
> >> >
> >> >We're going to move a lot of users and I've some questions about the move
> >> >mailbox proces.
> >> >
> >> >1. How large is the transaction log growth by the move mailbox wizard? Say
> >> >you move 25 GB of mailboxes, what is the a approximately logfile growth? Does
> >> >it grow?
> >> >
> >> >2. How much time does it cost to move 25 GB of mailboxes to another server?
> >> >
> >> >3. Is it possible to import a exchange 2000 database or storage group to
> >> >another exchange 2003 server
> >> >
> >> >I would be very pleased if someone can share his/her experiences about the
> >> >questions above.
> >> >
> >> >Kind regards,
> >> >BvdB
> >>
> >> The transaction log will be similar to data moved. That's why it's a
> >> good plan to do a couple of backups after you have moved each batch of
> >> users. It keeps the number of logs to a manageable level.
> >>
> >> Elapsed time depends on the loading of the server whilst the moves are
> >> going on and how powerful the boxes are. 25GB should take quite a few
> >> hours.
> >>
> >> You can bring a 2000 store into a 2003 database. There are steps. Why
> >> do you want to do this if you are doing a mailbox move migration? If
> >> you have two boxes you should do the move method so that you don't
> >> inconvenience the customer by having whole stores offline.
> >>
> >
> >The problem is that we've about 25.000 mailboxes and it will take some time
> >to move all the mailboxes.
> >
> >Any alternative quicker sollution will be very nice. If exchange can import
> >a DB we could save a lot of time. Even if the store has some downtime, the
> >customer will be satisfied more because the total move process will last
> >several weeks.
> >
> >I think the move process is more useful for a small account of mailboxes.
> >
> >What would you advice for about 80 stores with 25.000 users, a mailbox move
> >or a DB import?
> >
> >Kind regards
> >BvdB
>
> 25,000 mailboxes and 80 stores. How many servers have you got? The
> original post talked about one server and now you've scaled that up
> slightly.
>
>

Sorry for the misunderstanding, but I took 1 server as an example.

complete story....

Exchange 2000 environment:
3 frontend servers and 5 backend servers. 4 backend servers with maximum of
storage groups and stores and 1 backend server with less stores. so about 85
stores and 25,000 mailboxes

New exchange 2003 environment:
4 frontend and 7 backend servers, same amount of users and stores.

The new exchange servers are already installed and are in the same
organization.

How are we going to migrate the mailboxes to the new exchange servers in the
best and fastest way?

First choice was the move mailbox wizard, but when we looked more detailed
we calculated that the whole move process will last some weeks

So I'm looking for other solutions that are faster and I heared something
about an DB import function. That sounded good to me.
It will take some downtime but but the total process will probably faster as
the move mailbox method.

I want to aks if someone has some good or bad experiences with the move
mailbox or DB import method?

I hope this is more clearer than the first post?

Kind regards
BvdB
.

Relevant Pages

  • Problem sending mail from Exchange 5.5 to Exchange 2003
    ... Exchange 5.5 server. ... The difference between this migration ... Exchange 5.5 mailbox servers are placed in the users ... When migrating mailboxes home- and commonareas are ...
    (microsoft.public.exchange.misc)
  • Re: Move mailbox process experience
    ... Is it possible to start an Exchange 2000 store on an Exchange 2003 server? ... Best bet is to move the users mailboxes to the new stores. ... renaming the new servers to match, holding your breath while the store gets ...
    (microsoft.public.exchange.setup)
  • Re: Exchange 2003 WAN - Design/Sizing Question
    ... you'll want to ensure that your servers in the core site are ... >> Looking for anyone's input on a proposed Exchange 2003 design. ... >> The WAN is currently limited to 24Mb by its slowest link to an MPLS ... >> mailboxes over a WAN connection. ...
    (microsoft.public.exchange.design)
  • Re: QUICK 5.5 TO 2003 UPGRADE?
    ... MVP - Exchange ... Exchange servers however this domain has a trust with two other legacy ... child domain and one of those two servers handle public folders. ... orphaned Exchange mailboxes would there be anyway to outright remove that ...
    (microsoft.public.exchange.admin)
  • RE: Move Exch. 2000 Ent. to New Hardware
    ... We have Exchange 2000 running on a server and want to install it ... Would I need to move any mailboxes since my info. stores are on a SAN? ...
    (microsoft.public.exchange2000.setup.installation)