Server Availability. The System Administrator will strive to maintain continuous availability by design and by practice. Necessary and planned downtime will be scheduled when it will have least impact, for the shortest possible amount of time, and will only come after timely communication to all participants. If a user discovers server is down, the user will report immediately to their Agency Administrator. The System Administrator will notify users by email if they become aware server is down (unplanned). All other procedures for maximizing server availability, recovering from unplanned downtime, communicating, and avoiding future downtime are the responsibility of the System Administrator and Wellsky Information Systems.
Server Availability. Company’s servers are monitored 24 hours a day, 7 days a week, 365 days per year and support agents are available by phone or email as posted in the support section of Company site. Company is fully committed to providing quality service to all customers. To support this commitment, Company sets a 99.999% uptime benchmark.
Server Availability. MSC production server will be operated with the goal of being available for use by Member Libraries for circulation and other transactions 24 hours a day, 7 days a week, 365 days a year, except for scheduled maintenance and upgrades. Uptime/downtime statistics will be tracked. Availability statistics can be viewed on the MSL website. Downtime will be scheduled so as to cause the least disruption of service. The MSC system administrators agree to provide participants with at least 24 hours prior notice of scheduled system downtime. In cases of downtime due to emergency system maintenance, the system administrators will attempt to provide as much advance notice as possible. Access will be via the Internet; Internet access is the responsibility of each Member Library.
Server Availability. Server Availability shall consist of the following components that are provided as part of DYOPATH’s Services: Virtual Servers provided on DYOPATH High Availability platform, Storage provided on DYOPATH Storage Area Network (SAN) devices, and Server primary services/applications which are provided by DYOPATH (e.g. Exchange) Client owned physical servers or other network connected devices co‐located in the DYOPATH cage are not included in this Service Level Category. DYOPATH only provides Infrastructure Availability for these devices. Table 9 Server Availability Service Level Category Service Level Metric Server Availability including primary services (Metric 16) Server and primary services for the overall virtual data center available 99.5% of the time; excluding scheduled maintenance. Reported monthly. DYOPATH and the Client will jointly identify Critical Server and Critical Server clusters and availability will be reported and tracked accordingly. Critical Servers and related applications include, without limitation, the following (Others may be added from time to time in the form of a contract amendment): Critical Server(s) Critical Application Server Name Server Function
Server Availability. 5.1. We shall provide you with sufficient technical information to allow you to connect to and use the Server.
Server Availability. All MSC system software is now implemented as Software as a Service (SaaS). The Vendor will also act as the SaaS host. The MSC will continue to maintain both a TEST and PROD SaaS instance of the software so that MSC staff can test new updates and upgrades before implementing in PROD. The PROD server is available for use by Member Libraries 24 hours a day, 7 days a week, 365 days a year, excepting scheduled maintenance and upgrades. Downtime is scheduled to cause the least disruption of service. The MSC system administrators agree to provide participants with at least 24 hours prior notice of scheduled system downtime. In cases of downtime due to emergency system maintenance, the system administrators will attempt to provide as much advance notice as possible. Access will be via the Internet; Internet access is the responsibility of each Member Library.
Server Availability. MSC production server will be operated with the goal of being available for use by Member Libraries for circulation and other transactions 24 hours a day, 7 days a week, 365 days a year, except for scheduled maintenance and upgrades. Uptime/downtime statistics will be tracked. Availability statistics can be viewed at: xxxx://xxx.xx.xxx/Statewide_Projects/Montana_Shared_Catalog/For_Members/Incident_Tracker/default.asp. Downtime will be scheduled so as to cause the least disruption of service. The MSC system administrators agree to provide participants with at least 24 hours prior notice of scheduled system downtime. In cases of downtime due to emergency system maintenance, the system administrators will attempt to provide as much advance notice as possible. Access will be via the Internet; Internet access is the responsibility of each Member Library.
Server Availability. Openminds will use all reasonable means to allow for a minimum server availability of 99.75%, measured per month. This paragraph only applies to lease agreements for a dedicated server.
Server Availability. Server Availability shall consist of the following components that are provided as part of DYONYX’s Services: • Virtual Servers provided on DYONYX VMware High Availability platform, • Storage provided on DYONYX Storage Area Network (SAN) devices, and • Server primary services/applications which are provided by DYONYX (e.g. Exchange) Customer owned physical servers or other network connected devices co-located in the DYONYX cage are not included in this Service Level Category. DYONYX only provides Infrastructure Availability for these devices. Table 9 Server Availability Service Level Category Service Level Metric Server Availability including primary services (Metric 16) Server and primary services for the overall virtual data center available 99.5% of the time; excluding scheduled maintenance. Reported monthly.
Server Availability. The System Administrator will strive to maintain continuous availability by design and by practice. • Necessary and planned downtime will be scheduled when it will have least impact, for the shortest possible amount of time, and will only come after timely communication to all participants. S a n L u i s O b i s p o C o u n t y C o C H M I S P a r t i c i p a t i n g A g e n c y A g r e e m e n t - A p p r o v e d b y H S O C 9 / 1 6 / 2 0 2 0 p g . 8 • If a user discovers server is down, the user will report immediately to their Agency Administrator. The System Administrator will notify users by email if they become aware server is down (unplanned). • All other procedures for maximizing server availability, recovering from unplanned downtime, communicating, and avoiding future downtime are the responsibility of the System Administrator and Bell Data Systems.
