[p4] Perforce Backup question
Dan Bloch
6.02e23 at gmail.com
Wed Jan 17 17:44:13 PST 2007
Hi, GC345C-
You're right that the server only has to be unavailable during the
checkpoint, but the rest of your process can be improved.
You don't need to, or want to, copy all of $P4ROOT. All you want to copy is
the depot. Everything else is already in the checkpoint. And the depot can
be copied after the checkpoint, since it isn't a problem if there are depot
revisions that aren't in the database. They're just ignored and/or
overwritten as necessary.
Finally you might want to think about rsync for your depot copy, which makes
copying even a large depot quite fast.
Regards,
Dan
On 1/17/07, G2345C <g2345c at yahoo.com> wrote:
>
> Hi all,
> I am trying to reduce the downtime of our back up, so
> here i have a question, What we are doing right now
> is:
> 1/ shut down p4 server
> 2/ make checkpoint and journal p4d -jc
> 3/ copy $P4ROOT to a save place
> 4/ Start Server
>
> The problem is that our depot is too big that step 3
> (copy) is taking too long. I am thinking of Mirror
> $P4ROOT, that has the following steps:
> 1/ shut down P4 server
> 2/ make checkpoint and journal p4d -jc
> 3/ stop the Mirror
> 4/ Start P4 server
> 5/ Copy the Mirror to a save place
> 6/ Turn the Mirror back on
> Is it doable? and any good or not good about it?
>
> Thanks
>
>
>
>
> ____________________________________________________________________________________
> The fish are biting.
> Get more visitors on your site using Yahoo! Search Marketing.
> http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
> _______________________________________________
> 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