On 4/20/07 6:32 AM, "Thompson, Graeme (AELE)"
<Graeme.Thompson@smiths-aerospace.com> wrote:
>
> Thanks Ryan,
>
> Does anyone know how to backup and restore the locks information when
> using svnadmin dump?
>
How about this - temporarily disable checkins to the repository and then do
a conventional backup of the repository. (no svnadmin dump) That will
definitely retain the locks.
-steve
> The hooks and conf can be easily done as they are in an obvious location
> and are simple text files....
>
> Thanks,
>
> Graeme
>
>> -----Original Message-----
>> From: Ryan Schmidt [mailto:subversion-2007b@ryandesign.com]
>> Sent: 20 April 2007 09:45
>> To: Thompson, Graeme (AELE)
>> Cc: users@subversion.tigris.org
>> Subject: Re: Svnadmin dump / load looses lock information
>>
>>
>> On Apr 20, 2007, at 03:33, Thompson, Graeme (AELE) wrote:
>>
>>>>> I have noticed that when a repository is dumped using
>> svnadmin dump
>>>>> and them loaded into a fresh repository using svnadmin
>> load it lost
>>>>> all of the locking information.
>>>>
>>>> [snip]
>>>>
>>>>> Is there anyhting that I am missing here?
>>>>
>>>> Yeah, you're missing the lock information. :-) Sorry, I couldn't
>>>> resist.
>>>>
>>>> As far as I know, the lock information simply does not get
>> included
>>>> in the dumpfile, and I don't know of another way to preserve it
>>>> across dump/load cycles.
>>>
>>> Does anyone know whether this is a design feature or is this a bug
>>> with the dump system?
>>>
>>> I would have expected that any repository restored from a
>> dump to be
>>> functionally identical to the original repository (after all it is
>>> intended to be a backup system to recover from server failures)
>>
>> I think it was a conscious decision to only include revision
>> data in dumps. Other data, such as information about locks
>> and the contents of the hooks and conf directories, is not
>> included. Backing up hooks and conf in other ways is easy.
>> I'm not sure how to back up lock data; I don't use locks myself.
>>
>>
>
>
> ************************************************
> The information contained in, or attached to, this e-mail, may contain
> confidential information and is intended solely for the use of the individual
> or entity to whom they are addressed and may be subject to legal privilege.
> If you have received this e-mail in error you should notify the sender
> immediately by reply e-mail, delete the message from your system and notify
> your system manager. Please do not copy it for any purpose, or disclose its
> contents to any other person. The views or opinions presented in this e-mail
> are solely those of the author and do not necessarily represent those of the
> company. The recipient should check this e-mail and any attachments for the
> presence of viruses. The company accepts no liability for any damage caused,
> directly or indirectly, by any virus transmitted in this email.
> ************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 20 14:38:34 2007