DR Clustering Considerations for Disk and Tape Drives
Sun Cluster rejects DR remove-board operations on active drives in the primary node. DR remove-board operations can be performed on non-active drives in the primary node and on any drives in the secondary node. After the DR operation, cluster data access continues as before.
Note - Sun Cluster rejects DR operations that impact the availability of quorum devices. For considerations about quorum devices and the procedure for performing DR operations on them, see DR Clustering Considerations for Quorum Devices.
See the Sun Cluster 3.1 System Administration Guide for detailed instructions on how to perform these actions.
DR Clustering Considerations for Quorum Devices
If the DR remove-board operation pertains to a board containing an interface to a device configured for quorum, Sun Cluster rejects the operation and identifies the quorum device that would be affected by the operation. You must disable the device as a quorum device before you can perform a DR remove-board operation.
See the Sun Cluster 3.1 System Administration Guide for detailed instructions on how to perform these actions.
DR Clustering Considerations for Cluster Interconnect Interfaces
If the DR remove-board operation pertains to a board containing an active cluster interconnect interface, Sun Cluster rejects the operation and identifies the interface that would be affected by the operation. You must use a Sun Cluster administrative tool to disable the active interface before the DR operation can succeed (also see the caution below).
See the Sun Cluster 3.1 System Administration Guide for detailed instructions on how to perform these actions.
Caution - Sun Cluster requires that each cluster node has at
least one functioning path to every other cluster node. Do not disable a private
interconnect interface that supports the last path to any cluster node.
DR Clustering Considerations for Public Network Interfaces
If the DR remove-board operation pertains to a board containing an active public network interface, Sun Cluster rejects the operation and identifies the interface that would be affected by the operation. Before removing a board with an active network interface present, all traffic on that interface must first be switched over to another functional interface in the multipathing group by using the if_mpadm(1M) command.
Caution - If the remaining network adapter fails while you
are performing the DR remove operation on the disabled network adapter, availability
is impacted. The remaining adapter has no place to fail over for the duration
of the DR operation.
See the Sun Cluster 3.1 System Administration Guide for detailed instructions on how to perform a DR remove operation on a public network interface.