You can use the repShare command to make a slave repository
“shareable” so that multiple MDM Servers can load it. Conversely, you
must use the repExclusive command to return the slave to an
unshared state before synchronizing it, so that a single MDM Server can
issue the synchronization command.
An alternate method is to leave the slave shared and loaded, then:
1.
2.
3.
4.
Create a new slave from the Master.
Make that new slave “shareable.”
Load the new slave without ports in the background using the
repPreload command on each MDM Server that acts as a host.
After each host completes the background load, use the repSwap
command to swap the new slave for the old on the same port.