Just remember to have a script to change server references within the database before you switch the DNS otherwise your disaster recovery server will not function correctly.
Regards Danny -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of patchsk Sent: 06 February 2009 06:59 To: [email protected] Subject: Re: Setting up Remedy Redundancy Server My2Cents: 1. Production Failover: We have Server A and Server B with Veritas Cluster (VCS). VCS maintains a shared drive like setting that arserver installation files and oracle dababase will reside on share drive with Server A active. Due to any hard ware problem if Server A fails, VCS points Server B to the share drive. So its basically one arserver installation shared between two CPUs(Computers). The failover is automatic,transparent and immediate. In case if you have your database remotely then you need to set up similar thing for database also. 2. Disaster Recovery: We have another separate remedy installation with its own database in a different location(Geographically Dispersed). This is a passive hot backup server. We start it only if fail over fails. Its not immediate. It takes around 15-30 min to get the users back to system. We point productionDNS/IP address point to the DR box during DR mode. So its transparent to the end users. We are using oracle data gurad to synchronize data between production db and DR db. For (1) since its basically one arserver installation you don't need to buy any separate license. For (2) I think you need to have a hot backup license I am not sure if its another term. I heard that its free since only one server will be up at a time , but I might be wrong. 3. ServerGroup. You need to have a load balancer configured for ServerGroup to have an automatic failover of user connections. Without the load balancer only certain process like Escalation, Email Eninge, Flashboards, DSO etc.. will be failed over among the servers in the servergroup. Not the user connections. Each server in the server group will have its own remedy installation, so you need to buy a arserver license for each server where as the fixed and floating licenses are stored in database and can be shared across the group. 4. For web users, we have several midtiers under a load balancer. So if one midtier fails only the users connected to that will see broken connection and all other users will use remedy as normal. Load balancer will take care of directing any new user connections to other midtiers. I am sure there might be some more better processes. Mostly what you choose depends on the budget,time and criticality of your application to your business. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" __________ Information from ESET NOD32 Antivirus, version of virus signature database 3832 (20090206) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
