Old repo backup, checkout current, lost repo, create new repo?

[Tom Browder]

I have three svn repos I recently (6 months ago) moved to my private,
remote server. Due to life and negligence, I only have one svn hotcopy of
two of them made immediately after the move.

A week ago the disk with the three repos failed.

I have current copies of each repo’s trunk (I’m not not using branches) and
want to know the best way to get the repos back in place and working again.

I am the only user, and I use the svn+ssh access to the repo completely
owned by myself. History is not terribly important.

From what I can find in various docs, I think the easiest way to recover is
to copy the 6-month-old hot copy to the original path and resume working
from there as usual (plus make sure my backups work in the future!). For
the other I will just recreate the repo from scratch.

Given that history will be lost, does anyone see any problems with my
recovery plan?

Thanks for any advice.

Best regards,

-Tom

[Tom Browder]

...

Given that history will be lost, does anyone see any problems with my recovery plan?

...

If you have working copies and you don't care about history, why are
you spending any cycles on doing anything with hotcopy? You've lost
history anyway, why keep any of it?

...

So, again, would my plan work to re-establish my repo and work flow?

Ping? I really need some expert opinion here so I can proceed: is my
plan to replace the lost repos with their hotcopies okay?

Thanks.

-Tom

[Stefan Sperling]

Post by Tom Browder

...

Given that history will be lost, does anyone see any problems with my recovery plan?

...

If you have working copies and you don't care about history, why are
you spending any cycles on doing anything with hotcopy? You've lost
history anyway, why keep any of it?

...

So, again, would my plan work to re-establish my repo and work flow?

Ping? I really need some expert opinion here so I can proceed: is my
plan to replace the lost repos with their hotcopies okay?
Thanks.
-Tom

Your current working copy will be invalidated if repositories are
back-dated. The SVN client will complain that it cannot find revisions
which are not present in the old hotcopy.

So if you use the old hotcopy, you need to check out a fresh working
copy and then move your current files from your current working copy
over to the fresh working copy, record any tree structure changes with
'svn add', 'svn remove', or 'svn move' as appropriate, and then commit
the result. This giant commit will then contain a combined version of all
the commits you have lost. Then you can continue working with SVN as usual.

[Tom Browder]

On Mon, Dec 10, 2018 at 15:56 Stefan Sperling <***@elego.de> wrote:
...

Thank you, Stefan!

Best regards,

-Tom