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

Re: Backup using ZFS Snapshots

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Thu, 15 Dec 2016 16:43:29 +0000

Mark Phippard wrote on Thu, Dec 15, 2016 at 09:40:43 -0500:
> 2. The easier approach is the start-commit hook. Just have a single master
> hook-script that all repositories are symlinked to. Assuming you do not
> use this hook for anything else, you can just have it in place with content
> like:
>
> exit 0;
>
> Then when you are doing a backup you change it to something like:
>
> echo "Server is in read-only mode for backup. It should be available again
> within N minutes"
> exit 1;

If you do this, you need to do the check in pre-revprop-change too,
because revprop changes don't call start-commit; and also in pre-commit,
in case a commit-in-flight is currently uploading data — has passed
start-commit but not yet called pre-commit.

> That said, based on the approach you are taking, I do not think you need to
> do any of this. Your ZFS snapshot of the filesystem can happen while a
> commit is happening since the ultimate backup will be done with an svnadmin
> hotcopy and that command will not care if the snapshot grabbed an
> in-progress commit.
Received on 2016-12-15 17:46:34 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.