Re: Move mailbox process experience
- From: "Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx>
- Date: Tue, 9 Aug 2005 16:08:18 -0400
Fastest way would have been to upgrade in place. More complex and more risk
as well.
Why do you calculate that it would take several weeks to move that many
mailboxes? What are you basing your calculations on?
Is it possible to start an Exchange 2000 store on an Exchange 2003 server?
Supposed to be. Is it a good idea? I don't think so because of the
complexity, risk etc that goes along with that.
Best bet is to move the users mailboxes to the new stores. If you're not
getting the speed you need, let us know what you're basing the calculations
on, the timelines you have to work with (what work times you can move the
mailboxes), etc. In the end, it shouldn't take a whole lot longer than
shutting down the existing server, moving the db's to the new servers,
renaming the new servers to match, holding your breath while the store gets
converted (how long does that take in your environment exactly?) and then
verifying that it works. No matter what, the bulk of your time is spent
moving the data. The rest is fairly small amounts of data and goes quickly.
If you're not able to achieve the speeds you need, it may be you need to
rethink the way you plan to move the mailboxes. Be creative with schedules
and destinations etc. It can be very fast.
Al
"BvdB" <BvdB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:427C6BA1-D3E1-4AB7-8723-C4F660D16488@xxxxxxxxxxxxxxxx
>
>
> "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
.
- Follow-Ups:
- Re: Move mailbox process experience
- From: Mark Arnold [MVP]
- Re: Move mailbox process experience
- References:
- Move mailbox process experience
- From: BvdB
- Re: Move mailbox process experience
- From: Mark Arnold [MVP]
- Re: Move mailbox process experience
- From: BvdB
- Re: Move mailbox process experience
- From: Mark Arnold [MVP]
- Re: Move mailbox process experience
- From: BvdB
- Move mailbox process experience
- Prev by Date: Re: How many?
- Next by Date: Re: How many?
- Previous by thread: Re: Move mailbox process experience
- Next by thread: Re: Move mailbox process experience
- Index(es):
Relevant Pages
|
