Cameron, Steve writes:
>
> [smc] As one who's paranoid about backups, I wonder what
> measures are being taken to back up the CVS repository that
> contains CVS. Even in the event of catastrophe, I'm sure somebody
> will have a recent checkout of the CVS source, but it's not so clear
> that all the history (the *,v files) would be preserved in such a
> case.
Since I do nightly testing on a number of platforms, I always (except in
the event of system hangs and such) have a checkout that's no more than
a day old. The checkout is on a fileserver, so it goes through our
normal corporate backup process which includes on-line, on-site
off-line, and off-site backups, so in the event of a catastrophe I'm
reasonably confident that we could recover a reasonably current copy of
the code without any problem. This would not, unfortunately, include
any history. I presume that SourceGear is taking reasonable precautions
to backup the CVS server, but I do not know for a fact that they are,
nor do I have any way of doing it remotely.
It seems to me that it should be possible to write something very
similar to CVSup using only the offical CVS client/server protocol,
which would allow anyone to backup any CVS repository they had access to
-- anyone looking for a project?
-Larry Jones
Geez, I gotta have a REASON for everything? -- Calvin
