Переместите жесткий диск с репозиторием SVN к другому компьютеру
Я соглашаюсь с MattB, что это вероятно не из-за входа в систему, локально устанавливающего.
Как сторона при установке анонимного пользователя для использования идентификационных данных пула приложений, только необходимо поддержать 1 пользователя. Это - моя предпочтительная установка. Обратите внимание, что необходимо отобразить 1 сайт на 1 пул приложений, или все сайты в пуле приложений должны доверять друг другу. Если это не так затем сохраните его со значениями по умолчанию.
To make life simple, I would install on the new server the same version of subversion server that you were using on the old box, even if it is not the latest version, and upgrade later once you have the data in place.
If the repository is the fsfs repository type, then you can just mount the repository and it will work, since fsfs is portable across OS and cpu architectures.
If you were using bdb, then you will need to ensure the target machine has the same OS and architecture, since bdb is not portable across environments. Even if you just us a machine of the same OS/architecture temporarily just to mount the repo so you can do a svnadmin dump to dump the contents of the repo in a text format, whch you can then load on your ultmate target machine without worrying about OS and architecture. (The dump format is portable across OS, architecture and svn version.)
See Strategies for Repository Deployment, which discusses portability of the various subversion repository types (bdb/fsfs).
Once svnserve is up and runing, hosting your repository, existing clients will need to relocate their working copies, using svn switch -relocate .
As far as I know, you shouldn't have any issue since the repository will have the same GUID. Just chekout/checkin on the new URL and everything should be fine.
I have not had an issue with simply redeploying a repository on another server. And, as long as you use the same OS, architecture, and Subversion version, there shouldn't be any issue. In fact, it's probably also true if you do use various operating systems, architectures, etc., but that is not guaranteed by the developers of the Subversion project. They make no promises in compatibility between Subversion versions, operating systems, or hardware architecture.
It's always safest to do an svnadmin dump when moving a repository. Then, doing an svnadmin load on the new system. It's guaranteed to work or double your money back!
In your case, since the old server isn't available, I would mount the repository on a machine that's configured as close as possible to the previous server. Do an svnadmin dump, move that to the new server, then do an svnadmin load.