Change Management within Storage

In an article published by Network World, Change Management reins in Sans, Ron Alon explains that it is prudent to implement change management software within the SAN to acquire the SAN architecture, store the configuration of that architecture, and notify administrators when a change or failure occurs. By automation, Alon asserts that “organizations can gain dramatic improvements in risk and cost reduction of their SAN environments” (Alon, 2004). Without the change management software, the SAN administrator would have to manage change events with time-consuming manual techniques using legacy spreadsheets and other documentation software. The change management engine will automate all monitoring processes: “First, the software establishes a baseline map of the entire SAN environment that is stored in a configuration data repository. The map captures device data and configuration information, including all physical devices, cables, and logical access paths and dependencies between components such as storage devices, servers and switches. The server performs all the mapping and continuously communicates with all SAN devices. It analyzes any configuration change and correlates events and device data to generate a uniform, accurate picture of a SAN and its access paths” (Alon, 2004). The engine also analyzes the SAN and tests for unauthorized paths and vulnerabilities within zoning and clustering and notifying administrators. The software is a “checks-and-balances” layer that permits simulation of changes and examines the probable effects of those changes and monitors them.

Alon, R. (Dec 20, 2004). Change management reins in SANs. Network World, p.29. Retrieved June 17, 2009, from Academic OneFile via Gale