On Sun, 22 May 2022 08:40:55 -0400, Nico Kadel-Garcia <nka...@gmail.com> wrote:
>On Sun, May 22, 2022 at 4:24 AM Andreas Stieger <andreas.stie...@gmx.de> wrote: >> >> Hi, >> >> On 5/18/22 16:54, Mark Phippard wrote: >> > If you can use the same DNS hostname for the new server there will be >> > no impact on your clients >> >> >> Except for possibly a change server-side certificate which may have >> changed (and not properly verified before). Can be addressed with >> testing, and it helps to use a service name instead of a host name. >> >> If you are looking to make this seamless, you can set up replication and >> write-through proxying as you move the configuration and scripts first. > >Why would you want to move a Subversion server to a Windows system? I think that he said: >>>We need to move Subversion off of a Windows 2012 server and onto a Windows >>>2019 server. So the relevant question for him is what kind of server they are running... If it is VisualSVN then they should go to that maintainer and ask for help. >There are real performance tuning issues for either httpd or svn+ssh >based access which are more easily handled in a Linux or UNIX >environment, and high reliability and backup setups far more difficult >to resolve in a Windows environment. > >Definitely activate an svnsync to allow the new service to run in >parallel for a while, and to avoid any split-brain issues. I have a similar problem where I have installed VisualSVN back in 2017 on a Windows 2016 Server and now I face problems keeping it updated. It is still on VisualSVN 3.7.0 and since I am remote to the server by 8,500 km I do not really dare experimenting with the updates.... This server runs SVN version as follows: H:\>svn --version svn, version 1.9.7 (r1800392) compiled Nov 21 2017, 12:52:53 on x86_64-microsoft-windows6.1.7601 It is still working but should be upgaded, only I don't know how to do it safely. The server is svn synced nightly over the Internet to a server I host in my premises, which is an Ubuntu Server 20.04.4 LTS and this runs: ~$ svn --version svn, version 1.13.0 (r1867053) compiled Apr 8 2022, 09:43:33 on x86_64-pc-linux-gnu On Linux the subversion upgrade is seamless with the apt program used to update/upgrade the whoile computer. So the OP (and myself) really need to create a Linux server to host the Subversion service going forward... What would be the proper way to migrate to a Linux based server and keeping the repository structure the same and allow user seamless access to these? -- Bo Berglund Developer in Sweden
