Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1707
  • Last Modified:

Exchange Public folders Tombstones are evil!!

I have a bit of a problem.
We are performing a domain migration.  And it all went a big wrong.
We are using th Quest Migration tools to Migrate our 160Gb of Public folder data.
On the day of the migration we noticed that some of the folders had not been synced accross.  So we decided to stop and figure out why not all of our 30,000 Public folders were being synced. and it turns out that becsue we had used some live folders during the test phase they were now not syncing.  At this point we did something we have beenregretting ever since.  We all the public folders in the Target domain.
Now we cant sync because the Server cant create items with the same Unique ID.  We have to wait untill the Tombstone clears.  we have already changed the following key to start aging the Tombstones over 1 day old.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersPublic\Replication Folder Tombstone Age Limit
Trouble is the Server can only clear 500 a day.
We have 20 or so Public folders store globally.
We have 30,000 folders. At this rate it will take nearly 3 months to clear.
I need to find a way of doing this faster.

Any Ideas?
Any help at all will be most welcome.
0
Adam_james_Stockton
Asked:
Adam_james_Stockton
  • 4
  • 3
1 Solution
 
patelbg2001Commented:
I do have a solution for this provided by Quest, it for EMW, I guess it may work with MME if thats what your using..  I'll dig it out and post when I get back to my flat tonight... sorry it's on a pst.

In a nut shell... if I remember correctly to re-sync folders that were previously sync'd ..... it a process of the deleting the Target folder and creating a new one, and moving the source folder into and out the
Aelita EMW Recycle Bin.
0
 
Adam_james_StocktonAuthor Commented:
Thanks,
It would be good to shee the solution you were given..
We have the problem that the ID;'s of all the folders exist already in both domains,  And MME tried to create items folders and items in the traget domain with the same ID.
However, the target domain already has used these ID's and they exist as tombstones now.
0
 
patelbg2001Commented:
lets have alook to see if the EMW solution eases your issue... if not.... the fastest thing would be is to create a new folder tree and migrate into that.... EMW and MME are pretty similar but that cannot be said for Exchange 5.5 and 2003....

what have Quests eastern european support team come back with???
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
patelbg2001Commented:
also have you put this on the Quest Exchange forum..... alot of us Quest consultants check that forum
0
 
Adam_james_StocktonAuthor Commented:
To be fair I have not been dealing with Quest.
The Migration Project was handled by different people.
They have not got a solution, so i have started looking around for my self.
The following Technote is a fairly Resonable description about what was done and the issues we are now having.
http://qlist1.quest.com/read/attachment/8986/1/htmlversion.html

Currently I suspect I am going to have to Make a new copy of the source Tree and then delete the original.
Obvious problems with this are Mail Enabled Public folders, and Time taken to actually copy 30,000 Folders.
I have about 500 Mail Enabled Public folders.  my concern is that that would take more than a weekend ( the longest time I can keep the users out of email).

With the New Copy at Least I would get new Unique ID's and therefore be able to Sync using the tools as originally planned.
But thanks for any help you can give.
0
 
patelbg2001Commented:
Apologies for the delay

This is the process.


Stop the PF sync.
Delete the troubled folders in the target.
Take a backup of the troubled folders in source (PST)
Move the troubled folders (in source) to emw recycle bin
Delete sync job relating to those folders
Do pf sync.
Stop pf sync.
Recreate troubled folders in the target
Move the folders (in source) out of emw recycle bin
Create sync job relating to those folders

Job done

The best quest documentation I can find on it is;
ExchangeMigrationWizard_3.6_Resynchronization_112904.pdf
Exchange 2003 Public Folder Tombstone Cleanup

 
0
 
Adam_james_StocktonAuthor Commented:
Thanks u have been a big help
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now