Announcement

Collapse
No announcement yet.

Exchange 2k3 Public folders won't replicate to second server

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

  • Exchange 2k3 Public folders won't replicate to second server

    I’m trying to move public folders off of an Exchange server 2003 “A” and onto another Exchange server 2003 “B”. For the last week I tried various ways to replicate the data without success but I started over this week. Two days ago I set each public folder to replicate content to public stores on both server A and B. Then yesterday I set all public folders to “move All Replicas” to server B.
    I enabled diagnostic logging for this and both days there a lot of 0x20 Status Request. Since setting replica to only server B there been at most a dozen 0x8 Backfill Request sent for a few folders.
    On server B the “public folders” section is empty but the Public Folder Instance is still full. In “Replication status” on server B about a third of the folders are listed as “In Sync”, another third as “Local modified”, and the remaining third as “Both Modified”. I can't delete the public folder store or uninstall Exchange from Server A until the public folder content is moved.
    I’m getting frustrated with this as I need server A for other purposes by the end of the week. I looked at other form posted on this issue but none have helped.
    Any ideas? I appreciate any help.

  • #2
    Re: Exchange 2k3 Public folders won't replicate to second server

    Ignore the status. It cannot be relied upon. The only reliable way of knowing if data has been replicated is item count.

    What does message tracking show? The most common cause of replication problems is a smart host on the SMTP virtual server. The second most common problem is antivirus or antispam quarantining the content. Message tracking will show if that is happening.

    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


    • #3
      Re: Exchange 2k3 Public folders won't replicate to second server

      Thanks for your help, so far no luck.

      Neither of the servers is currently using any antivirus software, there is anti-spam software (GFI) but it should only be intercepting messages leaving our network. Neither server currently have a smart host set.

      In message tracking from serverA, There a lot of Status Request messages from server A. There only about a dozen Folder content from server B and Backfill Request messages from server A.

      Backfill Request message tracking starts with “smtp store driver: Message submitted from store” and ends at “message transferred to ServerB.domain.com through smtp”

      Folder content message tracking starts with “SMTP Message submitted to Advanced Queuing” and ends with”SMTP store driver: message delivered locally to store to [email protected]”.

      Comment


      • #4
        Re: Exchange 2k3 Public folders won't replicate to second server

        If the messages are being delivered in to the store, then the content is going across. If the last message is the delivered and you are not seeing an NDR being generated then the data is going across. Have you tried to send the hierarchy across?

        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


        • #5
          Re: Exchange 2k3 Public folders won't replicate to second server

          Are you doing this for the purpose of replacing Server A with Server B?

          Comment


          • #6
            Re: Exchange 2k3 Public folders won't replicate to second server

            Joeqwerty, yes I'm trying to replace server A with Server B. I'm unable to uninstall exchange without removing the public folders first, and I can't remove the public folder until this issue is resolved.

            Sembee, Does it matter which server I initiate the synchronize hierarchy on? I’d assume I should be running the command from serverB as the status request seems to travel from server it was initiated on. When I do this one Status Request message is generated, in tracking it seems to be recieived..

            However for the sake of testing I tried running Synchronize hierarchy from ServerA. From here a few status request and a backfill request message are generated and each tracking fails to be delivered. SMTP: Advanced Queue Failed to deliver message. Is this irrelevant since I’m trying to move folders to ServerB or is there a way for me to find out more details on why message failed to deliver?

            Comment


            • #7
              Re: Exchange 2k3 Public folders won't replicate to second server

              Personally I find the following procedure the easiest, fastest, and best method for replacing one Exchange server with another when you are trying to move Exchange to new hardware. I'm assuming that's why you're doing this and not for some other reason. This method take all of 10 minutes, excluding the time needed to build the new server and the time needed to backup and restore or move the databases. I've found that shutting down the exchange services on the original server and moving the database files to a temporary network share works the best.

              http://technet.microsoft.com/en-us/l...EXCHG.65).aspx
              Last edited by joeqwerty; 12th September 2008, 15:06.

              Comment


              • #8
                Re: Exchange 2k3 Public folders won't replicate to second server

                Originally posted by joeqwerty View Post
                Personally I find the following procedure the easiest, fastest, and best method for replacing one Exchange server with another when you are trying to move Exchange to new hardware. I'm assuming that's why you're doing this and not for some other reason. This method take all of 10 minutes, excluding the time needed to build the new server and the time needed to backup and restore or move the databases. I've found that shutting down the exchange services on the original server and moving the database files to a temporary network share works the best.

                http://technet.microsoft.com/en-us/l...EXCHG.65).aspx
                Unfortunately I think I'm too far along to do this as all the mailboxes are already moved and all other settings changed to the new server. I think new public folder content has also been stored on the new server so I'd have to move everything back and hope I don't run into this same issue. Everything is setup and ready except for the public folders remaining on the old server.

                I'm thinking about recreating the public folders and manually moving the content over to the new copies which should be created on the new server (Server B). My main concern though is will I run into issues with the system folders if they remain on the older server.

                Comment

                Working...
                X