Back-up and Recovery Sample Clauses

Back-up and Recovery. 1. Contractor is required to have a viable risk management strategy that is formally documented in a Business Continuity Plan (BCP) and/or a Disaster Recovery Plan (DRP). The BCP/DRP shall identify recovery strategies within the application service areas, outline specific recovery methods and goals, indicate data backup and recovery methodology, and provide the maximum time required to restore Services to County in the event of a system disruption or failure.
Sample 1Sample 2Sample 3See All (10)
AutoNDA by SimpleDocs
Back-up and Recovery. 7.1 The Customer acknowledges that the Services are backed up for the purposes of data recovery, where such recovery is required from a failure of one or more Service components.
Sample 1Sample 2Sample 3See All (7)
Back-up and Recovery. Vendor will (i) execute nightly database backups to a backup server in a secure offsite location and (ii) save the last ten (10) nightly database backups in a secure offsite location. The City will have the ability to download any of the backups to The City’s location. The Software shall be configured to perform incremental backups every eight (8) hours, such that the database can be restored to the last committed transaction and/or point in time of the last incremental backup, which will have occurred up to two-hours earlier, in the event of a system failure. Vendor will be responsible for importing back-up and verifying that The City can log-in to the Software. The City will be responsible for running reports and testing critical processes to verify the returned data. At The City’s written request, Vendor will provide test results to The City within a commercially reasonable timeframe after receipt of the request.
Sample 1
Back-up and Recovery. The Exhibit for each Software Product licensed to Customer specifies where Customer may use that Software Product. If any facility specified in that Exhibit becomes inoperable, Customer may use the Software Product temporarily at a back-up facility until use of the original facility is restored. Customer may also use the Software Product in a non-productive mode to test the use of such a back-up facility. Customer may change the data center to another Customer facility located in Canada, United States, United Kingdom, or Japan ("Approved Areas") as a back-up facility. However, Customer must always seek the prior written consent of CSC for any transfer of a Software Product to another location outside of the Approved Areas; CSC agrees it will not withhold its consent to change to another facility outside of the Approved Areas unless CSC has reason to believe the confidentiality of the Software Product will be compromised. Customer shall keep accurate records of all locations at which any of the Software Products are installed, and shall provide such records to CSC upon request. This Section 3.4 does not permit any third party back-up facility provider to copy, use, or access a Software Product or any information that is confidential pursuant to Article 13 of this Agreement. Customer shall indemnify CSC against any and all damages or losses caused by an unauthorized use or disclosure of the Software Product or any CSC Confidential Information by a third-party owner or operator of a back-up facility used by Customer under this Section.
Sample 1

Related to Back-up and Recovery

  • Acquisition/Liquidation Procedure The Company agrees: (i) that, prior to the consummation of any Business Combination, it will submit such transaction to the Company's stockholders for their approval ("Business Combination Vote") even if the nature of the acquisition is such as would not ordinarily require stockholder approval under applicable state law; and (ii) that, in the event that the Company does not effect a Business Combination within 18 months from the consummation of this Offering (subject to extension for an additional six-month period, as described in the Prospectus), the Company will be liquidated and will distribute to all holders of IPO Shares (defined below) an aggregate sum equal to the Company's "Liquidation Value." With respect to the Business Combination Vote, the Company shall cause all of the Initial Stockholders to vote the shares of Common Stock owned by them immediately prior to this Offering in accordance with the vote of the holders of a majority of the IPO Shares. At the time the Company seeks approval of any potential Business Combination, the Company will offer each of holders of the Company's Common Stock issued in this Offering ("IPO Shares") the right to convert their IPO Shares at a per share price equal to the amount in the Trust Fund (inclusive of any interest income therein) on the record date ("Conversion Price") for determination of stockholders entitled to vote upon the proposal to approve such Business Combination ("Record Date") divided by the total number of IPO Shares. The Company's "Liquidation Value" shall mean the Company's book value, as determined by the Company and audited by BDO. In no event, however, will the Company's Liquidation Value be less than the Trust Fund, inclusive of any net interest income thereon. If holders of less than 20% in interest of the Company's IPO Shares vote against such approval of a Business Combination, the Company may, but will not be required to, proceed with such Business Combination. If the Company elects to so proceed, it will convert shares, based upon the Conversion Price, from those holders of IPO Shares who affirmatively requested such conversion and who voted against the Business Combination. Only holders of IPO Shares shall be entitled to receive liquidating distributions and the Company shall pay no liquidating distributions with respect to any other shares of capital stock of the Company. If holders of 20% or more in interest of the IPO Shares vote against approval of any potential Business Combination, the Company will not proceed with such Business Combination and will not convert such shares.

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