Setting up Transparent cloud tiering service on a remotely mounted client

When you use Transparent cloud tiering on a remote cluster, you must complete your administrative work and policy migration scheduling on the Transparent cloud tiering server nodes. User access to tiered data from remotely mounted clusters is available by setting up transparent recalls (which is outlined here).

Before you begin, ensure the following:

A local cluster and a remote cluster are created. For more information, see mmcrfs command.
A passwordless SSH is set up between the local and the remote clusters. For instructions on passwordless SSH setup and other prerequisites, see Problems due to missing prerequisites.
Transparent cloud tiering server RPMs are installed on the local cluster.

Create authentication between the local cluster and the remote cluster. For more information, see Mounting a remote GPFS file system.

Verify that the file system is mounted on the remote cluster (from the local cluster) by issuing the following command on the remote cluster:

mmremotecluster show

The system displays output similar to this:


Cluster name:    vm1.pk.slabs.ibm.com
Cluster id:      5646242228948715502
Contact nodes:   vm1.pk.slabs.ibm.com
SHA digest:      37a856428f565d017gg4abb935a81493d66cd0498917e8ef750c1b5e4bc60d56
SHA digest:      mygpfsnew (gpfs0)

On the local cluster, set the following GPFS variable, which will point to the gateway node of the remote cluster that needs to be connected for transparent recall:
1. For a single remote cluster mounted, set the variable, as follows:
```
mmccr vput tct<remote_cluster_name> <IP_address>
```
  For example, to set the GPFS variable on local cluster for remote cluster tctvm1.pk.slabs.ibm.com, issue the following command:
```
mmccr vput tctvm1.pk.slabs.ibm.com 192.0.2.0
```
2. For multiple remote cluster mounted, set the variable, as follows:
```
mmccr vput tct<remote_cluster1_name> <IP_address>
mmccr vput tct<remote_cluster2_name> <IP_address>
```
  For example, to set the GPFS variable on local cluster for two remote clusters, tctvm1.pk.slabs.ibm.com and tctvm2.pk.slabs.ibm.com, issue the following command:
```
mmccr vput tctvm1.pk.slabs.ibm.com 198.51.100.1
mmccr vput tctvm2.pk.slabs.ibm.com 198.51.100.2
```
Copy the mcstore script from the local cluster to the remote cluster by issuing the following command:
```
cp /opt/ibm/MCStore/scripts /opt/ibm/MCStore/bin/
```
Migrate data from the local cluster to the cloud by using the mmcloudgateway files migrate command.
Transparently recall data from the cloud (by issuing the cat or any similar command on the remote cluster CLI).