Removing a cluster from a grid and cluster cleanup
One or more TS7700 Clusters can be removed from an existing TS7700 Grid erased of virtual volumes and configuration information for reuse.
In some circumstances, it might be desirable to remove a TS7700
Cluster from a TS7700 Grid or restore it to a state similar to new. For instance, cluster removal
can be used with cluster cleanup in a datacenter consolidation scenario. In this scenario, a TS7700
Cluster that used Grid replication to copy data to a primary datacenter could be detached and then
cleaned up using FC 4016, Remove Cluster from Grid, and FC 4017,Cluster Cleanup. Following removal
and cleanup, the TS7700 Cluster can be relocated and reused.
TS7700 Cluster removal
You can
remove a TS7700 Cluster from a TS7700 Grid concurrently with operations on the remaining TS7700
Clusters if you do not inhibit inserts, ejects, or exports. Use FC 4016, Remove Cluster from Grid to remove a TS7700
Cluster from a TS7700 Grid. You must determine ahead of the removal process how to address volumes
that have only a copy consistency point at the TS7700 Cluster being removed. Before the cluster's
removal, these volumes must be ejected, moved to the scratch category, or copied to another cluster
through Management Class mount and demount operations.
Note: After the TS7700 Cluster is removed,
data still on that cluster (in cache or on tape) is unavailable. Development support must manually
recover any data from a TS7700 Cluster removed by using FC 4016, Remove Cluster from Grid.
TS7700 Cluster cleanup
You can clean up a stand-alone TS7700 Cluster or one that is removed from a TS7700
Grid to achieve a state similar to new. Use FC 4017,Cluster Cleanup to return the
TS7700 Cluster to a state similar to one received from manufacturing with the original feature codes
still in place.
Note: To ensure that all volumes are present following removal of a TS7700 Cluster,
you can decide to delay subsequent cleanup for a short period while the TS7700 Grid continues
operation. Recovery of any missed data requires development support.