TheGeezer2010
asked on
Exchange 2010 Public Folder HA
Have set up Public Folder replication on Exchange 2010 (does not work out of the box, you need to set HomeMDB attribute for the SA on the Public Folder Database first), and the content is now updating so in theory have replicas on different databases. Tested this by dismounting the database on which the folders are homed, and, using OL 2007, this simply does not work - cannot expand folders.
My understanding is that the reason for this is that the clients are assigned a default PF database. If this DB is available and there is a replica, no problem. If it is available and there exists no replica, it consults its heirarrchy and chooses best referral to an existing replica based on AD site configuration and/or cost assigned to referrals. If the default DB is NOT available, it cannot be consulted for referral to a suitable replica and you get the error described earlier. So is it now simply the case that one cannot achieve true HA for Public Folders - i.e. there is no failover mechanism if the dafault PF db is down ?
Thanks for guidance
My understanding is that the reason for this is that the clients are assigned a default PF database. If this DB is available and there is a replica, no problem. If it is available and there exists no replica, it consults its heirarrchy and chooses best referral to an existing replica based on AD site configuration and/or cost assigned to referrals. If the default DB is NOT available, it cannot be consulted for referral to a suitable replica and you get the error described earlier. So is it now simply the case that one cannot achieve true HA for Public Folders - i.e. there is no failover mechanism if the dafault PF db is down ?
Thanks for guidance
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It would have been better to supply a Microsoft URL confirming this statement - HA was removed. However, this set me on a personal investigation and a number of tests which seem to prove this is the case.
Kudos to Akhater for being so quick to respond - it is frustrating to have to wait !!
Kudos to Akhater for being so quick to respond - it is frustrating to have to wait !!
Hi
I'm also looking for a way to achieve HA on Public Folder setup. I’m aware of the way to change the default public folder database setting on the mailbox database. But a bigger problem is that receiving emails in mailenabled public folders is always sent to the PF database that is the msExchOwningPFTree. Normal this is the last created PF DB. If this DB is not available the mails just queuing up. The is no HA mechanism that can send the mails to other PF DBs. Please let me know if there is a workaround.
Regards, Lars Kvorning
I'm also looking for a way to achieve HA on Public Folder setup. I’m aware of the way to change the default public folder database setting on the mailbox database. But a bigger problem is that receiving emails in mailenabled public folders is always sent to the PF database that is the msExchOwningPFTree. Normal this is the last created PF DB. If this DB is not available the mails just queuing up. The is no HA mechanism that can send the mails to other PF DBs. Please let me know if there is a workaround.
Regards, Lars Kvorning
ASKER
It looks as if Microsoft are including an alterntive PF replica option in Exchange 2010 SP1 Rollup 2 due in December !!
Yes so I have read !
thank you for the update, Microsoft took back PF to pre-exchange 2000 with exchange 2010 when they removed anything related to HA from them ....
It is a pain I agree but it is their way of pushing them out of the life-cycle
Regards,