Laserfiche WebLink
SOLICITATION # CH16012 <br />the Order Form to allow Customer to retrieve Customer Data, or (ii) receives, <br />no later than thirty (30) days after the effective date of the termination of this <br />Agreement, a written request for the delivery to Customer of the then most <br />recent back-up of the Customer Data. SAP shall use reasonable commercial <br />efforts to deliver the back-up to Customer within thirty (30) days of its receipt <br />of such a written request, provided that Customer has, at that time, paid all <br />fees and charges outstanding and owed at termination. Customer shall pay <br />all reasonable fees and expenses incurred by SAP in returning or disposing of <br />the Customer Data. <br />SuccessFactors <br />I RPO and RTO are defined in the general terms and conditions <br />VMware <br />VMware Response: <br />VMware IaaS Services <br />VMware DR service. <br />We can discuss specific recovery information under NDA to participating entities during task order <br />negotiations as required. <br />AirWatch Hosted Services <br />We can discuss specific recovery information under NDA to participating entities during task order <br />negotiations as required. <br />FireEye <br />FireEye has a mature and documented Business Continuity Plan and Disaster Recovery Plan that <br />follows industry best practices that is reviewed and tested annually. The BCP/DRP plan has <br />RPO/RTO timing criteria and other critical business requirements that is available for review if <br />requested in the future. <br />VirtueStream <br />Basic Plus microVM's are designed for mission -critical workloads and for systems that require DR, <br />addition of reserved compute capacity in a secondary datacenter (i.e. Reserve uVM) and <br />automatic storage replication to facilitate the ability to restore operations in the event of an outage <br />at the primary data center. RPO and RTO for core microVM's are 15 minutes and 2 hours <br />respectively. <br />e. Describe your Recovery Point Objective (RPO) and Recovery Time Objective (RTO). <br />CA <br />APM <br />Recovery Point Objective (RPO): Maximum data loss: 24 hours <br />Data that is uploaded, but not backed up within the 24 hours may have to be re- <br />entered <br />Recovery Time Objective (RTO): 72 hours <br />MAA <br />Recovery Point Objective (RPO): Maximum data loss: 24 hours <br />Data that is uploaded, but not backed up within the 24 hours may have to be re- <br />entered <br />Recovery Time Objective (RTO): 72 hours <br />CA Agile <br />RTO: 2 hours <br />RPO: 12 hours <br />ASM <br />Recovery Point Objective (RPO): Maximum data loss: 24 hours <br />Data that is uploaded, but not backed up within the 24 hours may have to be re- <br />entered <br />Recovery Time Objective (RTO): 24 hours <br />Google <br />RPO/RTO objectives are zero hours. <br />AODocs <br />AODocs is hosted on Google App Engine which is designed to be highly available. Our standard <br />SLA is 99.5% . Specific financial penalties can be discussed as part of the AODocs license <br />contract. <br />Google App Engine is running in multiple datacenters on multiple continents. <br />carahsoft 109 carahsoft <br />