physically sits on a high availability environment made up of two HP V-class
series servers. The database sits on an EMC disk array that is shared
between the two servers.
I've set up the Server-name option in the ar.conf file to effective tell the
remedy server what its name is. After restarting remedy, it works just
fine.
We're using ARS 4.0.1 on HPUX.
Sean Christensen
Technical Specialist & Remedy Team Leader
Customer Service Support - IT, Franklins Limited
* desk - (02) 9722.1640
* mobile - 0412.029.054
* e-mail - christensens@franklins.com.au
"Let your Yes be Yes and No be No in all you do"
-----Original Message-----
From: Neil [mailto:disturbed@FREEWEBACCESS.CO.UK]
Sent: Friday, October 29, 1999 1:11 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: "Hot Spare" Server
We do something like this with Oracle on Solaris, but I'm sure the
principal will be the same.
We have two servers HFXSAM2 and HFXSAM3, and our Remedy app runs as
HXFSAM1. We update WINS to redirect our clients. We ship redologs to keep
the backup up to date, etc etc.
If you want more info mail me direct.
Neil Anderson
Remedy Developer
Halifax plc, UK
+44 (0)1422 830455
This message is attributable to the sender and does not necessarily reflect
the view of Halifax Group plc or its subsidiaries'
-----Original Message-----
From: HENDERSHOT,BRUCE D. [SMTP:HENDERBD@APCI.COM]
Sent: Thursday, October 28, 1999 12:50 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: "Hot Spare" Server
We're setting up a contingency plan for our Remedy server that will include
having a 'hot spare' server. Our intent is to keep the databases on both
servers synchronized by periodically copying the transaction log from the
production server to the spare and applying the changes to the database.
To
get around the problems related to the fact that the server name is
embedded
in the ARS workflow, we will use a 'Server-Name' entry in the ar.conf file
to specify the same alias name on both the production and the spare server.
This should cause the embedded references to contain the alias rather than
the server name. If we have a failure on the primary server, we'll modify
DNS to point the alias to the IP address of the hot spare server.
I'd be like to know if anyone has had any experience using either the
ar.conf Server-Name entry or the transaction log method of keeping two
databases in sync.
Environment:
Server: UNIX HPUX 10.2
Database: Sybase 11.5
ARS: 3.2
ooooooooooooooooooooooooooooooooooo
Bruce Hendershot
MIS Operations Engineering
henderbd@apci.com
610-481-8548
ooooooooooooooooooooooooooooooooooo
To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist
To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist
To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist