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

Re: Questions about a script for regular backups

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 27 Aug 2019 09:29:22 -0400

On Tue, Aug 27, 2019 at 5:06 AM Johan Corveleyn <jcorvel_at_gmail.com> wrote:

> On Mon, Aug 26, 2019 at 9:01 PM Mark Phippard <markphip_at_gmail.com> wrote:
> >
> > On Mon, Aug 26, 2019 at 1:29 PM Anton Shepelev <anton.txt_at_gmail.com>
> wrote:
> >>
> >> I have now set up a post-commit hook that makes an
> >> --incremental hotcopy. With the destination on the same
> >> machine's HDD, it takes about two seconds, but with a
> >> network share it lasts 30 seconds. Is it expected behavior
> >> for committing a tiny change in a text file? If not, then
> >> where shall I look for the possible performance problems? I
> >> have svn 1.8.16.
> >
> >
> > It is probably due to slowness of the IO across network to read what is
> in the target repository and then copy over the files. Other than tuning
> NFS or whatever you are using there is not much you can do. This is why my
> first recommendation was to use svnsync. You could have a second backup
> server running and then use svnsync via https or svn protocol to that
> server. This basically replays the commit transaction so performs
> comparably to the original commit. It also makes it a lot easier to send
> the backup around the world or to another data center since it is using a
> protocol that is meant for that sort of latency.
> >
>
> Does svnsync also copy locks and hook scripts?
>

No, neither of those are synced. You would not want the hooks to sync
since you need to run different hooks on the backup server but locks are a
problem for people using that feature.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2019-08-27 15:29:42 CEST

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