Failover Sample Clauses

Failover. The Registry shall practice fail over between data centers not less frequently than once every two years 1. The Registry will be responsible for establishing registration requirements for the .travel TLD. Registration will be limited to: people, businesses, organizations and entities, however constituted, whose primary area of activity is in the travel industry. 2. The Registry, with the advice of The Travel Partnership Corporation, may enumerate and identify industry sectors that are within the meaning of the registration requirements set out in item 1, above. The initial enumeration of such sectors is set out in item 4, below. 3. The Registry may establish stricter requirements for registrants than those set out in item 1, above, according to the Delegated Authority set out in Part II of this Appendix S. In the event that such stricter requirements are established at any time, the Registry will make such requirements public in the manner contemplated in its delegation of authority and will promptly inform ICANN of such requirements. 4. For the purposes of this Charter, without limitation, and as may be amended or clarified from time to time as contemplated by item 5, below, the Registry has enumerated the following sectors of the travel industry that are within the meaning of the registration requirements set out in item 1, above:
Sample 1Sample 2
AutoNDA by SimpleDocs
Failover. In the event of any system issues SSLP Group Ltd will manually fail over to a back-up system that will also allow continued functioning of the service. The following shall define the actions to be taken in relation to the problem’s assigned Severity Level: ● We will provide our Clients with a case number and inform them of the Severity Level of the support request via email. ● All inbound enquiries to the SSLP Group Ltd Helpdesk will be responded to either via an email or with a case number (email ID). ● We may also contact the Client at this stage or at any further time since the incident has been reported to SSLP Group Ltd to request more information or to discuss the problem in more detail. ● If we are unable to speak to them directly, we will send an email either requesting more information or requesting that they contact us. Step 1 represents the acknowledgement of the problem and the beginning of the information gathering process. SSLP Group Ltd will identify and notify the Client of the problem. Step 2 represents the target time frame during which the issue is to be actively addressed and a temporary fix, patch, correction or work-around is provided. The goal will be to provide a fix or a work-around for a problem as soon as possible. Critical problems will be worked on continually until a satisfactory problem resolution can be reached. This will be notified in the form of an ‘Incident Report’. Step 3 represents the target time within which a permanent solution will be available which meets SSLP Group Ltd quality standards. Third Party represents the target time within which a solution to an issue caused by an SSLP Group Ltd third-party supplier will be resolved.
Sample 1Sample 2
Failover. 1. Each data centre facility has a minimum of two sources of electrical power, including a power generation capability for extended off-grid operation. Environmental controls are self-contained and remain operational if the facility and contained systems remain online. 2. Physical security controls are designed to “fail closed” during power outages or other environmental incidents. In case of fire or situations that could threaten life safety, the facilities are designed to allow egress without remaining exposed.
Sample 1
Failover. Process whereby a secondary system assumes functions of a primary system should the primary system become unavailable due to failure or scheduled down time (see DUPLEX)
Sample 1
Failover i. The failover process of the Customer’s environment at the secondary data center will begin within 1 hour of the Customer notifying the NTTA CEC that they have validated the snapshot. ii. Subject to Sections 2, 3 and 4 hereof, for each failover that NTTA fails to successfully initiate within the time periods provided in clause C (i) above, and as the Customer’s sole and exclusive remedy for such failure, Customer will receive a credit equal to one day’s worth of the total recurring monthly fees paid by Customer to NTTA for the applicable calendar month for NTTA Remote Data Replication Service.
Sample 1
Failover. Because we will are transporting crucial audio traffic over the VSAT we need the facility of a backup or failover hub in case of disruptions to the link in Prague. This hub is located in Lampertheim, Germany. In case of the primary hub located at the provider’s Earth station, then Ismaning must have direct connectivity to the Earth station. Lampertheim must on all accounts act as a smaller version of Prague in terms of setup. However it will not need a full time connection because of it being a failover station and so RFE should be paying relatively little or nothing at all for Lampertheim connection. The exact location of Lampertheim can be given upon request for use by the provider to ascertain costs associated with connecting Lampertheim to the VSAT network.
Sample 1

Related to Failover

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

  • Contract Management To ensure full performance of the Contract and compliance with applicable law, the System Agency may take actions including: a. Suspending all or part of the Contract; b. Requiring the Grantee to take specific corrective actions in order to remain in compliance with term of the Contract; c. Recouping payments made to the Grantee found to be in error; d. Suspending, limiting, or placing conditions on the continued performance of the Project; e. Imposing any other remedies authorized under this Contract; and f. Imposing any other remedies, sanctions or penalties permitted by federal or state statute, law, regulation, or rule.

  • Automation Customer agrees that all shipping locations will use a FedEx online or FedEx compatible shipping solution that is approved and authorized by FedEx, and an agreement for the placement or use of any such shipping solution shall be accepted prior to such use.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

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