very helpful thanks again eric On May 28, 2014 3:46 PM, "Eric Broch" <[email protected]> wrote:
> On 5/28/2014 2:41 PM, Dave M wrote: > > Thanks eric, > > > > I will have a look at that . > > > > > > > > On 5/28/2014 1:22 PM, Eric Broch wrote: > >> On 5/28/2014 12:47 PM, Dave M wrote: > >>> Replication. > >>> Anyone doing replication, ie to backup servers using Jakes replication > >>> videos, > >>> More specifically, anyone tried replication from master to two backup > >>> servers, > >>> I would like to see how it was done. > >>> > >>> FYI, I have successfully replicated from my Centos 5 qmailtoaster > >>> server to my new build Centos6 qmail toaster, > >>> As the New server was " empty " the only caveat I needed to do was , > >>> when syncing initially with " unison " > >>> mkdir -p /home/vpopmail/domains/dmain1.com > >>> mkdir -p /home/vpopmail/domains/dmain2.com > >>> > >>> etc, for all your email domains. > >>> Every thing else worked no problems. > >>> > >>> Dave M > >>> > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: > >>> [email protected] > >>> > >> Hey Dave, > >> > >> I have done the following for my own server and two clients' servers: > >> http://wiki.qmailtoaster.com/index.php/QMT_Failover_replication_Setup. > >> It is, unlike Jake's video, I think, in that when the primary server > >> fails a script (qmail-replicateb) must be run on the backup server to > >> activate it rather than > >> the servers running in unison. I have not yet used the backup server > >> after failure, so, I pretty much have my fingers crossed, but see no > >> reason why it won't work. > >> > >> Two things: > >> 1) I have DAG repo enabled to install unison rather than installing > >> 'manually.' > >> 2) I did change the call to unison in qmail-replicatec on the primary > >> server in the following way: /usr/bin/unison -force / -batch -owner > >> -group -times qmail >> $LOG 2>&1 > >> so that owner, group, and time information is replicated to the backup > >> server which means that the owner and group must exist on that server. > >> > >> Eric > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: > [email protected] > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > Dave, > > Also, I modified the backup server's unison server software 'run' script > (unison-run), below, adding 'status' capability, location of unison > binary under DAG rpm, and unison-run location: > > [begin script] > > #!/bin/sh > > #Script created by Craig Smith - [email protected] > #Script for Unison Start up shutdown > #Set the socket number in the /unison/unison -socket # line. > > # Source function library. > . /etc/init.d/functions > > case "$1" in > start) > # have a silent kill in case someone tries to start the service when it > # is already running > /etc/init.d/unison-run stop >/dev/null 2>&1 > echo -n "Starting Unison Socket Server" > /usr/bin/unison -socket 5301 & > echo $! > /var/run/unison.pid > echo "." > ;; > stop) > echo -n "Stopping Unison Socket Server" > kill `cat /var/run/unison.pid` > rm -rf /var/run/unison.pid > ;; > status) > status -p /var/run/unison.pid /usr/bin/unison > RETVAL=$? > ;; > help) > HELP > ;; > *) > echo "Usage: unison-run{start|stop|status}" > exit 1 > ;; > > esac > > [end script] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
