 
|
| Mime-Version: |
1.0 (Apple Message framework v752.2) |
| Content-Type: |
text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed |
| Date: |
Wed, 29 Nov 2006 10:22:30 -0500 |
| Reply-To: |
|
| Subject: |
|
| From: |
|
| In-Reply-To: |
|
| Content-Transfer-Encoding: |
quoted-printable |
| Sender: |
|
On Nov 29, 2006, at 5:57 AM — 11/29/06, Kev Ward wrote:
> Hi Guys,
>
> I'm currently preparing a LISTSERV installation and need some
> information regarding system integrity.
>
> Our current deployment scenario is as follows:
>
> Windows 2003.
> Two separate servers containing identical installations of LISTSERV
> with one server to act as the Primary, which will handle all
> LISTSERV traffic sitting behind a virtual IP address. The other
> server acts as a “Warm standby.”
>
> Somehow, I need to keep the standby server in sync with the Primary
> so that in the event of the Primary failing, we switch to the
> standby, with potentially little or no loss of data.
>
> The issue here is how do we keep the second server up to date?
Why not use rsync? Google for it if you need information. This is the
tool that my colleagues who run Windows servers here, such as web
servers, use for keeping a DR server in sync with a production
server. It works nicely. Of course, you need a reasonably fast
network for it to work effectively.
|
|
|
