On Fri, 27 Dec 2024 15:52:58 -0600, Ryan Carsten Schmidt
<subversion-2...@ryandesign.com> wrote:

>On Dec 27, 2024, at 15:44, Bo Berglund wrote:
>> 
>> Well there are 11 repositories totalling 18.8 GB in size
>> So a full backup is not a simple task, also regarding disk space on the
>> virtualized server. Don't know how much disk it actually has.
>
>You could do a trial run on a local machine instead of the server. 

I can't do that since I don't have another Windows machine with a Subversion
server...

All my other devices except my laptop are Linux boxes.

The Windows Server 2016 runs VisualSVN 3.7
and it uses svn version 1.9.7 (r1800392)

I know that there are upgrades but I have never understood how to do the upgrade
while protecting our data. And now it is a really long step from where we are to
the current version....

Another question:
-----------------
Can I use the direct svn commands in a command prompt window (using cmd.exe) to
load dump files while the VisualSvn service is stopped?

I have stopped the service so that no accidental commits can be done before the
repositories are up-to-date as per Dec 6th. Now at July from the old computer
backup. And I can still use the svn command line program.

NEW TESTING IDEA?
-----------------
Is it possible to do an in place "clone" of one of my smaller repositories with
missing changes to a separate repo which has all the same content but a
different name?

If the *repo name* is part of the dumpfile *content* so it must be applied to
the same name repository then this would not work of course...

If the dump file I have for the original repository *can* be used on the clone
instead with the suggested commands in a cmd window then I can do a real test
before I touch the actual repositories...

In that case what would be the best approach to copy the repository?

Can I issue a copy command on the command line for the repository top directory
to a new directory name or do I have to do something else?
Will windows copy the full content inside the directory if I do this:

copy source_repo_directory_name new_repo_name


-- 
Bo Berglund
Developer in Sweden

Reply via email to