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.
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. Extraordinary Event. Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.
High Availability. Dual Edge Devices deployed at the Location setup in a configuration to provide redundancy. The Edge Devices, deployed in a high availability configuration, are connected to each other with a fallback mechanism based on pre- determined policies.
High Availability. Genesys Hub utilizes AWS services to provide highly available environments, including, but not limited to, the following:
High Availability. For their critical services, BMOs need highly reliable systems based on high availability services. The Target Service Availability figure of the SLA needs to be used carefully and must often be complemented by additional measures to ensure the required level. See §4.2 “Service Availability”. Extra testing and monitoring In the set up of such a service, clearly defined tests must be carried to verify performance and stability over time and under worst case traffic scenarios. Monitoring and measurement during transmission is also essential to quickly identify a deterioration of performance, so as to prevent an eventual failure. That is why a proactive provider’s Network Operating Centre (NOC) is very important to BMOs. Reaction procedures and protection mechanisms must be specified precisely in addition to target availability. Fast repair time is needed in case of failure and it must be specified in SLAs too.
High Availability. XxXXX 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 XxXXX . XxXXX ’s emergency operations department shall be available at all times to respond to extraordinary occurrences.
High Availability. To attain a high level of availability, the BMP system can provide duplicated data links toward the network elements. To prevent any loss of data, BMP uses mirrored disks for secure storage of all data. To further increase availability, BMP can be configured as a high availability system where dual computer systems back each other up. During normal run-time, the two BMP systems work completely independently of each other and run separate jobs, but if a single hardware failure occurs the BMP package on that particular hardware will migrate over to the other machine. The high availability function therefore ensures the flow of BMP operations. The hardware investment is also fully utilized, since both servers are running during normal operation. The configuration shown below is not the complete hardware specification, but merely an outline of the main parts. [LOGO OF CAP GEMINI ERNST & YOUNG] [LOGO OF EUROTEL] -------------------------------------------------------------------------------- Appendix I [GRAPHIC OMITTED] Figure 15. High Availability
High Availability. 2.1 All systems will be operational and available during the Hours of Operation for the specific Point of Sale. Downtime for maintenance will be scheduled during low transaction volume periods, such as nights and weekends, and should not exceed * a week, from Sunday to Saturday, unless otherwise reasonably requested by TRX in advance. Downtime will be scheduled at least * in advance, must be approved by Expedia, and must not affect Service Levels. Exceptions for emergency maintenance will be reviewed and approved by Expedia on a case-by-case basis. TRX will notify Expedia as promptly as possible if it need to conduct emergency maintenance.
High Availability. Guaranteed up-time as defined in Exhibit B. Redundancy of components and clustered servers to ensure high availability of the Hosted Services.
High Availability. The NMS hardware and software tools shall consist of a main station mirrored remotely on a hot standby station, and a stand-by station. They shall reside in three areas, namely: • The main NMC with data center • A hot standby NMC with data center • A remote data center It shall be possible at any time to changeover, either automatically or manually, from one NMS platform to a hot standby failover platform. The NMS shall also be accessible by a remote console from any point in the telecommunications network using SSH client application, or by other secure means.
