[Webinar] Streamline your web hosting managementRegister Today

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

exchange 2003 public folder db move

i am in the process of decommissioning an exchange 2003 server.  i have moved the mailboxes, but now i need to move the public folders.

i need a better understanding of the "move all replicas" option.  if i choose this option and it replicates, will users who are pointing to the old public folder store as there default experience an outage?  if so at what point?  (during the move, after the move, or both)

thanks
0
xrpk03y
Asked:
xrpk03y
  • 4
  • 4
1 Solution
 
AkhaterCommented:
no in most of the cases your users will not experience any outage unless we are talking about real big public folders.

the process happens as follows

1. new replicas are added to the pf
2. old references are removed
3. replication is taking place

so, in theory, users are directly pointing to the new PF (which is empty) and will be populated as replication goes. in my experience in most of the cases no one will feel this unless you have a lot of PF (300gb +)
0
 
xrpk03yAuthor Commented:
how are users pointing to the new PF store?  the exchange policy points them to the old one.  i thought it was switched when the old pub folder was deleted...
0
 
AkhaterCommented:
no i mean users trying to access the pf that are being migrated are redirected to the new PF on the new server.

if you want to be on the safe side it is better to

1) add replicas to the new server
2) wait for replication
3) remove replicas on the old server
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
xrpk03yAuthor Commented:
i am not sure if this is answering my question.  does anyone else have some advice?
0
 
AkhaterCommented:
Can you please tell me which part of the question remains unanswered so I can help?
0
 
xrpk03yAuthor Commented:
So you are saying if they are pointing to the old public store and the info is not there they will get it from the new store?  Also, does move all replicas remove the data from the original store or just create a replica copy?

Thanks
0
 
AkhaterCommented:
>>So you are saying if they are pointing to the old public store and the info is not there they will get it from the new store? <<

yes exactly. see when talking about PF you have only one PF hiearchy per enterprise so, no matter to which PF database you are pointing to, you will see all the PF available in the organization. When you select a specific PF the server will redirect you to another server holding a copy/replica of that PF


>> Also, does move all replicas remove the data from the original store or just create a replica copy?<<

move all replicas will REMOVE the data from the original server and this is where problems might happen if you have big public folders.

let me try to explain this

1. Replicas is added to the new PF
2. Reference to the old PF is removed
at this point data replication is not finished yet
3. a user tries to access a PF. no matter to which PF he is pointing to he will be redirected to the NEW PF since it is the only one that has reference to this public folder. and since data replication is not done yet he will see a missing PF

0
 
xrpk03yAuthor Commented:
Thanks for the help!
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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