19 messages in com.perforce.perforce-userServer hardware recommendations
FromSent OnAttachments
Fred...@mydata.se08 Sep 1998 14:13 
Mark...@tus.ssi1.COM08 Sep 1998 14:34 
Davi...@home.chat.net08 Sep 1998 16:50 
Mark...@tus.ssi1.COM08 Sep 1998 17:31 
Davi...@home.chat.net08 Sep 1998 17:55 
Mark...@tus.ssi1.COM08 Sep 1998 18:13 
Paul...@sam.engr.sgi.com08 Sep 1998 18:32 
Davi...@home.chat.net08 Sep 1998 19:04 
J.Bo...@hotmail.com08 Sep 1998 20:09 
Nick...@pobox.com09 Sep 1998 02:38 
Paul...@zergo.com09 Sep 1998 04:39 
Jame...@perforce.com09 Sep 1998 09:48 
Mark...@tus.ssi1.COM09 Sep 1998 10:57 
Mark...@tus.ssi1.COM09 Sep 1998 11:00 
Nick...@pobox.com10 Sep 1998 03:11 
WesP...@softweyr.com10 Sep 1998 07:17 
Mark...@pml.com10 Sep 1998 10:00 
Nick...@pobox.com11 Sep 1998 07:56 
Mark...@tus.ssi1.COM11 Sep 1998 10:08 
Subject:Server hardware recommendations
From:Davi...@home.chat.net (Davi@home.chat.net)
Date:09/08/1998 04:50:58 PM
List:com.perforce.perforce-user

On Tue, Sep 08, 1998 at 02:35:12PM -0700, Mark Blair wrote:

I'm setting up a new Perforce server for use by my group, and I'm looking for some advice about hardware selection. I plan to run p4d on a Linux system, and I have temporarily installed it on a P90 that I had laying around. I expect to have about 30+ users pretty soon, and based on experience with our previous revision control system (SourceSafe), I want to set up a reliable, high-performance server that will serve my group well for a long time to come (with emphasis on "reliable"). I'm looking for advice on a few things:

My best advice is this:

Any money you spend on getting a reliable server in place is wasted if you don't setup periodic backups right away. Perforce has an excelent 'robust online backup' procedure. Make sure you setup a job to ask p4d to generate a checkpoint, and then backup the whole p4d database.

At my last company I had it setup to checkpoint every night at 3am, the backups ran after that. I also suggest making sure someone does a 'fire-drill' and restores from a p4d checkpointed backup to validate your procedure.

Having said that, I never had to restore from a p4d backup (although I've saved and restored quite a few checkpoints for other reasons). While at my current company (using MS SourceSafe) we run tools to correct corruption about every month and a half.

-------

Becoming familiar with Perforce's robust checkpoint and restore facilities will also help when you decide you need to upgrade to higher performance hardware. By doing a checkpoint/backup/restore on the database, it's very straighforward to get the repository up on a completely different machine quickly.

--- David Jeske (N9LCA) + http://www.chat.net/~jeske/ + jeske at chat.net