System Backup Clause Samples

The System Backup clause establishes requirements for regularly creating and maintaining copies of data or system configurations to prevent data loss. Typically, this clause outlines the frequency of backups, the types of data to be backed up, and the procedures for securely storing and restoring backups in case of system failure or data corruption. Its core function is to ensure business continuity and data integrity by providing a reliable means to recover information in the event of technical issues or disasters.
POPULAR SAMPLE Copied 2 times
System Backup. The Company ensures that data is protected using backup to disk. Hosting company guarantees daily backups of the whole system. The Company performs a full database backup to disk once every month. These incremental backups will be retained for 12 months in case the Customer need to retrieve earlier data. Additional backups are performed by the Company prior to Releases. Maintenance and Support Services shall include maintenance of the Solution and Customer platform including corrective maintenance and enhancements and a customer support service for the Solution and Customer platform as set out below.
View Source
System Backup. The parties agree and acknowledge that all EPR FireWorks system data shall be housed in the secure Amazon Web Services cloud environment, with security, back up and disaster recovery built-in.
View SourceView Similar (2)
System Backup. To protect against possible loss of data, Distributor should inform end-users of the importance of backing up the Product on a regular basis in accordance with the Product's users guide.
View Source
System Backup. Conduct backups of user-level information contained in systems; conduct backups of system-level information contained in the system; conduct backups of system documentation including security-related documentation; and protect the confidentiality, integrity, and availability of backup information at storage locations.
View Source
System Backup. As files may be altered or damaged in the course of Novell providing services to You, You agree to take appropriate measures to isolate and backup Your systems.
View Source
System Backup. The system is backed up regularly by an automated system.
View Source
System Backup. The Company ensures that data is protected using backup to disk and digital vault. A full database backup is performed to digital vault and disk once every 24 hours with transaction logs being secured throughout the day. The Company uses a grandfather, father, son (GFS) backup rotation scheme. Backups are automatically transmitted to an off-site location within the EEA and kept for 6 (six) months from the termination date of the Agreement.
View Source

Related to System Backup

  • Data Backup The Services do not replace the need for Customer to maintain regular data backups or redundant data archives. PROVIDER HAS NO OBLIGATION OR LIABILITY FOR ANY LOSS, ALTERATION, DESTRUCTION, DAMAGE, CORRUPTION OR RECOVERY OF CUSTOMER DATA.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Data Backup Plan Contractor must have established documented procedures to backup County PHI to maintain retrievable exact copies of County PHI or PI. The plan must include a regular schedule for making backups, storing backups offsite, an inventory of backup media, and an estimate of the amount of time needed to restore County PHI or PI should it be lost. At a minimum, the schedule must be a weekly full backup and monthly offsite storage of County data.