Laserfiche WebLink
SOLICITATION # CH16012 <br />Fieldglass <br />Fieldglass houses all backup data vaults within its production data centers. <br />Replicas of the vault are performed continuously across data centers more <br />than 1,000 miles apart. <br />SuccessFactors <br />All data is backed up to the secondary site and can be restored from there in <br />the event of a disaster recovery event at the primary site. <br />VMware <br />VMware vCloud Air Data Protection provides backup storage to disk <br />FireEye <br />All backup and restore procedures are in compliance with SOC 2 specifications. Data and server <br />ima es are backed up digitally and replicated to datacenters in geographically different locations. <br />VirtueStream <br />Virtustream performs backups on a nightly basis and replicated offsite for further protection. The <br />retention policies are determined by State of Utah per landscape and will be documented during <br />the on -boarding process. <br />Backup data is stored on local enterprise class disk storage systems and can be replicated to <br />systems in a secondary Virtustream datacenter. All of Virtustream backup is disk based solution. <br />Encryption keys are generated at the time of backup application install on the Client VM(s). <br />Encryption keys are at least AES-128 but can be AES-256. Keys are stored on the backup system <br />databases using the encryption key management tool, the data about the keys on the database is <br />in a unreadable format and cannot be decrypted <br />Alternate data center strategies for primary data centers within the continental United States. <br />CA <br />APM <br />The location where data is stored is generally in the country where the contract is <br />executed. <br />MAA <br />The MAA service is currently available from one data center only. <br />CA Agile <br />We have a hot/warm data configuration with both data centers located within the US <br />but —1300 miles apart. <br />ASM <br />ASM has a warm standby with near time data replication between the data centers. <br />Google <br />Google does not use the N+1 data center assignment due to the risk of cascading failures. <br />Google's infrastructure makes a dynamic decision for each unique login session which data center <br />is the closest, most highly available data center and which data centers will be used as secondary <br />and tertiary. This assignment would shift for that session throughout the day based on availability <br />and is done completely seamless to the end user. <br />Virtru <br />We utilize multiple availability zones in AWS, and backup all data stored in our database to <br />se arate datacenters <br />Salesforce <br />Customer Data for customers in Salesforce's Government Cloud is stored in two of our U.S. data <br />center locations. <br />The Salesforce service performs near real-time replication at each data center and annual disaster <br />recovery tests for the service verify the projected recovery times and data replication between the <br />production data center and the disaster recovery center. The disaster recovery site is a 100% <br />replica of the primary production site of capacity (host, network, storage, data). Data is transmitted <br />between the primary and disaster recovery data centers across encrypted links. Additionally, back- <br />ups of data are performed and data is retained on backups at the geographically separated <br />disaster recovery data center location. <br />ServiceNow <br />Please see our response to 8.8.2a <br />QTS <br />The QTS cloud alternate storage sites are located at the following data centers: Richmond, VA, <br />Atlanta, GA, and Suwanee, GA. <br />The entire QTS cloud is a unified standalone Active cloud architecture and is backed up in both <br />Atlanta and Richmond to include: <br />Customer data in the Service Delivery Hypervisor Cluster, and; <br />Cloud Hypervisor Management Infrastructure and Configuration backups. <br />carahsoft 118 carahsoft <br />