RE: Rebuilding server

[Teala Spitzbarth]

I'm pretty sure (i.e. I have done it, for testing purposes
and it works, but not actually on a production cvs tree) 
that what you want to do is cpio or tar up the repository to back 
it up. Reinstall your server and then layout the tree again.
That is certainly the only way you are going to
retain your revision history. All of that is stored
within the ,v rcs files in the repository itself.

Since I haven't done this in production, I'd like to 
see other confirm this though!  

It may be good to rerun cvs init?

Thanks,
Teala


-----Original Message-----
From: Ashley M. Kirchner [mailto:address@hidden
Sent: Wednesday, August 15, 2001 5:41 PM
To: Info CVS Mailing List
Subject: Rebuilding server



    I'm looking at a server (machine) rebuild.  How can I preserve my
CVS tree(s)?  I don't know if it's as simple as tarring up my entire
/CVS directory, then untarring it when I'm done
(formatting/reinstalling/blah/blah), or what else is involved.  I must
maintain all of the version histories on everything, branches and all.
I know I can't just checkout everything, then re-import after the
rebuild because that'll skew the file versioning.  So, what's the proper
way of doing this?

--
H | "Life is the art of drawing without an eraser." - John Gardner
  +--------------------------------------------------------------------
  Ashley M. Kirchner <mailto:address@hidden>   .   303.442.6410 x130
  Director of Internet Operations / SysAdmin    .     800.441.3873 x130
  Photo Craft Laboratories, Inc.            .     3550 Arapahoe Ave, #6
  http://www.pcraft.com ..... .  .    .       Boulder, CO 80303, U.S.A.



_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs