Perforce Public Knowledge Base - Migrating workspaces and labels in commit/edge environments
× PRODUCTS SOLUTIONS CUSTOMERS LEARN SUPPORT
Downloads Company Partners Careers Contact Free Trials
Menu Search
Perforce
Reset Search
 

 

Article

Migrating workspaces and labels in commit/edge environments

« Go Back

Information

 
Problem
How do I move workspaces and labels between servers in a commit/edge environment?
Solution
Migrating workspaces and labels between servers in a commit/edge environment is accomplished using the p4 unload and p4 reload commands. 

Before the p4 unload and p4 reload commands can be used against a workspace, workspace owners must first submit or revert any promoted shelves or exclusively locked (+l) files

Beginning with the 2014.2 Helix Server release, the p4 unload command is no longer required to migrate a workspace:
 
	#777628 **
	    When using 'p4 reload -c <client> -p <port>' to migrate your
	    unlocked workspace from one Edge Server to another, it is no
	    longer necessary to first issue the 'p4 unload -c <client>'
	    command to the remote Edge Server. The reload command will
	    automatically issue the 'p4 unload' command for you, and will
	    wait for it to complete, prior to reloading your workspace into
	    the new Edge Server.


Workspace Examples (2014.2 and later Helix Servers)

User bruno migrates workspace projectX_dev from a remote edge server to his local edge server:
 
p4 -p edge_local:1666 reload -c projectX_dev -p edge_remote:1666
Client projectX_dev unloaded.
Client projectX_dev reloaded.

Helix Administrator admin migrates workspace bruno_dev from the commit server to an edge server:
 
p4 -p edge:1666 reload -f -c bruno_dev -p commit:1666
Client bruno_dev unloaded.
Client bruno_dev reloaded.

Note the -f flag for p4 reload is required for the administrator to work with workspaces they don't own.


Workspace Examples (2014.1 and earlier Helix Servers)

With 2014.1 and earlier Helix Servers, both p4 unload and p4 reload are required.

User bruno migrates workspace bruno_dev from the commit server to an edge server:

p4 -p commit:1666 unload -c bruno_dev
Client bruno_dev unloaded.

p4 -p edge:1666 reload -c bruno_dev -p commit:1666
Client bruno_dev reloaded.
 
Helix Administrator admin migrates workspace bruno_dev from the commit server to an edge server:
 
p4 -u admin -p commit:1666 unload -f -c bruno_dev
Client bruno_dev unloaded.

p4 -u admin -p edge:2000 reload -f -c bruno_dev -p commit:1666
Client bruno_dev reloaded.
 
Note the -f flag for p4 unload and p4 reload are required for the administrator to work with workspaces they don't own.


Label Examples

For labels, both p4 unload and p4 reload are required. 

User bruno migrates global label bruno_hotFix from the commit server to an edge server. 

p4 -p commit:1666 unload -l bruno_hotFix
Label bruno_hotFix unloaded.

p4 -p edge:1666 reload -l bruno_hotFix -p commit:1666
Label bruno_hotFix reloaded.

Helix Administrator admin migrates global label bruno_hotFix from the commit server to an edge server:

p4 -u admin -p commit:1666 unload -f -l bruno_hotFix
Label bruno_hotFix unloaded.

p4 -u admin -p edge:1666 reload -f -l bruno_hotFix -p commit:1666
Label bruno_hotFix reloaded.

Note, the -f flag to p4 unload and p4 reload is required in this case for administrators to work with labels they don't own:
Related Links

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255