You can rename a BCC-enabled pool or volume in its original cluster, that is, where it was created rather than from a peer cluster.
IMPORTANT:If you cannot BCC-migrate the resource back to its original cluster, such as in a disaster situation, you must permanently relocate the pool to its current cluster as described in Section 8.9, Permanently Relocating a Cluster Resource to a Peer Cluster. You can rename the pool or volume as part of this re-assignment process.
Migrate the resource to the master node of its original cluster.
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 for the resource as described in Section 8.7, Disabling BCC for a Cluster Resource, following the process to keep it cluster-enabled in its original pool.
(Optional) Rename the clustered pool as described in Renaming a Clustered NSS Pool
in the OES 2023: OES Cluster Services for Linux Administration Guide.
(Optional) Rename a clustered volume as described in Renaming a Clustered NSS Pool
in the OES 2023: OES Cluster Services for Linux Administration Guide.
Re-enable BCC for the resource as described in Section 8.2, BCC-Enabling Cluster Resources.
Reconfigure any of the custom settings for the resource based on its current cluster.