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:Jame...@perforce.com (Jame@perforce.com)
Date:09/09/1998 09:48:49 AM
List:com.perforce.perforce-user

On Tue, 8 Sep 1998, Mark Blair wrote:

David Jeske <jeske at home.chat.net> wrote:

The Perforce checkpoint mechanism is designed so that you never have to take the database offline.

What if the database is modified during the backup? If I restore from the last checkpoint + journal + RCS files, then there will be revisions in some RCS files with no corresponding metadata. That does not sound like a Good Thing.

Perforce is designed to handle this. As far as Perforce is concerned, if it isn't in the metadata then it doesn't exist. If an extra revision does actually exist then it will be replaced as needed.

You can check this out for yourself - suppose you have a file //depot/foo with 2 revisions, both text. Then /server/root/depot/foo,v will contain 1.1 and 1.2. If you "cd /server/root/depot", do "co -l foo", modify foo, then "ci foo", there will be a revision 1.3 - you can see this with "rlog foo". p4 filelog //depot/foo will only show revisions 1 and 2. If you do "p4 edit foo" then "p4 submit" you will see that /server/root/foo,v now has the revision 1.3 that Perforce put there - the old revision 1.3 that you added "behind Perforce's back" is overwritten.

--- James Strickland Perforce Software james at perforce.com