Hi Erik,
No of course things happen which we have no control over. That's part of
the fun/headache of IT right? ;-)
What I am saying I that I am surprised there are no tools available to
be able to recover a repository into a usable state. A simple(no such
thing I know) tool is all that is needed to be able to mark a revision
as bad and let and svnadmin dump/verify and the other tools work as they
should.
Do you think this is unreasonable?
Cheers,
Chris Melikian
Important: Fidelity Investments International (Reg. No.1448245),
Fidelity Investment Services Limited (Reg. No. 2016555), Fidelity
Pensions Management (Reg. No. 2015142) and Financial Administration
Services Limited (Reg. No. 1629709, a Fidelity Group company) are all
registered in England and Wales, are authorised and regulated in the UK
by the Financial Services Authority and have their registered offices at
Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11
9DZ. Tel 01732 361144. Fidelity only gives information on products and
does not give investment advice to private clients based on individual
circumstances. Any comments or statements made are not necessarily those
of Fidelity. The information transmitted is intended only for the person
or entity to which it is addressed and may contain confidential and/or
privileged material. If you received this in error, please contact the
sender and delete the material from any computer. All e-mails sent from
or to Fidelity may be subject to our monitoring procedures. Direct link
to Fidelity's website -
http://www.fidelity-international.com/world/index.html
-----Original Message-----
From: Erik Huelsmann [mailto:ehuels@gmail.com]
Sent: 29 June 2007 11:31
To: Melikian, Chris
Cc: Ulrich Eckhardt; users@subversion.tigris.org
Subject: Re: Re: Lack of Subversion repository recovery tools
On 6/29/07, Melikian, Chris <Chris.Melikian@uk.fid-intl.com> wrote:
> Hi Ulrich,
>
> I completely agree that you need to use backups but I think that
subversion should also have some tools to repair revisions so that you
can at least get the repository back into a consistent state even if
there is data loss.
>
> Surely, any production-ready version control system has such a tool?
And, given hardware failure (RAM chips?) how do you determine
consistency? Subversion provides tools to asses
consistency/correctness and prevents getting into an inconsistent
state under 'normal operation', but you can't expect it to be able to
recover from situations which aren't predefined, right?
Or would 'cutting the repository off at the last valid revision' also
match your requirement? (it sure doesn't sound like any help to me!)
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 29 14:51:07 2007