Actually, Jody... I have already looked at the information
in the FAQ's and
distributed around Netwin's site. I posted in that regard
yesterday. I
have done the research and as is probably apparent I am
still having issues.
Not to FLAME but...
If you do not have any real information that will help...
why bother
posting.
---
Thanks,
Chris Guest
-----Original Message-----
From: Jody McAlister [mailto:jodymac iscweb.com]
Sent: Friday, October 27, 2006 1:05 PM
To: surgemail-listnetwinsite.com
Subject: Re: [SurgeMail List] Mirroring Setup
Make sure you have read the mirroring FAQ and setup made my
netwin.
But to get the users to be on the slave, you need to issue
the
tellmail command on the master that sends the account
listings over.
I'll leave it cryptically blank so you look up the mirroring
page
setup by netwin that explains in detail how to do the whole
mirroring
thing. Not to be mean, but knowledge given is never as
valuable as
knowledge learned and I used it without a hitch. Plus it
explains
things that just giving you the type this command answer
would never
give you.
On Oct 27, 2006, at 7:48 AM, Chris Guest wrote:
> I've got the server mirroring... or I think I have it
partially
> mirroring.
>
> This is what I see on the Master Status:
> Mirror out: NoSSL Que/sent add=20209/15923 (782932332
bytes)
> del=31347/7135
> ren=22822/0/3681 qfile=0k -ERR rename
>
(/var/surgemail/grady.k12.ga.us/qc/hc/a.gordon/mdir/new/
> 1161946784.2789_5596
> 1.mail~2,(1911,10684)[1161961184])
>
(/var/surgemail/grady.k12.ga.us/qc/hc/a.gordon/mdir/new/
> 1161946784.2789_5596
>
> State: Done file ok
> Upto 0/-1 -0.0%
/var/surgemail/grady.k12.ga.us/eb/jg/c.yates
> Adding to que: 29388 0.4/s (reque=0)
> Sending to rmt: 24958 0.3/s
> Sent live: 0 0.0/s
> Gone before sent=0, Getlost ok=0, missing=0
> Mirror in: Received add=0 del=0 rename=0 fail=0
delfail=0
> renfail=0 p=0
>
> On the Slave Status I see:
> Mirror out: NoSSL Que/sent add=0/105 (3128 bytes)
del=0/0 ren=0/0/0
> qfile=0k
>
> State: OpenList2-NULL
> Upto 0/-1 -0.0% ./
> Adding to que: 8 0.0/s (reque=0)
> Sending to rmt: 7 0.0/s
> Sent live: 0 0.0/s
> Gone before sent=0, Getlost ok=0, missing=0
> Mirror in: Received add=15880 del=6891 rename=0 fail=0
delfail=2193
> renfail=3737 p=0
>
> Can anyone tell me if this looks normal?
> Also, I noticed that when I look under 'accounts' on
the slave...
> there is
> no users listed. The total says there are two in the
database but
> they do
> not display? Should I be able to see all the user
accounts just
> like I
> would from the master?
>
> ---
> Thanks,
> Chris Guest
>
>
> -----Original Message-----
> From: Jody McAlister [mailto:jodymaciscweb.com]
> Sent: Wednesday, October 25, 2006 6:33 PM
> To: surgemail-listnetwinsite.com
> Subject: Re: [SurgeMail List] Mirroring Setup
>
> Use the ip addresses of the servers instead of their
dns names in the
> mirror section and leave the rest of the surgemail
settings the same.
>
> If you are going to use the mirror as a backup only,
then you are
> done.
>
> On Oct 25, 2006, at 3:08 PM, Chris Guest wrote:
>
>>
>>> I read I was suppose to copy the surgemail.ini
over from Mail to
>>> Mail1...
>>> but never could get the server up. Not sure
exactly what to
>>> change...
>>> what not to change.
>>
>> What you need to change is server specifics. The
surgemail.ini from
>> the
>> master will have a few lines here and there that
are specific to that
>> server (ie the ip address and any urls). The slave
should have its
>> own
>> specific settings. The rest of the ini can and
should be the same
>> so the
>> users get the same result regardless of which one
they are on.
>>
>> [Chris Guest wrote:] That is the part that is so
confusing. When I
>> setup
>> the Mirror server which is mail1.grady.k12.ga.us...
do I run the
>> setup as if
>> I am setting up a completely different server for a
different
>> domain? Or...
>> do I set it up with the same domain as if it is
going to be the
>> mail server
>> for our domain?
>>
>>
>>> My ultimate goal is to have a failover server
to prevent email
>>> outage and
>>> loss. Any suggestions/recommendations would be
great.
>>
>> To fully realize that goal consider mitigating any
single point of
>> failure.
>> For example, do you have all servers in a single
location? If so
>> can you
>> move one to somewhere else that will not likely be
affected by
>> flood, fire,
>> power loss etc. Secondly will both be available on
the internet if
>> your ISP
>> fails? If not then you might want to find a backup
service for the
>> slave.
>>
>> [Chris Guest wrote:] I saw somewhere in my reading
about using a
>> floating
>> IP. Would that be the best way to handle the
failover so that
>> users would
>> never know if a server was down? What would the
best
>> implementation be to
>> achieve that?
>>
>> The nice thing about the surgemail mirror feature
is that once
>> configured
>> correctly you can use both servers and switch
between them at will.
>> So if
>> users find one to be slow they can switch to the
backup and get
>> better
>> performance (if its not network related slowness).
You will be
>> able to
>> achieve this relatively easily because your using
nwauth. Nwauth will
>> automatically be mirrored to the slave.
>>
>> Good luck.
>>
>> =================================
>> Kevin W. Gagel
>> Network Administrator
>> Information Technology Services
>> (250) 562-2131 local 448
>> My Blog:
>> http://mail.cnc.bc.
ca/blogs/gagel
>>
>>
------------------------------------------------------------
-------
>> The College of New Caledonia, Visit us at http://www.cnc.bc.ca
>> Virus scanning is done on all incoming and outgoing
email.
>> Anti-spam information for CNC can be found at http://avas.cnc.bc.ca
>>
------------------------------------------------------------
-------
>>
>>
>>
------------------------------------------------------------
-------
>> Confidentiality Notice: The information contained
in this message
>> is confidential and is intended for the addressee
only. If you have
>> received this message in error or there are any
problems, please
>> notify the sender immediately. The unauthorized
use, disclosure,
>> copying or alteration of this message is strictly
forbidden.
>>
------------------------------------------------------------
-------
>>
>
>
>
>
------------------------------------------------------------
-------
> Confidentiality Notice: The information contained in
this message
> is confidential and is intended for the addressee only.
If you have
> received this message in error or there are any
problems, please
> notify the sender immediately. The unauthorized use,
disclosure,
> copying or alteration of this message is strictly
forbidden.
>
------------------------------------------------------------
-------
>
------------------------------------------------------------
-------
Confidentiality Notice: The information contained in this
message is confidential and is intended for the addressee
only. If you have received this message in error or there
are any problems, please notify the sender immediately. The
unauthorized use, disclosure, copying or alteration of this
message is strictly forbidden.
------------------------------------------------------------
-------
|