-
Title
Fiber attached drives are not processed by RUM or VMOVER -
Description
Under a Windows File Clusters where the disks are mounted via Fiber Attached Netapp Storage. When using Quest RUM or Vmover directly on the server only the servers Local C:\ OS Drive is processed. All Fiber attached drives are not processed. There is a 14 year old KB article describing this problem .
https://support.quest.com/migration-manager-for-ad/kb/27673/qmm-rum-resource-updating-manager-does-not-process-all-drives-attached-to-a-computer
The article suggests using the Volume command which I think would work but that would require me to have an inventory of all said clusters with the UNC paths to the shares. Under large environments this is a time consuming task.
-
Cause
the 8.15 version from vmover.exe skips fiber attached drives as they are not enumerated. -
Resolution
A custom newer version of the vmover.exe has been provided from Dev team to dealt this issue and will be subsequently added to the overall product version for a future release.
The new custom version of the vmover.exe is for version 8.15.5.1 (version generated on the 7/21/2022) that will not skip Fiber attached drives.
-
Defect ID
374144 -
Additional Information
Note: Sendomly is been seen the vmover.exe skipping drives based on fiber attached drives due to been so low the level of customer using this type of configuration that, the workaround ( KB 27673) should be enough. But the size and scope (ticket of this project the issue was address in ticket number 5116713) . This newer vmover.exe will be added for future releases of the QMMAD tool.