Disaster Recovery Testing Sample Clauses
The Disaster Recovery Testing clause establishes requirements for regularly testing an organization's disaster recovery plans and procedures. It typically mandates scheduled simulations or drills to ensure that systems, data, and operations can be restored effectively after disruptive events such as natural disasters or cyberattacks. By enforcing routine testing, this clause helps identify weaknesses in recovery strategies and ensures preparedness, ultimately minimizing downtime and data loss in the event of an actual disaster.
POPULAR SAMPLE Copied 2 times
Disaster Recovery Testing. 4.1 During project implementation, Interactive will perform a non-disruptive Disaster Recovery Bubble Test as part of internal acceptance testing. Neither the Customer nor the Customers third parties will be involved in this acceptance testing and it does not include application or Customer specific steps.
4.2 From the Service Start Date (after completion of the activities in clause 4.1), it is recommended that the Customer conduct one annual non disruptive Disaster Recovery Bubble Test which is included in the monthly Service Fee. To initiate this Disaster Recovery Bubble Test, the Customer must make a Complex Service Request and provide Interactive with a minimum of three weeks' written notice, specifying the preferred testing date. Interactive will work with the Customer to accommodate the Disaster Recovery Bubble Test on the preferred date. This Disaster Recovery Bubble test does not include application specific steps or testing.
4.3 The Customer may during the Individual Term, for an additional fee, request additional Disaster Recovery Tests (which may be either disruptive or non-disruptive) either during Business Hours or After Hours by making a Complex Service Request. If Interactive approves the request, a quote for the relevant Disaster Recovery Test will be provided to the Customer. Upon the Customer's written acceptance of the quote the parties may enter into an Addendum to the CMS SOW to document the requirements before the completion of the additional Disaster Recovery Test.
4.4 During any Disaster Recovery Testing, Interactive and the Customer will each perform their respective duties (where applicable) as set out in the Disaster Recovery Runbook.
4.5 The Customer shall manage any third parties engaged by the Customer in relation to Disaster Recovery Testing.
4.6 Interactive is not liable to the Customer for, and the Customer irrevocably releases Interactive from all claims arising out of, or in relation to, loss or liability suffered by the Customer as a result of one or more of the following:
(a) the Customer not completing Disaster Recovery Testing in accordance with item 4.2 at no fault of Interactive; and
(b) the Customer making significant changes to the Customer’s applications or environment since the last Disaster Recovery Test was performed.
Disaster Recovery Testing. 10.1 The Operator shall execute a Disaster Recovery test as soon as reasonably practical within nine
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 i. Formal documentation describing the disaster recovery testing process for the Services shall be reviewed and updated at least annually.
ii. The backup/restore procedures upon which the Services’ disaster recovery processes are based shall undergo continuous testing as part of regular capacity management exercises.
iii. A complete test of the Services’ disaster recovery process, including simulation of datacenter failure, shall be conducted on an annual basis. Each test shall be followed by a report of the testing exercise, confirmation whether current RTO and RPO targets were met, as well as lessons learned and process improvements to decrease RTO and RPO values.
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. 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. 4.1 The Customer shall conduct Disaster Recovery Testing at least once per year. The Customer shall provide Interactive with a minimum of 8 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.
4.2 During Disaster Recovery Testing, Interactive and the Customer will each perform their respective duties as set out in the Disaster Recovery Runbook. The Disaster Recovery Tests will be non-disruptive Bubble Tests unless otherwise agreed.
4.3 The Customer may request to perform more than one Disaster Recovery Test in a year, or to conduct a Disaster Recovery Test After Hours, by making a request to Interactive. If Interactive agrees to the request, Interactive will provide a quote to the Customer for the cost of the Disaster Recovery Test. If the Customer agrees to pay the quoted amount, the Customer may perform the Disaster Recovery Test.
4.4 The Customer shall manage any third parties engaged by the Customer in relation to Disaster Recovery Testing.
4.5 Interactive is not liable to the Customer for, and the Customer irrevocably releases Interactive from all claims arising out of, or in relation to, loss or liability suffered by the Customer as a result of one or more of the following:
(a) the Customer not completing Disaster Recovery Testing in accordance with item 4.1 at no fault of Interactive; and
(b) the Customer making significant changes to the Customer’s applications or environment since the last Disaster Recovery Test was performed.
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:
1. Establish joint test objectives with DIR and DIR Customers designed to verify that all systems will be available within an established timeframes.
1.1. Provide for DIR and DIR Customer acceptance of test plan.
2. Schedule and test all components of the Disaster Recovery plans as required in cooperation with DIR and DIR Customers.
3. Schedule testing dates with DIR and DIR Customer’s approval and give DIR and DIR Customers the opportunity to observe and participate in the tests.
3.1. Record and report to DIR when a DIR Customer chooses not to test, including the identification of the affected DR Plans and Applications.
4. Assume coordination and administrative responsibility for Third Party Vendors utilized by DIR and DIR Customers during testing in accordance with the Disaster Recovery plans.
5. Continue to operate and manage the Services during periodic Disaster Recovery tests.
6. Provide DIR and DIR Customers with a formal report of the test results within thirty (30) days of each test. At a minimum, these reports should include:
6.1. The results achieved.
6.2. A comparison of the results to the measures and goals identified in the respective plans.
6.3. A report on the feedback from Authorized Users as to the adequacy of continuity for their respective areas.
6.4. A plan and a schedule to remedy any gaps revealed during testing.
6.5. Through coordination with DIR Customer ensure that Application integrity exists after restoration in accordance with the formal DR Plan.
7. Retest within ninety (90) days if any disaster simulation(s) fails to achieve specified results as a result of Service Provider’s failure to perform its responsibilities.
7.1. Update the Disaster Recovery plans upon re-testing and verify that the remedy was successful.
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.
2. In cooperation with DIR Customers, Service Provider will establish and schedule reasonable windows to accomplish all DR testing for DIR Customer Applications as documented in the Service Provider’s annual DR test plan and schedule, in accordance with Attachment 3-C.
3. Service Provider will assist DIR and the appropriate governance committee, as specified in
4. Service Provider will actively engage DIR Customers in planning and preparation for annual test activities; including setting the objectives of the test.
5. Each such test shall address the specific needs of each DIR Customer (e.g. split-window testing, preparation testing prior to an annual test, off-site tape location review and reconciliation, etc.) The Service Provider’s test execution must demonstrate, at a minimum, the Service Provider’s ability to meet or exceed the designated RTOs for those Applications in the event of a disaster.
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.