Hammerspace DSX Store/Storage Data Services

In the Storage Systems tab, click on the + (plus sign), on the right side.

The DSX must be added using this method even though it may not have any storage attached to it. Any of the DSX services hosted on the DSX, such as Data Portals, Cloud Mover, and Data Mover, will not function unless the DSX is added to the cluster. It is not required to have storage attached to the DSX node.

Select the volumes to add from DSX. Each configured block device will automatically be formatted with an XFS file system during the installation process.

See the Hammerspace 5.2 Administration Guide for instructions on adding new block storage after the DSX has been installed.

The second step detects existing data on the volume and prompts the user to go through the data assimilation process.

For a brand-new DSX installation, there will be no existing data to assimilate.

Hammerspace enables live data mobility for all data stored on Hammerspace volumes. With this core functionality, it is now possible to have the system automatically load-balance across storage volumes without any disruption for data access.

The manage-to capacity for volumes allows administrators to set the desired high threshold of a volume before the system will no longer place new data on this volume unless it determines that all other volumes are full and that there is no object storage volume available. The data placement logic is driven by a machine learning engine that automatically takes capacity, placement and user-driven needs into account for placing data.

The Low Threshold setting determines how much data moves off a volume once the High Threshold has been reached. The system will schedule mobility from the volume until the low threshold has been met.

The high and low percentage value can be changed on the volume settings screen after the volume has been added.

Each volume type is configured with a default set of capabilities. It is recommended to leave the Durability and Availability setting to the default values.

Objectives such as place-on-<volume name>, exclude-from-<volume-name> and confine-to-<volume-name> are auto-created when following the default GUI workflow. Unchecking the Auto Create box will require the admin to manually create those objectives after the volume is added.

The performance test will do a quick IOPS and throughput test of the volume; these values are used as the basis for performance-oriented objectives. The performance test will take approximately 1-2 minutes per volume.

A storage volume can have one or more IP addresses. Add or remove additional IPs as needed. The IP addresses can also be edited after the volume is added using the Management GUI or the Admin CLI. IP addresses are generally auto-discovered.

This final screen in the volume add step gives a summary of what will be done when clicking on Add Volumes.

Adding a volume is a background process and may take a few minutes to complete per volume. The progress of the volume add can be viewed in the task window or on the CLI.

Alternatively, you can use the following command to add the volume:

For NAS storage systems other than those listed in the GUI/CLI, the NFS Other type can be used to add the third-party storage into the namespace.

The Management IP address represents the actual NFS export IP address. If the storage supports multiple IP addresses, those can be added later using the volume-update command.