You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Henrik Holst <he...@ecovision.se> on 2006/06/14 09:21:13 UTC

How to recover when the client is more up-to-date than the server

Hello,

  we had an accident where the repository storage crashed hard before
the daily backup was run so we are now in a situation where the clients
are seeing revision 69 and the server/repository is seeing revision 60,
that is 9 revisions where lost due to the crash and missing backup.

Now, is there any possibility to force out the missing revisions from
the client somehow? Even if it would be impoissible to exactly recreate
the 9 revision steps, is there any ways to force out a diff between the
current state on the clients as revision 61 to the repository and then
to force the clients to "downgrade" to revision 61?

Sincerely yours, Henrik Holst

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

Re: How to recover when the client is more up-to-date than the server

Posted by Henrik Holst <he...@ecovision.se>.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Jacob Atzen wrote:
<blockquote cite="mid20060614112019.GA1130@nezbo.dhcp.aub.dk"
 type="cite">
  <pre wrap="">On Wed, Jun 14, 2006 at 11:21:13AM +0200, Henrik Holst wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Hello,

  we had an accident where the repository storage crashed hard before
the daily backup was run so we are now in a situation where the clients
are seeing revision 69 and the server/repository is seeing revision 60,
that is 9 revisions where lost due to the crash and missing backup.

Now, is there any possibility to force out the missing revisions from
the client somehow? Even if it would be impoissible to exactly recreate
the 9 revision steps, is there any ways to force out a diff between the
current state on the clients as revision 61 to the repository and then
to force the clients to "downgrade" to revision 61?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I would do something like:

- Backup the current working copy to somewhere safe
- Remove every .svn folder from the working copy (thereby making it
  unversioned)
- Checkout a fresh working copy from the repository
- Copy the unversioned copy into the fresh working copy
- Commit the differences, creating r61
- Perform a fresh checkout on the rest of the clients

  </pre>
</blockquote>
Many Thanks for this tip, it really did the trick!<br>
<br>
/Henrik Holst<br>
</body>
</html>

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

Re: How to recover when the client is more up-to-date than the server

Posted by Jacob Atzen <ja...@aub.dk>.
On Wed, Jun 14, 2006 at 11:21:13AM +0200, Henrik Holst wrote:
> Hello,
> 
>   we had an accident where the repository storage crashed hard before
> the daily backup was run so we are now in a situation where the clients
> are seeing revision 69 and the server/repository is seeing revision 60,
> that is 9 revisions where lost due to the crash and missing backup.
> 
> Now, is there any possibility to force out the missing revisions from
> the client somehow? Even if it would be impoissible to exactly recreate
> the 9 revision steps, is there any ways to force out a diff between the
> current state on the clients as revision 61 to the repository and then
> to force the clients to "downgrade" to revision 61?

I would do something like:

- Backup the current working copy to somewhere safe
- Remove every .svn folder from the working copy (thereby making it
  unversioned)
- Checkout a fresh working copy from the repository
- Copy the unversioned copy into the fresh working copy
- Commit the differences, creating r61
- Perform a fresh checkout on the rest of the clients

-- 
Cheers,
- Jacob Atzen

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