[p4] backup strategy

Stephen Vance steve at vance.com
Wed Mar 16 16:59:55 PST 2005

Turn off -v or redirect output to a file. Make sure you are running the 
command on the server or over the fastest network connection possible. Make 
sure the tarball is on the server or accessible over the fastest network 
connection possible. Tune your FS (see Shiv Sikand's paper from the 2003 
user conference). Even some of these suggestions should be done only if the 
metrics indicate they are advisable.


At 03:35 PM 3/16/2005, John-Mason P. Shackelford wrote:
>Greetings all.
>In the process of moving our Perforce installation to an active / passive 
>Linux cluster I discovered that a tarball of our depot files (about 5 
>gigs) takes about 6 hours to explode, that's without compression 
>(though  I am using -v). This is rather disconcerting given that our depot 
>is tiny in comparison to what it will be a year from now as we are still 
>rolling out the tool to the development groups in our organization and 
>that, in the event of a disaster--God forbid it should ever occur--we 
>cannot afford an outage this long to restore.
>The depot files are stored on a SAN so theoretically it should be fairly 
>fault tolerant and we shouldn't need to restore from the tar, but for the 
>sake of Murphy I'd like to develop a back up strategy that is optimized 
>for a relatively quick restore. I'd be interested to hear how others are 
>coping with this.
>Much appreciated,
>John-Mason Shackelford
>Software Developer
>Pearson Educational Measurement
>2510 North Dodge St.
>Iowa City, IA 52245
>ph. 319-354-9200x6214
>john-mason.shackelford at pearson.com
>Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
>Learn more: http://www.perforce.com/conf
>perforce-user mailing list  -  perforce-user at perforce.com

Stephen Vance
mailto:steve at vance.com

More information about the perforce-user mailing list