Understanding how volume moves work Data ONTAP supports moving volumes in one aggregate to another within the

same V server. The destination aggregate can be in the same node as the source aggregate or in a di fferent node in the cluster. You can rapidly deploy new storage with no downtime required. For example, you can move data to a newly added storage system, and then rebalan ce the volumes across the cluster with no downtime or processing interruptions. When you move a volume, client access to the volume is not disrupted. You can move your data in the following s cenarios: From a full aggregate to an aggregate that has space for growth. From a node that is being serviced to another node to continue data access. For load balancing volumes in a cluster. Data ONTAP moves volumes in multiple phases which does not disrupt client access . You must meet certain requirements, however, before you can begin a nondisruptive volume move. Related concepts Understanding disk space usage on page 127 How moving a volume works You can move a volume from one aggregate or node to another within the same Vser ver for capacity utilization, improved performance, and to satisfy service-level agreements. Moving a volume does not disrupt client access when the system is moving the vol ume. Moving a volume occurs in multiple phases. A new volume is made on the destination aggreg ate. The data from the original volume is copied to the new volume. During this time, the orig inal volume is intact and available for clients to access. At the end of the move process, client acce ss is temporarily blocked. During this time the system performs a final replication from the sourc e volume to the destination volume, swaps the identities of the source and destination volumes, and the destination becomes the source. After completing the move, the system routes client traffic to the new source volume and resumes client access. The move is not disruptive to client access because the time in which client acc ess is blocked ends before clients notice a disruption and timeout. Client access is blocked for 45 seconds by default. If the volume move operation cannot finish in the time that access is denied, the s ystem aborts this final phase of the volume move operation and allows client access. The system will run the final phase of the volume move operation until the volume move completes or until the default o f three attempts is reached. If the volume move operation fails after the third attempt, the process goes into a cutover deferred state and waits for you to initiate the final phase. You can change the amount of time client access is blocked or the number of time s the final phase of the volume move operation, known as cutover attempts, are run if the defaults ar e not adequate. Also you can determine what the system does if the volume move operation cannot be co mpleted during 121

The volume move doe s not start if the volume has unsupported settings or if there are conflicting operations. such as array LUNs. From a full aggregate to an aggregate that has space for growth. Ways to use volume move You can perform a nondisruptive volume move in different scenarios. Requirements for performing a volume move Before you move a volume nondisruptively.netapp. You can move the volume in the following scenarios: From a high-speed disk to a lower-speed disk or from a lower-speed disk to a hig h-speed disk. 122 | Data ONTAP 8. you must be aware of the type of volum es you can move and the operations that might conflict with the volume move. You cannot move the following types of volumes: A root volume A FlexCache volume A compressed 64-bit volume to a 32-bit volume The source volume must be consistent.com NetApp Interoperability Matrix-support. See the volume move start man page for detail s about moving a volume without disrupting client access. SSDs. The volume must be online. For load balancing nodes in a cluster. then the volume move is terminated an d an error message is . Between different types of disk drives. The following conflicting operations must not be running: SnapRestore of the source volume or the containing aggregate WAFLIron operation on the source or the destination aggregate Revert operation on the storage system Note: FlexClone volumes of the source volume are not moved along with the source volume. Your FAS system or V-Series system must be running Data ONTAP 8. Between different RAID types.the time client access is blocked.1 Cluster-Mode S AN or later. the system checks if the volume you plan to move meets t he specified requirements. All hosts that access any LUNs in the volume must be supported in the Interopera bility Matrix. to satisfy SLA requirements. During the setup phase. such as RAID-DP and RAID4.1 Cluster-Mode Block Access Management Guide for iSCSI and FC Related concepts How the setup phase of volume move works on page 123 How the data copy phase of volume move works on page 123 How the cutover phase of volume move works on page 124 Related information Data ONTAP documentation on the NetApp Support Site-support. FC. such as movi ng it from a busy aggregate to a less busy aggregate or from a high-speed disk to a lower-speed di sk.com/NOW/products/interoperability How the setup phase of volume move works The setup phase creates a temporary destination volume in the destination aggreg ate and initiates data transfer from the source volume to the destination volume. From an aggregate laid out on third-party disks to an aggregate laid out on NetA pp disks by using V-Series systems. From a node that is being serviced to another node to continue data access. or S AS. SATA.netapp. If any of these checks fail.

after which the cutover phase can begin. After each block of data is transferred. You can then manually . After the volume is moved. the data in the source volume and the destination volume is synchronized. Depending on the number of cutover attempts. You must resolve the issue before you can manually resume the volume move. If the cutover phase is successful. or giveback occurs during the volume move. then th e cutover phase is timed out. If the volume move is not completed within the specified cutover period. If a SnapRestore or a WAFLIron operation is started on the source volume. Note: The host application might encounter I/O disruptions if storage system reb oot. The destination volume takes the identity of the source volume. the volume move operation is paused and the reason for the pause is displayed. nondisruptive upgrade (NDU). the LUN at the destination starts processing I/O oper ations. it results in the following: The contents of the destination volume are identical to the source volume. Related concepts Requirements for performing a volume move on page 122 How the setup phase of volume move works on page 123 How the cutover phase of volume move works on page 124 Related tasks Performing a manual cutover of a volume move operation on page 138 How the cutover phase of volume move works The cutover phase is the final phase of the volume move. Understanding how volume moves work | 123 If the volume move finds any unsupported settings or conflicting operations befo re entering the cutover phase. takeover. You should follow the guidance of the error message before you can ma nually resume the volume move. In the d ata copy phase. shutdown. the volume move tries to enter the cutover phase again.displayed. or the containing aggregate. Related concepts Requirements for performing a volume move on page 122 How the data copy phase of volume move works on page 123 How the cutover phase of volume move works on page 124 Related tasks Performing a manual cutover of a volume move operation on page 138 How the data copy phase of volume move works The data copy phase follows the setup phase of a volume move operation. I/O operations are red irected to the destination volume and the volume move is complete. and the volume move reverts t o the data copy phase. logging the appropriate error messages. If cutover is not completed within the specified number of cutover attemp ts. the volume move is canceled and an appropriate erro r message is recorded in the log file. then the volume move is paused and an appropriate error message is recorded in the log file. data is transferred automatically from the source volume to the destination volu me. During the cutover phas e. the de stination volume. the volume move determines whether the cutover phase can be initiated.

Related concepts How moving a volume works on page 121 Requirements for performing a volume move on page 122 How the setup phase of volume move works on page 123 How the data copy phase of volume move works on page 123 124 | Data ONTAP 8.resume the volume move.1 Cluster-Mode Block Access Management Guide for iSCSI and FC Related tasks Performing a manual cutover of a volume move operation on page 138 Understanding how volume moves work | 125 126 | Data ONTAP 8.1 Cluster-Mode Block Access Management Guide for iSCSI and FC .