You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Luke Mauldin <lu...@icloud.com> on 2021/11/02 21:09:36 UTC
Svnadmin verify question
Can anyone tell me the details of the svnadmin verify command? Does subversion store any internal hash of each commit to verify its correctness and that it has not changed over time due to disk/memory errors or software bugs?
Luke Mauldin
Re: Svnadmin verify question
Posted by Luke Mauldin <lu...@icloud.com>.
Does the Svnadmin verify do checksum checks? How does it verify validity?
> On Nov 3, 2021, at 1:44 PM, Nathan Hartman <ha...@gmail.com> wrote:
>
> On Tue, Nov 2, 2021 at 5:09 PM Luke Mauldin <lu...@icloud.com> wrote:
>>
>> Can anyone tell me the details of the svnadmin verify command? Does subversion store any internal hash of each commit to verify its correctness and that it has not changed over time due to disk/memory errors or software bugs?
>>
>> Luke Mauldin
>
> Yes. The purpose of 'svnadmin verify' is to check for exactly those
> kinds of errors.
>
> By default it runs through each revision one-by-one and stops/reports
> if it finds a problem. There's also a --keep-going option since SVN
> 1.9.
>
> It is a good idea to run 'svnadmin verify' periodically on
> repositories to ensure their integrity.
>
> It is also crucial to have a good backup process in place, i.e., keep
> multiple good up-to-date backups of repositories in different physical
> locations and make sure you can restore from them before disaster
> strikes. Obviously it's of no use to detect corruption if you don't
> have backups to restore from.
>
> Hope this helps,
> Nathan
Re: Svnadmin verify question
Posted by Nathan Hartman <ha...@gmail.com>.
On Tue, Nov 2, 2021 at 5:09 PM Luke Mauldin <lu...@icloud.com> wrote:
>
> Can anyone tell me the details of the svnadmin verify command? Does subversion store any internal hash of each commit to verify its correctness and that it has not changed over time due to disk/memory errors or software bugs?
>
> Luke Mauldin
Yes. The purpose of 'svnadmin verify' is to check for exactly those
kinds of errors.
By default it runs through each revision one-by-one and stops/reports
if it finds a problem. There's also a --keep-going option since SVN
1.9.
It is a good idea to run 'svnadmin verify' periodically on
repositories to ensure their integrity.
It is also crucial to have a good backup process in place, i.e., keep
multiple good up-to-date backups of repositories in different physical
locations and make sure you can restore from them before disaster
strikes. Obviously it's of no use to detect corruption if you don't
have backups to restore from.
Hope this helps,
Nathan