[p4] How import a production database on a fresh server .

[Jeff A. Bowles]

Depends on the license file itself.  Some of the Perforce-issued license
files have the TCP port built into the license file, some do not.
Me, I would have a separate file "just in case", that works for the
backup-machine IP address.

[Aside: If this were a Windows machine, I would test on a separate machine,
always. To repeat:  I would not mix production-server and test-server on the
same Windows machine. It would be far too easy to accidently connect to the
wrong one, thinking you were doing a test operation, and make a devastating
change to the production server. (Running against the wrong P4ROOT directory
is a variation of this risk.) Because of system-wide registry entries (to
support starting the production server as a service), the chances of a
user-mistake paint a gloomy outcome.]

    -Jeff Bowles


On Sat, Apr 5, 2008 at 11:05 AM, Rick Macdonald <rickmacd at shaw.ca> wrote:

> Just so I know, do I need a second license file to do this or a similar
> task if I do it on the same machine but change P4ROOT and the port number in
> P4PORT?
>
> I expect people will suggest a second machine regardless, for safety's
> sake and/or machine loading?
>
> Rick
>
>
> Jeff A. Bowles wrote:
>
> > Send email to the license-folks / support-folks asking if you can have a
> > second license file with the IP address of your backup/test machine.
> > I believe they have a procedure (in effect, it's "sign this and send it
> > back, and we'll take care of you then") that will address this.
> >
> > Do not bother figuring out how to excise the workspace definitions from
> > your
> > checkpoints. (In general, checkpoint-surgery is messy, and worse, the
> > workspace definitions are multiple-line entries with joins to other
> > tables.
> >  The rule-of-thumb for checkpoint surgery is, "don't - and if you do,
> > have
> > someone from tech support on the telephone hearing the keystrokes and
> > perhaps even watching over your shoulder."  The reasoning is, when you
> > break
> > the checkpoint, you're gonna call 'em for assistance anyway, so why not
> > give
> > yourself better odds by involving them before the break happens.)
> >
> > Go the second-license-file route.  It's easier and faster.
> >
> >   -Jeff Bowles
> >
> >
> > On Sat, Apr 5, 2008 at 9:13 AM, Loïc Dalbègue <ldalbegue at edengames.com>
> > wrote:
> >
> >
> >
> > > Hi,
> > >
> > > I have a perforce server in production with a database with 80 users
> > > and
> > > 260 workspace. Recently i found some corruption in my database so I
> > > want
> > > to verify that with the p4 verify command, but i takes to long time
> > > for
> > > my production server. So i want to restore my database on another
> > > fresh
> > > perforce server with no licence to launch the p4 verify with no impact
> > > to my production server.
> > > I copy my depot files, and i want to restore my database with a
> > > checkpoint file but on the fresh no licenced server i have some
> > > limitation !! 2 users and 5 workspaces so after the restore the fresh
> > > server doesn't start.
> > >
> > > I already drop the users from my checkpoint file with this command :
> > > grep -v @db.user@ checkpoint > checkpointnew.
> > > But how drop the workspace (clients) from my checkpoint too because
> > > the
> > > server doesn't start anymore with this error :
> > > Perforce server error:
> > >   Unlicensed server cannot start while over user/client quota.
> > >   Try deleting old clients with 'client -d'.
> > >   License count: 263 clients used of 5 licensed.
> > >
> > > Thx for your help.
> > > _______________________________________________
> > > perforce-user mailing list  -  perforce-user at perforce.com
> > > http://maillist.perforce.com/mailman/listinfo/perforce-user
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>


-- 
---
Jeff Bowles - jeff.a.bowles at gmail.com