Re: Move mailbox process experience

Tech-Archive recommends: Speed Up your PC by fixing your registry

On Tue, 9 Aug 2005 16:08:18 -0400, "Al Mulnick"
<amulnick_No_SPAM@xxxxxxxxxxx> wrote:

>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.

Thanks Al, yes, and the store pasges itself would only update slowly
over time and as accessed.
>
>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.

Agreed, lots of tiny (22MB) mailboxes wouldn't take long to move and
be available to the users. It would be different if there were a
smaller number of huge databases that knocked out important users for
long periods, but doing mailbox moves for small mailboxes is the best
solution
>
>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.


Do the moves FROM the Exchange 2003 server where they can be
scheduled. Don't select to PUSH the mailboxes from 2000 to 2003.

>
>Al
>
Teamwork!
.

Relevant Pages

  • Re: Exchange 2003 Private Store Corruption
    ... Once you've pulled the faulty RAM, create the new mailbox store and move ... then you can start working on the problem mailboxes. ... have DIMM's installed in pairs in this server? ... Online Diagnostic Utility says "Correctable Memory Threshold Exceeded" ...
    (microsoft.public.exchange.admin)
  • Re: no mailboxs in private foulder
    ... limited experince with exchange. ... Ping the exchange server ... Right click the mailbox store, is the first option "mount store" or is it ... Where are you seeing "Mailboxes and stuff"? ...
    (microsoft.public.exchange.admin)
  • Re: public folders are not all in sync
    ... Exchange 2003 server about the calendar connector. ... then just dismount the public store. ... Network Administrator mailboxes are supposed to be moved. ... I don't have very many folders so I ...
    (microsoft.public.exchange.admin)
  • RE: Suggestions for freeing up mailbox store space plan?
    ... Our current servers don't have enough space to mount another store in the RSG ... exchange srvs do send emails out, but only to domains that dont need Rdns. ... We also have 1 server that runs OWA. ... how you slice it or what mailstore your mailboxes are in. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 Private Store Corruption
    ... I think you're on the right track with creating a new mailbox store. ... Moving mailboxes is one option. ... Online Diagnostic Utility says "Correctable Memory Threshold Exceeded" ... get the server back up and running without the faulty memory installed. ...
    (microsoft.public.exchange.admin)