On 21 Jan 2004, [EMAIL PROTECTED] spake:
I'm installing Cyrus on a ssytem that will have access to an IBM
FAStT SAN with GPFS (a parallel filesystem allowing multiple servers
to share a filesystem on a SAN).
For redundancy, I was thinking of creating the IMAP folder dir and
spool dir on the
I'm installing Cyrus on a ssytem that will have access to an IBM FAStT
SAN with GPFS (a parallel filesystem allowing multiple servers to share
a filesystem on a SAN).
For redundancy, I was thinking of creating the IMAP folder dir and spool
dir on the SAN and then having two mailservers setup
Prentice Bisbal wrote:
I'm installing Cyrus on a ssytem that will have access to an IBM FAStT
SAN with GPFS (a parallel filesystem allowing multiple servers to share
a filesystem on a SAN).
For redundancy, I was thinking of creating the IMAP folder dir and spool
dir on the SAN and then having
Ken, I'm not too familiar with QFS SANs. Does that have a filesystem
interfacewhere the filesystem itself allows multiple SAN clients to
access the same filesystem, etc?
What if the 2nd system was treated as a hot spare, and would't actually
do any mailserving functions until the primary
Prentice Bisbal wrote:
Ken, I'm not too familiar with QFS SANs. Does that have a filesystem
interfacewhere the filesystem itself allows multiple SAN clients to
access the same filesystem, etc?
Yes, its a shared filesystem. Multiple clients can r/w simultaneously.
What if the 2nd system was
Prentice Bisbal wrote:
For redundancy, I was thinking of creating the IMAP folder dir and
spool dir on the SAN and then having two mailservers setup identically
using cyrus. If the primary server goes down for any reason, the
secondary would automatically begin receiving/delivering mail based
