Laserfiche WebLink
SOLICITATION # CH16012 <br />The QTS cloud Security documentation is backed up in alternate site located Suwanee, GA to <br />include: <br />Software/operating Systems, Configuration Data and Security Documentation <br />QTS cloud Management Infrastructure and Configuration Data: <br />Richmond, VA: The Richmond Cloud Management Layer (Cloud Hypervisor Management Cluster) <br />and Customer data in the Service Delivery Hypervisor Cluster, and Configuration data is backed <br />and staged locally in Richmond on the management layer then backed up across the Site -to -Site <br />Management VPN to Atlanta, GA. This process is separate and independent of the Customers <br />Service Delivery Layer. Atlanta, GA: The Atlanta Cloud Management Layer (Cloud Hypervisor <br />Management Cluster) and Configuration data is backed and staged locally in Atlanta on the <br />management layer then backed up across the Site -to -Site Management VPN to Richmond, VA. <br />This process is separate and independent of the Customers Service Delivery Layer. <br />This process maintains both local and remote management layer data and configuration backup <br />for both locations. <br />Suwanee, GA: software/operating systems, configuration data and security documentation at <br />Rocstor Rocsecure Amphibious X7s with Secure -Encrypted Two -Factor Authentication, Utilizing <br />AES-256 CBC Real -Time Hardware Encryption, with NIST and FIPS 140-2 Certified Cryptographic <br />Modules, in a firerated safe located at Suwanee, GA. <br />SAP <br />Ariba <br />We have a warm site for failover. Equinix (Our primary data center) is located <br />in San Jose, California and our disaster recovery site is located at CenturyLink <br />Data Center in Sterling, Virginia. The act of failing over from the main data <br />center to the recovery site data center has a design goal recovery time <br />objective (RTO) of four hours. The design goal Recovery Point Objective <br />(RPO) is five minutes. <br />In the event of a fail -over to the disaster recovery site location, all URLs that <br />customers use to reach the San Jose data center will continue to work. We <br />will notify customers via their email addresses in the event of unplanned <br />downtime. <br />Internally, we use a documented system recovery plan that outlines the <br />approach and steps for recovering the applications. <br />The document defines roles and responsibilities in the event of disaster: <br />Local staff maintains the hardware remotely <br />We maintain the application software <br />Processes are in place to keep database and fileservers in sync between <br />primary and backup data centers <br />In the event of a catastrophe, we will declare the primary data center ""down <br />and our local staff will follow a script to start the applications at the remote <br />data center <br />We test power outage backup scenarios and the Disaster Recovery Plan on a <br />periodic basis. <br />Fieldglass <br />Please see the answer to Question 8.8.2A. above. Fieldglass' backup data <br />center is located in San Jose, CA. <br />Hanna <br />The backup of SAP systems in HEC is executed on EMC DataDomain <br />deduplication storage. This is done using EMC Networker for backup and <br />administration. The backups on Site A are also replicated to remote Site B. <br />For example, site A &B may be Santa Clara, CA and Sterling, VA, <br />respectively. <br />Hybris <br />In the case of catastrophic failure to your primary production data center, we <br />offer anywhere from best efforts to enhanced DR solutions. Enhanced DR <br />carahsoft 119 carahsoft <br />