headers
Siddesh Bg | 2 Mar 2009 09:57
Picon
Favicon

[p4] Moving a Perforce server contents to an another existing server

Hi,
We need to move a Perforce server contents in location 'A' to another Perforce server in location 'B', both
are identical in architecture & text file formats.
Location 'B' server is currently fully functional with many depots. 
Please help me with the procedure/scripts to move location 'A' depots along with it's history (database)
to location 'B' server.

In "Perforce Admin guide" document, only procedure to 'move a p4 server to new machine' is explained. Is
there any link which explains "migrating a p4 server to another functional p4 server"?

Thanks,
Siddesh

      
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 4 comments |
headers
Stephen Vance | 2 Mar 2009 10:10

Re: [p4] Moving a Perforce server contents to an another existing server

This can be a complicated procedure. Please contact Perforce Support for 
assistance with this. It will require some additional tools that they 
typically only give out on a support request.

Steve

Siddesh Bg wrote:
> Hi,
> We need to move a Perforce server contents in location 'A' to another Perforce server in location 'B', both
are identical in architecture & text file formats.
> Location 'B' server is currently fully functional with many depots. 
> Please help me with the procedure/scripts to move location 'A' depots along with it's history (database)
to location 'B' server.
>
> In "Perforce Admin guide" document, only procedure to 'move a p4 server to new machine' is explained. Is
there any link which explains "migrating a p4 server to another functional p4 server"?
>
> Thanks,
> Siddesh
>
>
>
>       
> _______________________________________________
> perforce-user mailing list  -  perforce-user <at> perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>   

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
M | 2 Mar 2009 17:05
Picon
Favicon

Re: [p4] Moving a Perforce server contents to an another existing server

It the same procedure. It's quite simple.

The only compliction will be your license file. You'll need to contact
Perforce and explain the situation, and have your licenses from server A
license transferred to the license file on server B.

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Siddesh Bg
Sent: Monday, March 02, 2009 12:58 AM
To: perforce-user <at> perforce.com
Cc: siddesh.gurusiddappa <at> rsa.com
Subject: [p4] Moving a Perforce server contents to an another existing
server

Hi,
We need to move a Perforce server contents in location 'A' to another
Perforce server in location 'B', both are identical in architecture &
text file formats. Location 'B' server is currently fully functional
with many depots. 
Please help me with the procedure/scripts to move location 'A' depots
along with it's history (database) to location 'B' server.

In "Perforce Admin guide" document, only procedure to 'move a p4 server
to new machine' is explained. Is there any link which explains
"migrating a p4 server to another functional p4 server"?

Thanks,
Siddesh
(Continue reading)

Permalink | Reply | 2 comments |
headers
Stephen Vance | 2 Mar 2009 17:22

Re: [p4] Moving a Perforce server contents to an another existing server

If he just wants to create a second server instance on B, it's simple. 
If he wants the data from A to reside in the existing server on B, then 
it's not simple and he needs to contact support.

Steve

M wrote:
> It the same procedure. It's quite simple.
>
> The only compliction will be your license file. You'll need to contact
> Perforce and explain the situation, and have your licenses from server A
> license transferred to the license file on server B.
>
>
>
> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com
> [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Siddesh Bg
> Sent: Monday, March 02, 2009 12:58 AM
> To: perforce-user <at> perforce.com
> Cc: siddesh.gurusiddappa <at> rsa.com
> Subject: [p4] Moving a Perforce server contents to an another existing
> server
>
>
> Hi,
> We need to move a Perforce server contents in location 'A' to another
> Perforce server in location 'B', both are identical in architecture &
> text file formats. Location 'B' server is currently fully functional
> with many depots.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Matt Janulewicz | 2 Mar 2009 18:58
Favicon

Re: [p4] Moving a Perforce server contents to an another existing server

The 'perfmerge' utility is now generally available on the Perforce FTP 
site, but I agree with Stephen in that you should call support first if, 
in fact, you are wanting to merge databases together.

It's an 'easy' operation in that it's a single, simple commandline 
command. But this is a high risk maneuver and everything with both 
databases has to be picture perfect (no errors or inconsistencies) for 
it to work properly.

-Matt

Stephen Vance wrote:
>
> If he just wants to create a second server instance on B, it's simple.
> If he wants the data from A to reside in the existing server on B, then
> it's not simple and he needs to contact support.
>
> Steve
>
> M wrote:
> > It the same procedure. It's quite simple.
> >
> > The only compliction will be your license file. You'll need to contact
> > Perforce and explain the situation, and have your licenses from server A
> > license transferred to the license file on server B.
> >
> >
> >
> > -----Original Message-----
> > From: perforce-user-bounces <at> perforce.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
Roy Smith | 3 Mar 2009 19:54

[p4] Change numbers not in chronological order?

I just did "p4 changes ..." on a portion of our source tree.  The very  
end of the output looked like this:

Change 10446 on 1993/04/09 by ouster <at> cvs2p4 '.  [imported from CVS by  
cvs2p4'
Change 10437 on 1993/04/03 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10435 on 1993/04/01 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10433 on 1993/03/19 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10432 on 1993/03/19 by ouster <at> cvs2p4 '.  [imported from CVS by  
cvs2p4'
Change 10426 on 1993/02/06 by ouster <at> cvs2p4 '.  [imported from CVS by  
cvs2p4'
Change 10425 on 1991/09/08 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10410 on 2006/12/15 by helenw <at> USENHELENWD2E 'code refactory '
Change 10391 on 2006/12/14 by pogren <at> pogren_ECOM 'Start work  
converting stream op'
Change 10388 on 2006/12/14 by buncew <at> build-san-mediation-all 'remove  
disconnect of s: drive '
Change 10387 on 2006/12/14 by buncew <at> build-cimom-all 'remove  
disconnect of s: drive a'
Change 10383 on 2006/12/14 by gaih <at> gaih-ecom-andvm5 'Modified MOF to  
have start, sto'
Change 10381 on 2006/12/14 by steng <at> p4webapps 'modify for build  
environ '

How it is possible that the changes are not in chronological order?  I
(Continue reading)

Permalink | Reply | 5 comments |
headers
Grills, Jeff N | 3 Mar 2009 20:11
Picon

Re: [p4] Change numbers not in chronological order?

Those files out of order came from cvs2p4.  Perhaps that tool attempts
to preserve the original submission date through some trickery?

j 

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Roy Smith
Sent: Tuesday, March 03, 2009 12:55 PM
To: perforce-user <at> perforce.com
Subject: [p4] Change numbers not in chronological order?

I just did "p4 changes ..." on a portion of our source tree.  The very
end of the output looked like this:

Change 10446 on 1993/04/09 by ouster <at> cvs2p4 '.  [imported from CVS by
cvs2p4'
Change 10437 on 1993/04/03 by ouster <at> cvs2p4 'Branching  [imported from
CVS b'
Change 10435 on 1993/04/01 by ouster <at> cvs2p4 'Branching  [imported from
CVS b'
Change 10433 on 1993/03/19 by ouster <at> cvs2p4 'Branching  [imported from
CVS b'
Change 10432 on 1993/03/19 by ouster <at> cvs2p4 '.  [imported from CVS by
cvs2p4'
Change 10426 on 1993/02/06 by ouster <at> cvs2p4 '.  [imported from CVS by
cvs2p4'
Change 10425 on 1991/09/08 by ouster <at> cvs2p4 'Branching  [imported from
CVS b'
Change 10410 on 2006/12/15 by helenw <at> USENHELENWD2E 'code refactory '
(Continue reading)

Permalink | Reply | 1 comment |
headers
Matt Janulewicz | 3 Mar 2009 20:17
Favicon

Re: [p4] Change numbers not in chronological order?

The cvs2p4 import script (both the new-school and old-school versions) 
back-date your changelists to when the CVS checkins were originally 
submitted, regardless of what changelists already exist.

If you (or someone else in the past) use the old-school 'scripty' 
importer, this is how it will look. If you use the new-school 'db-based' 
importer and merge it with an existing P4 database using perfmerge's '-t 
append' switch, it will look like this, too.

-Matt

Roy Smith wrote:
>
> I just did "p4 changes ..." on a portion of our source tree.  The very 
> end of the output looked like this:
>
> Change 10446 on 1993/04/09 by ouster <at> cvs2p4 '.  [imported from CVS by 
> cvs2p4'
> Change 10437 on 1993/04/03 by ouster <at> cvs2p4 'Branching  [imported from 
> CVS b'
> Change 10435 on 1993/04/01 by ouster <at> cvs2p4 'Branching  [imported from 
> CVS b'
> Change 10433 on 1993/03/19 by ouster <at> cvs2p4 'Branching  [imported from 
> CVS b'
> Change 10432 on 1993/03/19 by ouster <at> cvs2p4 '.  [imported from CVS by 
> cvs2p4'
> Change 10426 on 1993/02/06 by ouster <at> cvs2p4 '.  [imported from CVS by 
> cvs2p4'
> Change 10425 on 1991/09/08 by ouster <at> cvs2p4 'Branching  [imported from 
> CVS b'
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ivey, William | 3 Mar 2009 20:18
Picon
Favicon

Re: [p4] Change numbers not in chronological order?

Looks like cvs2p4 is setting the change time to that of the
original CVS checkin. In that case, the changes themselves are
in chronological order, but that's not related to the date
recorded in the change.

-Wm

-----Original Message-----
From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-bounces <at> perforce.com] On Behalf
Of Roy Smith
Sent: Tuesday, March 03, 2009 12:55 PM
To: perforce-user <at> perforce.com
Subject: [p4] Change numbers not in chronological order?

I just did "p4 changes ..." on a portion of our source tree.  The very  
end of the output looked like this:

Change 10446 on 1993/04/09 by ouster <at> cvs2p4 '.  [imported from CVS by  
cvs2p4'
Change 10437 on 1993/04/03 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10435 on 1993/04/01 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10433 on 1993/03/19 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10432 on 1993/03/19 by ouster <at> cvs2p4 '.  [imported from CVS by  
cvs2p4'
Change 10426 on 1993/02/06 by ouster <at> cvs2p4 '.  [imported from CVS by  
cvs2p4'
Change 10425 on 1991/09/08 by ouster <at> cvs2p4 'Branching  [imported from
(Continue reading)

Permalink | Reply | 0 comments |
headers
Barbieri, Ross | 3 Mar 2009 20:26

Re: [p4] Change numbers not in chronological order?

Hi Roy,

I think the order of the changelist numbers is correct here.

It looks like after CL 10410, code was imported into Perforce from cvs
using the cvs2p4 script.  This script actually changes the date field of
the changelist to match the cvs commit date.  However, the actual submit
into perforce (for instance CL 10425) happened after 10410.

I hope that helps to answer your question.

-Ross

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Roy Smith
Sent: Tuesday, March 03, 2009 1:55 PM
To: perforce-user <at> perforce.com
Subject: [p4] Change numbers not in chronological order?

I just did "p4 changes ..." on a portion of our source tree.  The very  
end of the output looked like this:

Change 10446 on 1993/04/09 by ouster <at> cvs2p4 '.  [imported from CVS by  
cvs2p4'
Change 10437 on 1993/04/03 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10435 on 1993/04/01 by ouster <at> cvs2p4 'Branching  [imported from  
CVS b'
Change 10433 on 1993/03/19 by ouster <at> cvs2p4 'Branching  [imported from
(Continue reading)

Permalink | Reply | 0 comments |

Gmane