Hi
One thing to separate is the DR from the HA. 1. Will this architecture be feasible solution for failover and high availability? Let's look at the HA. You have a load balancer in front of the AR Servers in a server group. I have not seen a switch in front of 2 load balancers before but I guess that's HA on the load balancers themselves. So as far as HA is concerned, the application servers are good. You don't mention how the databases are. If they are in a cluster / RAC etc then that's good too. You don't mention about how you are getting your data from site A to B. But remember a few things. There are server references within the database so if you are doing any log shipping or db copy etc then remember that these need to be changed. Also, you have 2 options on the network side. You could allow your service desk / support users to have 2 servers configured in their User tool configuration and they know the DR procedure includes ticking the DR site and unchecking the prod site. End users in a DR situation (which is not that often in most cases, e.g. bomb, act of god etc) would have to phone the service desk to raise calls or the second option would be to get DNS to change the host names to the DR IP addresses. Although this could take time to propagate through the network etc and the same when you recover. In my experience, the time is ok as in a DR situation e.g. building collapse, bomb, flood etc, people are not rushing to raise change requests. How would those incidents look (Summary: I can't connect as my office is no longer there) J 2. How will we find out in case any of the server goes down? Is there any need for health check script to run on each of the ARS Server box to see if the server is alive or not? There are plenty of options here. If your company has any monitoring tools then all AR Servers have an SNMP interface. Some customers run simple cron scripts to check for the processes and email out when they can't find any etc. 3. To have a zero downtime at the time There is no such thing as zero downtime and every service including the AR System should have a maintenance slot per month / quarter etc. This is an important thing to remember as you could get mixed up in spending months trying to plan a zero down time solution. It's not reality. Just remember that to bring all other servers in the server group down except the one running the admin thread, make your changes, then bring the others up. As for coping to the DR site, that is not effecting your service SLA and can be done over the next few hours via log shipping/data guard etc. 4. Is there some recommendation for setting the stickiness value in the load balancer. If you have a load balancer in front of midtiers then set the session infinity (sticky) bit but not on the load balancers in front of the AR Servers. 5. Has someone used this kind of scenario with F5 Load balancer and can share how things are configured? Remedy only has a documentation with Cisco LB. I can request but I don't think we can share too much info at this site. If I can I will forward to your email and not on the list. 6. Are there any critical things you'd like to list which needs to be taken care of in this environment. Server references in the DB. This has been covered in the list. Licenses will be difference. Have all the licenses in the database e.g. the ones for your live and ones for your DR. The AR Servers are clever enough to find them. Remember that notifications that go to support groups have the midtier server address or the artasks will have the AR servers name in there so if you choose to not change the DNS then these links won't work. (Actually this may only be ITSM 7 etc but worth saying so) I think that's it for now..... J Hope this helps in some way. Kind regards Danny From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ankur Gulati Sent: 22 January 2009 14:35 To: [email protected] Subject: Issues::Remedy in Load balanced environment ** Hi Listers, I've been assigned a task of developing a load balanced environment for our remedy infrastructure. It has become a headache now since I am stuck with few things. Here's bit of description of the architecture. We have planned for having two sites A and B, A will be Primary and B a Disaster Recovery Site. On the top we have Users connecting through Citrix to any of the ARS application servers through two F5 1600 Load Balancer. The Load Balancers are in active - passive mode with a switch above them to shift the connection incase any of the LB goes down. Then we have 4 ARS application server all in Active mode in server group architecture. These servers have two Database to connect to. Databases are in Active - Passive mode. Each of these DBs are connected to their own SAN for storage. We will have a dataguard for replication of the database. DSO is not proposed in this architecture. We have a home grown application. ARS version 7.1.0 on Solaris 10 Oracle 10g on RHEL 5 Midtier 7.1.0 on Windows 2003 server Questions that concern us are: 1. Will this architecture be feasible solution for failover and high availability? 2. How will we find out incase any of the server goes down? Is there any need for health check script to run on each of the ARS Server box to see if the server is alive or not? 3. To have a zero downtime at the time of application upgrade, if we take one side completely down then is there an option in Load Balancer to restrict the users to access the admin server so that we can use it to do our workflow updates in the passive database. Then the dataguard will copy the changes from this database to the active. Is this scenario possible? if not then is there any other option where I can achieve zero downtime or minimal downtime for workflow and form updates. 4. Is there some recommendation for setting the stickiness value in the load balancer. 5. Has someone used this kind of scenario with F5 Load balancer and can share how things are configured? Remedy only has a documentation with Cisco LB. 6. Are there any critical things you'd like to list which needs to be taken care of in this environment. Any thoughts are appreciated.....! -- Ankur __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

