Workaround:

Below are the steps that can be used to help address this issue:

1. Open Registry Editor (start > run > regedit)

2. Browse to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\VolumeManager

3. Change the RetryEnumMountPoint value from 0 to 1

4. Once the above is enabled (set to 1), the RetryEnumMPAttempts value is used to determine how many times Volume Manager will make use of the API to determine the drive letter / drive path for a volume. By default, this value is 5 and should be used first. If issues are still seen, then this value can be increased until the issue is no longer occurring.

Note: Using the above workaround has a performance impact on the service group offline and failover operations. This happens because, during the service group offline or failover operation, the performance of the disk group deport operation is impacted by "n/2" seconds maximum, where "n" is the number of volumes in the disk group. To resolve this issue, the operation needs to be retried after a few milliseconds so that the Microsoft API GetVolumePathNamesForVolumeName() returns correct information. As a workaround, a new retry logic is added to the GetVolumePathNamesForVolumeName() API so that it retries the operation in case the mount path returned is empty. It will retry after every 100 milliseconds for "n" number of attempts (5 by default), which can be configured using the registry. This retry logic is disabled by default.

During a failover, when a disk group gets imported, SFW mounts all volumes of the disk group by querying the mount points using Microsoft API GetVolumePathNamesForVolumeName(). Due to issues with this API, it sometimes returns NUL (as if the volume is not mounted); therefore, VEA will not display the proper drive letter or drive path for the volume.

An enhancement was made in Cumulative Patch 7 (CP7) for SFW-HA 6.0.1. It is strongly recommended systems impacted by this issue upgrade to the latest Cumulative Patch which can be found on  https://downloads.infoscale.com/

In addition, a workaround can be implemented that will result in Volume Manager calling the API again in hopes it returns the proper value, and not NUL.

Following a failover of a cluster group containing a Volume Manager Diskgroup (VMDg) resource, VEA does not show the drive letter or mounted folder paths of a volume even though the volume is successfully mounted with the expected drive letter or mount path.

ETrack: 3347495 ETrack: 3347491