San on windows 2008

Behavior of multi-path software varies greatly between vendors. If you cannot find the multi-path software, contact your SAN vendor.

If the hosts that are attached are part of a Windows cluster solution, you must use one HBA for the boot process and a separate HBA for shared storage. This section describes several issues that may prevent a Windows server from successfully booting from a SAN:. A common problem when you configure a SAN is that it is possible that multiple hosts may have access to the same logical disk.

This usually occurs because proper LUN management was not employed. The default behavior of Windows is to attach and mount every logical unit that it detects when the HBA driver loads. If multiple hosts mount the same disk, file system damage can occur. It is up to the configuration of the SAN to insure that only one host can access a particular logical disk at a time. Symptoms of multiple hosts accessing the same logical disk are: Disk Management displays the same logical disk on multiple hosts.

Plug and Play notification that new hardware is found may occur on multiple hosts when you add or configure a new logical disk. When you try to access a logical disk by using My Computer or Windows Explorer, you may receive an "Access Denied", "Device not Ready", or similar error message that may indicate that other hosts have access to the same logical disk.

This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Important Specifying OnlineAll on a server that shares disks could lead to data corruption. In this article. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped.

Didn't match my screen. Incorrect instructions. If you download the "Dell EqualLogic Host Integration Tools for Microsoft Installation and user guide" from the support site, it has a description on how it works.

Follow me on Twitter: joesatdell. View solution in original post. You can change from thick to thin provisioning at the EQL side at anytime as long as you have the space availalble in the pool. So if they are all thick now, you know that is not an issue.

When using thin provisioned volumes, it is possible to over provision a pool. Two the OS has to support it. Also if you have EQL snapshots you will likely not get back all the space, since space to be unmapped is likely still allocated in a snapshot. You also need to verify your firmware version as I think it was 6. Also note that if your volume is thick provisioned, re-thinning won't give you any space back; you'd have to turn on thin provisioning on the volume to actually get the space back.