Re: hotcopy and clean-logs??

[Ryan Schmidt <su...@ryandesign.com>]

On Dec 31, 2007, at 15:15, George Georgalis wrote:

> Can I get some clarification on the --clean-logs
> switch for svnadmin?  What are "redundant Berkeley
> DB log files" and when would they arise?
>
> I'm using hotcopy weekly and doing tar bzip2 to the
> result. If there is an md5 difference between
> my hotcopy archive and the real backup I move the
> new archive to the backup.
>
> My problem is every time I tar bzip2 a hotcopy, I
> get a few bytes difference, even when there is no
> change to the repo.  I'm looking to get an exact
> archive from each hotcopy taken when the repo hasn't
> changed.
>
> Maybe the access times are updated or not duplicated
> with hotcopy?  Is there any way to change this
> behavior?

Have you tried doing the comparison before bzipping the archive? or  
even before tarring the folder? Maybe tar or bzip2 are introducing  
the differences.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: hotcopy and clean-logs??

[George Georgalis <ge...@galis.org>]

On Mon, Dec 31, 2007 at 06:47:44PM -0600, Ryan Schmidt wrote:
> On Dec 31, 2007, at 15:15, George Georgalis wrote:
>
>> Can I get some clarification on the --clean-logs
>> switch for svnadmin?  What are "redundant Berkeley
>> DB log files" and when would they arise?
>>
>> I'm using hotcopy weekly and doing tar bzip2 to the
>> result. If there is an md5 difference between
>> my hotcopy archive and the real backup I move the
>> new archive to the backup.
>>
>> My problem is every time I tar bzip2 a hotcopy, I
>> get a few bytes difference, even when there is no
>> change to the repo.  I'm looking to get an exact
>> archive from each hotcopy taken when the repo hasn't
>> changed.
>>
>> Maybe the access times are updated or not duplicated
>> with hotcopy?  Is there any way to change this
>> behavior?
>
> Have you tried doing the comparison before bzipping the archive? or even 
> before tarring the folder? Maybe tar or bzip2 are introducing the 
> differences.

yeah, I was thinking I could compare time stamps of archive and
repo and remake archive if it is older. is there a particular repo
file that is best to check for timestamp update?


I'm still interested in the --clean-logs switch, what context is
it needed?  I can't find anything other than in hotcopy help,
which doesn't actually explain, but assumes we know what are and
causes redundant log files. Do I have any? Do I ever need them?

// George


-- 
George Georgalis, information system scientist <IXOYE><

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org