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? 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.
