[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnserve & hotbackup of FSFS without user access

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-01-19 16:04:18 CET

On 1/19/06, Bill Williams <billwilliams@qcsoftware.com> wrote:
> I know there have been several questions asked recently about backing
> performing a hotbackup of FSFS. This one is a little different.
> We are a small development company about to start using subversion.
> Currently, I plan on having svnserve running as a daemon on our linux
> server.
> We use the tar command to perform a backup every night onto a tape.
> Since out backups are performed after midnight, we do not have
> developers accessing the system; therefore, we should not have any
> issues with changes occuring to the repository as the backup is performed.
> My question is will the backup be "good" if svnserve is running but no
> one is accessing the repository? My concern is if svnserve is somehow
> holding files opened (buffered data) which is not committed to the disk.

From what I've gathered, hotcopy won't hurt if you use it on an FSFS
repository. Is it required if no one's in the office? I think I'm
hearing "no" but I'd still be wary of not using hotcopy. Let's say,
for argument's sake, that you're into crunch time on a development
project. One of your developers is in the office late, and starts a
large commit at 11:55 PM. The commit is still running at the stroke
of midnight, and your backup starts at 12:05 PM, what happens?

My plan is to use hotcopy unless I can find a compelling reason why I
shouldn't. My current backup script keeps the past 7 days' hotcopy
backups on the server, available to the tape backup system.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 19 18:19:35 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.