Backup module Sample Clauses

Backup module. As explained in the previous sections, each connected device results in a mounted subtree of the gateway filesystem. Once the folder is mounted, the backup module performs synchronization with the GW-attached storage, in order to have a first local backup inside the Home Network. As soon as new device and new folders are mounted, the corresponding synchronized copy is saved on the GW storage. Specific resources' access rights are maintained as in the original device both at the file system level (in the synchronized copy) and as additional metadata to be scheduled for backup in the federation, as well as all the information coming from the VFS level (position, size, ownership, etc.). In this way, as soon as a resource changes access rights policy (i.e., from read/write to read-only for a certain user), the modification is propagated the same on the gateway's storage and, by consequence, on the backup. Furthermore (see Figure 1) the Backup module will use the DAM level, by querying the DAM database to retrieve the user-generated tags associated to each resource, to be stored and saved as metadata as well. After the synchronization step and the extraction of the resources' metadata, files are scheduled for the backup on the federated network. Each gateway in the federation offers a fixed part of its own physical resources for storing fragments computed out of the synchronized files. From this time on, the Backup process will act as follows. Resources scheduled for the backup will be encoded into blocks and spread into the Federation, resulting in other gateways to store those blocks. By exploiting erasure coding techniques, it will be assured that a subset of the stored blocks can be further downloaded into the owner's gateway for restoring after a crash. Whenever, e.g., for other gateways' crashes, the number of encoded blocks reaches a lower bound, a maintenance procedure will take place computing new parity blocks to be stored in other locations (see also Section 5.3).
Sample 1
AutoNDA by SimpleDocs

Related to Backup module

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • Backup Copies You may also make copies of the SOFTWARE PRODUCT as may be necessary for backup and archival purposes.

  • Backups Provider agrees to maintain backup copies, backed up at least daily, of Student Data in case of Provider’s system failure or any other unforeseen event resulting in loss of Student Data or any portion thereof.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

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