Jeff A. Bowles wrote:
Quite a long while ago, I started using Perforce at a company
I was at and downloaded a number of user-contributed scripts
from perforce.com. The simplest, and most useful, were two
scripts from Bob Andrews at WebLogic: a Unix "startup/shutdown"
script for Perforce, and a Unix "backup" script that dutifully
did a checkpoint, tar'ed away the depot/* subdirectory, and
then "aged" the checkpoints so that older copies were deleted.
One word of caution: It is important to take note of the p4d exit status
when checkpointing. A while ago I managed to corrupt the p4 database
(external cause, not p4d's fault) in a way that it mostly worked, just one
rarely used (but not unimpotant) project was affected. However checkpointing
was failing and generating incomplete checkpoints. I to dutifully "aged" my
checkpoints, and by the time the problem with the database was recognized all
healthy checkpoints had been aged out of existence... So it is impotant that
your backup scripts sound all kinds of alarms if the checkpointing fails.
Gerd
2 messages in com.perforce.perforce-userUnix init/backup scripts?
