Back-Up Data and Disaster Recovery Sample Clauses

Back-Up Data and Disaster Recovery. (a) You shall back up the Site and Data daily and retain those back-ups on or off, the Site.
AutoNDA by SimpleDocs
Back-Up Data and Disaster Recovery. (a) ContractCoach shall back up the Website and Client’s data daily and retain those back-ups on site.
Back-Up Data and Disaster Recovery. (a) The Service Provider shall back up the Website and Client’s data upon written request. There will be a fee for restoring/backing up the Client’s data.
Back-Up Data and Disaster Recovery. You shall back up the Site and Government’s data daily and retain those back-ups on or off, the Site. In the event that Government’s data is lost from Government’s servers, you shall restore the back- up data to Government’s servers. Government may wish to mirror its data and/or its Site in another location. You shall not be responsible for files that cannot be recovered due to force majeure, unless such loss is due to your error, omission to act, negligence or willful misconduct.

Related to Back-Up Data and Disaster Recovery

  • Archival Back-Up and Disaster Recovery Licensee may use and copy the Product and related Documentation in connection with: i) reproducing a reasonable number of copies of the Product for archival backup and disaster recovery procedures in the event of destruction or corruption of the Product or disasters or emergencies which require Licensee to restore backup(s) or to initiate disaster recovery procedures for its platform or operating systems; ii) reproducing a reasonable number of copies of the Product and related Documentation for cold site storage. “Cold Site” storage shall be defined as a restorable back-up copy of the Product not to be installed until and after the declaration by the Licensee of a disaster; iii) reproducing a back-up copy of the Product to run for a reasonable period of time in conjunction with a documented consolidation or transfer otherwise allowed herein. “Disaster Recovery” shall be defined as the installation and storage of Product in ready-to-execute, back-up computer systems prior to disaster or breakdown which is not used for active production or development.

  • Business Continuity and Disaster Recovery Bank shall maintain and update from time to time business continuation and disaster recovery procedures with respect to its global custody business, which are designed, in the event of a significant business disruption affecting Bank, to be sufficient to enable Bank to resume and continue to perform its duties and obligations under this Agreement without undue delay or disruption. Bank shall test the operability of such procedures at least annually. Bank shall enter into and shall maintain in effect at all times during the term of this Agreement reasonable provision for (i) periodic back-up of the computer files and data with respect to Customer and (ii) use of alternative electronic data processing equipment to provide services under this Agreement. Upon reasonable request, Bank shall discuss with Customer any business continuation and disaster recovery procedures of Bank. Bank represents that its business continuation and disaster recovery procedures are appropriate for its business as a global custodian to investment companies registered under the 1940 Act.

  • Disaster Recovery PFPC shall enter into and shall maintain in effect with appropriate parties one or more agreements making reasonable provisions for emergency use of electronic data processing equipment to the extent appropriate equipment is available. In the event of equipment failures, PFPC shall, at no additional expense to the Fund, take reasonable steps to minimize service interruptions. PFPC shall have no liability with respect to the loss of data or service interruptions caused by equipment failure, provided such loss or interruption is not caused by PFPC's own willful misfeasance, bad faith, gross negligence or reckless disregard of its duties or obligations under this Agreement.

  • Disaster Recovery Plan Contractor agrees that upon request of System Agency, Contractor shall provide copies of its most recent business continuity and disaster recovery plans.

  • Network Upgrades and Distribution Upgrades The Participating TO shall design, procure, construct, install, and own the Network Upgrades and Distribution Upgrades described in Appendix A. The Interconnection Customer shall be responsible for all costs related to Distribution Upgrades. Unless the Participating TO elects to fund the capital for the Distribution Upgrades and Network Upgrades, they shall be solely funded by the Interconnection Customer.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • DISASTER RECOVERY AND BUSINESS CONTINUITY The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Effective Date Term Termination and Disconnection 3.1 Effective Date 3.2 Term of Agreement 3.3 Termination

  • Procurement of Recovered Materials (1) In the performance of this contract, the Contractor shall make maximum use of products containing recovered materials that are EPA-designated items unless the product cannot be acquired

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