
Select Digital Storage Options
Answer the questions below to describe your storage needs, skipping any that are not applicable to your project. The tool will display supported University of Minnesota solutions that may work best.
To explore data options available to members of the UMN Health Care Component please visit the Health Sciences Technology: Request Services page.
For more information, contact the Research Cyberinfrastructure Champions at [email protected].
Adapted from: Cornell University Research Data Management Service Group and Cornell Information Technologies Custom Development Group (2018). Finder Module. Drupal 8. https://github.com/CU-CommunityApps/CD-finder
Step 1
Identify Your Needs
Your answers will exclude unsuitable Services and Technologies options.
-
What campus are you on?
Availability of storage solutions vary by campus. Please indicate which campus you represent to identify the storage available to you. -
Are your data regulated by external security regulations? If yes, please select the regulation that applies.
If multiple regulations apply to your data, please select the most restrictive option. For assistance in determining the security requirements of your data, visit http://z.umn.edu/classify-data. -
If your data are not regulated by any of the external requirements above, they are subject to the University's Security Classifications. Please select the appropriate University classification for your data.
If you selected a regulation above, you should leave this question blank. If you are unsure of which regulations or classifications apply to your data, visit http://z.umn.edu/classify-data. -
Where will you be using the data?
Not all storage can be accessed from all devices or locations, as it depends on specific access protocols or available drive mapping. To ensure you can access your data where you need it, please select all devices or locations that apply. If you’re not sure, we recommend leaving this question blank to avoid restricting your options. -
What data protections do you need built into your storage?
The storage solutions offer various types of data protection (see details in each option for more information). If you’re not sure what you need, we recommend leaving this question blank to avoid restricting your options. -
How much data do you expect to store in the next two years?
If applicable, please indicate the amount of data you may need to store today and in the future. For reference, 5TB is about 650,000 digital images or around 7,500 CD-ROMs. If you’re not sure, we recommend leaving this question blank to avoid restricting your options. -
Who needs access to your data?
The storage solutions offer various types of sharing options and permissions (see details in each item for more information). If you’re not sure, we recommend leaving this question blank to avoid restricting your options.
Step 2
Select Services and Technologies
Select the options you would like to compare and details will display at the bottom of the screen. Select Compare Selections to jump to the details.
Step 3
Compare Selections
0 option(s) selected
Application Storage (OIT) | Administraive Data Storage | Box Secure Storage | CrashPlan | Crookston Storage | DRUM | Duluth Storage for Servers | Elevator | Google Drive | Google Shared Drives | High Performance Storage (MSI) | HST Storage | Kaltura (Canvas) | Kaltura (MediaSpace) | Morris Storage | Research Archive (MSI) | Research Data Storage (OIT) | Research Tier-2 | Stratus Block Storage | Stratus Object Storage | Systems Backup Storage | UMN Github | YouTube | Consult with an RC Champion | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Service Description | This service provides a redundant, shared space to store application data. The data stored here will have snapshots and replication to another data center to ensure availability. | For University of Minnesota departments, this service provides a central, shareable document storage system for UMN faculty and staff. Administrative Data Storage (ADS) is intended for primary work and administrative data files used in everyday tasks and provides “mapped drives” from which you can access your documents. | Box is a secure, cloud-based storage option for storing, sharing, and working with data, including sensitive data and protected health information (PHI). | CrashPlan is a backup software developed by an outside vendor (Code 42). It is targeted at backing up smaller disks found in desktops and laptops. It is not intented for backing up servers or desktops with more than 1 TB of storage. Restores are easy and users can restore files from CrashPlan from a browser. CrashPlan is secure and encrypted. This is a local cloud service with the CrashPlan servers housed in two redundant data centers at the University. | Storage to support virtual server infrastructure and unique departmental requirements (e.g. applications and data). | The Data Repository for the U of M (DRUM) is a publicly-accessible archive for research data generated by U of M researchers, students, and staff. Data in DRUM receive a DOI and are fully curated for long-term access, presentation, and citation. | Storage to support virtual server infrastructure. | Elevator is a flexible, cloud-based, open source platform for digital asset storage, organization, and display. | Google Drive is the preferred solution for most users: ablity to access anywhere, file versioning, and real-time colloboration. With Google Drive, you can create and share files and folders online and collaborate with others on group projects. Files in Google Drive can be accessed from any smartphone, tablet, or computer. | Google Shared Drives is a shared space where teams can easily store, search, and access their files anywhere, from any device. Files in Shared Drives belong to the team instead of an individual. Even if members leave, the files stay exactly where they are so your team can continue to share information and get work done. | All MSI researchers have access to a high-performance, high capacity primary storage platform. MSI provides each group a shared home directory space on the high performance primary storage that is accessible from all MSI systems. | Health Sciences Technology (HST) storage is for storing PHI or HIPAA data and for users who are part of the Health Care Component (HCC) at the University of Minnesota. | Kaltura is a media management system for the distribution of media in Canvas courses. This cloud solution automatically optimizes files for viewing on any device and tracks usage and other analytics. Kaltura is only accessible through Canvas and Moodle and is only for course-related materials. | Kaltura is a media management system for the distribution of media in Canvas courses. This cloud solution automatically optimizes files for viewing on any device and tracks usage and other analytics. Kaltura is only accessible through Canvas and Moodle and is only for course-related materials. | Storage for the University of Minnesota Morris campus. | This Archive-tier storage solution gives researchers a robust, secure, and inexpensive place to store very large datasets for five years or more. Think of this as a good alternative to purchasing a bunch of USB hard drives to back up important data or to archive data that you don't have to access on a regular basis. | Research Data Storage is intended for current research data that is frequently accessed but does not require high transactional (compute) capacity. Appropriate data files include datasets, lab workbook data, research group papers, and certain types of Private-Highly Restricted data (PHR). Other types of PHR data are not allowed, including HIPAA, CUI, PCI, or other highly restricted frameworks. | MSI's second tier storage is designed to address the growing need for resources that support data-intensive research. It is tightly integrated with other MSI storage and computing resources in order to support a wide variety of research data life cycles and data analysis workflows. This object storage platform offers an Amazon S3 (Simple Storage Service) interface, so that researchers can better manage their data and more seamlessly share data with other researchers whether or not the other researcher has an MSI account or is at the University of Minnesota. These characteristics make it a good option for exchanging data with outside colleagues, porting cloud-based workflows to MSI systems, or storing inactive data separately from our high performance storage systems. Usage quotas will be set by the allocations committee and reviewed on an annual basis. | Stratus Block Storage is part of the Stratus cloud service for research on controlled-access data. Users can only reach the storage via Stratus virtual machines. Users are allowed self-service control over block storage, and decide how their quota is partitioned into either storage backing virtual machines, snapshots, and/or supplementary storage volumes attached virtual infrastructure. A paid subscription is required to keep data alive. | The Stratus Object Storage is part of the Stratus cloud service for research on controlled-access data. Users can only reach the storage via Stratus virtual machines. Two classes of storage are provided by this service: a) S3cache, which allows users to park controlled-access data with a 60-day lifecycle; and b) S3secure, which allows users to park analysis derivatives and other controlled-access data with an unbounded life-cycle. Neither of the two classes of storage are considered long-term archive tiers, and there are no backups (as stipulated by controlled-access data data-use agreements). A paid subscription is required to keep data alive. | This service will provide a reliable and inexpensive place to copy or sync data that does not need to be backed up, snapped, or replicated. This service will provide a space for IT staff or system administrators to sync a copy of data files from other servers or desktops as a backup. Primarily for IT uses, not intended for individual device backups. | GitHub is a powerful collaboration, code review, and code management system for open source and private projects. Git is the version control system. GitHub is a hosting service for Git repositories. The University hosts a private GitHub Enterprise instance for use by students, faculty, and staff. | YouTube allows users to upload, view, rate, share, add to favorites, report, comment on videos, and subscribe to other users. It offers a wide variety of user-generated and corporate media videos. Available content includes video clips, TV show clips, music videos, short and documentary films, audio recordings, movie trailers, live streams, and other content such as video blogging, short original videos, and educational videos. | The Research Cyberinfrastructure Champions (RCC) Network is a group of individuals on campus who are experts on storage, compute, networking, and other cyberinfrastructure issues for each department, college, or unit. They can help you find the right storage solution for your project! |
Security Level
Low, medium, or high
|
Medium
|
Medium
|
High
|
Medium
|
High
|
Low
|
High
|
Low
|
Medium
|
Medium
|
Low
|
High
|
Medium
|
Medium
|
Low
|
Low
|
High
|
Low
|
Medium
|
Medium
|
Medium
|
Medium
|
Low
|
Learn more about data security levels at the University of Minnesota: http://z.umn.edu/classify-data. A Research Cyberinfrastructure Champion can also help you identify the correct security level for your data. |
Cost | There will be a common-good allocation, but this will be a paid service for outliers. Showback will occur during FY21 to inform future funding models. Cost for data exceeding common good is estimated to be approximately $365.56 per TB per year. This rate does not include any labor charges, this will be updated as data becomes available. | N/A |
No cost to user
|
$42.85 per year per license
|
No cost to user
|
No cost to user
|
Consultation required
|
Amazon Web Services (AWS) pricing
|
No cost to user
|
No cost to user
|
$220/TB/Yr after 20TB
|
Special projects or large requests vary depending on need, and storage price begins at $5.88 per TB per month for basic storage.
|
No cost to user
|
No cost to user
|
No cost to user
|
$456/6TB/5Yrs ($15/TB/Yr)
|
There will be a common-good allocation, but this will be a paid service for outliers. Showback will occur during FY21 to inform future funding models. Cost for data exceeding common good is estimated to be approximately $72.92 per TB per year. This rate does not include any labor charges, this will be updated as data becomes available. |
$41/TB/Yr after 120TB
|
$165/TB/Yr
|
$76/TB/Yr
|
There will be a common-good allocation, but this will be a paid service for outliers. Showback will occur during FY21 to inform future funding models. Cost for data exceeding common good is estimated to be approximately $41.78 TB per year. This rate does not include any labor charges, this will be updated as data becomes available. |
No cost to user
|
No cost to user
|
Research Cyberinfrastructure Champion consultations are free of charge.
|
Capacity Details
One terabyte (TB) is a significant amount of space. 1TB is about 130,000 digital images or around 1,500 CD-ROMs.
|
There is current no fixed cap for this service. Systems requiring more than 4TB of space will require consultation or review. | Allows for many types of files and file sizes. | Box has unlimited storage space, however individual files must be less than 15GB. | N/A | N/A | 160 GB via web form, larger files accepted manually. | Consultation required | Elevator uses Amazon Web Services Storage, so users pay for the storage they need. Individual files must be less than 5TB. | Students: 50GB Staff: 100GB Faculty: 300GB | Each shared drive has a 100GB capacity. | 150GB granted by default for each PI (group). With minimal justification, PIs can request up to 5TB of storage. Between 5 and 20TB can be requested with additional justification and panel review. Beyond 20TB, PIs are charged per TB/year. | No set limits but some restrictions apply. | Unlimited | Unlimited | N/A | 6-12TB per tape depending on compression. This system works best for very large objects--zip/tar small files together into a larger archive. | There is current no fixed cap for this service. Systems requiring more than 5TB of space will require consultation or review. | 120TB per PI (research group). Individual users must put their data under the PI's data bucket. | Volumes are self-serve and limited by project quotas. Quotas can be increased a la carte (billed by TB/yr) | Purchase in 1TB increments. Object storage can be accessed via S3 tools like Boto API, S3cmd, and Minio Client. | There is no fixed cap. Data stored here must follow a standard data protection rotation schedule. This service does not allow long-term storage or archival of data. | The system is intended for source code, configurations, and scripts. It is not intended to be a bulk storage system. | Unlimited | |
Individual File Size Maximum | N/A | N/A | 15GB | N/A | N/A | 160GB | N/A | 5TB | 5TB | 5TB | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | 100MB | 128GB | |
Backup Details | Replicated to another site. | Data is replicated to another physical site to protect data in case of facility failures. | Deleted data is available in users trash for 60 days for restoration. Box provides encrypted backups on their system. | Storage is replicated by writing to multiple locations simultaneously. | Incremental hourly backup. | Snapshots are taken 3x daily. 90% of storage is replicated across multiple locations. A total of 90 snapshots are retained (i.e., 30 days). | Daily incrementals, 4 snapshots/day. | Amazon Web Services (AWS) S3 replication. | Deleted data is available in users trash for 55 days for restoration. | Deleted data is available in users trash for 55 days for restoration. | Snapshots (daily) are retained for up to four weeks. Backups to tape are done for disaster recovery. | Contact HST support to restore data if needed. | Dual data centers (east and west coast), Isilon N+2:1 parity scheme; rolling two weeks of DB snapshots. | Dual data centers (east and west coast), Isilon N+2:1 parity scheme; rolling two weeks of DB snapshots. | N/A | No backup of data are made. When data is written, it goes to two tapes. The redundant tape functions as a backup | Replicated to another site | No explicit backups of data are made. Storage is replicated with (4,2) erasure encoding, which ensures that the original data files can be restored in the event of disk failures. For physical backups, MSI recommends users tier storage down to Tier 3 Research Archive (tape). | No backups in compliance with NIH GDS Policy. | No backups; users can manually snapshot volumes and create their own backups so long as they continue to satisfy their data-use agreements. | N/A | GitHub's primary use is to track changes to text based source code. As such, all revisions and changes are tracked by the system. The system itself is protected by normal virtual machine backup routines and that process is managed by OIT Data Protection and the Linux Platform Team. | N/A | |
Versioning Details | Snapshots | We take snapshots of all data every eight hours and are kept for thirty days to protect data from unintended file deletion. | Yes | N/A | N/A | Versions are mediated. Both are kept and public. | 90 days backup, 2 weeks snapshot recovery. | Amazon Web Services (AWS) S3 asset versioning, with 90 day retention. | Yes | Yes | Versioning is not a supported feature. | Shadow copies once a day for 30 days in some cases. Contact HST support for more details. | It may be possible to extract previous versions of a file using the Kaltura API. | It may be possible to extract previous versions of a file using the Kaltura API. | N/A | No automatic versioning is done. | Snapshots every 8 hours | No automatic versioning is done. The service does support S3 Versioning API for users to post new versions of files. | No automatic versioning. Users may snapshot their Volumes manually, except when the snapshot would include controlled-access. | No versions enabled. | No versioning | Versions are automatically created based on commits. | N/A | |
Access Protocol | NFS; SMB | NFS; SMB | Ftps; Browser; Client | Browser (read); Client | SMB | Browser (read) | iSCSI | Browser | Browser; Client | Browser; Client | NFS | Variable | Browser; Kaltura Classroom app for Windows can write; Kaltura CaptureSpace app for macOS/Windows can write; Kaltura Capture app for macOS/Windows can write | Browser; Kaltura Classroom app for Windows can write; Kaltura CaptureSpace app for macOS/Windows can write; Kaltura Capture app for macOS/Windows can write | SMB | Globus | NFS; SMB | S3 clients; Globus | NFS | S3 | NFS; SMB | Browser; Client; HTTPS; SSH | Browser | |
Drive Mapping | Allows for many types of standard drive mappings (i.e. Net Use/Net Map/Mount). | Allows for many types of standard drive mappings (i.e. Net Use/Net Map/Mount) | Box Drive | N/A | N/A | No drive mapping | Block storage can only be attached to UMD VMs. | N/A | Googe Drive File Stream; Google Backup & Sync (for backup of local machine) | Google File Stream | This storage is mounted globally at MSI and available to researchers when they log into any MSI system. User home directories and group shared research space are stored on this system. This storage cannot be mounted on non-MSI-managed systems. | Drive Mapping if computer is bound to HST AD | No drive mapping | No drive mapping | N/A | Interact via Globus | Allows for many types of standard drive mappings (i.e. Net Use/Net Map/Mount) | Interact with data via the S3 API or Globus | Block Storage can only be attached to Stratus VMs. | permissions via CIFS/NFS folder and file restrictions | Allows for many types of standard drive mappings (i.e. Net Use/Net Map/Mount) | N/A | No drive mapping | |
Hosted
Cloud or on-premise
|
On-premise | On-premise | Cloud | On-premise | On-premise | On-premise | On-premise (UMD) | Cloud | Cloud | Cloud | On-premise | On-premise | Cloud | Cloud | On-premise | On-premise | On-premise | On-premise | On-premise | On-premise | On-premise | On-premise | Cloud | |
Sharing
Permissions or access level details
|
SMB: Users with a valid UMN account may be granted access to the files and folders by request. NFS: NFS exports are limited by a IP address that is allowed to access the export. From there, sharing and rights to the files and folders are controlled by the system mounting the export. | SMB: Users with a valid UMN account may be granted access to the files and folders by request. NFS: NFS exports are limited by a IP address that is allowed to access the export. From there, sharing and rights to the files and folders are controlled by the system mounting the export. | Data and folders can be shared with individuals with UMN or external Box account. | N/A | Data is public and available to anyone by default. An embargo can be placed on the data in which users request access to the files for up to two years. | Data can not be shared | Data and folders can be shared publicly, with anyone with a link, internal UMN users with a link, and individuals inside or outside the University. | Individual files can be shared publicly, with anyone with a link, internal UMN users with a link, and individuals inside or outside the University. Folders can only be shared with members of the team drive. | Data is private by default. Users can store files in their home directory without sharing to the rest of their group. However, research group PIs "own" all data in the research group space and can request administrator intervention to get access to their data. PIs can add any users internal or external to the U to their research group. However, all users require a UMN ID in order to gain access to storage and resources. Data can be shared via Research Tier-2 | HST AD account and Sponsored UMN Internet Accounts for VPN and DUO access | Reassign ownership to another UMN user; share administrative control to UMN users as co-editor/co-publisher; share viewer rights to UMN users to be co-viewer; grab link to view that requires no authentication; post to Canvas within any page that uses the RIch Content (HTML) editor; post to course Media Gallery. | Reassign ownership to another UMN user; share administrative control to UMN users as co-editor/co-publisher; share viewer rights to UMN users to be co-viewer; grab link to view that requires no authentication; make media "unlisted" and thus available to users who have not logged in; create Channel that requires UMN auth or specific UMN users, publish media there. | N/A | Data is private by default and owned by the research group PI. | SMB: Users with a valid UMN account may be granted access to the files and folders by request. NFS: NFS exports are limited by a IP address that is allowed to access the export. From there, sharing and rights to the files and folders are controlled by the system mounting the export. | Data is private by default. PIs can add any users internal or external to the U to their research group. However, all users require a UMN Internet ID in order to gain access to storage and resources. Data can be shared s3 acls or via Globus. If sharing via Globus, individual users can be specified. S3 ACLs can open data to the public or individual users. | stratus users are allocated to a project. Within a single project, multiple users can collaborate and share data with one another by accessing the same VM or data volume. However, per data-use agreements, users must have approval to access the data. No sharing outside Stratus (or outside MSI) is allowed. | Data is private by default. Users must have a UMN ID and Stratus Account to gain access to this storage. Once they have access, they are allowed to share data with peers within their specific Stratus Project. No additional sharing options are allowed for this storage. For similar storage with extended options, see MSI Tier II. | SMB: Users with a valid UMN account may be granted access to the files and folders by request. NFS: NFS exports are limited by a IP address that is allowed to access the export. From there, sharing and rights to the files and folders are controlled by the system mounting the export. | Repositories can be private, shared with specific UMN users, or shared "publicly" with anyone with a UMN internet id. | ||||
Potential use cases | Storing application files that need to be accessed by multiple servers. | Primary work and administrative data files used in everyday tasks | Store identity linking documents for human subjects research data; Share videos that contain sensitive information with external collaborators; Store sensitive or identified research data; Store health information. | For those who primarily work on their own PC, provides a layer of data protection | Unique departmental needs to store data, log files, and/or applications specific to their unit. | Research data that are ready to be published and cited (i.e. DOIs) in conjuction with a grant project or a research article. | Campus IT/phone/network infrastructure and support including web/email/application development. Unique departmental needs to store data, log files, and/or applications specific to their unit. Personal/Department shared storage for faculty/staff. Student computing support/VDI. | Organize, catalog, and share thousands of archival slides, hundreds of hours of video footage, documents, 3D objects, whole slide images, and much more. | Store large public datasets pulled from the web; Collaborative editing of documents, sheets, and slides; Store non-sensitive research data. Not approved for HIPAA-sensitive data. | Store files for a lab group or team where all members have access to all folders/files and ownership of files is retained with drive owner even if members leave. Similar storage to Google Drive, different permissions. Not approved for HIPAA-sensitive data. | Dedicated primary storage is a high performance file system that can be accessed from all MSI computing systems. Storage designed to support genomic and other large computational workloads. | Users that need to store PHI and/or HIPAA data. AHC Department data. | Video uploads and storage for academic purposes | Video uploads and storage | Underlying VM structure. | Research data products that need to be stored for at least 5 years. Users may turn to Archive Storage to backup critical research data stored on other storage servers. | Storing data sets for active research projects. | Research data (both inputs and products) that are not accessed frequently. Data can be shared with a large group and accessed by individuals from other institutions. | The system is a locally-hosted cloud environment, designed to store and analyze protected data such as dbGaP data. Stratus is isolated from other MSI storage and compute resources in order to meet the data use requirements of some of our funding agencies. Block storage provides backing for VM filesystems and active analysis workspaces. | The system is a locally-hosted cloud environment, designed to store and analyze protected data such as dbGaP data. Stratus is isolated from other MSI storage and compute resources in order to meet the data use requirements of some of our funding agencies. Object storage allows users to park controlled-access data with a 60-day lifecycle (S3cache), and analysis derivatives with an unbounded life-cycle (S3secure). This is not a long-term archive tier, and there are no backups (as stipulated by controlled-access data data-use agreements). A paid subscription is required to keep data alive. | Backup or second copy of data, workstation backups, SQL flat files | CSE faculty are using GitHub in the classroom, giving student a real world experience through their coursework. IT@UMN uses it to ensure consistency and integrity of their processes, configurations, and software code. It is used by over 2,000 people each month. | Video uploads and storage | |
Also known as
This service may be known by these alternative names
|
Application NAS; App Shares | Administrative Storage, ADS, Administrative NAS | Box; UMN Box | N/A | Data Repository for the U of M | Block storage | N/A | Google Docs; Google Sheets; Google Slides | Google Docs; Google Sheets; Google Slides | Panasas; Tier 1 | AHC storage | VM Storage | Tier 3; Blackpearl | Research Storage, RDS, Research NAS | S3; Ceph | Stratus Volumes; VM Storage; block storage | Object Storage; Stratus Ceph; Stratus S3cache; Stratus S3secure | Backup Storage | ||||||
Website
Learn more about the storage solution
|
OIT Application Storage | Administrative Data Storage | Box | Crashplan FAQs | DRUM | UMD File Storage | Elevator | Google Drive | Google Shared Drives | MSI High Performance Storage | HST Storage | Kaltura | Kaltura | Archive Tier Storage | OIT Research Data Storage | Research Tier 2 | Stratus Block Storage | Stratus Object Storage | OIT Systems Backup Storage | Github | Research Cyberinfrastructure Champion Network | |||
UMN HCC
Availability for members of the University's Health Care Component (HCC)
|
Not available | Not available | Available | Not available | Not available | Limited | Limited | Not available | Limited | Limited | Not available | Available | Limited | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not Available | Not available | Not available | |
Request access | Request Application Storage | Request Administrative Data Storage | User can create a Box account, and sign into Box by visiting box.umn.edu website. More info: box.umn.edu | Submit requests through the CrashPlan Licensing Form. Note: CrashPlan is available for free for CSOM faculty and Ph.D. students. | Contact the UMN Crookston Computer Help Desk ([email protected] or 218-281-8000) to learn about available storage options and/or to request access. More info: https://www.crk.umn.edu/units/computer-help-desk | Users can upload their data for access and discovery by signing into DRUM and filling out the metadata form. A data curator will contact you to finalize the submission and mint a DOI. More info: http://conservancy.umn.edu/drum | Send an email to [email protected] and we'll schedule a conversation to talk about how to best implement an Elevator instance for your use case. More info: elevatorapp.net | Contact Helpdesk and a Service Now ticket is created for new storage request. Changes is access to existing storage require a Data File Server Access Request form be submitted and approved by the Data Owner. DFSAR form is located on the forms.ahc.umn.edu website. | Contact the UMN Morris Help Desk ([email protected] or 320-589-6150) to request access. | Research Data Storage Request Form | Contact the MSI Help Desk ([email protected] or 612-624-0802) to request access. | Contact the MSI Help Desk ([email protected] or 612-624-0802) to request access. | Request Systems Backup Storage | Research Cyberinfrastructure Champion Network (RCC) webpage | ||||||||||
Contact
Contact via email for more information or to request services
|
[email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected]; [email protected]; [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] | [email protected] |
Step 4
Request Help or Save Your Results
Email your answers and the potential services and technologies you selected to yourself, and/or to the Research Cyberinfrastructure Champion Network (RCC).
If you send your results to the RCC, you will be connected within two business days to a champion in your area who can provide more assistance.