Back-up and Disaster Recovery. 1. CI shall back-up Customer’s data daily and retain those back-up copies for use in disaster recovery.
Back-up and Disaster Recovery. The Contractor shall provide a fully scalable and robust suite of solutions to satisfy the State’s backup and recovery needs. The Contractor shall investigate, develop and integrate the CIVLS backup and disaster recovery plan into the overall State-wide backup and disaster recovery plans. This effort shall be led by the Contractor’s operations and maintenance team collaborating with DMV and DOIT. The Contractor shall provide a complete failover environment of redundant components if any primary production component fails. The backup and disaster recovery facilities are designed to provide full recovery from catastrophic failure, such as an entire hosting center failure. The Contractor’s CIVLS Solution shall be configured in order to blend into a highly configurable disaster recovery solution. The Contractor shall leverage the use of a SAN system that provides a shared disk resource for all servers that make up the platform for CIVLS. By using this shared device, operating system and data drives on each server can be backed up quickly without affecting server performance or the application running on the server. This process, called “snapshots” can be enabled quickly and executed in minutes. Snapshots can be replaced quickly by the host server to enable a recover from a hardware failure or from a degraded application or operating system module. By leveraging this technology, the Contractor’s platform is positioned to meet DMV’s recovery needs well into the future. For long-term off-site data preservation, the Contractor shall provide a virtual tape library (“VTL”) solution to back up snapshots of data volumes that host database or file data. By using a VTL, information life cycle management can be achieved through migration of data from high-performing storage to inexpensive tape media. Specifically, primary SAN disk storage may be reduced by moving older snapshots to the VTL, which then can migrate the data to backup tape. This solution also is positioned to take advantage of the existing backup infrastructure already in the DMV network. Data recovery of systems and servers can be achieved using the same technology by replaying the snapshots back to the primary SAN volume that the degraded or affected server uses. By using this technology, high-performance database systems and applications can be recovered quickly with little downtime.
Back-up and Disaster Recovery. (a) BBDS shall not be responsible for backing up data on products that were not sold by BBDS, and is only responsible for backing up data in accordance with a BDR SLA.
Back-up and Disaster Recovery. Vendor shall provide backup, disaster recovery and storage capabilities so as to maximize availability of the Services during an event that would otherwise affect the delivery of the Services. At a minimum, such capabilities will provide for restoration of Services within the timeframes set forth in the Disaster Recovery Plan. As a part of its recovery requirements, Exelon and Vendor will meet to determine and define the “Recovery Time Objective”, i.e., how long the system can be unavailable, and the “Recovery Point Objective”, i.e., how much data is lost. Vendor’s responsibilities shall include the following:
Back-up and Disaster Recovery. The Application Model and Customer Data is automatically backed-up daily. Back-ups are stored in secure, geographically dispersed locations and Mendix offers disaster recovery services. Upon termination of this Agreement or the expiration of the last term under an Order Form Mendix shall no longer have the obligation to preserve or back-up any Customer Data.
