[p4] Moving p4d to a new server (Mac OS -> Linux)

[Robert Cowham]

Do you need to update all the depots to point to a new root location for
each one (The Map: field)?

This step does depend on  how you originally configured it (i.e. did you use
relative or absolute paths).

For any one of the files with an error:

P4 print //depot/buildroot/Config.in#2 

And check the error message to see where it is looking for the original file

Robert 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Steve Sakoman
> Sent: 03 March 2007 21:51
> To: perforce-user at perforce.com
> Subject: [p4] Moving p4d to a new server (Mac OS -> Linux)
> 
> I'd like to move my perforce server from an old PPC Mac to a 
> shiny new Linux
> x86 box.
> 
> Following the directions in the Perforce administrator's 
> manual  appeared to work, but didn't pass the "p4 verify -q 
> //..." test.  Lots of MISSING!
> errors :-(
> 
> Can anyone see the flaw in the procedure below?
> 
> p4d on the Mac is configured so that it is launched liked this:
> 
>         /usr/local/bin/p4d     -d \
>                 -r /Users/perforce/p4root \
>                 -J /Users/perforce/p4journal/journal \
>                 -L /Users/perforce/p4logs/errors
> 
> To start the migration I did the following on my Mac:
> 
> #p4 verify -q //...
> 
> All is well, no errors.  So next I stop p4d and create a checkpoint:
> 
> # /usr/local/bin/p4d -r /Users/perforce/p4root/ -J 
> /Users/perforce/p4journal/journal -jc checkpoint-migration 
> Checkpointing to checkpoint-migration.ckp.4...
> Saving journal to checkpoint-migration.jnl.4...
> Truncating /Users/perforce/p4journal/journal...
> #
> 
> Again, all seems to be well.  I go to my new LInux box, 
> download p4d & p4 and move them to /usr/local/bin and set the 
> permissions. Then I create a new user "perforce", and log in 
> as perforce.
> 
> I copy the files from the Mac machine to the perforce home 
> directory and create the journal and logs directories:
> 
> $ cp -pR /mnt/nfs/perforce/p4root /home/perforce/ $ cd 
> /home/perforce $ mkdir p4journal $ mkdir p4logs
> 
> And now remove the db.* files:
> $ rm p4root/db.*
> 
> Finally, as per the manual, I recreate the db files:
> 
> $ p4d -r /home/perforce/p4root/ -jr /home/perforce/p4root/checkpoint-
> migration.ckp.4
> Perforce db files in '/home/perforce/p4root/' will be created 
> if missing...
> Recovering from /home/perforce/p4root/checkpoint- migration.ckp.4...
> $
> 
> So to see if it worked I start p4d:
> 
> $ /usr/local/bin/p4d -d -r /home/perforce/p4root/ -J 
> /home/perforce/p4journal/journal -L 
> /home/perforce/p4logs/errors Perforce Server starting...
> $
> 
> Looks good, no errors in the log file.  So lets try the p4 
> verify test:
> 
> $p4 verify -q //...
> //depot/buildroot/Config.in#2 edit change 27 (text) 
> 3CABEEF6CCC275C68 ...
> MISSING!
> (and hundreds more just like it)
> 
> So no joy.  Anyone have an idea of where I went wrong?
> 
> Thanks much!
> 
> Steve
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>