Disk ownership determines which node owns a disk and what pool a disk is associated with.
Data ONTAP stores ownership information directly on the disk.
More information
Guidelines for assigning ownership for disks
When you assign ownership for disks, you need to follow certain guidelines to keep automatic ownership assignment working and to maximize fault isolation.
Assigning ownership for unowned disks and array LUNs
Disks and array LUNs must be owned by a storage system before they can be used in an aggregate. If your system is not configured to assign ownership automatically, or if your system contains array LUNs, you must assign ownership manually.
Removing ownership from a disk
Data ONTAP writes disk ownership information to the disk. Before a spare disk or its shelf is removed from a storage system, you should remove its ownership information so that it can be properly integrated into another system.
Verifying the existence of two paths to an array LUN
If the primary path to any array LUN fails, Data ONTAP automatically maps each port of the Data ONTAP system to a secondary path. You must ensure that there are two paths to each array LUN so that the Data ONTAP system can continue to work when running on a single path.
Verifying path failover for array LUNs
You want to demonstrate that the Data ONTAP system continues to work when running with a single path, for example, when a switch or storage array port is taken offline. You can test path failover by physically removing fibre cables or taking ports offline using Data ONTAP commands.
Guidelines for assigning disks or array LUNs to SyncMirror pools
Assigned disks and array LUNs are associated with a pool, either pool0 or pool1. Keeping all disks on a loop or stack in the same pool ensures redundancy and supports automatic disk assignment.
