Steve, You will need to get them nailed down regarding what they want before you can engineer a solution, but having worked government for a short while, that's like nailing jello to the wall.
That being said, here are a few thoughts for you regarding various solutions. - If you intend to have both servers up and running at the same time you will need to have licensing for all servers and users involved, hot backup licenses will not work in this instance. If you intend to do a hot/cold then you can get away with hot backup licenses on your secondary server. - Regardless you will not be able to do a 'server group' because that requires two instances of an app server to be pointing to the same DB instance, and the latency across the country would be too high to have the second app server on the other coast, plus it wouldn't give you the 'backup' portion of coop Just some things to think about. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Steve Michadick Sent: Friday, February 27, 2009 9:17 AM To: [email protected] Subject: COOP vs. High Availability Across Country Background: We're being tasked to engineer the Remedy solution for our fail-over site. However, the definition of that fail-over site keeps changing from a cold COOP site, to a High Availability sort of follow the sun site. With our current configuration, I believe that we can do a cold COOP site sufficiently, but not a High Availability. That would require more money and engineering. Current Configuration: Main Site (east coast)- Single ARS v7.1 ITSM 7.0 server (Win 2003 Server). Single Web server (IIS 6, Apache/Tomcat 5.5.27). Two SQL servers clustered (SQL Server 2005), with Db on a NetApps Filer. Alt Site (west coast) - Single ARS v7.1 ITSM 7.0 server (HOTBACKUP license). Single Web server. Single SQL server. (same OS and applications) Current COOP: SQL Db backed up at main site, sent to Alt site via robocopy, then restored. DNS change required for cut over. Questions: 1. What is the industry and/or BMC's "Standard" recommendation for doing COOP across country? What setup is recommended? What Hardware/Software/Licensing is recommended? A. Also looking at how to load balance or route users logging in to the Remedy server to the alt site only if the main site is down/gone. For this would I use server groups, HW load balancing (physically somewhere between the main and alt site), MS clustering (not sure if this is possible across country)? 2. Is it recommended or even possible to do High Availability across country? If not, why? If so, what would we need to add to our configuration/system to be able to do so (including licensing)? 3. If we wanted to do a follow the sun solution, what would we need to add to our current configuration to be able to do so (including licensing)? Steve Michadick Remedy Application Administrator Marine Corps Network Operations and Security Center (MCNOSC) Phone: 703-432-6726 ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
