Announcement

Collapse
No announcement yet.

Moving an Exchange 2003 database to a new Exchange 2003 server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Moving an Exchange 2003 database to a new Exchange 2003 server

    Has anyone followed this document with success on moving an exchange 2003 database to another 2003 server within the same domain? http://support.microsoft.com/kb/555603

    I need to move our existing exchange databases to another win2k3 standard member server and really do not want to go through the hassle of replicating public folders because we have soo many of them.

    thanks
    Jamie

  • #2
    Re: Moving an Exchange 2003 database to a new Exchange 2003 server

    Is it the case that you simply want to move Exchange (including the databases) from one server to a new server? If so, what is your intention for the current server, does it provide anything other than Exchange?

    Comment


    • #3
      Re: Moving an Exchange 2003 database to a new Exchange 2003 server

      Yes !

      The existing server is going to get wiped and reloaded and used for something else.

      Comment


      • #4
        Re: Moving an Exchange 2003 database to a new Exchange 2003 server

        In that case it's must easier and faster to follow this article:

        http://technet.microsoft.com/en-us/l...EXCHG.65).aspx

        If you follow this article to the letter you should be fine. The most time consuming part of this is probably going to be the backup and restore of the actual database files. Note that you can copy the files from one server to the other rather than backing up and restoring them.

        Comment


        • #5
          Re: Moving an Exchange 2003 database to a new Exchange 2003 server

          I would still use the swing method, no matter how many public folders there are. No reason to do anything. Swing is zero risk, zero downtime and does not require manually hacking about to get Exchange to accept the database.
          Even if you have thousands of public folders I would still swing and regularly do so. With the tools that Exchange 2003 SP2 added to ESM it is quite easy to add the replicas to all of the folders at once, or you could use pfmigrate to do that for you.

          You do realise that the 555xxx solutions are community solutions and may not be something that Microsoft recommend?

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment


          • #6
            Re: Moving an Exchange 2003 database to a new Exchange 2003 server

            Yes, but my cioncern is those public folders. Adding replicas and setting them to "urgent" is fine but i dont have any control on how quickly the msgs move. i sometimes have to wait while they are being processed, and then whatever it skips, i see all the backfill logs appear of whatever it missed.

            that's why i thought - well, if i simply copy the databases to the other server and then remount them , i technically shouldnt have a problem. but (lol) i say "technically" quite loosely

            Comment


            • #7
              Re: Moving an Exchange 2003 database to a new Exchange 2003 server

              True - public folder replication does have a mind of its own. That is why I set the replication up a week before I plan to move the mailboxes.
              Exchange 2003 SP2 also introduced the "Send Content Now" command, which basically forces Exchange to send the entire contents of a folder across immediately.

              Nothing you have said so far would persuade me to do anything other than a swing migration. I certainly wouldn't do a backup/restore and the fiddling about that is required when I can let Exchange do all the work for me if I am patient.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: Moving an Exchange 2003 database to a new Exchange 2003 server

                You know the more I read your post and thought about it, the more I would agree with you. The last time I went through moving my public folders, my delieveryTable kept building and building and just hosed up my exch box. I found a microsoft hotfix for this problem (http://support.microsoft.com/kb/919417/en-us) which really helped me in replicating the public folder emails. I think i'll stick with the swing migration on this one .. it is a lot safer and much easier to do.

                Thanks for your input

                Jamie

                Comment


                • #9
                  Re: Moving an Exchange 2003 database to a new Exchange 2003 server

                  I certainly hate to contradict our esteemed colleague Simon, but I have used the MS method for moving Exchange to a new server with the same name and it works flawlessly and takes all of 15 minutes (except for the actual moving of the database files). IMHO, this is the quickest, least prone to problem way to go about what you are trying to accomplish.

                  Comment

                  Working...
                  X