Previous Table of Contents Index Next
Perforce 2012.3: P4Sandbox User's Guide

Chapter 5
We designed P4Sandbox to require minimal administrative oversight by both users and Perforce Administrators. Generally, if you encounter an issue while using P4Sandbox, contact your Perforce Administrator.
Understanding prohibited and unnecessary tasks
Note the following prohibited and unnecessary tasks:
Do not run p4 protect to create a protections table. Issuing this command harms P4Sandbox's internal protections table.
Do not create scripts to run triggers. Running such scripts harms P4Sandbox's internal trigger logic and behavior and may break the interoperability of a P4Sandbox workspace specification and its shared repository.
However, you can run daemons, such as a review daemon.
Managing your P4Sandbox: user tasks
To maintain your P4Sandbox, do the following:
Verify that P4Sandbox is secure, particularly if you work remotely and transfer proprietary information between P4Sandbox and a shared service. Your Perforce Administrator can confirm that your implementation complies with Perforce's security settings and your company's security policies and procedures.
Confirm that P4Sandbox automatically creates checkpoints and journals and stores them in the .p4sandbox directory. Your Perforce Administrator needs these files to restore P4Sandbox.
For more information about backup recovery, checkpoints, journaling, and security, contact your Perforce Administrator.
Editing the file pulling interval
You define the periodic file pulling interval during the initial P4Sandbox configuration.
To edit this setting, use one of the following methods:
In P4V, select a new pulling interval option on the Replication Settings page of the P4Sandbox Configuration Wizard; see Using the configuration wizard.
In p4, issue p4 counter p4sandbox_schedule_copy and adjust the interval. See p4 counter.
Performing miscellaneous tasks using p4
The following administrative tasks require you to issue p4 commands. If you do not use p4, contact your Perforce Administrator for help.
This section discusses:
For more information, see the following in the Perforce System Administrator's Guide:
Configuring Unicode mode
To configure P4Sandbox to operate in Unicode mode, see the Usage Notes for p4sandbox init.
Managing jobspecs and jobs
P4Sandbox propagates only job fixes, not jobs. You must manually copy jobs between the shared service and your P4Sandbox. Additionally, you can only submit changelists for job fixes that meet certain conditions; see p4 submit for these conditions.
If your use of P4Sandbox requires jobs, do one or both of the following:
p4 -p <shared service's P4PORT> jobspec -o | p4 -p <sandbox server's P4PORT> jobspec -i
Edit the job template using p4 jobspec, as necessary.
Improper modifications of the Perforce job template can lead to corruption of your server's database. Before modifying any of the existing job functionality, be sure to read the chapter "Customizing Perforce: Job Specifications," in the Perforce System Administrator's Guide.
Supporting P4Sandbox: backup and recovery
The .p4sandbox folder contains all of your db.* metadata files and your versioned files. It also contains the three most recent checkpoint files.
P4Sandbox automatically creates checkpoint and journal files with the prefix rolling once per day based on the p4sandbox_schedule_checkpoint counter. For example: rolling.chk.0 and rolling.jnl.0.
Backing up a P4Sandbox
To back up a P4Sandbox:
(Optional) Issue p4sandbox stop.
This command ensures that the db.* metadata files are consistent and faster to restore from than restoring from a pair of checkpoint and journal files.
Copy the .p4sandbox folder to your backup media.
Note the following:
Run p4 verify to validate the backup; type:
$ p4sandbox start -r path to backup copy
$ p4 -p path to backup copy verify
$ p4sandbox stop -r path to backup copy
Restoring a P4Sandbox
To restore a P4Sandbox:
Copy a .p4sandbox folder from backup media to your machine's hard disk.
Issue p4sandbox start -r path to .p4sandbox to start your restored P4Sandbox.
Managing P4Sandbox users: Perforce Administrator tasks
Perforce Administrators have minimal oversight of P4Sandbox users, and can perform the following tasks:
Determine who is using a P4Sandbox by issuing p4 clients and scanning for lines that start with p4sandbox-, such as the following:
p4sandbox -username -computername
Determine which files P4Sandbox users have accessed and when the files were checked out and checked back into a shared service by analyzing the following information from the client list's view mapping:
Update time: Shows when files were copied from the shared service to a P4Sandbox.
Access time: Shows when files were copied from a P4Sandbox to the shared service.
View: Shows which files are currently copied into a P4Sandbox.
Root: Shows the root of a P4Sandbox's workspace on the user's computer.
Perform standard administration, such as restoring an accidentally deleted P4Sandbox, or managing the P4Sandbox broker (p4sandbox) and Perforce Server (p4sandbox-p4d)distribution.
For more information on performing administrator tasks, see the Perforce System Administrator's Guide and the Perforce Command Reference.
Administrators must ensure that all new and existing form trigger scripts that run on shared services used by P4Sandbox do not affect the P4Sandbox workspace specification.
P4Sandbox creates a workspace specification that begin with p4sandbox-when creating the remote depot (see p4 remote). If the workspace specification is altered in any way (either the name or contents), P4Sandbox will be unable to work properly with its shared repository.
For more information, see the Perforce System Administrator's Guide: Scripting Perforce, Triggers and Daemons, Triggering on Forms and also the Perforce Command Reference: p4 triggers.

Previous Table of Contents Index Next

Perforce 2012.3: P4Sandbox User's Guide
Copyright 2012-2013 Perforce Software.