Frequently Asked Questions#
Access#
Can I Access Elm from Sherlock and/or SCG?#
Yes. Although Elm is not mounted on Sherlock or SCG directly, you can use the S3 API to access Elm using many of the same tools you'd use to interact with common cloud vendor stroage like rclone, aws-cli, and s5cmd. See our Elm Gateways page for more information.
How does Elm handle access control and file sharing?#
Moving Data#
Can I access Elm from my desktop/laptop?#
Yes, please see the Elm Gateways page.
Can I mount Elm on my own computer at Stanford?#
Yes. Tools like rclone, allow yout to mount S3 storage targets like Elm.
Backup#
Is Elm backed up?#
No, Elm is not backed up. While Elm has redundancy features like erasure coding, it’s still located on campus. This means Elm should be considered a single copy of your data. If there’s a big disaster (think earthquakes), there’s a chance you might lose access. For extra-important data, it’s a good idea to keep a second copy on another system.
Quotas#
How are Elm quotas measured?#
Elm quotas are measured in allocations of 1 TiB. Your quota is a hard limit that you set before you upload data to Elm. This ensures you never get a surprise storage bill and unlike cloud competetors, ongoing costs can be predictably managed and forecasted.
News & Alerts#
How can I stay up-to-date on Elm?#
We highly recommend that all Elm users join the SRCC Slack workspace (SUNet ID Required) and follow the #elm-announce channel to stay abreast of system updates, maintenance, or outages. #elm-users is best for sharing best practices and asking questions among a welcoming community of other Elm users.
Email notification for system maintenance and issues#
Elm administrators maintain a mailing list called Elm-announce. This very low-traffic list is used for official announcements such as planned maintenance. Elm users are automatically subscribed to this list by default. For more information, please see the following page: