Best Practices: Why you can't go it alone


This article can also be found in the Premium Editorial Download "Storage magazine: CDP 2.0: Finding success with the latest continuous data protection tools."

Download it now to read this article plus other related content.

Network consolidation is just one of the technologies forcing storage pros to build stronger IT teams.

BACK IN THE early days of computing, there were do-it-all IT teams to manage your system, network and storage. Then technologies became more complex, and it was more efficient to create silos for network, storage and systems administration. The storage admin role that we know today was born out of the need to manage storage as an independent entity--online and offline, including backup and recovery. The same could be argued for network administrators who were tasked with managing these new environments, making networks secure while connecting them to the powerful and potentially dangerous Internet. Systems admins were left to manage the rest. Recent advances in the technology landscape, however, may signal that history is repeating itself.

Recent acquisitions by Cisco Systems illustrate this point. Remember when Cisco was known as a leading network solutions provider? Now the company is an industry front-runner in Fibre Channel (FC) and IP SAN in large part due to its acquisition of Andiamo Systems. By "platform sharing" between its IP and SAN products, Cisco delivers a multiprotocol uber-device that has Layer 2 and Layer 3 capabilities for TCP/IP and FC stacks. This allows administrators to have a common platform for IP and FC SANs.

Requires Free Membership to View

Cisco's recent acquisition of Nuova is another indicator that it's serious about creating a single, unified access mechanism (akin to InfiniBand) for transparent sharing, provisioning and administration of everything from server access all the way to the application I/O stack. Other vendors are traveling down the same path. For example, Brocade recently acquired Foundry Networks. A few years ago, this acquisition might have left everyone scratching their heads. Today, it makes more sense as we see vendors consolidating the I/O and access stack.

From an IT-preparedness standpoint, it's not too early to start thinking about how IT silos or teams at your company cooperate and collaborate as new technologies merge.

New attitudes for new technologies
In a flat organizational chart, all teams should be considered equally important. This allows for greater cooperation and collaboration. In the same way, new technologies shouldn't be treated as a specific team's responsibility. Is your virtualization project the property of the storage team or the server team? People still need IT managers. But that manager needs to ensure that they're perceived as an equal (not superior) member of the team; more importantly, they need to guarantee that each team has all of the information it needs regarding IT operations and expectations. It's called transparency and it's important to your overall success.

Consider creating a cross-functional architecture team. It helps system architects stay in touch with the operational reality of the solutions they design. It can also create an IT team that considers issues related to all of the functional teams impacted by their work. A case in point is boot from SAN with its quick deployment of multiple images of the same build or platform, quick patch rollback mechanisms, point-in-time copies and replication of the OS. As challenging as it may sound, only complete collaboration between the storage and systems folks can make this project a success.

Perhaps server virtualization or blade server deployment is the single largest catalyst for changing the way we view IT roles and responsibilities. Virtualization is somewhat analogous to how boot from SAN was treated when it first became feasible for OS file systems. These systems were traditionally stored on local disk on the SAN, a spot previously reserved for application data. Suddenly, a new world of possibilities emerged. Virtualization is changing things in a similar way. For example, a favorite location for storing guest images is on NAS. This means provisioning, supporting and troubleshooting for virtual systems on NAS already involves the systems, storage and network teams. However, most systems currently have dedicated access paths for FC and IP, respectively. You could therefore argue that each team has its own access paths to manage and maintain the system. For example, when the network team configures a network interface, the storage paths (via FC) aren't affected. Assuming industry predictions prove true, there will soon be a single port on the back of the server that will be used for both types of access. Now you have the network team configuring a network interface that may have the potential to affect storage traffic. That could be tricky.

Add storage virtualization to this scenario and things begin to look downright dangerous. Today, storage virtualization enjoys the benefit of a dedicated FC or IP network (for NAS virtualization). Tomorrow, with a unified network, that may no longer be true. The teams managing tomorrow's network will also need to be connected in new ways.

This was first published in October 2008

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: