How can i remove a backfill response for a public folder in Ex2k7? I had tried replicating some public folders between sites, however i eventually found that it would be easier to post the messages (large applications with static data) to each individual MBX server at the different sites. I set the public folder replication schedule to "never" and deleted the messages from the queue. Within 12 to 15 hours though, the backfill responses return, and with them are copies of the large applications stuck in the queues again.Thanks in advance!

Remove the replica? Those backfill requests will continue until Exchange knows the folders are syncronized.

i set the replication to "never". what's the point of setting it that way if it's still going to try and synchronize? the replica i removed is the one that was queuing but never made it to the remote site. that's why i ended up posting the files locally to each mbx instead of replicating from one site.

Backfill request is triggered by normal replication or status messages Status message is sent from one store to other stores which have the replica of same public folder, if changes are equally matched on the receiving stores, no action is taken. But if there’re missing change being found, receiving store will send the backfill request There’re three circumstances that will make a status message to be generated and send: if there’s a new store just being mounted, or a new store being added to the replica list of that folder (Obviously not suit for you), or the old store being deleted from the replica list. That changed store will send the status request to another store, and then the status messages will occur You said “the replica i removed”, so, the backfill is triggered by status message if needed the replica you removed has the content that other stores don’t have. You need to ensure that the other replicas have all latest content Please see the “Sequence of events when you remove a replica from a public folder store” section in Backfill Requests and Backfill Messages

You will have either manually delete those messages or let it time out Backfilling occurs when a public folder database determines that it has not received all the updates for a replicated folder (or for the hierarchy) and must therefore retrieve the missing updates from another public folder database. To streamline the backfill process, Exchange 2007 stores information about missing updates in the backfill array. The following events may alert a public folder database to missing updates that need to be backfilled: The status information in an incoming replication message indicates that the replica on the public folder database that sent the message has updates that are missing on the receiving database. The receiving database identifies the missing change numbers and stores them in its backfill array. A public folder database starts for the first time. The new database sends status requests to get information about the other databases in the hierarchy. After the corresponding status messages arrive, the database populates its Replication State Table and, if necessary, the backfill array. The backfill array may contain entries for both the hierarchy and for any content replicas that the database must host. An incoming hierarchy message indicates that a new content replica is to be placed in the public folder database. The new database sends status requests to get information about content that might be available for this replica in the other databases in the hierarchy. After the corresponding status messages arrive, the database populates the Replication State Table and, if necessary, the backfill array. The backfill array stores this information for a specified length of time (called the backfill time-out ). If the missing updates arrive in subsequent replication messages during this time, they are removed from the backfill array. The following table lists the default backfill time-out values, which depend on where the missing updates exist and whether they were previously requested. Default time-outs used for backfill requests Type of request Content exists on a database in the local Active Directory site Content exists on a database in a remote Active Directory site Initial backfill 6 hours 12 hours First backfill retry 12 hours 24 hours Subsequent backfill retries 24 hours 48 hours If the backfill time-out expires, and the updates are still missing, Exchange creates one or more backfill requests and determines which servers to use as backfill sources. Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

i set the replication to "never". what's the point of setting it that way if it's still going to try and synchronize? the replica i removed is the one that was queuing but never made it to the remote site. that's why i ended up posting the files locally to each mbx instead of replicating from one site. So where are the backfill requests queuing now? On which server?If you connect to a server that has a replica, does it also show the replica you removed?

i wasn't clear before when i said i deleted a replica. what i meant to say was that i deleted the message in the queue that contained the replica's message/data. since the data was already on the other servers (by me logging into a mailbox homed on each mbx server and uploading the data directly to the local public store) it was no longer necessary to use replication. anyway, it seems to have cleared up for now. i'm going to give another 72 hours or so before i declare victory.