Considerations for reverting Hyper-V over SMB configurations

Before you revert to a Data ONTAP version that does not support nondisruptive operations for Hyper-V over SMB, you must be aware of certain considerations to ensure that you are prepared for the revert.

Before you revert, you must consider the following and take action where necessary:

• If you are reverting to a version of Data ONTAP that does not support SMB 3.0 and persistent handle locks, operations such as failover and giveback are disruptive because Hyper-V servers cannot reclaim disconnected durable handles.
• There must be no file access by the Hyper-V servers to virtual machine files when you revert:
  • You can use the Hyper-V application to migrate virtual machine files to another storage device or to local storage.
  • You can power down all virtual machines and manually terminate Hyper-V server connections to the data LIFs.

    Data ONTAP disables SMB 3.0 before reverting; therefore, if the SMB connections are not manually terminated, Data ONTAP terminates them during the revert.

• You cannot use the Hyper-V over SMB solution if you revert to a version of Data ONTAP that does not support it.

  You must configure the Hyper-V servers to use connected LUNs to store and access virtual machine files. You must then copy the virtual machine files from the SMB shares to the connected LUNs.

• To revert, there can be no ongoing Remote VSS shadow copy operations.

  If there are any, you must wait for the operations to finish or manually abort them before proceeding with the revert. If you need to abort any shadow copy operations, contact technical support for assistance. Upon a revert, Data ONTAP does not delete existing Snapshot copies.