Veritas InfoScale 7.3.1 Release Notes - Windows
- Release notes for Veritas InfoScale
- Limitations
- Deployment limitations
- Cluster management limitations
- Storage management limitations
- Multi-pathing limitations
- Replication limitations
- Solution configuration limitations
- Internationalization and localization limitations
- Interoperability limitations
- Known issues
- Deployment issues
- Cluster management issues
- Cluster Server (VCS) issues
- Cluster Manager (Java Console) issues
- Global service group issues
- VMware virtual environment-related issues
- Cluster Server (VCS) issues
- Storage management issues
- Storage Foundation
- VEA console issues
- Snapshot and restore issues
- Snapshot scheduling issues
- Storage Foundation
- Multi-pathing issues
- Replication issues
- Solution configuration issues
- Disaster recovery (DR) configuration issues
- Fire drill (FD) configuration issues
- Quick recovery (QR) configuration issues
- Internationalization and localization issues
- Interoperability issues
- Miscellaneous issues
- Fibre Channel adapter issues
- Deployment issues
Storage reclamation commands do not work when SFW is run inside Hyper-V virtual machines
This issue is observed on Hyper-V virtual machines where disks that support thin provisioning and reclamation are presented in a pass-through mode. SFW storage reclamation commands run inside a virtual machine appear to succeed, but the provisioned size of the LUNs remains unchanged. Hyper-V filters certain SCSI commands sent from the guest operating systems to the pass-through disks. Refer to the Microsoft Hyper-V documentation here:
http://technet.microsoft.com/en-us/library/dd183729(WS.10).aspx
This issue occurs because SFW uses one of the filtered SCSI commands to request thin storage reclamation. (2611988)
Workaround: In Windows Server operating systems, Hyper-V allows disabling the filtering of SCSI commands. This allows the full SCSI command set to be sent to the pass-through disks mapped to the virtual machine.
Note:
Hyper-V does not support disabling filtering of SCSI commands on Windows Server operating systems.
To disable SCSI command filtering, modify the virtual machine configuration and set the
property to . Use the Virtualization WMI provider or edit the virtual machine configuration xml file manually. Refer to the Microsoft Hyper-V documentation for more details.Alternatively, you can also use the following PowerShell script to disable SCSI command filtering for a virtual machine:
$HyperVGuest = $args[0]
$VMManagementService = gwmi Msvm_VirtualSystemManagementService -namespace "root\virtualization"
foreach ($Vm in gwmi Msvm_ComputerSystem -namespace "root\virtualization" -Filter "elementName='$HyperVGuest'")
{ $SettingData = gwmi -Namespace "root\virtualization" -Query "Associators of {$Vm} Where ResultClass=Msvm_VirtualSystemGlobalSettingData AssocClass=Msvm_ElementSettingData" $SettingData.AllowFullSCSICommandSet = $true $VMManagementService.ModifyVirtualSystem ($Vm,$SettingData.PSBase.GetText(1)) | out-null }
Save this script to a file and run it from the PowerShell command line on the Windows Server Hyper-V host system. The name of the virtual machine must be passed as an argument.
For example, if you save this script to a file named disablescsifiltering.ps1, run this script from the PowerShell command prompt as follows:
C:\>.\disablescsifiltering.ps1 virtualmachine_name
This script sets the AllowFullSCSICommandSet property value to True.
Note:
Before you run this script, you may have to set the PowerShell execution policy to allow execution of unsigned scripts on the local system. Refer to the Windows PowerShell documentation for more information.