Den sön 22 maj 2022 kl 17:59 skrev Bo Berglund <bo.bergl...@gmail.com>: [...]
> 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.... > I would be more worried about doing Windows updates remote (even seen a server not coming online after an update?) than updating VisualSVN. The few updates I have done on VisualSVN have been seemless and, as you said yourself previously, as long as you have a valid support contract, I'm sure VisualSVN will be more than happy to help you resolve any problems. > 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? > If you have not used any of the advanced features in VisualSVN (ie, only using regular FSFS repositories and only Subversion authentication) you should be able to follow the same advise already given in the thread: Stop the service, copy the repository folders to the new server, configure the new server to use the existing authn/authz files, point the existing DNS names to the new server. As already pointed out you should check for any dependencies in existing hook scripts (in particular, if you have any binary hook scripts or using BATCH language). Kind regards, Daniel
