Swapping out a central file to a different path?

[cmr240844]

Here's the situation, there's 2 servers (for now, they are named A and B) that sync up with each other at night in different physical locations. Our main project server (A) is having some issues and won't be up and running at the least 3 more days. Is it possible to reconfigure our local files to link up to server B (possibly pushing updates to it as it has fallen out of sync)? Or is the only way to get this semi up and running to recreate new local files from server B.

So, is there anything we can do, or are we S.O.L. for the next couple days?

[Steve_Stafford]

You need to move the central file to Server B. Just replicating (assuming typical replication process) the file is really creating a local file version of the central (from Server A) on Server B. Once the central is on Server B you can create new local files from it to continue working.

Use Detach from Central to break the project free of Server A, Save the file on Server B which creates a new central file in the process.

[The Monk]

Additionally, you should delete the temp folders at the desktop computers and potentially at the old central file location. We have experienced some interesting processes with Workshared projects. The backup / temp folders can cause unexpected continous connection problems even if the central file has been detacted.

Once you have the new server up and running you will need to go through the same process. It would not hurt to re-establish the cental file as a "central file" in the permanet location as well.