MOSS 2007Windows 2008SQL 2008Clustering is not an optionData Mirroring is not an optionWe will soon have 2 MOSS 2007 environments in 2 different geographical locations.Locale1: U.S.Locale2: EMEALocale1 needs to store and retain their data locally on the U.S. server.Locale2 needs to store and retain their data locally on the EMEA server.Locale1 needs to access/share/modify data on the EMEA server.Locale2 needs to access/share/modify data on the U.S. server.Preferred:Locale1 and Locale2 Depts. use the same Site(s) in order to not end up with duplicate Sites, workspaces, etc...Fairly new to MOSS, and would greatly appreciate some direction and options on this scenario. General links to whitepapers are a bit above my head at the moment.M

Nothing out of the box, but there are several third party solutions. Google "sharepoint synchronization". Two that I looked at a while back for a client were www.colligo.com and www.avepoint.com. Each product out there has a different feature set. Thinks to think about... do you need to replicate everything, just select sites or selected libraries and how "real time" must it be? How do you want to deal with "collisions" when two users update the same item before the resync occurs.Mike Smith TechTrainingNotes.blogspot.com

Thank you,Syncronizing data over this link was shot down from above.The end goal is to have Locale1's data be accessible to Locale2 users, but leave it on the Locale1 server, etc..., etc...M

> The end goal is to have Locale1's data be accessible to Locale2 users, but leave it on the Locale1 server, etc..., etc...They can just login into the remote server. Might be slow, but no different than accessing a web server on the otherside of the "pond". You might also consider some kind of remote desk top type of access. or am I misunderstanding your question?Mike Smith TechTrainingNotes.blogspot.com

Although a very good idea, not an acceptible resolution according to the V.P.It must all be in the Sharepoint interface. If Locale1 has a site called Marketing, that must be accessible from both sides of the pond, but if the data is local to EMEA, then that data stays in the EMEA database, etc..., etc...ESP