Shared storage on the Hoffman2 cluster is available for purchase, subject to IDRE’s terms and conditions. Each group that purchases storage will be given a document specific to their request that must be signed by the responsible PI. Please note that the High Performance storage provided by us is the only option for buying or using the storage on Hoffman2 shared cluster. For security and performance reasons we will neither mount any external file system on to Hoffman2 nor export Hoffman2’s file system to the outside world.
Rates for HPC storage are quoted on the Service Pricing and Ordering Information page of this website.
To purchase storage, please go to store.idre.ucla.edu
Space Usage Duration – Space will be made available to you for the number of years you have purchased. During your purchase period you will be notified of the amount of time you have available on your current purchase, and ultimately when it needs to be renewed. If you decide that you will renew your purchase it can be done with no interruption in access to your storage at the then current rate. If you decide that you will not renew your purchase you will have to make arrangements to move your data off of the storage server within a maximum of 30 days. During this 30-day period your data access will be changed to read-only. IDRE personnel are available to assist you with moving your data.
If your storage purchase did not include backups, that means that no backups will be done on your data unless you specifically ask for this service. Although we have made every effort possible to ensure reliability and fault-tolerance of our storage systems there is no guarantee that you will not lose your data.
Export Restricted Software
Pursuant to federal export control regulations, certain export restricted software must be protected. Export restricted software which must be protected includes: (1) certain strong encryption software, (2) software controlled under the Department of Energy 10 CFR §810 regulations, (3) software controlled under the Department of State, International Traffic in Arms (ITAR) regulations 22 CFR §120-130.
If you are storing any of the above export restricted software, we strongly recommend you remove it immediately. If you do decide to keep it, you must inform the Director of the IDRE Research Technology Group, in writing, about the export restricted software in your account. If a security breach occurs, you, as the custodian of the software, are liable for the exposure and subsequent export control regulatory violations. If you have questions about how your software is controlled under export regulations, contact Claudia Modlin, Research Policy and Compliance Coordinator at email@example.com.
Protecting Personal Information (PI) on Hoffman2
Pursuant to UCLA Policy 404 any Personal Information (PI) data stored on the Hoffman2 Cluster file systems must be protected.
Personal Information is defined as “an individual’s first name or first initial, and last name, in combination with any one or more of the following: (1) Social Security number, (2) driver’s license number or California identification card number, (3) account number, credit or debit card number, in combination with any required security code, access code, or password that would permit access to an individual’s financial account, (4) medical information, and (5) health insurance information.”
Other key point from Policy 404
- Personal Information in the custody or control of UCLA should be stored only when there is an academic, patient care or business purpose.
- Electronically stored Personal Information must be encrypted. Each organization must maintain an inventory of their electronically stored Personal Information, including individuals responsible for this Personal Information.
- Organization Heads have the authority to impose more restrictive standards for electronically storing Personal Information in their area of responsibility.
- Employees who violate this Policy will be subject to the disciplinary process in accordance with University policies and collective bargaining agreements.
- If a breach should occur, as per UCLA Policy 420, Breaches of Computerized Personal Information, its cost will be the responsibility of the organization in which it occurred.
Since IDRE has responsibility for the Hoffman2 cluster it also has responsibility for ensuring that users of the Hoffman2 file systems understand what is required of them.
To that end we need to know if you are storing any Personal Information on the Hoffman2 Cluster. If so, we strongly recommend you remove it immediately. If this is not possible then you must encrypt the data per UCLA Policy 404 guidelines. If you do decide to keep it you must inform the IDRE Director, in writing, what kind of Personal Information you have and why you must keep it on Hoffman2. If a security breach occurs and unencrypted Personal Information is exposed then YOU as the custodian of the data are liable for the exposure.