Hot Backup Requirement Sample Clauses

Hot Backup Requirement. As set forth in the applicable Statement of Work, using applicable Client Software, Provider shall maintain, throughout the Term of the Agreement a dynamic back up of Client Data that is actively accessible to users or may be in the process of being updated, and which does not require system downtime (hereinafter ‘hot backup’). The hot backup requirement shall be applicable to all Client Data managed by Provider that is transmitted, stored or used on Provider, Client or third party computer systems, servers, or storage media, whether such Client Data is located at a Provider facility, Client facility, or third party facility. As set forth in the applicable Statement of Work, Provider shall employ ‘redo logs’ or other mechanisms to preserve the integrity of Client Data to address standard risks associated with ‘hot backups’ (e.g. inconsistency of data that may be altered while the backup is in progress). Notwithstanding the foregoing, Client shall be entitled to require Provider to provide standard offline database backups, which require system downtime (hereinafter ‘cold backups’) with respect to all Client Data of such Client, as set forth in the applicable Statement of Work.
AutoNDA by SimpleDocs
Hot Backup Requirement. Contractor shall maintain, throughout the Term of the Agreement a Hot Backup of all County Data managed by Contractor in the form of SQL server transaction logs that is transmitted, stored or used on Contractor managed systems, services or storage media. Notwithstanding the foregoing, County shall be entitled to require Contractor to provide Cold Backups with respect to all County Data of such County, as set forth in the applicable Scope of Work. Subject to applicable law, the County shall permit Contractor and its Subcontractors to have access to, and make appropriate use of, County Data solely to the extent Contractor requires such access and use in order to properly and appropriately perform the Services as contemplated by this Agreement. Contractor may only access and use County Data in connection with performance of its duties under this Agreement or as specifically directed by the County in writing and may not otherwise use, disclose, modify, merge with other data, commercially exploit, or make any other use of County Data or take, or refrain from taking, any other action that might, in any manner or form, adversely affect or jeopardize the integrity, security, or confidentiality of County Data, except as expressly permitted herein or as expressly directed by the County in writing. Contractor acknowledges and agrees that, as between the Parties, the County owns all right, title, and interest in, and all Intellectual Property Rights in and to, all County Data.
Hot Backup Requirement. Contractor shall maintain, throughout the Term of the Agreement a Hot Backup of all County Data managed by Contractor in the form of SQL server transaction logs that is transmitted, stored or used on Contractor managed systems, services or storage media. Notwithstanding the foregoing, County shall be entitled to require Contractor to provide Cold Backups with respect to all County Data of such County, as set forth in the applicable Scope of Work.

Related to Hot Backup Requirement

  • W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • MEMBERSHIP REQUIREMENT 1. All employees covered by this Collective Agreement shall, as a condition of employment, become and remain members of the British Columbia Teachers’ Federation and the local(s) in the district(s) in which they are employed, subject to Article A.3.

  • Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx. (2) The Contractor shall report the following information pursuant to paragraph (d)(1) of this clause (i) Within one business day from the date of such identification or notification: the contract number; the order number(s), if applicable; supplier name; supplier unique entity identifier (if known); supplier Commercial and Government Entity (CAGE) code (if known); brand; model number (original equipment manufacturer number, manufacturer part number, or wholesaler number); item description; and any readily available information about mitigation actions undertaken or recommended. (ii) Within 10 business days of submitting the information in paragraph (d)(2)(i) of this clause: any further available information about mitigation actions undertaken or recommended. In addition, the Contractor shall describe the efforts it undertook to prevent use or submission of covered telecommunications equipment or services, and any additional efforts that will be incorporated to prevent future use or submission of covered telecommunications equipment or services.

  • Release Requirement Notwithstanding any provision herein to the contrary, except as otherwise determined by the Company, in order for the Grantee to receive Shares pursuant to the settlement of Vested RSUs under Section 6(a), (b), (c), (d) or (e) above, the Grantee (or the representative of his or her estate) must execute and deliver to the Company a general release and waiver of claims against the Company, its Subsidiaries and their directors, officers, employees, shareholders and other affiliates in a form that is satisfactory to the Company (the “Release”). The Release must become effective and irrevocable under applicable law no later than 60 days following the date of the Grantee’s death, termination of employment or transfer of position, as applicable.

  • Child Abuse Reporting Requirement Grantee will: a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements. c. use the System Agency Child Abuse Reporting Form located at xxxxx://xxx.xxxx.xxxxx.xx.xx/Contact Us/report abuse.asp as required by the System Agency. d. retain reporting documentation on site and make it available for inspection by the System Agency.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

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