Re: [p4] Journal restore on server after obliterating some depots

Posted on behalf of forum user 'Matt Janulewicz'.

Replaying journal A into B after B experiences some obliterates would most
certainly cause havoc. Very sketchy. Would not recommend.

I can think of two ways to do this off the top of my head.

1. Make System B a fully-populated read-only replica of System A. This will
update it in real time. Switchover is then either a case of a DNS change and
decommission System A at the same time, or point people to the new Master B
(change their local P4PORT.) We swap servers in and out of our environment all
the time with this method as it minimizes downtime (usually less than a minute,
you essentially have to just shut down both servers, then change the
'mode' of your new master and fire it up again.)

2. Use Perforce's built in distributed functionality to clone then push the
depots you need from A to B, then switch over to B one day. I use this often to
absorb rogue p4 servers into our master server. You don't have to deal with
journals and whatnot this way and can build out a new server without
obliterating anything.

I'm personally averse to obliterating unless it's really, really
necessary. In scenario 1 I'd still leave everything around but just hide it
with the protections table. That's your history in there, no matter how
inane, and you'll kick yourself if someone needs that stuff from backup five
years from now.

It goes without saying, but we all say it anyway, be sure to make and fully test
a backup of System A before you do anything, with 'forever' retention
...



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5720-journal-restore-on-server-after-obliterating-some-depots
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user