Dear SVN experts,

I am on a Debian linux system.

My fs-type is fsfs.

My svn version is 1.10.4

I am using a project management tool called Redmine which is the front
end for SVN projects and which in turn is relying on Apache as a web
server.

1. I wish to use :

svnadmin dump my-repository > my-repository-backup.dump

on a daily basis at the same time to backup my-repository.

Then I think  that I do *** not *** need to turn off Apache while
doing the above.

Suppose a commit is in process while I am running the above command. I
think SVN supports concurrency as far as commits go. But does SVN
support concurrency while using svnadmin dump? I do not mind losing
out information on that ONE commit since the next day that ONE
particular commit will get dumped into my-repository-backup.dump.
Is there any disadvantage to doing an svndump on a LIVE system ? Will
we experience transaction anomalies if we do this? Is there a way to
setup isolation levels for transactions in Subversion like in
databases?

I do not wish to use svnadmin hotcopy since it's output is not as
portable as svnadmin dump's output. I would need the same filesystem
to restore the svnadmin hotcopy output.

2. Suppose the www-data user is writing to the SVN repositories. My
query is : Should I put the backup cron job into the www-data user's
crontab or the root user's crontab?

My repository is owned by user : www-data and group : root

Many thanks,
Ashim

PS: I am not subscribed to this list so please CC me while responding
to this email.

Reply via email to