[p4] backups

[Peter Jackson]

'P4 verify' is indeed labour intensive for a server but a highly 
valuable integrity check.  Another approach is to break it down into 
smaller chunks, verifying different parts of your repository over a 
longer cycle.  Again, you have to experiment with what granularity suits 
your needs best.

The outcome might be that your whole repository is verified less often, 
but this is much better than not verifying at all because the task is 
too onerous.

If you maintain a replica service as backup you can of course verify 
that much more aggressively.

Pute.


Robert Cowham wrote:
> Minor tip - you can run verifies in parallel - will hit your server hard but
> tends to speed things up overall.
> 
> The no of concurrent tasks to achieve max throughput on your particular
> server given i/o config etc will depend somewhat - experiment.
> 
> As an example, on a system taking 48 hours for a single verify, this came
> down to 17 hours with the parallel version.
> 
> Robert 
> 
>> -----Original Message-----
>> From: perforce-user-bounces at perforce.com 
>> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
>> Daniel Beukers
>> Sent: 23 January 2008 11:28
>> To: duncan.bowring at realtimeworlds.com
>> Cc: perforce-user at perforce.com
>> Subject: Re: [p4] backups
>>
>> .	Check the depot
>> 	o	This is 'p4 admin verify'
>> 	o	At Guerrilla this takes to long to run it daily (20hrs)
>> 	o	If  you can, run this every day, otherwise 
>> whenever you can
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> .
>