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

Re: Subversion backup

From: <kmradke_at_rockwellcollins.com>
Date: Tue, 5 May 2009 09:00:19 -0500

Irfan Sayed <irfu.sayed_at_gmail.com> wrote on 05/05/2009 05:17:16 AM:

> there will be a proper communication well in advance will be sent to
> development community mentioning the backup window with mentioning
> that access to repository will be unavailable for any write / update
> operation during backup so that they will also aware that daily
> backup happene between specific time frame and no one will try to
> access svn repo.
>
> if i am taking daily full backup then that backup shud be full proof
> including all the commit operation. in my daily full backup i dont
> want any commit operation left unbackedup. if backup is
> getting started at 11.00 PM then all the commit operation till 10.59
> PM shud be there in backup with full data integrity.

Both svnadmin hotcopy and svnadmin dump will be a full valid backup
as of the revision the backup started. If commits happen during
the hotcopy or dump timeframe they will be considered part of the
next days transactions.

> this is what i want. because of this only i want to lock the repo. i
> red the svbook but as per design as of now svn only gives file level
> locking mechanism and not dir. level lock mechnaism so i cant use
> "svn lock" is this correct???
>
> as there is no any full proof lock mechanism on repo level , i dont
> have other option but to stop the apache service to disable the svn
> URL access.

There is no need to lock out users during the backup time period
like other systems, but if you want, you can either disable the
apache service, reconfigure apache to put up a "backup in process"
message, or use a pre-commit hook on the repositories stating
that a "backup is in process". But I repeat, there is no
need to "lock" the database during backups since the hotcopy
and dump commands have been designed to correctly copy the
repository contents as of the revision number when it started.

Another option is to backup each revision as an incremental
dump as it occurs to a secondary storage device/location using
a post-commit hook.

See:
http://svn.collab.net/repos/svn/trunk/tools/server-side/svn-backup-dumps.py

Lots of options. No need to lock your users out during the backup
timeframe, but as others have stated, you can do anything you want.

Kevin R.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2069659

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-05 16:01:58 CEST

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