Hi,
We outgrew our e2k server so I decided to replace it with a faster server with more storage.
Server1 is called rugrat and and is a Compaq Proliant 1850R Dual Pentium II-450 with 1 GB of ram and a SCSI Raid. Connected by switched gigabit to a backbone.
Server 2 is called MsKitty and is a DL380 Dual PIII-733 with 1.2GB ram (soon to be 2.2 GB) and has SATA Raid and switched Gigabit connected to the same hub.
I managed to get the second server installed, mailboxes moved and smtp traffic routed to the new server.
However, I'm stuck on the public folder migration.
I did manage to create a replica, but I don't think it's replicating.
I have the replication properties set to Always Run, Urgent for all folders.
The public folder store is set to always run, with 5 minute intervals for replication and no message size limit.
On my destination server it says "local Modified" for all folders. Does this mean it is not in synch?
On my source server some folders say "in synch" while others say "local Modified".
My desired solution is:
1. Clarify my understanding of the replication status of my two servers.
2. Assist in making replication work so that I can decommission my old Exchange server.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Ugggh.... so many gains so little satisfaction with Exchange.
Any ideas on how to fish that data out quickly?
I thought about taking the store offline on the old server and seeing what I could see.
What is the simplest and most efficient way to get the data into a PST? My workstation is on G/bit switched to the backbone where the servers are.
Thanks,
Pub1.edb on source is 3.1 GB and on target is 2.8GB.
We have 4 distinct email users and 4 people who use a common "shop" account.
We use public folders as a workflow management and job data storage tool.
I have no idea how many folders we actually have but it's well over 2000
Typically one per job and then one per quarter per order class.
We keep certain types for 1 year and then others are kept indefinately at present.
It's basically an online filing cabinet and very handy for fetching 18 month old order data for customers. Esp. when it comes to email for such and such.
I'd guess at some level replication has to be occurring for the file sizes to be what they are. Maybe one day it will catch up. It's just annoying that Exchange doesn't have a "MOVE PUBLIC FOLDER" function.
The reason it doesn't have a "move public folder" function is due to replication. Exchange is designed as a multi server environment. Public folder data is held on the same server as the the mailboxes (unless configured differently) so you could end up with the same data on mutiple machines.
I have found that once replication is up and running it keeps itself up to date pretty well.
If you only have a 3.1gb pub.edb then that is 2 pst files. I have moved a lot more using the pst file method when I have been doing migrations against the clock. It is a bit of a fad to do it, but does work. Simply move the data out of the public folder in to a new pst file.
However if you are only 300mb different then it is just a matter of finding which folders haven't replicated - use the item count to compare the numbers and see which it is.
Simon.
Business Accounts
Answer for Membership
by: SembeePosted on 2004-12-21 at 08:21:49ID: 12876890
Local modified does mean that it isn't in sync. But it might be. The only way to know is to use the item count of both servers. If it is the same then you can be pretty sure that it is in sync.
When you setup the replica you need to have both servers listed in the tab.
However...
Exchange 2000 PF replication is notorious for being flaky. I have seen it take in excess of 3 weeks before it starts replicating fully. If you cannot wait that long then you will have to do it the slow way - export to pst files and move by hand.
Replication has been improved somewhat in Exchange 2003, in that there is a way to force replication to occur immediately.
Simon.