Configuring and tuning your system for cloud services

This topic describes the procedure for configuring and tuning your IBM Storage Scale node for cloud services.

Configuration command execution matrix
This topic describes which cloud services commands can be run from which nodes. Typically, nodes can be categorized into 3 categories based on what software package (rpm) is installed on them. They are, cloud services server node, cloud services client node, and non-cloud services node.
Designating the cloud services nodes
This topic describes how to designate a node as cloud services node in the IBM Storage Scale cluster.
Starting up the cloud services software
This topic describes how to start the cloud services software on IBM Storage Scale nodes.
Managing a cloud storage account
You can manage a cloud storage account by using the mmcloudgateway account create/update/delete command.
Defining cloud storage access points (CSAP)
The Cloud Storage Access Point (CSAP) provides access between the cloud account on your object storage and IBM Storage Scale. You must create at least one CSAP per cloud account so your cloud services have a path to the object storage. Extra CSAPs can also be created. CSAPs that all have about the same lowest latency (which is tested every 30 minutes) to a node are used evenly. CSAPs with higher latency are put in standby and are used only in error scenarios. This provides greater throughput and higher availability in various error scenarios.
Creating cloud services
You must create at least one cloud services for each cloud account that is created. You can associate a single cloud services with only one cloud account but can use it with multiple file systems or file sets.
Configuring cloud services with SKLM (optional)
To encrypt data that is tiered to the cloud storage, you need to first configure a key manager, before creating a container pair set in the next step. Two types of key manager are supported - local key manager (simple JCEKS based one) and IBM® Security Key Lifecycle Manager (SKLM) server. You need to create one local key manager per cluster. The SKLM key manager is optional and might be created per cluster or per sets of file systems, depending on your security needs.
Binding your file system or fileset to the Cloud service by creating a container pair set
Up to this point, the configuration work was about creating access out to the cloud. Now, you need to bind all this to the data on your cluster, and you do that by creating a container pair set that associates your file system or fileset to the Cloud service. Once you create your container pair set, your Cloud service is usable.
Backing up the cloud services database to the cloud
transparent cloud tiering database stores critical information, such as the list of files that are migrated to the cloud and the list of files that are deleted from the cloud, which is associated with each container. It is essential to back up this database for any type of disaster recovery.
Backing up the cloud services configuration
It is critical that the cloud services configuration data that is stored in the CCR is always backed up.
Configuring the maintenance windows
This topic describes the procedure for setting up a maintenance window in cloud services.
Enabling a policy for cloud data sharing export service
This topic describes how to create a policy for export, a service provided by the IBM Storage Scale cloud services, cloud data sharing.
Tuning cloud services parameters
This topic describes the tunable parameters for cloud services and the commands to modify them.
Integrating cloud services metrics with the performance monitoring tool
This topic describes the procedure for integrating cloud services server nodes with the performance monitoring tool.
Setting up transparent cloud tiering service on a remotely mounted client
Deploying WORM solutions
This topic describes how you can set up a WORM (write once and read many) solution by using IBM Storage Scale, transparent cloud tiering, and IBM Cloud® Object Storage.

Parent topic: Configuring