Managed Application Availability and Uptime Sample Clauses

Managed Application Availability and Uptime. 6.7.1 If CipherWave is responsible for the management of certain applications (e.g. Microsoft SQL Server, Microsoft Exchange, etc.) and server roles (e.g. Hyper-V, Active Directory, etc.) per this Agreement and specified in Schedule A. CipherWave undertakes that these shall be made available with a minimum uptime of 99.9% measured monthly. If the managed application uptime does not meet these objectives except as the result of an Excused/Scheduled Outage, Customer will be entitled to a Service Credit off of the monthly service charge for affected services as stipulated in the table in 6.9
AutoNDA by SimpleDocs
Managed Application Availability and Uptime. 6.7.1. If Mezobyte is responsible for the management of certain applications (e.g. Microsoft SQL Server, Microsoft Exchange, etc.) and server roles (e.g. Hyper- V, Active Directory, etc.) per this Agreement and specified in Schedule A, Mezobyte undertakes that these shall be made available with a minimum uptime of 99.9% measured monthly. If the managed application uptime does not meet these objectives except as the result of an Excused/Scheduled Outage, Customer will be entitled to a Service Credit off of the monthly service charge for affected services as stipulated in the table in 6.9 Service Credits.

Related to Managed Application Availability and Uptime

  • General Availability The commitment to availability specified in the letter of appointment shall be subject to mutually acceptable revision. Such revision will occur once per year, or, if mutually agreed between the Employer and the employee, on a more frequent basis. The Employer will issue a revised letter of appointment to reflect approved changes to employee’s general availability.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • System Availability System Availability percentage is calculated as follows:  Total MinutesintheMonth −Downtime   System Availability%age =  Total MinutesintheMonth *100    System Availability SLA (“SLA”) 99.5% System Availability percentage during each Month for productive versions Credit 2% of Monthly Subscription Fees for each 1% below SLA, not to exceed 100% of Monthly Subscription Fees Excluded Downtime Total Minutes in the Month attributable to: (i) a Scheduled Downtime for which a Regular Maintenance Window is described in Section 4 below, or (ii) any other Scheduled Downtime according to Section 4 for which the customer has been notified at least five (5) business days prior to such Scheduled Downtime or (iii) unavailability caused by factors outside of SAP’s reasonable control, such as unpredictable and unforeseeable events that could not have been avoided even if reasonable care had been exercised. Scheduled Downtime Scheduled Downtime for the applicable Cloud Services to which customer has subscribed is set forth in Section 4 below entitled “Maintenance Windows for Cloud Services”.

  • Product Availability Under no circumstances shall Company be responsible to Representative or anyone else for its failure to fill accepted orders, or for its delay in filling accepted orders, when such failure or delay is due to strike, accident, labor trouble, acts of nature, freight embargo, war, civil disturbance, vendor problems or any cause beyond Company's reasonable control.

  • RDDS availability Refers to the ability of all the RDDS services for the TLD, to respond to queries from an Internet user with appropriate data from the relevant Registry System. If 51% or more of the RDDS testing probes see any of the RDDS services as unavailable during a given time, the RDDS will be considered unavailable.

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • Therapist Availability Therapist’s office is equipped with a confidential voice mail system that allows Patient to leave a message at any time. Therapist will make every effort to return calls within 24 hours (or by the next business day), but cannot guarantee the calls will be returned immediately. Therapist is unable to provide 24-hour crisis service. In the event that Patient is feeling unsafe or requires immediate medical or psychiatric assistance, he/she should call 911, or go to the nearest emergency room.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Fund Availability Financial obligations of the University payable after the current Fiscal Year are contingent upon funds for that purpose being appropriated, budgeted, and otherwise made available.

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.

Time is Money Join Law Insider Premium to draft better contracts faster.