No. In order to present a LUN to more than one server you will need to use something like Windows Cluster Server. Your only option would be to take a snapshot of the LUN and present that snap to the second host. ---- To add to this, in order to share a LUN you need someway to "lock" the data on that LUN from being concurrently accessed AND written to. If you didn't, you'd have data corruption. the Symmetrix (i'm assuming a DMX-3?) really doesn't care what you do to the data; concurrent access is HOST issue and thus, would require clustering, where each host has awareness as to what the other host is doing to data. If you have TimeFinder/Clone, you could simply clone the lun and mount to a different host. We do this for a lot of reporting situations where performance of the primary production luns cannot be affected by another host.

No. In order to present a LUN to more than one server you will need to use something like Windows Cluster Server. Your only option would be to take a snapshot of the LUN and present that snap to the second host. ---- To add to this, in order to share a LUN you need someway to "lock" the data on that LUN from being concurrently accessed AND written to. If you didn't, you'd have data corruption. the Symmetrix (i'm assuming a DMX-3?) really doesn't care what you do to the data; concurrent access is HOST issue and thus, would require clustering, where each host has awareness as to what the other host is doing to data. If you have TimeFinder/Clone, you could simply clone the lun and mount to a different host. We do this for a lot of reporting situations where performance of the primary production luns cannot be affected by another host.