The Perforce service stores two kinds of data: versioned files and metadata.
Versioned files are files submitted by Perforce users. Versioned files are stored in directory trees called depots.
There is one subdirectory under the server’s root directory for each depot in your Perforce installation. The versioned files for a given depot are stored in a tree of directories beneath this subdirectory.
Database files store metadata, including changelists, opened files, client workspace specifications, branch mappings, and other data concerning the history and present state of the versioned files.
Database files appear as db.*
files in the top level of
the server root directory. Each db.*
file contains a
single, binary-encoded database table.
This chapter describes the commands and processes you use to backup and recover your Helix Versioning Engine. For information about backup and recovery of distributed systems, see Helix Versioning Engine Administrator Guide: Multi-Site Deployment.