Re: [p4] Shared depot to multiple servers
Matt Janulewicz <[email protected]> Mon, 19 Mar 2018 11:50:01 -0700
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'Matt Janulewicz'. Having had experience in all three scenarios (remote depots, trying to sync two servers, and just merging two servers together) I'd put a +800 vote on what Sam says. The first two scenarios will inevitably end in disaster. With Perforce's built-in DVCS, merging two servers together is much, much easier than it used to be. Ask some of us old timers about perfmerge some day. Great tool in its day, but murder trying to coordinate merging a couple really large servers with 100's of thousands or millions of changes with TB of data. Anyhoo, once you merge together the servers and pick which one is the master/commit, you could at least roll a p4proxy in one of the buildings. Unless those buildings are pretty close together, and you might ask yourself why a second server has to exist in the first place. I wouldn't go down the commit->edge road unless your buildings/offices are separated by a significant distance or a high latency network. -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/5661-shared-depot-to-multiple-servers _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user