Tony Stevenson <t...@pc-tony.com> writes:
>> It is possible to do the operation on a copy of the slave repository and
>> keep the existing slave repository online but this requires doing
>> somthing to ensure that revprop changes made on the master during the
>> svnsync get to the copy.
If there is diskspace to have the copy on the same disk then one option
is to the leave the slave online. When the svnsync finishes on the copy
the slave will have up-to-date revprops. Then replace the slave
repository with the copy repository but keep the revprops:
- hotcopy the slave repository
- do the rewind/backdate/recover/svnsync operation on the copy
- stop apache
- move copy repository's db/revprops/ away
- move slave repository's db/revprops/ into copy repository
- move slave repository away
- move copy repository to replace slave repository
- start apache
The move operations are quick on the same disk, so the repository is
only offline for a short period.
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
