Shaun T. Erickson wrote:
I have set up a new cvs server. I've made sure that users of the old
server can successfully connect to and use the new server.
Is moving the repository as simple as deleting the test repository on
the new server and copying the old one into its place?
Pretty much. Don't delete the old repository, though, until after the
new one is set up and running.
Are there any issues to be had from the fact that many files will still
be cheched out from the old location and will later be checked into the
new location?
Yes. The easiest way to do the migration is to have everyone check in
their changes, lock down the repository (if you're using pserver, create
an empty file named CVSROOT/writers).
If that's not possible, you can use the newcvsroot script (it's in the
source code distribution, in the contrib/ directory).
To simplify any future moves, give your new machine an alias on your
local DNS server (if you have one). That way, moving the repository is
as simple as setting up the new machine, copying the repository over,
and switching DNS entries to point at the new machine.
Be sure to back up the repository before you do anything.
When I did this at my last company, we scheduled the changeover on a
weekend, and did a dry-run first to iron out any problems. We were also
migrating from FreeBSD to Solaris, so we had to modify the scripts. The
dry run came in handy, as it exposed some problems (nothing major, as I
recall) in our migration strategy.
--
Jim
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
