Does anyone know of a document that describes the pitfalls in running
an incoming mail server? Things like how to protect the hardware
against failure and/or running a [remote] secondary server. So far my
Google searches have produced nothing but specific server HOW-TOs.
David Segall wrote:
> Does anyone know of a document that describes the pitfalls in running
> an incoming mail server? Things like how to protect the hardware
> against failure and/or running a [remote] secondary server. So far my
> Google searches have produced nothing but specific server HOW-TOs.
It depends on which vendor's mail server you are running.
1) have at least two
a. Make sure the servers you choose are fault tolerant.
2) use centralized management
3) have a common storage that is Fault tolerant (drives, power supplies,
etc.)
AK
AK
>David Segall wrote:
>
>> Does anyone know of a document that describes the pitfalls in running
>> an incoming mail server? Things like how to protect the hardware
>> against failure and/or running a [remote] secondary server. So far my
>> Google searches have produced nothing but specific server HOW-TOs.
>
>It depends on which vendor's mail server you are running.
Why?
>
>1) have at least two
> a. Make sure the servers you choose are fault tolerant.
>2) use centralized management
>3) have a common storage that is Fault tolerant (drives, power supplies,
>etc.)
Thanks (again) AK but I was looking for a document that I could give
to a manager that they could give to the responsible staff member. The
manager's aim is that if anything goes wrong they could assure their
bosses that they had done everything reasonable to avoid the disaster
that has just occurred but to avoid it would have cost...
I'm not disputing your advice but I think it belongs in an appendix to
the document I am looking for :)
David Segall wrote:
> AK
>
>
>>David Segall wrote:
>>
>>
>>>Does anyone know of a document that describes the pitfalls in running
>>>an incoming mail server? Things like how to protect the hardware
>>>against failure and/or running a [remote] secondary server. So far my
>>>Google searches have produced nothing but specific server HOW-TOs.
>>
>>It depends on which vendor's mail server you are running.
>
> Why?
>
>>1) have at least two
>> a. Make sure the servers you choose are fault tolerant.
>>2) use centralized management
>>3) have a common storage that is Fault tolerant (drives, power supplies,
>>etc.)
>
> Thanks (again) AK but I was looking for a document that I could give
> to a manager that they could give to the responsible staff member. The
> manager's aim is that if anything goes wrong they could assure their
> bosses that they had done everything reasonable to avoid the disaster
> that has just occurred but to avoid it would have cost...
>
> I'm not disputing your advice but I think it belongs in an appendix to
> the document I am looking for :)
What I have outlined is the general principle involved in setting up and
managing a mail server deployment that provides resiliency and fault
tolerance. i.e. if email traffic spikes up, the cost of adding capcity
will be cheaper and pain free.
You can always write the document you seek. I have not looked for nor
know of a document that outlines what you seek which sounds more like a
CYA. There are many firms that have the capacity and ability to provide
your firm with the service for email handling which presumably your firm
now uses.
You must first define what the email solution must provide. Then you
can contact the various vendors to see whether they accomodate your
needs and at what price.
Each vendor's Email handling product has its own benefits and draw backs.
AK