All data in transit to and from a storage node, and stored in the storage node is encrypted by the CTERA Portal.
To add or edit a storage node:
-
For NFS storage nodes, NetApp (NFS) and NFS-Compatible:
- Log in to the server as
root, using SSH. - Create a folder for the NFS mount on the server.
- Mount the NFS storage node to each server, except the preview server, by running the following script on each server:
portal-mount.sh mount_storage_node nfs_ip:/NFS_FOLDER
where nfs_ip is the IP address of the NFS mount point, and NFS_FOLDER is the name of the folder you created on the NFS server.
- Log in to the server as
-
In the global administration view, select Main > Storage Nodes in the navigation pane.
The Storage Nodes page is displayed.

-
Either,
- Add a storage node, click New Storage Node.
The New Storage Node page is displayed.

Or,
- Edit an existing storage node; click the node's name.
The storage node page is displayed.

The details displayed depend on the type of storage node. When editing a storage node you can only edit enabled values, such as Storage Node Name.
- Add a storage node, click New Storage Node.
-
Enter the generic details for the storage node in the Settings tab. These details are the same for every type of storage node.
Type – The type of storage node you are adding. When you select the type, more fields are displayed so that you can add the specific details for the storage node, as described for each storage node listed in step 7.
Storage Node Name – A unique name to identify the storage node.
Storage Class – The storage class that will include this storage node. After defining the storage node, the storage class cannot be changed.NoteThe storage classes are defined using CLI. For details, see Defining a Storage Class under Cloud Storage Routing: Grouping Storage Nodes.
Dedicated to Portal – Dedicate the storage node to one team portal selected from the drop-down list. The storage node is used for this team portal and no other team portal uses it. The team portal will only write to storage nodes that are dedicated to it and not to other storage nodes.
NoteWhen defining an Amazon Web Services (S3) storage node with AWS Snowball, you must dedicate the storage node to one virtual portal.
Once data is written to a dedicated storage node, you cannot change this setting.
-
Complete the additional, Advanced, fields that are displayed when you choose the type and then click Save.
- Amazon Web Services (S3)
- Cloudian (S3)
- Cohesity Data Platform (S3)
- DataCore Swarm (S3)
- Dell ObjectScale (S3)
- Dell PowerScale (NFS)
- Dell PowerScale (S3)
- Google Cloud Storage (S3)
- Hitachi Vantara HCP (S3)
- IBM Cloud Object Storage (S3)
- IBM Storage Ceph (S3)
- Isilon (S3) has been renamed to Dell PowerScale (S3)
- Local Filesystem
- Microsoft Azure Blob Storage
- MinIO Object Storage (S3)
- NetApp (NFS)
- NetApp StorageGRID (S3)
- NFS-Compatible
- Nutanix (S3)
- OpenStack Swift
- Oracle Cloud Infrastructure (S3)
- PureStorage Flashable (S3)
- Quantum ActiveScale (S3)
- Qumulo (S3)
- S3-Compatible
- Scality ARTESCA (S3)
- Scality RING
- Seagate Lyve Cloud Object Storage: See S3-Compatible
- VAST Data (S3)
- VSP One Object (S3)
- Wasabi Cloud Storage (S3)
- Zadara (S3)