Disaster Recovery Testing. A full Failover to the Secondary Site and DR Test shall be satisfactorily conducted prior to go-live. If any DR Test indicates a fail point, Company shall promptly work with Saint Luke’s to correct any such failure in order to successfully complete a DR Test. The parties shall cooperate in developing a DR Test plan and objectives for each DR Test. The parties shall cooperate after each DR Test to identify lessons learned and analyze the strengths and weaknesses identified in the DR Test, and to determine actions to be taken to improve disaster recovery capability. Saint Luke’s and Company will determine whether a DR Test was successful based upon the mutually developed DR Test objectives, including whether the RTO and RPO have been met. Saint Luke’s shall have overall responsibility in developing DR Test objectives to which Company and Saint Luke’s will mutually agree. Saint Luke’s may test specific criteria and may utilize documentation related to the DR Test scenario and performance as appropriate to permit Saint Luke’s to meet its legal, regulatory, accreditation, and mission needs. If the DR Test was unsuccessful, within thirty (30) days the Parties will develop a remediation plan and promptly implement such remediation plan within the timeframes mutually agreed upon therein. Saint Luke’s may have the right to request a follow-up DR Test to demonstrate that remediation was effective, which will not count against Saint Luke’s allotted testing cycle.
Disaster Recovery Testing. Service Provider will be responsible for the development and modification of Disaster Recovery testing for the Services in coordination with DIR and DIR Customers. Such tests will be scheduled in compliance with Exhibit 16. Service Provider’s responsibilities include:
Disaster Recovery Testing. 1. Service Provider will assume the DR test schedules in existence at the Commencement Date, and work with DIR Customers to ensure that the DIR Customer annual test schedules continue without disruption.
Disaster Recovery Testing. 10.1 The Operator shall execute a Disaster Recovery test as soon as reasonably practical within nine
Disaster Recovery Testing. Supplier’s responsibilities for Disaster Recovery Testing related to the Services includes (“Disaster Recovery Testing”):
Disaster Recovery Testing. Supplier’s responsibilities for disaster recovery testing related to the Services include the tasks, subtasks, and Deliverables set forth in Table 19 (Disaster Recovery Testing Responsibilities) below.
Disaster Recovery Testing. Once per year WizCom shall conduct a disaster recovery test to determine compliance with the procedures in the Disaster Recovery Plan. Avis may monitor and participate in such tests to the extent reasonably required for Avis to verify the adequacy of disaster recovery procedures for Avis processing. WizCom shall provide Avis with a report and/or presentation of the test results. WizCom shall use commercially reasonable efforts to resolve identified problems and retest unsuccessful test components in a timely manner.
Disaster Recovery Testing. All critical systems and critical applications shall be fully tested, through Simulation Testing, at least twice during every three hundred and sixty five (365) day period until RCSI verifies satisfactory test results, at which time Simulation Testing will be conducted annually, unless it is otherwise agreed by the Parties that additional testing is required by regulation or mutual evaluation of functionality, infrastructure or that a New Service points toward a need to retest. First Data shall use Commercially Reasonable Efforts to schedule any major infrastructure changes in order to align with scheduled Simulation Testing, in accordance with the Change Control Procedures in Section 9.5 of the Main Body of the Agreement.
Disaster Recovery Testing i. Formal documentation describing the disaster recovery testing process for the Services shall be reviewed and updated at least annually.
Disaster Recovery Testing. 4.1 The Customer shall conduct Disaster Recovery Testing at least once per year. The Customer shall provide Interactive with a minimum of 3 weeks’ notice of the date it requests to conduct Disaster Recovery Testing. Interactive will work with the Customer to allow the Disaster Recovery Testing on the date requested. The Customer may conduct Disaster Recovery Testing for the amount of days specified in the CMS SOW.
