Title: RE: How to switch DB Server
**

Axton:

I have had to do this on several UNIX operating systems.  I don't think this is necessary for Solaris, which I do work with, but was required for AIX and HP-UX which I have worked with.

James McKenzie
L-3 GSI
 

-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton
Sent: Thursday, October 12, 2006 12:41 PM
To: arslist@ARSLIST.ORG
Subject: Re: How to switch DB Server

Reboot unix for network interface changes?  I don't think so.  This is how Veritas VCS works for hot backup configurations; though it does a little more as well (moun/unmount storage, etc.).

Axton

On 10/12/06, McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED]> wrote:
> **
>
>
> Axton:
>
> This would require a reboot for most UNIXes.
>
> I still like the idea of a load balancer on the front end feeding to
> two different ARS servers configured for database sharing.  This makes
> the load balancer responsible when the primary fails.  Of course, this
> depends on where the servers are located.
>
>
> James McKenzie
>
>
> ________________________________
>
> From: Action Request System discussion list(ARSList)
> [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton
> Sent: Thursday, October 12, 2006 11:47 AM
> To: arslist@ARSLIST.ORG
> Subject: Re: How to switch DB Server
>
>
> **
> Instead of using DNS to repoint traffic to the backup host, you can
> disable the ip on the primary node, then reassign the ip to the backup
> node.  Only delay will the the arp requests in this scenario. 
> Multiple ip's can be assigned to both hosts to ensure the machines stay network accessible:
>
>
> During normal operation (primary active):
> hostA (primary):
> trunk0: 10.1.1.100, 10.1.1.101
> hostB (backup):
> trunk0: 10.1.1.111
>
> During failover operation (backup active):
> hostA (primary):
> trunk0: 10.1.1.101
> hostB (backup):
> trunk0: 10.1.1.100, 10.1.1.111
>
> Your DNS would then have an A record for the following:
> remedy.company.com -> 10.1.1.100
> remedy_primary.company.com -> 10.1.1.101 remedy_backup.company.com ->
> 10.1.1.111
>
> Your users would simply log in to remedy.company.com, regardless of
> which node is active.
>
> To access the servers using other tools (ssh, sftp, telnet, etc), you
> can use the other hostnames (e.g., remedy_primary).
>
>
> Axton Grams
>
>
> 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
>
>         DISCLAIMER:
>
> ----------------------------------------------------------------------
> -------------------------------------------------
>
>         The contents of this e-mail and any attachment(s) are
> confidential and intended for the named recipient(s) only.
>
>         It shall not attach any liability on the originator or HCL or
> its affiliates. Any views or opinions presented in
>
>         this email are solely those of the author and may not
> necessarily reflect the opinions of HCL or its affiliates.
>
>         Any form of reproduction, dissemination, copying, disclosure,
> modification, distribution and / or publication of
>
>         this message without the prior written consent of the author
> of this e-mail is strictly prohibited. If you have
>
>         received this email in error please delete it and notify the
> sender immediately. Before opening any mail and
>         attachments please check them for viruses and defect.
>
> ----------------------------------------------------------------------
> -------------------------------------------------
>
>
>         __20060125_______________________This posting was submitted
> with HTML in it___
>         __20060125_______________________This posting was submitted
> with HTML in it___
>
>
> __20060125_______________________This posting was submitted with HTML
> in it___ __20060125_______________________This posting was submitted
> with HTML in it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

__20060125_______________________This posting was submitted with HTML in it___

Reply via email to