Storage management with Chris Poelker - Part I

1. Which tasks take the most time in managing a SAN and why?

1. You can break out SAN management into the following tasks:

  • Discovery/mapping
  • Policy creation/management
  • Device management (LUN/RAID creation, deletion, expansion)
  • Subsystem management/tracking (versioning, firmware, maintenance)
  • Zoning
  • Chargeback/allocation monitoring
  • Performance monitoring/tuning
  • Quota management
  • Event/error management
  • Alarm/alert tracking and reporting
  • Backup/recovery
  • Replication/DR management
  • Documentation updates, topology updates
  • Labeling, Fibre/cable management
  • Capacity planning
  • Disaster recovery planning/testing
  • Scripting and automation generation

The three most time consuming of these is usually performance tuning, capacity planning and documentation. Most good storage management tools have the capability of providing statistical histograms, which are chartable for both performance and capacity. The hard part is to review these statistics and provide guidance and planning with the application/operations and business staffs.

There needs to be consensus from the business side with budget allocation and the technical application side for performance and capacity needs. Coordinating and advising on these efforts can be a time consuming task. This is where a SAN management team seems to spend a lot of time in meetings. Developing the proper recommendations by reviewing and analyzing all this data can take time, and must be done with input from all affected. This is one of the reasons moving control of data management and access to a separate central SAN group is essential in proper SAN management and coordination. This is a new paradigm for many in the applications groups who normally controlled storage attached to their individual servers.

On the documentation side, all labels and SAN topology diagrams MUST be updated to reflect changes during the lifetime of a SAN, especially SAN with multiple large fabrics. Wiring diagrams and cable labels are essential for proper troubleshooting. This takes time, even when the software uses self-discovery, because software cannot label cables. Mislabeled cables can cause nightmares and even outages during normal maintenance. I usually recommend a CMS (cable management system) for large SAN environments.

Click to view Part II.
This was first published in February 2002

Dig Deeper on Data management tools



Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.



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:



  • Tintri VMstore T5000

    Like all of its VM-aware storage systems, Tintri’s first all-flash array -- the Tintri VMstore T5000 -- allows admins to bypass ...

  • SolidFire SF9605

    The high-capacity SolidFire SF9605 uses SolidFire’s Element OS 8 (Oxygen) to deliver new enterprise features such as synchronous ...

  • HPE 3PAR StoreServ 20850

    HPE 3PAR StoreServ 20850 holds 1,024 solid-state drives (SSDs). Hewlett Packard Enterprise claims it can deliver more than three ...





  • Asigra Cloud Backup Version 13

    Asigra Cloud Backup Version 13 provides an AWS Elastic Block Store Snapshot Manager and the ability to support Docker container ...

  • Veeam Availability Suite v8

    Veeam Availability Suite v8 offers several key backup software components in one package, including Veeam Cloud Connect, Snapshot...

  • Druva inSync 5.5

    Druva inSync 5.5 endpoint backup software stands out with its proactive compliance, cloud app integration, full text search and ...