Skip to main content

Vault Storage

Vault storage is a tape-based product for long-term data retention to store data that is accessed infrequently, or for backups of data that is being stored locally on systems that do not provide their own backups

Vault storage uses a combination of front-end disk alongside substantial tape capacity to efficiently store large amounts of data. The disk cache allows data recently written to Vault to be accessed quickly, and magnetic tapes store files that have not been recently used. By default data is written to archival tape, and when the disk cache fills the oldest unaccessed data is freed. Files migrated to tape are still displayed in the relevant directory and data is automatically recalled to disk when it is accessed. Recalling data from tape can take up to five minutes, possibly much longer, depending upon the file size and number of files.

In order to ensure that data is recalled quickly and efficiently, it is strongly recommended that users store data in an orderly structure of folders that represent experiments, projects, instruments or people and also bundle large numbers of small files together into archives. This can be accomplished by using a file compression tool like ZIP, TAR or SquashFS. In this way a single archive containing a large number of files can be recalled far more quickly and efficiently than the same data stored as many individual files.

From July 2026 onwards, Monash eResearch is migrating the vault service from one set of infrastructure "vault-v2", to a newer system. Access methods differ between these two systems, and with the new Vault access is an explicit upload/download or remote transfer to/from other storage.

Use of the older vault storage as general purpose desktop or mounted filesystem storage has lead to an early retirement of this system, and degraded performance due to continuously changing data, and data held in many small files.

The older vault storage can be presented as a desktop share or network drive (SMB), can be mounted on a server (NFS) or can be accessed via SFTP or rsync. Access to SMB shares is controlled via secure access groups that can be managed through the University's GroupAdmin Tool. NFS shares are made available to specific machines using static IP addresses or preferably, hostnames.

For either of these systems, recalling data can be a lengthy process if a collection contains a large number of files due to the way that data is stored on magnetic tape1. For each file that needs to be recalled the tape robot must:

  • Look up the file in the database,
  • Locate the specific tape that contains the file (large files may span multiple tapes),
  • Collect the tape and load it into an available tape drive,
  • Move to the position on the tape where the data is stored, and
  • Copy the data to disk.

As a result, recalling collections with large numbers of files may take a long time especially if the files were added over a long period as they may be spread across multiple tapes. If there is a need to access a large number of files within a short timeframe, a “bulk recall" can be requested by contacting the RDS team (note that bulk recalls are assessed on a case-by-case basis).

There is a significant amount of Vault capacity available and allocations can be requested via the Data Dashboard.

Resources​

Technical Information​

FeatureDescription
Access protocolSFTP
Supported Operating SystemsWindows, macOS, Linux
Securityvia "secure access groups" managed in the Monash GroupAdmin system
Security ClassificationPublic, Restricted

Footnotes​

  1. Data on tape is stored in "chunks" and each chunk is written to a specific tape at a specific time. If large numbers of files are added to a collection over a long period then it is likely that the files will be stored across multiple tapes. As each tape needs to be loaded into a tape drive and then moved to the location of the chunk in order to retrieve each file, the fewer chunks there are to read and retrieve the more efficiently the data can be recalled. For this reason, bundling up individual files into archives helps to speed up the retrieval process because there will be a smaller number of chunks to locate and recall. ↩