On Mon, Apr 23, 2018 at 7:33 PM, Eric Johnson <eric_at_tibco.com> wrote:
> It should be OK to use rsync, so long as the "old server" is not in use and
> the repositories are not being modified while you're syncing them.
>
> Then, I strongly recommend a dump and load on the new server.
>
> Eric.
The "permissions" may not be what you expect if there is a discrepancy
between usernames and uuids. "cp" and "scp" don't preserve SELinux
permissions, which may matter if the Subversion repository is being
served as a web service. If I were working with "rsync", I'd use these
commands to do a dry-run first, then an rsync.
In general, to jump that many major revisions, I tend to use "svnsync"
to allow the repositories to stay synchronized while the client stays
talking to the first repository, then take the first repository
entirely offline. Note that this is probably the first opportunity, in
years, to obliterate content from the old repositories "and reset the
ID of the new repository, to avoid clients getting confused about
obliterated content.
Received on 2018-04-24 04:27:34 CEST