Common use of Disaster Recovery Testing Clause in Contracts

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.

Appears in 4 contracts

Samples: Cloud Draas Service Terms, Cloud Draas Service Terms, Cloud Draas Service Terms

AutoNDA by SimpleDocs

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 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. 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 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.

Appears in 1 contract

Samples: Disaster Recovery as a Service

AutoNDA by SimpleDocs
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!