While you can do your work on Jetstream2 using only the storage that you initially include in your instance, a best practice is to create separate volumes to hold large amounts of data. Such volumes can be attached to an instance, making their contents available from within the instance. They can later be detached from that instance, attached to another instance, or left unattached as your needs change. You can also attach more than one volume to an instance.

Some additional information about volumes:

• A volume can usually only be attached to one instance at a time. However, a volume that is attached to a running instance can be mounted as a network drive on other running instances.
• You cannot attach a volume that was created in one Jetstream2 region to an instance that was created in a different region.
• The Exosphere web interface does not provide a mechanism for changing the size of an existing volume. Extending a volume can be done using the Horizon web interface. Note that it is much easier to extend a supplementary volume than it is to extend the root volume of an instance.
• Information about the limitations on volumes and their costs is available in the Jetstream2 documentation. Policies and costs for volumes are subject to change.

Backing Up Your Volumes

Jetstream2 does not automatically back up the contents of either your instances or any volumes that may be attached to them. This is the responsibility of the user and a best practice is to regularly copy your work to a remote (non-Jetstream2) location. The Data Transfer roadmap provides information on several convenient and secure mechanisms that can be used to back up your files from Jetstream2 to another location.

Information on managing your Jetstream2 volumes is found on the following pages:

• Creating and Attaching Volumes
• Detaching and Deleting Volumes