STORAGE AND BACKUP. In the event contractor stores Montclair Data, contractor shall not have the right to reproduce, use, change, publish, display, distribute or transfer Montclair Data to any third party without Montclair’s prior written consent. If the Services are interrupted for any reason other than scheduled maintenance, Contractor will immediately activate its disaster recovery plan so that Services will continue without further interruption and notify Montclair of this activation.
STORAGE AND BACKUP. Individual member states are expected to follow the accepted procedures at their own institutions. However, recommended practice is for data to always be stored in at least two locations (e.g., on a portable hard drive or cloud server and laboratory drive on a department network) and to be backed up once- a-week. All multi-state data uploaded to the Data Management Center is stored and backed-up as follows: XXXX.
STORAGE AND BACKUP. All data is stored in FORTH’s private cloud, located in Heraklion, Crete, Greece. The private cloud consists of high-end servers that utilize the Openstack3 cloud technology and all the facilities of the private cloud are hosted in an enterprise grade data center that provides all the necessary technologies against common physical hazards, i.e. air-conditioning, fire protection, physical security access, redundancy in power supply etc, as well as firewall based network data access security and restrictions. The private cloud provides both Virtual Machines (VMs) for hosting services and executing computational tasks as well as resources for storage services (file storage, object storage, and block storage). One of the many advantages of cloud technology is its elastic and on-demand scalability, which can expand or shrink to provide the necessary resources without under- utilizing the available infrastructure. So, even though for the needs of BOUNCE project there is currently allocated a storage space of 150GB, should the need arise this can easily expand to a scale of Terabytes (TBs) that are available in the pool of resources of the private cloud without any disruption or migration to its deployed technologies. The storage facilities of the private cloud provide mechanisms to ensure data safety and integrity against software and hardware based hazards. The low-level storage is performed over a pool of disks linked with RAID4 60 hardware based technology, which ensures a high availability and fault tolerance of two hard drives, i.e. there has to be a simultaneous failure of three hard disks to result in data loss. On top of RAID technology lies the logical volume management (LVM) 3 xxxxx://xxx.xxxxxxxxx.xxx/ 4 xxxxx://xx.xxxxxxxxx.xxx/wiki/Standard_RAID_levels system which provides block storage for the Virtual Machines, such as the VM that hosts the BOUNCE services and data. A semi-automatic backup mechanism is available in the private cloud with the provision of an additional storage pool of many TBs, where archive backups are taken when necessary to provide time snapshots –not incremental backups.
STORAGE AND BACKUP. 7.1. The Customer’s Data and back-up media are placed with Penneo’s sub-supplier (Amazon Web Platforms, Inc. (“AWS”)). All Data is stored within the EU in EU (Dublin) Region and EU (Frankfurt) Region, respectively.
STORAGE AND BACKUP. Each Participant is responsible for defining and following procedures for storage of products and system backup, and in particular for backup of word processed documents and computer system application software components. As a minimum, electronic copies of controlled and partially controlled documents, and computer system application software components, should be backed up weekly, with off-site storage at least monthly. Use of DropBox (or similar cloud based systems) will be deemed to meet this requirement. Where there are paper only controlled and partially controlled documents, distribution off-site to other partners will be considered adequate backup. The Operational Co-ordinator has the right to review these procedures, and request changes where deemed necessary to protect the project against undue risk.
STORAGE AND BACKUP. 5.1. Provision The requirements for disk space within the project significantly exceed the basic capacities (“Grundausstattung”) of the participating institutes. Funding for additional storage has been applied for based on approximation of requirements, which has been carried out individually for each sub- project The storage will be provided in collaboration with regional computing centers and administration groups at the individual sites involved in the project. Tape archives of computing centers are used for regular and automatic backups. Z2 staff at each site is responsible to ensure that at least a weekly backup of all data is created and that access to this backup is possible.
STORAGE AND BACKUP. As Participant deems necessary, Participant, at its own expense, will maintain records of Data accessed through the HIE and used by Participant for Treatment. Participant will determine the form for such records, which may include incorporation of Data into patients’ medical records electronically, by hard copy or by other form of summary, notation or documentation. P rivacy, Security and Accuracy. Participant will maintain a secure environment that supports the security and privacy of Data in the HIE. Participant shall use sufficient administrative, physical and technical safeguards, in compliance with HIPAA Regulations. C ontribution of Data to the Camden HIE. With the support of the Coalition’s staff, Participant will explore the feasibility of contributing data to the HIE. If appropriate, the Coalition will connect its HIE vendor with the Participant’s EMR vendor so that the vendors may jointly explore the feasibility of contribution. The Coalition understands that contribution may ultimately be infeasible due to technological restrictions. If Participant determines that data contribution is infeasible, it shall provide a written explanation to the Coalition. R eport of Record. Participant may elect to receive the “Report of Record” of all tests performed by a particular clinical laboratory through the HIE by executing a separate provider authorization with the clinical laboratory. If Provider does not execute a provider authorization to receive the Report of Record through the HIE, Participant may receive testing results through the HIE, but expressly acknowledges that such Data is neither designed nor intended to replace the testing provider’s principal method of results delivery to Participant and does not constitute a “Report of Record.”
