Perforce 2007.2 System Administrator's Guide

More documents

Recommendations

Info

Chapter 1: Welcome to Perforce: Installing and UpgradingCase sensitivity issuesWhether your Perforce server is running on Windows or UNIX, if your site is involved incross-platform development (that is, if you are using Perforce client programs on bothWindows and UNIX workstations), your users must be aware of certain details regardingcase sensitivity issues.See “Case sensitivity and multiplatform development” on page 57 for details.Tune for performancePerforce is an efficient consumer of network bandwidth and CPU power. The mostimportant variables that determine server performance are the efficiency of your server’sdisk I/O subsystem and the number of files referenced in any given user-originatedPerforce operation.For more detailed performance tuning information, see “Tuning Perforce forPerformance” on page 119.24 Perforce 2007.2 System Administrator’s Guide
Chapter 2Supporting Perforce:Backup and RecoveryThe Perforce server stores two kinds of data: versioned files and metadata.• Versioned files are files submitted by Perforce users. Versioned files are stored indirectory trees called depots.There is one subdirectory under the server’s root directory for each depot in yourPerforce installation. The versioned files for a given depot are stored in a tree ofdirectories beneath this subdirectory.• Database files store metadata, including changelists, opened files, client specs, branchspecs, 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. Eachdb.* file contains a single, binary-encoded database table.Backup and recovery conceptsDisk space shortages, hardware failures, and system crashes can corrupt any of thePerforce server’s files. That’s why the entire Perforce root directory structure (yourversioned files and your database) should be backed up regularly.The versioned files are stored in subdirectories beneath your Perforce server root, and canbe restored directly from backups without any loss of integrity.The files that constitute the Perforce database, on the other hand, are not guaranteed to bein a state of transactional integrity if archived by a conventional backup program.Restoring the db.* files from regular system backups can result in an inconsistentdatabase. The only way to guarantee the integrity of the database after it’s been damagedis to reconstruct the db.* files from Perforce checkpoint and journal files:•A checkpoint is a snapshot or copy of the database at a particular moment in time.•A journal is a log of updates to the database since the last snapshot was taken.The checkpoint file is often much smaller than the original database, and it can be madesmaller still by compressing it. The journal file, on the other hand, can grow quite large; itis truncated whenever a checkpoint is made, and the older journal is renamed. The olderjournal files can then be backed up offline, freeing up more space locally.Perforce 2007.2 System Administrator’s Guide 25
Page 2 and 3: This manual copyright 1997-2007 Per
Page 4 and 5: Table of ContentsLogging errors....
Page 6 and 7: Table of ContentsDeleting groups ..
Page 8 and 9: Table of ContentsChapter 9Perforce
Page 10 and 11: Preface: About This Manual10 Perfor
Page 12 and 13: Chapter 1: Welcome to Perforce: Ins
Page 26 and 27: Chapter 2: Supporting Perforce: Bac
Page 40 and 41: Chapter 3: Administering Perforce:
Page 74 and 75:
Chapter 3: Administering Perforce:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Chapter 5: Customizing Perforce: Jo
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Chapter 6: Scripting Perforce: Trig
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Chapter 7: Tuning Perforce for Perf
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Chapter 8: Perforce and WindowsUser
Page 136 and 137:
Chapter 8: Perforce and WindowsWind
Page 138 and 139:
Chapter 8: Perforce and WindowsBefo
Page 140 and 141:
Chapter 8: Perforce and WindowsReso
Page 142 and 143:
Chapter 8: Perforce and Windows142
Page 144 and 145:
Chapter 9: Perforce ProxySystem req
Page 146 and 147:
Chapter 9: Perforce ProxyAdminister
Page 148 and 149:
Chapter 9: Perforce ProxyMaximizing
Page 150 and 151:
Chapter 9: Perforce Proxy150 Perfor
Page 152 and 153:
Appendix A: Perforce Server (p4d) R
Page 154 and 155:
Appendix A: Perforce Server (p4d) R
Page 156 and 157:
Indexcreating checkpoints 26creatin
Page 158 and 159:
Index.ini files 49installationWindo
Page 160 and 161:
IndexP4ROOT 12, 152and depot files
Page 162 and 163:
Indexforce flag 51Perforce, definin
show all

Perforce 2007.2 System Administrator's Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?