[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: James An <james_at_jamesan.ca>
Date: Thu, 26 Feb 2009 13:26:18 -0500

Thanks guys.

I was thinking about just using file:// since it would greatly simplify
everything, but worried about the consequences.

Currently, the setup I've implemented is clumsy. Because of the
confidentiality of work between researchers, they currently run a local
Apache service (logged in as them through the network to get the right
privileges to access the repo). The service authenticates against the
Windows authentication (Active Directory?), which svnserve can't do
(easily). So access to repos are by HTTP requests to the local workstation.

It works, but it's clumsy because:

   - there's a bunch of local Apache services running, when it should really
   be centralized at the server where the repos are stored,
   - user passwords are regularly changed and the researchers have to
   re-input their passwords for the local Apache service to continue to log in
   as them (to get the correct privileges to access the repo), and
   - the local workstation where the service is run has to be on (and logged
   in?) in order for the manager (the only other person accessing the repos) to
   access the remote repo

Am I circumventing the safety measures by having the SVN server retrieve the
repo over the network?

I don't have full access to the server that stores all these repos as I'm a
researcher myself. The IT folks don't want to maintain a collection of
research repos, so I'm looking for a work-around that is not as clumsy. -_-


On Tue, Feb 24, 2009 at 11:51 AM, <Ullrich.Jans_at_elektrobit.com> wrote:

> Hi,
> to throw in my two cents:
> why not use svnadmin hotcopy to copy it over? AFAIK, that's what it's meant
> for...
> Cheers,
> Ulli
> ------------------------------
> *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
> Hi,
> 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<http://svnbook.red-bean.com/en/1.2/svn.reposadmin.create.html>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?
> Thanks,
> James
> ----------------------------------------------------------------
> 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.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-26 19:32:28 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.