Due to lack of space and improvement of the server, I had to make a migration of the SVN server. When the operation was ended, all users could access to their projects without a problem.
But some users noticed that the files they had locked, they weren't, and other users could lock them instead.
The process I followed to make the migration was this.
Export from old SVN to dump file:
svnrdump dump http://svnserver/path/to/repository > /path/to/file.dump
Import dump file to new SVN Server:
svnadmin load --force-uuid /path/to/repository/ < /path/to/file.dump
I`ve repeated the import operation without --force-uuid parameter and I've got the same result.
Is there any way to keep the files locked doing a SVN migration?
Thank you.
Thank you all for your answers. I know the best practice to work with Subversion is with edit-merge method. I have always used it. But in this case, it is mandatory the use of files lock.
And other problem is that the new server environment has a different OS and a different version of Subversion, so I can't use hotcopy.
The solution that I found is copy the locks directory from old repository to the new one. The locks directory is placed in the db directory at the repository root (/old_server/repository_name/db/locks). I copy this to /new_server/repository_name/db/locks. Both repositories have the same name. After do that, users get their old locks as nothing was happened.