Perforce 2007.2 System Administrator's Guide

More documents

Recommendations

Info

Chapter 1: Welcome to Perforce: Installing and UpgradingFor additional safety, run p4 verify as part of your upgrade. See “Verifying files duringserver upgrades” on page 47 for details.Warning!Upgrading to Release 2001.1 or later requires an upgrade of your databasefiles. Downgrading thereafter requires that you restore from backups.If you want to keep a pre-2001.1 server available as a fallback option whenupgrading to 2001.1 or higher, you must back up your entire server root(including the db.* files) after you stop the server.Upgrading from UNIX Release 98.2 or laterIf you have a valid license (or require no license) and are upgrading from Release 98.2 orlater:1. Download the new p4d executable for your platform.2. Stop the current instance of p4d.3. Make a checkpoint and back up your old installation.4. Install the new p4d in the desired location.5. Run p4d -xu to upgrade the database.NoteIf your server has fewer than 1000 changes, the upgrade runs automatically.Larger installations require that you run p4d -xu manually. You must havesufficient disk space to complete the upgrade.6. Restart the new p4d with your site’s usual parameters.Your users should then be able to use the new server.Windows upgradesOn Windows, download the installer (perforce.exe) and follow the installation dialog.The upgrade process on Windows is extremely conservative; in the event of an errorcondition during an upgrade, you will be able to revert to your pre-upgrade Perforceserver or service.NoteIf your server has fewer than 1000 changes, the upgrade runs automatically.Larger installations require that you run p4d -xu manually. You must havesufficient disk space to complete the upgrade.If you have any questions or difficulties during an upgrade, contact Perforce technicalsupport.18 Perforce 2007.2 System Administrator’s Guide
Chapter 1: Welcome to Perforce: Installing and UpgradingInstallation and administration tipsRelease and license informationPerforce servers are licensed according to how many users they support.Licensing information is contained in a file called license in the server root directory.The license file is a plain text file supplied by Perforce Software. Without the licensefile, the Perforce server limits itself to two users and five client workspaces.You can update an existing file without stopping the Perforce Server by using the p4license command. See “Adding new licensed users” on page 45 for details.To view current licensing information, invoke p4d -V from the server root directorywhere the license file resides, or by specifying the server root directory either on thecommand line (p4d -V -r server_root) or in the P4ROOT environment variable.If the server is running, you can also use p4 info to view your licensing information.The server version is also displayed when you invoke p4d -V or p4 -V.Observe proper backup proceduresRegular backups of your Perforce data are vital. The key concepts are:• Make sure journaling is active.• Create checkpoints regularly.•Use p4 verify regularly.See “Supporting Perforce: Backup and Recovery” on page 25 for a full discussion ofbackup and restoration procedures.Use separate physical drives for server root and journalWhether installing on UNIX or Windows, it is advisable to have your P4ROOT directory(that is, the directory containing your database and versioned files) on a different physicaldrive than your journal file.By storing the journal on a separate drive, you can be reasonably certain that, if a diskfailure corrupts the drive containing P4ROOT, such a failure will not affect your journal file.You can then use the journal file to restore any lost or damaged metadata.Further details are available in “Supporting Perforce: Backup and Recovery” on page 25.Perforce 2007.2 System Administrator’s Guide 19
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 68 and 69:
Chapter 3: Administering Perforce:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
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?