Sections of this module:Introduction
Volume (block) vs Object storage
How many cores do I need?
Can I benefit from several VMs?
View all sections on one page (Printer friendly)
You may think of Volume Storage (also referred to as block storage) as a section of a large hard-drive which has been assigned for your use. Volume storage appears to the system and the user as attached drives. You will see it listed in your file explorer along with your other harddrives.
You have to request an allocation (see Module 5) to obtain access to Volume storage. Depending on your requirements and how you justify your needs, you may get access to very large Volumes.
Volume storage can live outside your instance. It appears as block storage which can be attached and then accessed from any of your instances. You can attach the Volume to your instance, read and write data, detach it, and make it available to another instance. Your data on a Volume is retained even when you terminate your instance. Volumes also offer a Snapshot feature which can be used to make convenient backups (this uses some of your overall Volume quota).
You can use the Volume storage as regular block storage, for example for your programs to read/write files to from within a program, or to operate your databases. You may also store all your important files on the Volumes — however don’t forget to do regular backups (more about this in Module 9)!
It is also possible to boot an instance from a Volume. For more information, please refer to the NeCTAR support website.
Volumes are local services and only instances living in the same Node where the Volume has been created can access it.