HI, We have a custom SharePoint portal built out of WSS 3.0 A similar instance has be set up on a different server (and a different network all together). We achieved this by export and import stsadm operations. Currently these two instances are in sync. However, developments are expected to take place on each server and it is needed that we maintain a sync. I wish to know the procedure to ensure that both the above instances are in sync at any point of time. Any pointers in this regard will be helpful and highly appreciated. Thanks in advance Mahesh B

Hi, I don't think there is a good way to do this. Why do you maintain two same sharepoint portal? If you just want to give the different addresses for different users, you can use AAM to realize it. Hope it is helpful!Seven

Thank You Seven for your response. The reason we have it on two different servers (with different networks) is that the custom portal is deployed for two different clients. Eg: Like one product sold for two different people. Scenario: Individual clients make their own developments/customizations/updates based on their needs. If these updates have to be migrated to other client - what's the best way to do? For now - we want to make a one way migration. That is, Client A makes any updates necessary and these will be migrated to Client B. There wouldn't be any changes made on Client B end. Let me elaborate it more: Consider a case where a no.of documents need to be updated. If these changes are made on Client A instance, then how do we move it to Client B. (without breaking any hyperlinks/references made to other documents within the portal) Any thoughts? Thanks again Mahesh B

Hi, For this need, sharepoint cannot support it even for two sites in a same farm. For the different networks, what you can sychronize are features through creating a new feature providing functions you need. Hope it is helpful!Seven