Well we did that...but there's no option for default public folder...both systems are
Exchange 2000...
-----Original Message-----
From: John Matteson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 09, 2003 2:41 PM
To: Exchange Discussions
Subject: RE: public folder replicas and redundancy
Check the properties of the storage group and see where the default public folder is
located.
John Matteson
Geac Corporate ISS
(404) 239 - 2981
Atlanta, Georgia, USA.
-----Original Message-----
From: Joe Berthiaume [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 09, 2003 12:01 PM
To: Exchange Discussions
Subject: public folder replicas and redundancy
2 Exchange servers. Exchange 2000 sp3, Windows 2000 SP3.
Started out with one Exchange server, ServerA. ServerA contains a complete copy of the
public store as well as the mailbox store. ServerB was brought online a short time ago
because ServerA is running low on disk space and horsepower, so we’re hoping to move
to ServerB.
Using System Manager I configured all our public folders to replicate to ServerB. I
thought that this would mean that ServerB would then carry the load of public folder
requests, should the public store on ServerA not be available. This however doesn’t
appear to be the case. If I dismount the public store on ServerA, and then try to
access the public folders, I get an angry “unable to display the folder
(ServerA).”
Does ServerA need to be turned off altogether for B to answer requests for the public
folders? Or is there just something I missed somewhere in setting this up. I know in
Exchange 5.5 there was the concept of folder “homing” but that’s gone now
isn’t it? All I did was use ESM to go to the top level public folders, set up the
replication, and then propagated it down. The pub store size on ServerB is indeed
large, suggesting that all the data is there…but it’s just not answering the
bell…
Thanks I advance.
.+--xm
,)r(ື \檆b=!6
0
&zǚ1r,:.˛
m隊[hy\z[,)rɄZ Zvh'+-i٢2 G(
.rzrmyzrŞvi
.+--xm ,)r( \ـb! 0
&ȭzǚr:.˛m隊[hy\z[,)rZZvh+-i٢2G(
