pshaduli
asked on
Public Folder issue in Exchange 2007
Dear Team,
We have an issue with our Public Folder replication in Exchange 2007. we have two servers clustered (CCR), NodeA and NodeB. The issue is, public folder is not replicating to NodeB. Status shows as Failed in both NodeA and NodeB. So if NodeA is down, Exchange and Balckberry server will not work even if we changed the ownership to NodeB. when i right click on the storage group i get the option Update storage Group. Please let me know whether it will work or how to solve the issue.
Thanks
We have an issue with our Public Folder replication in Exchange 2007. we have two servers clustered (CCR), NodeA and NodeB. The issue is, public folder is not replicating to NodeB. Status shows as Failed in both NodeA and NodeB. So if NodeA is down, Exchange and Balckberry server will not work even if we changed the ownership to NodeB. when i right click on the storage group i get the option Update storage Group. Please let me know whether it will work or how to solve the issue.
Thanks
Depending on the size of the database and your network speed, it might take a while to Reseed because it basically copies the whole active database to the target and then copies the log files over...
ASKER
Thanks MegaNuk3.
We have other two storage groups for mailboxes and both are showing Healthy. Only PF storage group is showing failed. The PF database size is 63 MB.
We have other two storage groups for mailboxes and both are showing Healthy. Only PF storage group is showing failed. The PF database size is 63 MB.
OK, do the Reseed as per above, it shouldn't take long at all if your DB is only 63mb like you say...
ASKER
Thanks MegaNuk3.
Should we need to take the backup of the PF or can we directly do the above procedure.
Also can we do it at any time or better in the less traffic time.
Should we need to take the backup of the PF or can we directly do the above procedure.
Also can we do it at any time or better in the less traffic time.
What do you keep in it? Not much by the sounds of things.
You can do the above procedure now because reseeding such a small database will have minimal effect and should be really quick. I wouldn't worry about a backup of it, but you can if you want because the backup should be really quick too.
You can do the above procedure now because reseeding such a small database will have minimal effect and should be really quick. I wouldn't worry about a backup of it, but you can if you want because the backup should be really quick too.
ASKER
Thanks MegaNuk3.
we Suspended and Resumed the PF storage group in NodeB but still the status is Failed.
We noticed now it shows "Loading data for server in SCR..Client access" in status bar of NodeA and NodeB. What it means?..is it normal or do we need to do any action?.
we Suspended and Resumed the PF storage group in NodeB but still the status is Failed.
We noticed now it shows "Loading data for server in SCR..Client access" in status bar of NodeA and NodeB. What it means?..is it normal or do we need to do any action?.
Do you have SCR setup? Is it setup for the PF database/SG?
ASKER
Yes. SCR is in remote site. This is for our two storage groups and for PF storage group also. The storage groups are replicating well and the PF is also replicating to SCR. But the logs are not terminated for PF in SCR since the issue with our CCR2 PF replication.
Do
Get-storageGroupCopyStatus |fl
And look at the PF SG
Verify that only the CCR target is the one that is out of date
Get-storageGroupCopyStatus
And look at the PF SG
Verify that only the CCR target is the one that is out of date
Also do get-storagegroupcopystatus -standbymachine <SCRTargetServer> |fl
To verify SCR is working properly for the PF database
To verify SCR is working properly for the PF database
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks for the points, did the Reseed work for you?
You can try Suspend then Resume, if that fails then do the Update with "Delete Existing Files" and that will Reseed the destination