No size shown after pfmigrate of public folders

I used

pfmigrate.wsf /S:SourceServer /T:DestinationServer /A /N:100 /F:C:\Logfile.log

to replicate public folders on the source to the destination server.  The logfile indicates that the folders were added to the replica list. And the replication status on the new server shows these folders to be "In Sync" however the size fo the folders in both the Public Folders directory and the Public Folders Instances is 0 for all folders on the destination server. I am worried that only the hierarchy has been sent and not the content.

I also ran

pfmigrate.wsf /S:SourceServer /T:DestinationServer /R /F:C:\report.log

This log confirmed that there were no folders with out a replica on both servers.

Can some one help me sleep better?

Thanks,
DaveChoiceTechAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
Item count is what I use to confirm whether anything is working correctly. It is more reliable than the "in sync" status.
Message tracking can also help, it will show whether the replication messages are being delivered to the store correctly or not.

Message tracking can also confirm that the messages are being delivered to the right server and aren't being swallowed by anything.

Simon.
DaveChoiceTechAuthor Commented:
Simon,

The item count is also zero on the new server. Is there any way to force the public folders to duplicated on both servers?

Dave



SembeeCommented:
Is this an Exchange 2003 to Exchange 2003 replication, or is there an Exchange 2000 server involved?

If it is pure Exchange 2003 then you can use the send changes now command.
If there is Exchange 2000, then you will have to wait.

Simon.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

DaveChoiceTechAuthor Commented:
I am familiar with "Send Hierarchy" and "Send Content" but I could not find anything like "Send Changes Now"

On "Send Content" I have to go the individiual public folder and specify that content should be sent from source servers to destination servers for the last X days.

What I want is for all the content in the public folders to be sent to the new server. Does this mean I have to go to each public folder ans rund "Send Content"?
SembeeCommented:
The names have been changed between Service Packs and I was quoting from memory.
It is "Resend Changes" in Exchange 2003 SP2. Unfortunately it does mean that you have to do it for each folder.

You don't want to try and set it for every folder anyway - as it floods the link. It is very good at getting content across very quickly, but at the expense of using all available bandwidth.

Simon.
DaveChoiceTechAuthor Commented:
Simon,

I ran "Resend Changes" on one of the folders I want to replicate using a period of the last 10000 days. After 72 hours thier is still no size info for the public folder instance on the new server.

This is very important to me since at some point we intend to remove the original server.

What about using "Move all Replicas"?

Dave
SembeeCommented:
Turn on Message Tracking and see if the messages are actually being sent.
Replication traffic is sent over SMTP and stick out in the message tracking system. If the messages aren't getting there (because they are being blocked or redirected) then you have another problem that you need to resolve.

Simon.
DaveChoiceTechAuthor Commented:
Simon,

I turned on message tracking and found messages indicating that replication messages had been sent but still no content. There are no errors in the event log.

1. Which Services/Categories should I enable higher loggin levels on?

2. A public folder on one server is only visible to users that are logged on to that server. I thought that public folders would be visible on any server in the Routing Group. Is this wrong? We have 2 member servers and one Master in our routing groups. There are no connectors. The two original servers are Exchange 2003 SP1. The new server is SP2

2. We ultimately want move from a 2 Exchange server model to a single Exchange Server. The increase of store size to 75GB in SP2 allows us to do this. Is there any problem with simply using .PST's as a method of moving content between servers?

Thanks,

Dave

SembeeCommented:
Does message tracking on the other server show that the messages have actually been delivered to the store, or that the messages are dropped? You have to look at both ends.

Logging would have to enabled in Exchange, under diagnostics logging. You will want the Transport and replication fields under MSEXCHANGEIS, Public Folders.

In my experience you only see the public folders on the server that you are connected to. While it is supposed to g looking for other servers for the public folders, in practise I find that it doesn't or does so in such a way that it cannot be relied upon for production use.

You could move the public folders using a PST file. You will take a hit in free busy information until everyone has made an update to the calendar to force it to republish.

Simon.
DaveChoiceTechAuthor Commented:
Simon,

I set the logging per your suggestion.

Replication of content between my two original servers works fine.

When I try to replicate content to the new server I get a message like this when I look at the message tracking by specifying Server... OLDSERVER It get,

From: Public Folder Store(OLDSERVER)
To: Public Folder Store(NEWSERVER)
Subject: Folder Content Backfill Response

Under the location OLDSERVER I see a bunch of SMTP messages such as "submitted from store", "started message submission to Advanced Queue" etc. culminating in "Message transferred to NEWSERVER.mydomain.locall"

Under the location NEWSERVER in the same message history I see another bunch of messages including message "Advanced Queue Failed to Deliver Message"  and eventually Non-Delivered Report (NDR) Genertated.

The next message in the message tracking is from postmaster to Administrator. Oddly in the Administrator Email  I get


From:      System Administrator
To:      myaccount@mydomain.local
Sent:      Thursday, April 13, 2006 12:25 PM
Subject:      Undeliverable:NEWSERVER-IS@mydomain.com - Local recipient does not exist - Folder Content Backfill Response
Your message did not reach some or all of the intended recipients.

      Subject:      NEWSERVER-IS@mydomain.com - Local recipient does not exist - Folder Content Backfill Response
      Sent:      4/13/2006 12:25 PM

The following recipient(s) could not be reached:

      myaccount@mydomain.local on 4/13/2006 12:25 PM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            <NEWSERVER.mydomain.local #5.7.1 smtp;550 5.7.1 Unable to relay for  myaccount@mydomain.local>


This is very odd for a number of reasons

1. I understand the relay since mydomain.local is not in our recipient policy but why am I getting an email sent to myaccount@mydomain.local in the first place? NDR's are configured on the default SMTP virtual Servers of both OLDSERVER and NEWSERVER to send a copy of the NDR to administrator@mydomain.com not to myaccount@mydomain.com. Why is there a message being sent to this account?

2. There is a conflict between the the subject line stating "Undeliverable:NEWSERVER-IS@mydomain.com" and the body. What sender is getting the NDR? Is it NEWSERVER@mydomain or NEWSERVER-IS@mydomain.com?

3. What is the account NEWSERVER-IS@mydomain.com? I think it is the email address for the public folder store on the new server. When I search message tracking using Sender NEWSERVER-IS@mydomain.com I get a list of message with sender "Public Folder Store (NEWSERVER)

Finally, when I specify message tracking with Server... NEWSERVER I see the same "Advanced Queue Failed to Deliver Message" as described above from sender OLDSERVER-IS@mydomain.com followed by the NDR message from postmaster@my-domain.com

To summarize it appears that the OLDSERVER submits the message to the NEWSERVER via SMTP. On the flip side on the NEWSERVER we get "Advance Queue Failed to Deliver Message". I'm guessing that this means that the public folder on the NEWSERVER is not accepting the message.

With this in mind I checked the permissions on the public folders on both servers and verified that they are identical.

I have to admit I am more confused then ever.

Thanks for any advice you can offer.



DaveChoiceTechAuthor Commented:
Simon,

On other tid bit of information. I looked in the queues on both servers and there was nothing in the SMTP failed message retry queue. I'm a bit surprised by this since if the message to public folder at NEWSERVER-IS@mydomain.com is not being delivered I would have thought it would appear in the retry queue on OLDSERVER.

Dave
SembeeCommented:
Most of the messages and behaviour you are seeing is normal - except the NDRs. Public Folder replication content is special, it goes over the SMTP stack but that is about where the similarity with regular emails stop. You cannot think of them as regular emails.

I would suggest that you take a look at this article on the KB: http://support.microsoft.com/default.aspx?kbid=842273
It goes over troubleshooting the replication process.

Simon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DaveChoiceTechAuthor Commented:
Simon,

The link you gave me from Microsoft helped me realize that Exchange wasn't the issue. Turns out the problem was caused by a 3'rd party spam filtering application. When I disabled this app's services public folder replication ran without problem.

Thanks for you help

Dave

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.