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

RE: FSFS repo on a network share

From: <Ullrich.Jans_at_elektrobit.com>
Date: Tue, 24 Feb 2009 17:51:59 +0100

to throw in my two cents:
why not use svnadmin hotcopy to copy it over? AFAIK, that's what it's
meant for...


        From: Bolstridge, Andrew [mailto:andy.bolstridge_at_intergraph.com]

        Sent: Tuesday, February 24, 2009 12:25 PM
        To: users_at_subversion.tigris.org
        Subject: RE: FSFS repo on a network share

        The best option is to host your filesystem SVN repository on the
local drive and regularly copy it to the network share. Then you have a
'online backup', and an 'offline' backup as the IT guys do their thing.


        I'd set up a nightly copy using rsync, or xcopy to copy the data
across. Obviously you may need to consider your options carefully if the
DB is very large as all those little files can introduce quite a lot of
network latency. If you have a very large number, it might be better to
zip them all up and copy the zip file (or use svnadmin dump and copy the
dump file)




        From: James An [mailto:james_at_jamesan.ca]
        Sent: Monday, February 23, 2009 5:29 PM
        To: users_at_subversion.tigris.org
        Subject: FSFS repo on a network share


        I've created an FSFS repository and would like to put it in a
remote network location that is regularly backed-up.
        I've read that it's poor practice to directly access repos over
a network and that I should set up svnserve or Apache. The SVN book
mentions that network shares are bad for BDB repos, but doesn't really
comment on its use for FSFS ones. Some people say there are potential
problems for network repos that are accessible by multiple users.
        If the FSFS repo (on a network share) is restricted so only a
single user can access it, are there any risks to directly accessing the
repo with an SVN client? If I extend the permissions so that multiple
users can read-only access the repo, but only one user can write to it,
are there any additional risks? If so, is there any way to mitigate
those risks without a local SVN server at that location?

Please note: This e-mail may contain confidential information
intended solely for the addressee. If you have received this
e-mail in error, please do not disclose it to anyone, notify
the sender promptly, and delete the message from your system.
Thank you.
Received on 2009-02-25 05:04:46 CET

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.