Home > Workload Solutions > Oracle > Guides > Design Guide—Modernize Your Oracle Database Server Platform and Accelerate Deployments > PowerStore node affinity
In this database configuration, we recommend having multiple volumes for DATA, REDO, and FRA to provide the flexibility to balance the workload across both nodes in a PowerStore appliance. Node Affinity describes the ownership of a volume by a node.
PowerStore performance is optimal when the system performance is balanced across both nodes. The Node Affinity is set when the volumes are mapped to a host. By default, volume Node Affinity alternates between the two nodes in the appliance when mapping volumes to a host to balance the workload. In most cases, this sufficiently balances the load across both nodes in the appliances. If the workload is unbalanced between the nodes, the Node Affinity of the workload should be adjusted.
In our configuration, by default, all the volumes of VM1 were owned by Node B. For the best practices, we changed Node Affinity of volumes so that two volumes of DATA, REDO and FRA are owned by Node A.
The assigned system values include “System select node A” and “System select Node B.”
Node Affinity can be set using the PowerStore CLI (CLI) or PowerStore REST API.
The volume ID is required to make changes to Node Affinity. You can locate the the volume ID using the following command:
pstcli -destination <PowerStore Manager URL/IP> -u <id> -p
<password> /volume -name “DB1_Data-001” show -select id
Once the volume ID is discovered, set preferred Node Affinity. The following command sets the Node Affinity for volume “a5edff43-e9a7-48bd-9b19-e46c7d87d7d2” to Preferred_Node_A. Valid values are Preferred_Node_A.
“Preferred_Node_B”, and “System_Select_At_Attach”.
pstcli - destination <PowerStore Manager URL/IP> -u <id> -p
<password> /volume <volume_id> set - node_affinity “Preferred_Node_A”
Make similar changes to Node Affinity volumes for VM2.