BACKGROUND IMAGE: iSTOCK/GETTY IMAGES

Storage

Managing and protecting all enterprise data

iSTOCK/GETTY IMAGES

Snapshot: Single initiator zoning

Do you practice single-initiator zoning?

Do you practice single-initiator zoning?



Do you use zoning?
Do you agree with this statement?
Who is your principal HBA manufacturer?
Who is your principal switch manufacturer?

Overall, Storage readers are avid zoners. A survey last month revealed that 88% of readers practice zoning of some sort or another. But readers are divided on single-initiator zoning (51% for, 49% against), where the number of HBAs in a zone is limited to one. One proponent of single-initiator zoning explained it this way: "The HBA in their respective servers don't need to talk to each other. Also, with one zone--one HBA policy, RSCNs [registered state change notifications] will not have any impact on the other servers if one of the servers in the fabric is rebooted." Not only that, writes one reader, "Some vendors only support single initiator zones." But for many readers, it's not worth the trouble: "Zones across large SANs can be an administrative nightmare." Performance can also be negatively impacted "if large zone sets are being pushed across ISLs."
Article 17 of 19
This was last published in December 2003

Dig Deeper on SAN technology and arrays

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

Get More Storage

Access to all of our back issues View All

-ADS BY GOOGLE

SearchDisasterRecovery

SearchDataBackup

SearchConvergedInfrastructure

Close