Frank:
This is a much better solution. However, this does not allow for geographic separation of the two servers (or does it.)
I think the OP was looking for a COOP type of solution with the database remaining in place but the Remedy server failing.
If this is at the same physical location, a multi-system with one being the primary and the other a backup with the load shared amongst several systems, would be the ideal solution in this case. If the locations are physically diverse, this may be hard to implement.
James McKenzie
L-3 GSI
________________________________
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Frank Caruso
Sent: Thursday, October 12, 2006 11:17 AM
To: arslist@ARSLIST.ORG
Subject: Re: How to switch DB Server
** Have you looked into Server Groups and load balancing your Remedy servers? You could have two (or more) ARS servers pointing to the same database so that if one goes the other continues to function. Then you need only worry about database replication. This would eliminate the need for DNS changes.
On 10/12/06, McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED]> wrote:
**
Have you looked at Hot Backup licenses?
Also, you will have to force a DNS update that may take hours, depending on DNS aging and how you setup your internal network.
James McKenzie
L-3 GSI
________________________________
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Bellamkonda Viswa Chaitanya
Sent: Thursday, October 12, 2006 11:08 AM
To: arslist@ARSLIST.ORG
Subject: How to switch DB Server
**
Hello List,
We have Remedy Servers installed on 2 separate boxes and have identical setup. Incase of fail over of Server1 We would like to Switch Server2 to the Server1's Database. Can someone please suggest the best way to do implement this switching with minimal down time.
Thanks in advance.
-Viswa
