On May 5, 2009, at 05:17, Irfan Sayed wrote:
> 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 you stop Apache, the repository will not just be unavailable for
write operations; it will be completely unavailable, for read-only
operations too. You can do as you please, but I wouldn't want to
impose that on my users, especially since (as has been discussed in
this thread) there is no need to.
> 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.
This is automatically achieved by using svnadmin hotcopy or svnadmin
dump. Shutting down access to the repository is not necessary to
achieve a full backup with complete data integrity.
> 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???
"svn lock" is not related to what you're trying to do.
> 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.
I suggest you leave Apache running and allow users to continue using
the repository as usual during the backup window. It will work fine.
If it will make you feel better to deny your users write access to
your repository during the backup, then still keep Apache running so
that read-only operations are still possible, but add code to your
pre-commit hook to lock out changes. If you allow revprop changes,
add the same code to your pre-revprop-change hook. An easy way to do
this would be for your backup process to touch a file (e.g. called
"BACKUP_IN_PROGRESS"), and remove it when done. Then your hook
scripts (if they're written in Bash) could begin with code like this:
if [ -f /path/to/BACKUP_IN_PROGRESS ]; then
echo "The repository is temporarily read-only because a backup is in
progress" 1>&2
exit 1
fi
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2091131
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-07 09:13:32 CEST