On 5/17/21 10:03 AM, Bo Berglund wrote: > On Mon, 17 May 2021 08:24:55 -0400, Mark Phippard <markp...@gmail.com> wrote: > >>> The current setup (v1.7) has the repo size of 500GB. we are using svn load >>> and svn dump method to migrate the repos from current setup (v1.7) to new >>> setup(v1.10) , but it takes a lot of time due to the size of the repo >>> (500GB) , Also the current setup (v1.7 is being currently used by the >>> customer ,soo even after taking the dump of one particular repo and loading >>> it in new setup , a newer revision is being made in the current setup >>> (v1.7 by the customer , thus making us to do the svn dump and lsvn load >>> again. >>> >>> now we need your help in identifying an efficient way in migrating the repo >>> from the current setup (v1.7 to the ew setup(v1.10) , Need your expert >>> advise on this please >>> >>> >>> Also let us know we can do rsync for this? >>> >>> Thanks & Regards, >>> Jackson J >> >> You do not have to do anything. Just point the new server at the existing >> repositories or move them to new location. You can use rsync, tar or >> whatever method you prefer. > > By the description it looks like the repository is *in use*, so there must be > two different Linux machines involved here. Not so easy to point the new > server > at tyhe same physical repo then. > And Jackson says that commits are also done during the migration process, > seems > like a not so good solution... > > A few years back I replicated our live SVN repository, to get a backup, by > using > a dump followed by a load on the replication server. The dump files were moved > over the Internet in tgz files before being used to load onto the new server. > > Then I set up svnsync to get the replica fully updated. That worked even over > the Internet, but my repo size was not as huge as here, only some 15 GB... > > Now the live server has a nightly svnsync script that keeps the two repos in > sync. If some network issues happen so that such a sync cannot be done then > the > following will catch up and make the replica current again. > > Something like that but running on the local LAN (for speed) would surely be > possible to migrate. > >
A faster method of copying the repository than dump while being read consistent would be svnadmin hotcopy. This allows the repository to be open while being copied. If possible you can NFS mount the destination location and hotcopy straight to it. Then you can use incremental dump/restore from the source to the destination to pick up changes until you are ready to do the final cutover. I've used this method many times. -- Dave
