In some disaster situations, it is possible that the pool cluster resource has been permanently relocated to the current peer cluster. You must create new Pool and Volume objects in its new permanent location in order in order to modify the pool or volume, or to perform other tasks like setting up Distributed File Services junctions or home directories. You receive an eDirectory error if the operation cannot find the information that it needs in the same context.
Because these changes need to send information to eDirectory, you should perform them from the master node of its new cluster location.
To cluster-enable the pool in its current cluster (that is, in a different peer cluster than where it was originally created):
Save any unique or custom information for this resource, such as custom load, unload, or monitoring scripts, BCC scripts for SAN management, and resource replacement values.
Disable BCC on the pool cluster resource.
Take the resource offline on the peer cluster where you want it to permanently reside.
Delete the Cluster Resource objects from eDirectory for the original cluster and the peer cluster.
You should be able to use the Clusters plug-in in iManager to delete the cluster resource. This should clean up the related resource objects, particularly the Virtual NCP Server object for the resource. You can alternatively delete the objects manually from eDirectory.
Check eDirectory manually to ensure that the Virtual NCP Server object, the Pool object, and the Volume object are also deleted for the resource you deleted. These objects reside in the landing zone of the peer cluster and in the normal context on the original cluster.
Use the option in NSSMU or in the Storage plug-in in iManager to create new Storage objects for the existing pool and its volumes.
The new names will be based on the server where you create the objects.
(Optional) After the new objects have been synchronized in eDirectory, you can perform tasks on the pool and volume, such as renaming the pool or volume, or adding new volumes.
Use the Clusters plug-in to cluster-enable the pool and its volumes in its current cluster.
BCC enable the resource, then reconfigure any of the custom settings for the resource based on its current cluster.