[p4] Sanity check
Jamison, Shawn
sjamison at ciena.com
Wed Feb 28 11:36:26 PST 2007
Also check to see if your depot mapping is a relative mapping from the
P4ROOT.
If your depot is named depot and your P4ROOT is c:\p4root then your
depot relative map line would look like this
Map: depot/...
And your depot files are stored under the c:\p4root\depot directory.
-Shawn J>
Babs/Perforce Admin
-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Russell Jackson
Sent: Wednesday, February 28, 2007 2:06 PM
To: perforce-user at perforce.com
Subject: Re: [p4] Sanity check
I would suggest contacting tech support. They are your best source of
help for these types of problems.
Also, I assume you ran a verify on the live server as well, and it
didn't report any problems?
MISSING! means that the server couldn't find the archive file, so go and
look to see if the archive file is there or not. If it isn't there, but
it is there on your live server, then I would question the tape backup
process.
BAD! means the archive's MD5 signature doesn't match the one that was
originally generated for the file on the live server. This could be due
to a restore problem as well, or something else changing something in
the file.
This on is more difficult to figure out, but with some help from tech
support, you most likely can find the source of the trouble.
Rusty
On 2/28/07, Smith, Jeff <jsmith at medplus.com> wrote:
>
> We thought we would perform a test restore of our Perforce
> installation just to prove that we could.
>
> We currently backup by performing a checkpoint and then backing up
> that along with the depot. The service is kept live during this
> process. As I understand it, the worst case is that there will be
> revisions in the revision files that would not have metadata and would
> therefore be effectively lost. Would this result in verify errors?
>
> After restoring and reloading the database from the checkpoint, there
> are a lot of MISSING! and BAD! verification errors. What is the most
> likely cause of these?
>
> Thanks,
> Jeff
>
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
--
--------------------------------------------------
RCJackson Consulting
Perforce Consulting Partner and Certified Trainer
--------------------------------------------------
rusty at rcjacksonconsulting.com
http://www.rcjacksonconsulting.com
tel: 512-535-7274
fax: 512-535-7322
--------------------------------------------------
_______________________________________________
perforce-user mailing list - perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
More information about the perforce-user
mailing list