[p4] Moving users between servers - any good tricks?

[Ivey, William]

Replaying the user information into the outer server sort of worked. All
the

users appeared.

 

However, all of their changelists were empty. It remembered that they
had

numbered changelists, but not what files were in each, nor what was in

their default changelist.

 

There's some linkage that was not restored/created when the user
information

alone was inserted. I've been browsing the checkpoint to see if I could
spot it,

but no luck.

 

Looks like a call to support is in order.

 

-Wm

 

________________________________

From: Stephen Vance [mailto:steve at vance.com] 
Sent: Thursday, June 28, 2007 10:00 PM
To: Ivey, William
Cc: dlewis78731 at gmail.com; perforce-user at perforce.com
Subject: Re: [p4] Moving users between servers - any good tricks?

 

Actually, it's not so much checkpoint surgery as a more simple journal
extraction and replay. And there's a command line way to do it, also.
The protection table may be the most difficult if it's not the same.

Here's a script (from memory and untested in this implementation) for
the command line version in sh:

# Save users
userlist=`p4 users | cut -d ' ' -f 1`
for u in $userlist
do
  p4 user -o $u > user.$u
done

# Restore users
for f in user.*
do
  p4 user -i < $f
done

Alternatively, you can just grep the checkpoint for lines with
'@db.user@' and restore those lines into the other server with 'p4d
-jr'. I've even used this technique for live replication of
user/password changes between servers.

Steve

Ivey, William wrote: 

No, everything except the users is already there. It's
already an independent server except that it gets its
user information/authentication from our main server.
 
It looks as though all I have to do is shut it down,
remove P4AUTH, install the license then create each
of the user accounts. From what I can tell when it
comes back up it won't know the difference (except
that user passwords will be reset).
 
The alternative appears to be checkpoint surgery,
moving the user information from the main server
checkpoint to the other server's checkpoint.
 
-Wm
 
 
-----Original Message-----
From: Dave Lewis [mailto:dlewis78731 at gmail.com] 
Sent: Thursday, June 28, 2007 9:50 AM
To: Ivey, William
Cc: perforce-user at perforce.com
Subject: Re: [p4] Moving users between servers - any good tricks?
 
it doesn't sound like anything needs to be done!
 
so perhaps you want to move their source base and clients, open files
and etc to the other server?
 
dave
 
On 6/27/07, Ivey, William <william_ivey at bmc.com>
<mailto:william_ivey at bmc.com>  wrote:
  

	I need to split a server's user population into two,
	moving about 20% of the users from one to the other.
	 
	Currently the "other" server uses P4AUTH to
	authenticate from the primary server so these will be
	"new" users only in the sense that they are local to
	the server now. (These are also the only users who
	ever used the other server, so there shouldn't be any
	mismatch between file-related metadata and users.)
	 
	I've never tried to do this before. Anyone have any
	tips?
	 
	-Wm
	 
	_______________________________________________
	perforce-user mailing list  -  perforce-user at perforce.com
	http://maillist.perforce.com/mailman/listinfo/perforce-user
	 
	    

 
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user