[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: backing up of cvs repositories

From: Mark D. Baushke
Subject: Re: backing up of cvs repositories
Date: Sun, 04 Jun 2006 23:59:34 -0700

Hash: SHA1

ankush grover <address@hidden> writes:

> > I expect that this is generally what you want to use:
> >
> >   --exclude '#cvs*' --exclude ',*,'
> >
> > If you feel you want something more specific, then perhaps:
> >
> >   --exclude '#cvs.lock' \
> >   --exclude '#cvs.history.lock' \
> >   --exlcude '#cvs.val-tags.lock' \
> >   --exlcude '#cvs.rfl*' \
> >   --exlcude '#cvs.pfl*' \
> >   --exlcude '#cvs.wfl*' \
> >   --exlcude ',*,' \
> >   --exclude 'CVS'
> >
> hey Mr. Mark,
> Thanks for your guidance and efforts. I was able to backup and restore
> a cvs repository on a test machine.
> The command is like this
> rsyncz -avuptz --exclude '#cvs*' --exclude ',*,' --exclude 'CVS'
> srcpath    destinationpath

I am not familiar with the rsyncz command. Is it some variation on the
rsync command like the rsyncX command that Apple folks use under MacOS X
to deal with the extras like resource forks that may be present in the
HFS+ filesystem?

> a--> archive

- -a is shorthand for -rlptgoD on the rsync command-line.
(aka --recursive --links --perms --times --group --owner --devices)

> z---> compress
> v-->  verbose
> u-->update

Well, the --update switch would not let you incrementally improve your
destinationpath with the lastest changes. It would probably be okay for
a one-shot as long as you didn't get an exit 24 return code which means
that something was not properly copied.

> p--> preserve permissions
> t--> preserve  times
> On a test machine I created one repository, added a module made some
> changes to the file, commited those changes to the repository. Took
> the backup of that module, deleted that module  and then restore that
> module into that repository again with the command "cp -r module"
> Is this the right way of taking the backup and restoring the modules ?

I do not believe there is any single right way. There are many
possibilities. If your 'cp' command has a -p (preserve) flag, then I
suspect it may have been a slightly better approach. Even so, the 'cp'
is likely going to change the owner of the restored files unless you are
running it as root.

You could have used the same basic rsync command:

  rsync -auvz destinationpath/module srcpath/module

to do your restore.

        -- Mark
Version: GnuPG v1.4.3 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]