Re: syvnsync or svnadmin dump?

On Monday 01 Nov 2010, Les Mikesell wrote:
> On 11/1/2010 4:23 PM, Taro Fukunaga wrote:
> > Dear users,
> >
> > From what I've read, svnsync is *intended* for mirroring repositories
> > (in read-only fashion) while svnadmin dump is for dumping a repository
> > (for the purpose of loading it to a new repository). If I wanted to
> > migrate a repository from one server to another, which solution is
> > better? Is there a rule like, "never use svnsync for migration" or
> > "svnadmin must be used for migration"? I don't find hard rules about
> > this so I don't know if it's up for interpretation.
>
> Dump/load is probably a bit simpler since you can shut down your
> svnserver/http remote access to make sure nothing changes and loading to
> an empty repository sets the uuid from the dump to maintain
> compatibility with checked-out workspaces. But, svnsync should work
> too, or there wouldn't be much point to having it. You need to fix up
> the hooks to match the old version either way.

If downtime is an issue or if like me the dump/load takes a very long time
then it is possible to do this whilst the original server is still running.
Do the main dump/load then take a second dump using the --incremental option
and start it at the next revision of the original dump. This second dump/load
should be much quicker and the server downtime will be kept to a minimum.

The dump/load approach is also useful if you want to prune the repository
whilst moving it. ie, if you're splitting it into several new repositories or
prermanently removing certain paths.

-- 
__________________________________________________________________________________
Sword Ciboodle is the trading name of ciboodle Limited (a company 
registered in Scotland with registered number SC143434 and whose 
registered office is at India of Inchinnan, Renfrewshire, UK, 
PA4 9LH) which is part of the Sword Group of companies.
This email (and any attachments) is intended for the named
recipient(s) and is private and confidential. If it is not for you, 
please inform us and then delete it. If you are not the intended 
recipient(s), the use, disclosure, copying or distribution of any 
information contained within this email is prohibited. Messages to 
and from us may be monitored. If the content is not about the 
business of the Sword Group then the message is neither from nor 
sanctioned by us.
Internet communications are not secure. You should scan this
message and any attachments for viruses. Under no circumstances
do we accept liability for any loss or damage which may result from
your receipt of this email or any attachment.
__________________________________________________________________________________