COMMANDCENTRAL STORAGE AND ITIL

Transcription

1 WHITE PAPER Considering A Storage Management Solution? COMMANDCENTRAL STORAGE AND ITIL Key Concepts and Guidelines VERSION INCLUDES TABLE OF CONTENTS STYLES 1

2 TOPICS DISCUSSED Configuration Management What does my storage infrastructure contain? Capacity Management Do I really need to buy more storage? Do my priority application services have sufficient resources? Cost Management How do I explain who is using all of this storage? How can I get my users to be more efficient in the use of their allocated storage? Service Quality Management Is my storage infrastructure performing well? Incident/Problem Management Am I the first to know when an incident occurs? Can I isolate the issue and its cause? How can I be more proactive in reducing incidents in the storage infrastructure? Change Management If I need to update the storage infrastructure, what will be impacted? Can I articulate who, what, and when a change was made in the storage infrastructure? To management? To an Auditor? Release Management Would you like it to take less time and effort to fulfill a request for more storage capacity? Would you like the effectiveness of your best people to be reflected in the actions of the broader storage team? 2

3 EXECUTIVE SUMMARY The purpose of this document is to act as a quick reference guide for the key concepts and features considered in a storage management investigation, proof of concept assessment, or product deployment. The concepts in this document have been aligned with the industry best practices outlined by ITIL (IT Infrastructure Library). The information included in this document are guidelines and are not exhaustive in their discussion of storage management. 3

4 Configuration Management Automatically discover, classify and report on ALL assets in your storage infrastructure, thus creating an always up-to-date repository of information for managing the cost and service quality of your storage environment. Objectives Automated Asset Discovery Enabling Product Architecture Automated Asset Discovery Reduce the Full Time Equivalents (FTE's) required to track storage assets and their dependencies. Asset Compatibility Step 1: Asset Support Are your storage assets supported? Can they be automatically discovered? Example of Supported Vendors Storage Switches HBAs OS Database EMC Brocade Emulex Solaris Oracle HDS/SUN McData QLogic Windows MS SQL IBM Cisco HP HPUX DB2 Engenio CNT IBM AIX Sybase HP EMC (Connectrix) JNI (AMCC) LINUX NEC QLogic SUN NTAPP STK SUN Asset Dependency Mapping Step 2: Asset Dependencies Automated identification of all assets and their associations MS SQL Server Dependency Group - Mapping from the database to spindle Example Fields: Hosts, Device Handles, Filesystems, Files, Volumes, Disks, SQL Instances, SQL Databases, SQL Tablespaces, SQL Files SAN Topology Map 4

5 Asset Inventory Step 3: Automated inventory and categorization of discovered assets Hardware Assets Hosts Arrays/NTAPP Switches HBAs Devices Hubs Bridges/Routers Tapes Software Assets Oracle MSSQL DB2 Sybase Exchange Microsoft Cluster Server VERITAS Cluster Servers NetBackup Asset Reporting Step 4: Report on relevant asset attributes Hardware Attribute Report: HBA Inventory Example Fields: Vendor/Model, Driver, Firmware Version, Worldwide Name, IP Address, Host Software Attribute Report: Oracle Inventory Example Fields: Product Name, Version, Host, Home Directory, Instance, State (Running), Capacity (MB), Used (%), Tablespace/File Group Count Enabling Product Architecture Product Scalability Step 1: CommandCentral Scalability Supporting the largest heterogeneous environments (Customer References Available Upon Request) 5

6 Product Performance Step 2: CommandCentral Performance Optimize responsiveness Tunable Explorers Explorer Details HBA Zoning Virtual Hub Microsoft SQL Server Microsoft Cluster Server Array Management SNMP Bridge Oracle Microsoft Exchange File Scanning Explorer SNMP trap MGEX (Switch Exploration) DB2 VERITAS Cluster Server File Systems and SWAPI Cisco MDS Sybase VERITAS NetBackup Volumes Product Security Step 3: CommandCentral User Access Classify and assign the correct set of privileges User Roles 6

7 Example: Selectable User Privileges Bind Ports Build LUN Groups Build LUNs Create Custom Topologies Customize Reports Define Roles View Data And Reports Edit Database Settings Edit Server Settings Manage Raw Storage Volumes Manage Snapshots Manage Switch Configuration Manage Tasks Manage Users Manage Volumes Manage VSANS Manage Zones Mask LUNs Manage Array Virtual Ports Manage Group Objects Manage HBA Port Groups Manage Host Connections Manage Licenses Manage LUN Groups Manage Objects And Attributes Manage Policies Manage Provisioning Accounts Provision Storage Provision Virtual Ports Provision Zones Replace or Clone HBA Storage Account Based Provisioning Dismiss And Acknowledge Alerts 7

8 Capacity Management Extend the time to your next storage procurement by identifying immediate opportunities to streamline the available storage capacity for hard-savings. Prioritize and forecast storage capacity for your critical applications. Objectives o Increase Storage Utilization/Reduce Procurement Frequency o Plan Storage Infrastructure Capacity in Context of Applications Increase Storage Utilization/Reduce Procurement Frequency Reclaiming Storage: Can I post-pone my next storage procurement? Step 1: Unclaimed Storage Identify Un-configured or Unknown Storage for the Creation of Logical Devices Step 2: Unassigned Storage Identify Available, Unallocated and Unknown LUNs for Allocation Step 3: Underutilized Storage Identify Underutilized Storage Assigned to an LVM Step 4: Storage Allocation Tuning Identify Un-configured or Unknown Storage for the Creation of Logical Devices Total Online Storage Drill-through graphic to identify where higher storage utilization can be achieved 8

9 NTAPP Unified Storage Example Fields: Quota Detail, QTree Detail, SnapMirrors, Snapshots Storage Allocation by Vendor What is my utilization of a particular vendor's storage? Potentially Wasted Storage Where is there unclaimed capacity that can be utilized? 9

10 Plan Storage Infrastructure Capacity in Context of Applications Application Management: Produce a capacity plan predicting the storage resources needed to achieve agreed service levels Step 1: Databases - Oracle, MS SQL, DB2, Sybase 10

11 Step 2: - Exchange Example Fields: Mail Box Stores, Mail Boxes, Messages, Used(MB), files Step 3: Backup NetBackup Example Fields: LUNs, Tape Device, Path Count Additional Capacity Planning Reports When Will I Run Out of Storage? Top Ten Clients - File System Space File System Capacity Trend Allocation by Array Top Ten Clients LUN Available Top Ten Clients - LUN File System Details LUN Details Top Ten Clients LUN Utilization Top Ten Clients - Ports File System Utilization Trend LUN Capacity Trend Top Ten Databases Top Ten Clients - Volumes Allocation by Array Vendor Top Ten Clients File System Top Ten Clients File System Space Allocation by LUN RAID Utilization Available Level 11

12 Cost Management Because we have detailed information about your storage capacity and can map the utilization of that capacity to your customers, we can enable you to transparently reflect storage consumption to your users. We can also create opportunities to drive more efficient use of the capacity allocated to your customers! Objectives o Recovering Storage Costs o Encourage More Efficient Use of Storage Resources Recover Costs from Storage Capacity Allocated to Customers Step 1: Define cost drivers Example Metrics Driving Storage Management Costs Assets Current Capacity (TB) Capacity growth/month (TB) Estimated storage cost for growth '07 Annual rate of growth Unburdened cost per TB (.01/MB) Estimated storage cost for growth '08 Projected Capacity in 12 months (TB) Burdened cost per TB (50% load) Estimated storage cost for growth '09 Projected Capacity in 24 months (TB) Annual decrease in storage costs Total 3 year storage costs Projected Capacity in 36 months (TB) Management Effectiveness Process Efficiency Personnel Costs Current utilization rate Estimated automation time savings Burdened FTE Storage Admin ($US) Estimated "unclaimed" storage SA's required today TB's managed per SA Risk Provisioning tasks/month Probability of human error Probability of error being severe/critical Cost per critical/severe error Other Economies Improved hardware vendor leverage Tiered storage savings Reduced software point tool costs Step 2: Define cost recovery model - Charging needs to be seen as being simple, understandable, fair and realistic Possible charging policies include: Cost: Price = Cost Cost-plus: Price = cost+/- X% Going rate: Price is comparable with other internal departments costs within the organization or with similar organizations Market rate: Price matches that charged by external suppliers Fixed price: A set price agreed for a set period with the customer, based on anticipated usage Possible chargeable storage metrics include: Used File System Capacity Total File System Capacity Ports Assigned to Host Claimed LUN Capacity 12

13 Step 3: Deliver reports reflecting the consumed storage capacity and associated cost Example: Cost/Capacity Mapping Drive chargeback systems with accurate storage capacity information to ensure IT operations correctly recaptures total cost of storage infrastructure. Encourage More Efficient Use of Storage Resources Can I show my users/customers how to reduce their storage costs? Step 1: Identification of Potentially Wasted Space Influence the demand for storage resources by sharing relevant areas for users/customers to reduce their wasted space. Duplicate Files 13

14 Examples: Potentially Wasted Space Duplicate File Summary For each file, the number of files and the amount of storage used. Stale Files Summary - By Last Accessed Date The files that have gone the longest without being accessed by a user or application, ranked by the date they were last accessed. Stale Files Summary - By Last Modified Date The files that have gone the longest without being modified by a user or application, listed by the date they were last modified. Stale Files Summary - By Creation Date The files that have existed the longest, listed by the date they were created. 14

15 Service Quality Management Ensure the quality of storage service meets internal customer expectations by managing performance of key storage components, specifically switch port, HBA and array performance. We can help you identify a potential service quality issue before it impacts your customers. Objective: Deliver Optimal performance to Users/Customers Deliver Optimal performance to Users/Customers Asset Performance Metrics Reduce risk of performance problems and failure Monitor Quality of Service Delivery: Host Performance Example Performance Metrics: Host, Physical Disk/Tape, Virtual Disk/LUN Host Physical Disk/Tape Virtual Disk/LUN BlocksRead (blocks) BlocksRead BlocksRead BlocksWrite (blocks) BlocksWritten BlocksWritten DeviceReceiveUtilization (%) Disk bytes Read (per sec) IO_ReadPerSecond DeviceTransmitUtilization (%) Disk bytes Written (per sec) IO_WritePerSecond HBAReceiveUtilization (%) KbytesRead_PerSecond KbytesRead_PerSecond HBATransmitUtilization (%) KbytesWritten_PerSecond KbytesWritten_PerSecond ReadOps (ops) Reads_PerSecond Reads_PerSecond ReadTime (milliseconds) Tape bytes Read (per sec) PercentageCacheReadMisses WriteOps (ops) Tape bytes Written (per sec) PercentageSequentialReads WriteTime (milliseconds) Writes_PerSecond Read_IO_Requests ReadCacheHits ReadHitRatio Write_I WriteCacheHits WriteHitRatio Writes_PerSecond 15

16 Example Performance Metrics: Array/Cache, CPU Array/Cache CPU Performance CacheReadHitsPerSecond # CPUs CacheWriteHitsPerSecond CPU Busy % PercentageCacheReadWriteHits CPU Switch Invocations PercentageDirtyCachePages CPU Context Switches ReadCacheHits ReadHitRatio ReadWriteCacheHitRatio WriteCacheHits WriteHitRatio WriteMissRatio Example NTAPP Performance Metrics: Storage Operations, FC Controller/Storage Adapter NTAPP Unified Storage Operations NTAPP FC Controller/Storage Adapter # CIFS Operations (per sec) Bytes Received # DAFS Operations (per sec) Bytes Sent # FCP Operations (per sec) FC Kbytes In # Http Operations (per sec) FC Kbytes Out # iscsi Operations (per sec) iscsi Kbytes In # NFS Operations (per sec) iscsi Kbytes Out Streaming Packets Asset Performance Metrics Elimination of unnecessary spare capacity and optimization of equipment Monitor Quality of Service Delivery: Switch Performance 16

17 Incident/Problem Management Reduce the mean time to resolution (MTTR) for all storage related incidents through pre-defined policies and alerts, alert forwarding and visual dependency maps to identify root cause for an event. When an event does occur, we can give you the JIT (just-in-time) information to identify, understand and remediate the problem, Objectives o Issue Identification o Issue Isolation o Proactive Reduction of Incidents Issue Identification Step 1: Leverage pre-defined alert notification policies Incident classification and prioritization Alert Policies Leverage Pre-Defined Policies to Drive Prioritized Alerting Step 2: Forwarding alerts to the appropriate framework, team or individual Incident ownership, monitoring, tracking and communications Event Management Forward Alerts via SNMP traps, , etc 17

18 Step 3: Receiving Alerts - Incident detection and recording Alert Notifications: Summary of Active Alerts Issue Isolation How is the alert related to the infrastructure and storage services? Step 1: Isolating events and impact to storage service Investigation and diagnosis Event Isolation Rapidly resolve service interruptions with accurate configuration information supporting root cause analysis into the service infrastructure 18

19 Step 2: Isolating events caused by changes to the infrastructure What changes were made before the outage occurred?. Proactive Reduction of Storage Incidents Step 1: Historical Alert Analysis Trend Analysis/ Targeting support action Are there recurring issues? Can a solution be put in place to prevent the problem from occurring again? Total Active Alerts Count The number of alerts, by severity, currently active in the network. Top Critical Objects by Alert Count Objects reporting the greatest number of critical alerts over the report time frame. Top Critical Objects by Alert Duration Objects having active critical alerts for the longest total duration over the report time frame. (These are objects likely to have persistent or long-term problems.) Total Alert Duration Average, maximum, and minimum duration for all alerts, in minutes. Data is grouped by alert severity level over the report time frame. Time to Acknowledge Duration Average, maximum, and minimum time from when an alert was created until it was acknowledged, in minutes. Data is grouped by alert severity level over the report time frame. Acknowledge to Clear Duration Average, maximum, and minimum time from when an alert was acknowledged until it was cleared, in minutes. Data is grouped by alert severity level over the report time frame. 19

20 Change Management Reduce the mean time to failure (MTTF) by proactively validating the upstream impact of a storage infrastructure change. Don't make changes blindly know the customer impact to a change before taking the action. Objectives o Assess the Impact and Risk of a Planned Change o Track Changes and Change Requests Assess the Impact and Risk of a Planned Change Reduce service disruptions by identifying storage service dependencies before executing a planned change. Clarify the upstream and downstream impact of making a change to the storage infrastructure. How will the modification to an existing LUN impact a customer's database? SAN Topology Map 20

21 Track Changes and Change Requests Fulfill storage infrastructure audit requirements by automatically capturing changes to the storage infrastructure. Change History Report Audit the frequency of requested changes by event type and user 21

22 Release Management Reduce the FTE's required to make a modification to the storage infrastructure. Once you have identified which changes that you want to make, leverage the process automation/workflow and tools to take the appropriate action against the storage infrastructure in a structured and systematic fashion. Capture your team's best practices in a workflow that guarantees the same quality level every time you take an action against the infrastructure. Objective: Reduce Time and Increase Quality for Storage-Related Requests Reduce Time and Increase Quality for Storage-Related Requests Leverage a common portal to manage storage-related requests Guarantees best practices are being applied to every activity and back-out plans are predefined for each service requests 22

23 Closed-Loop Management of Storage Requests Guarantees changes released into the storage infrastructure are of a known quality and all associated tasks for a given request are sequenced and executed appropriately 23

24 Leverage Tools to Rapidly Execute Steps in Storage Management Requests Tool Storage Provisioning Tool Zone Set Builder Zone Builder Zone Alias Builder Virtual Fabric Builder RAID Group Builder LUN Builder LUN Query Tool Port Bundle Tool HBA Replacement Tool Hub Editor Host Editor Group Builder Enclosure Editor Snapshot Editor Description Provision storage for a host on the network. Create a new zone set or edit an existing one. Create a new zone or edit the contents of an existing one. Create a new zone alias or edit the contents of an existing one Create a new virtual fabric or edit the contents of an existing one Create a Volume Space, Disk Group, Volume Array, or Volume Group on an array. Create a new LUN, device, LDEV, or LUSE on a supported enclosure. Search the storage network for LUNs described by the query parameters you provide. Create a new port bundle or edit an existing one. Replace a failed HBA with a working HBA on the same host and reassign its associations. Create a new hub or edit the contents of an existing one. Create a new host and assign HBA or orphan nodes to it, or edit the nodes assigned to an existing host. Create a new group or edit the contents of an existing one. Create a new enclosure on the storage network and add storage objects to the enclosure, or edit the contents of an existing enclosure. Create a new SAN Snapshot or edit or delete an existing one. 24