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
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1220280
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-24 12:26:36 CET