FLAT FILE BACKUP Sample Clauses

FLAT FILE BACKUP. Flat file backup is supported on servers. An encrypted copy of your information is kept on a local storage device and in a cloud storage system. ADVANTAGE implements a program to run backups so that they are updated every night. In the event of server failure, client will open a support ticket with ADVANTAGE, who will attempt to recover the existing server. If the server is not recoverable, the server will be repaired, and a copy of the local backup will be restored (estimated downtime up to 24 hours). If the local backup cannot be restored, then the cloud based backup will be restored upon server repair (estimated downtime up to 24 hours). It is important to note that estimated downtime is based on the time from a server operating system being repaired where we can begin to Page 10 of 15 restore the client data. Expected data loss is whatever data was modified between the last backup (the night prior to failure) and the point of system crash. 14.5(B) IMAGE BASED BACKUP WITH CLOUD PLUS BDR SOLUTION. Complete image backup is supported with the BDR. A copy of the managed server will be hosted on the CloudPlus BDR device and in a cloud storage system, updated every 1 hour. In the event of server failure, client will open a support ticket with ADVANTAGE, who will attempt to recover the existing server. If the server is not recoverable, the BDR solution will be brought online, and the client can work as normal off of the BDR solution. Once the main server is repaired, the data will be migrated from the BDR to the main server. Estimated downtime is 30 minutes. Expected data loss is whatever data has been modified in the past hour since the last backup.
Sample 1
AutoNDA by SimpleDocs

Related to FLAT FILE BACKUP

  • COMPUTER GRAPHICS FILES The Engineer agrees to comply with Attachment G, Computer Graphics Files for Document and Information Exchange, if determined by the State to be applicable to this contract.

  • Access to Files 12.01 A copy of any completed evaluation which is to be placed in a nurse's file shall be first reviewed with the nurse. The nurse shall initial such evaluation as having been read and shall have the opportunity to add views to such evaluation prior to it being placed in a file. Each nurse shall have reasonable access to the file for the purposes of reviewing any evaluations or formal disciplinary notations contained therein in the presence of the supervisor. A copy of the evaluation will be provided to the nurse at the nurse's request.

  • Access to File 12.01 An employee shall upon written request, made a reasonable time before the time of viewing, have an opportunity to view their personnel file in the presence of the Director of Human Resources or their designate. The information the employee may review will be:

  • Grievance Files Written grievances and responses will be maintained separately from the employee’s personnel file.

  • Electronic Files a. It is the Buyer's responsibility to maintain a copy of any original Electronic File provided by the Buyer.

  • Grievance File Records involving the processing of an employee's grievance, such as the grievance form, step appeals/responses, and settlement documents, will be kept in a file separate from the employee’s personnel file. It is not the intent of this section to exclude from the employee's personnel file final disciplinary action documents, including those that result from a settlement agreement.

  • Project Reports 1. The Borrower shall monitor and evaluate the progress of the Project and prepare Project Reports in accordance with the provisions of Section 5.08 of the General Conditions and on the basis of the indicators agreed with the Bank. Each Project Report shall cover the period of one calendar semester, and shall be furnished to the Bank not later than one month after the end of the period covered by such report.

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to Image Access via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

  • Personnel File Review a. A unit member has the right upon his/her own request to review the contents of his/her personnel file. The review will be conducted in the presence of the administrator, or his/her designee, responsible for the safekeeping of such file. The employee may have a committee person assist in said review. Such review shall be conducted at a mutually agreeable time. A copy of requested material will be provided.

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to <<customer_name>> via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage Feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

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