Ready To Learn More?
Contact COOP Systems today and speak with one of our team members. We're pleased to talk about how our industry-leading solutions can optimize your Business Continuity program.
What's New at COOP?
Stay ahead of the curve. Sign up now to receive press release updates from COOP Systems as we disclose new features, partnerships and customers.
world class implementation
Customer Hosting Overview
For customer who choose to host themselves, the myCOOP™ architecture allows the use of multiple front end web/application servers to provide expansion and fail-over protections as well as multiple back end SQL databases for data redundancy and fail-over availability (see graphic below).
Initial installation can be completed with as few as two servers. This would include a front end web server running IIS and a SQL Server database server on the back end. Also needed is access to an Active Directory container which is used to house the myCOOP™ user accounts.
Customer Infrastructure Sample Requirements
- Web/Application Server can use multiple servers that may be load balanced via NLB
- Software: Windows Server 2003 R2 Std x64 SP2; Symantec Antivirus Corporate v10.1
- Hardware: two 146GB SAS HDD's in RAID 0; 4GB RAM; pair of 3 GHZ dual or quad core Xeon CPU's or equivalent
- Database Server can also use multiple servers may be mirrored for availability and scalability
- Software: Windows Server 2003 R2 Standard x64 SP2; SQL server 2005 SP1 Standard or Enterprise Edition; Symantec Antivirus Corporate 10.1
- Hardware: Four 146GB SAS HDD's in RAID 10; 8GB RAM (16GB preferred); pair of 3 GHZ quad core Xeon CPU's or equivalent
As Active Directory often functions as the user repository, many customers add a separate container for the myCOOP™ users.
COOP Systems Implementation
After implementing the hardware and software, COOP Systems engineers require terminal access to the newly provisioned machines in order to complete the configuration of the myCOOP™ application and provide ongoing support as needed.