There are a few issues you must consider when completing dynamic reconfiguration (DR) operations on disk and tape devices in a cluster.
All of the requirements, procedures, and restrictions that are documented for the Solaris 8 DR feature also apply to Sun Cluster DR support (except for the operating environment quiescence operation). Therefore, review the documentation for the Solaris 8 DR feature before using the DR feature with Sun Cluster software. You should review in particular the issues that affect non-network IO devices during a DR detach operation.
DR remove operations on active devices in the primary node are not allowed. DR operations can be performed on non-active devices in the primary node and on any devices in the secondary nodes.
Cluster data access continues both before and after the DR operation.
DR operations that affect the availability of quorum devices are not allowed. See "4.1.1 Dynamic Reconfiguration With Quorum Devices" for more information.
If the current primary node fails while you are performing the DR operation on a secondary node, cluster availability is impacted. The primary node will have no place to fail over until a new secondary node is provided.
To perform DR operations on global devices, complete the following steps in the order indicated.
Table 3-1 Task Map: Dynamic Reconfiguration with Disk and Tape Devices
Task |
For Instructions, Go To... |
---|---|
1. If a DR operation that affects an active device group must be performed on the current primary node, switch the primary and secondary nodes before performing the DR remove operation on the device. | |
2. Perform the DR remove operation on the device being removed. |
Sun Enterprise 10000 Dynamic Reconfiguration User Guide and the Sun Enterprise 10000 Dynamic Reconfiguration Reference Manual (from the Solaris 8 on Sun Hardware collection) |