CODEWITHSUNDEEP
perforce
Bart Vanherck
Bart Vanherck

Reputation: 76

Putting changelists on another perforce machine

I did a migration of the perforce server. Because there are many depots and many data and because our department does not want that the server is down for a day, I did the following:

Step 2 : Stop the 'old' perforce server on machine A Step 1 : Copy all data from machine A to machine B Step 2 : Start again the 'old' server Setp 3 : Do the complete migration and start the new server at machine B

Now the problem is that in the meanwile, there are several changelists submitted to machine A.

Is there an easy way to copy the changes to machine B ? Note that I have a checkpoint, so the metadata is not the problem.

I know that on version controls like git it is easy with patches. Is such a thing also possible in perforce in an easy way?

Upvotes: 0

Views: 95

Answers (2)

randy-wandisco
randy-wandisco

Reputation: 3659

Did you truncate your journal when you did the first migration? If so, you can probably replay the latest production journal and then rsync/robocopy the archive content (files in the depots). That'll let you catch up.

I assume this is a one-off activity?

You should probably check in with Perforce tech support just to make sure you're not overlooking anything.

Upvotes: 2

Raghuveer
Raghuveer

Reputation: 1493

You may want to look at p4 pull and p4 replicate command given by perforce.

P4 Pull and P4 Replicate are the 2 commands given for purpose like these. I am assuming that your p4 server is p4d 2010.2 or above for these commands.

Also, I would recommend you reading Perforce's knowledge base for their article on Offline check pointing. This article is not a direct solution to your problem, but it gives you insight of how you may tackle your situation.

Hope this helps.

Upvotes: 3

Related Questions