Storage Management on Artemis
0.0.1 Storage overview
Virtual Machines (VMs) have access to two types of storage:
- Allocated disk space on the VM itself
- Access to CARC storage allocations via the mounted /home1 and /project file systems.
The home and project file systems are not available on Windows VMs.
0.0.1.1 Local storage
Artemis has a 200TB dedicated SSD-backed network file system with 100 Gbps bandwidth. Each user has 200GB of the storage quota that can be distributed across their VM images and local scratch space. In a Windows VM, this makes up the *C:* partition, and in Linux VMs, it includes the root and a fast local scratch mounted automatically as /scratchlocal.
Data stored here is not automatically backed up. Use the snapshot feature to manually back up data. For more information on how to create a snapshot, see our Virtual Machine Management user guide. Snapshots are stored locally on the Artemis system and saved for two weeks.
0.0.1.2 CARC storage allocation
Virtual machines deployed in the private cloud have access to the mounted /home1, /scratch1, and /project file systems. They are mounted automatically at /home1/<username>, /scratch1/<username>, and /project/<projectname>, respectively. Data saved to the home or project file systems is backed up every day.
Windows Server VMs are an exception and do not have access to mounted file systems—users will need to transfer their data just as they would to and from their local computer.
0.0.2 Modifying the size of local storage
The amount of local storage for Linux and Windows VMs can be increased after creation. Select the VM from the VM dashboard, move to the Storage tab, and select the edit button.
Enter the new amount of storage (in MB) and accept the changes.
Storage size can only be increased, not decreased.
0.0.3 Transferring data
Data transfers can be done either through the command line or using a graphical user interface (GUI). The user guide for command line transfers can be found here and the guide for GUI transfers is here.
Data transfers while using a VM are performed the same way as they are with other CARC systems, with one key difference. Enter in the VM’s IP address instead of “hpc-transfer1.usc.edu” or “discovery.usc.edu” in the Server field.
