Skip to main content
ONTAP FLI

Perform ONTAP FLI Windows post-migration host remediation

Contributors netapp-barbe
PDFs

After migration, Windows hosts require remediation steps to ensure the newly imported LUNs are properly recognized and functional.

Post migration - Offline FLI

For Offline FLI, bring the LUN online after deleting the lun import and confirming host initiators are connected.

Filesystem devices Physical drives (no filesystem) WFSC Hyper V

Step 1: Rescan the storage on all the mapped hosts

Step 1: Rescan the storage on all the mapped hosts

Step 1: Rescan the storage on all the mapped hosts

Step 1: Rescan the disk management, All the Disks Should connect.

Step 2: Identify the drives that are listed and online the disks

Step 2: add the physical disk to the required application and start.

Step 2: Identify the drives that are listed and online the disks.

Step 2: Select the disks and bring them online, all Should come ONLINE and should get original name and Disk letter.

Step 3: Verify if all the filesystem disks are available and working

Step 3: verify if the all the mapped hosts has the drives available and ONLINE

Step 3: Try to power-on Virtual Machines, Virtual Machine should come online without issue

Step 4: Start the required applications

Step 4: Start the WFSC cluster application and configure the required clustered resources.

Post migration - Online FLI

After deleting the LUN import, check if the LUN is set with -space-reserve disabled and -space-allocation enabled. If not, modify it accordingly.

Filesystem devices Physical drives (no filesystem)

Step 1: Rescan the storage on all the mapped hosts

Step 1: Rescan the storage on all the mapped hosts

Step 2: If the space-allocation is enabled on the target side, then a host reboot is required to reflect the changes.

Step 2: If the space-allocation is enabled on the target side, then a host reboot is required to reflect the changes.

Filesystem devices

Steps

  1. Rescan the storage on all the mapped hosts

    Update-HostStorageCache

  2. Identify the drives that are listed and online the disks.

    Get-Disk | Where-Object IsOffline -eq $true
Set-Disk -Number <DiskNumber> -IsOffline $false

  3. Verify if all the filesystem disks are available and working.

    Get-Volume | Format-Table DriveLetter, FileSystemLabel, Size, SizeRemaining

  4. Start the required applications.

    Start-Service -Name <ServiceName>

Physical drives (no filesystem)

Steps

  1. Rescan the storage on all the mapped hosts.

    Update-HostStorageCache

  2. Add the physical disk to the required application and start.

WSFC

Steps

  1. Rescan the storage on all the mapped hosts.

    Update-HostStorageCache

  2. Identify the drives that are listed and online the disks.

    Get-Disk | Where-Object IsOffline -eq $true
Set-Disk -Number <DiskNumber> -IsOffline $false

  3. Verify if all the mapped hosts has the drives available and ONLINE.

    Get-ClusterResource | Where-Object ResourceType -eq "Physical Disk"

  4. Start the WSFC cluster application and configure the required clustered resources.

    Start-Cluster -Name <ClusterName>
Start-ClusterResource -Name <ResourceName>

Hyper V

Steps

  1. Rescan the disk management, all the disks should connect.

    Update-HostStorageCache

  2. Select the disks and bring them online, all should come ONLINE and should get original name and disk letter.

    Get-Disk | Where-Object IsOffline -eq $true
Set-Disk -Number <DiskNumber> -IsOffline $false

  3. Try to power-on Virtual Machines, Virtual Machine should come online without issue.

    Start-VM -Name <VM_Name>