If you do the svn hotcopy or even svndump starting at 11:00pm, then all
commits up to 11:00pm will be included in the backup.
There is no need to stop the service.
You will have a full backup.
You might even have some of the atomic commits from after 11:00pm, but you
will have a fully functionaly backup with everything upto and including
11:00pm (with the possibility of having even more)
There is no need to stop the service.... but if you want to, it's not my
service, I ain't going to stop you
-Stephen
2009/5/5 Irfan Sayed <irfu.sayed_at_gmail.com>
> 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.
>
> 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.
>
> please advice.
>
> Regards
> Irfan.
>
>
>
>
> On Tue, May 5, 2009 at 3:37 PM, Olivier Sannier <obones_at_free.fr> wrote:
>
>> Irfan Sayed wrote:
>>
>>> i got the solution. as i am using apache for subversion, i will stop the
>>> apache service before i start the backup so that no one will able to access
>>> subversion URL
>>> Thanks all
>>> Regards
>>> irfan
>>>
>>
>> Except that your users won't get any message explaining why the servcr is
>> down.
>> Using a pre commit hook, you can put a message saying "backup in progress,
>> please come back later".
>>
>> In the end, you're the one deciding what way you'll do things, but I
>> always find it nicer to have a message explaining the situation instead of
>> being left with a dead server.
>>
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2067691
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-05 12:31:47 CEST