subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nico Kadel-Garcia <nka...@gmail.com>
Subject Re: Temporary repository.
Date Wed, 11 Nov 2015 12:53:32 GMT
On Wed, Nov 11, 2015 at 3:51 AM, Andreas Stieger <Andreas.Stieger@gmx.de> wrote:
> Hi,
>
>> due, to a datacentre migration , a temporary SVN repository was set up to allow devs
to continue working for a week or two.
>>
>> When the PROD SVN repository is brought online what is the best method of adding
the changes  in the temporary repository back in to the Prod SVN repository ?
>
> Depending on your specific procedural requirements (relating to downtime etc), svnadmin
dump/load, svnrdump dump/load or svnsync.
> http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.reposadmin.maint.migrate
> The capable administrator can perform this completely transparent to users.
>
> Andreas

svnadmin dump/load does not bring commit scripts or file ownership. It
can also require downtime, and careful handling for updating the
replica. svnsync can be a bit more graceful about keeping a slave
up-to-date until the final moment, but also takes attention to make
sure all the hook-scripts and file ownership and .conf files get
replicated correctly.

If you're not changing the version of Subversion on the servers in the
process, it can often be safest and fastest to simply "rsync" the
content, schedule a switchover, *move aside* and disable access to to
the original server, take a final backup, and only then enable access
to the remote server.

Mime
View raw message