Storage Mounts & Data Persistence on Instances
Introduction
This guide explains how data persistence works on Instances and how to use mounted datasets (EOS & Disk) for additional or shared storage.
Data Persistence in Instance
- By default, files saved in
/home/jovyanpersist even if the node is stopped and restarted. - Files outside
/home/jovyando not persist unless saved to a mounted volume. - Packages installed manually inside the node must be re-installed after restart.
Volume Mounts in Instance
Volumes extend storage and enable dataset integration. Common use cases:
- Access large datasets without downloading each time.
- Ensure persistence for sensitive or large files.
- Share data efficiently across multiple instances.
Datasets
Datasets act as containers for storing and sharing data. They can be mounted on nodes with different access modes. Mounted volumes appear under "Associated Datasets" in the instance
EOS (E2E Object Store)
- Best for large datasets.
- Can be mounted on multiple instances (read-only).
How to Mount EOS
During Node Creation:
- In the "Datasets" section, select EOS datasets.
- Finish node creation; datasets will auto-mount.
After Node Creation:
- Go to "Associated Datasets" in the instance.
- Select dataset(s) and click Mount.
Disk (High Performance Disk)
- Optimized for fast access and throughput.
- Single read-write access (only one node at a time).
How to Mount Disk
During Instance Creation:
- In the "Datasets" section, select the disk dataset.
- Complete instance creation; dataset auto-mounts.
After Node Creation:
- Open "Associated Datasets"
- Select dataset(s) and click Mount.
Access Modes
- EOS: Read-only, supports multiple instances.
- Disk: Single-node read-write.
Note
All datasets (EOS and Disk) mount at /datasets/dataset-name