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

From: Henrik Holst <henrik.holst_at_ecovision.se>
Date: 2006-06-14 16:03:24 CEST

Jacob Atzen wrote:

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

  

Many Thanks for this tip, it really did the trick!

/Henrik Holst
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.org Received on Wed Jun 14 16:05:40 2006