9 messages in com.perforce.perforce-user[p4] backup strategy
FromSent OnAttachments
John-Mason P. Shackelford16 Mar 2005 12:35 
Stephen Vance16 Mar 2005 16:59 
John-Mason P. Shackelford17 Mar 2005 13:00 
Ivey, William18 Mar 2005 07:36 
Ken....@thomson.com18 Mar 2005 07:39 
John-Mason P. Shackelford18 Mar 2005 10:09 
Dave Lewis18 Mar 2005 13:43 
Chuck Karish19 Mar 2005 11:38 
Nick Barnes19 Mar 2005 14:24 
Subject:[p4] backup strategy
From:John-Mason P. Shackelford (john@shackelford.org)
Date:03/17/2005 01:00:29 PM
List:com.perforce.perforce-user

Thanks all for your feedback.

A number of you suggested that exploding the tarball is taking too long. Good. I'll have to bug the admin and see if he can't figure out the problem.

A little more info about how I performed the untar:

I ran $ tar -xvf depot_files.tar > /dev/null so I wasn't being slowed down by terminal output. There was also no copying across a network or even across a file system involved since I exploded the tar to the same directory where the tarball lived.

Do you think that the sheer number of directories could be at issue? The depot holds java projects which, given java package structure, contains many directies.

As this box is newly connected to the SAN it could just be a tuning issue.

Thanks for the help!

John-Mason