Backing Up a Repository
A CVS repository can be backed up using the
same backup tools and schedule that you use for ordinary text and
binary files. You must be able to restore the repository with the
same permissions and structure it had when it was backed up. You must
restore the CVSROOT directory and its contents
before the project directories are useful, but you can restore
project root directories and their contents independently of each
other.
If a file in a repository is being written to while a backup is in progress, it is possible that the file could be backed up in a state that might make it difficult for CVS to read it accurately when it is restored. For this reason, you should prevent processes from writing to the repository during a backup.
Freezing a Repository
Freezing a repository is CVS-speak for the act of preventing users from changing the repository. The most common reason to freeze a repository is to ensure that a backup operation copies all the repository files in a consistent state.
The simplest way to freeze a repository is to block clients from
accessing the CVS server. There are many ways to do this, such as
shutting down the CVS server program, disallowing logins to the
server system, blocking the server with a firewall rule, setting the
server to single-user mode, or pulling out the network cable. Rather
than blocking access to the server completely, you can use
CVS’s locks to read-lock the
repository.
To keep the server running and allow clients to continue ...
Get Essential CVS now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
