Heterogeneous Storage Management using SMI-S and CIM John Harker Hitachi Data Systems

1. Heterogeneous Storage Management using SMI-S and CIMJohn HarkerHitachi Data Systems

2. Agenda • The Customer Problem • How and why standards play into this • DMTF, CIM, WEBM, SNIA and SMI-S, WMI and WMX • Storage Management • Understanding and managing your infrastructure • Data Management • Virtualized tiered storage • What’s still needed

3. Bus and Hardware I/O Standards Distributed Environment Standards Software Management Standards Hi-Speed interconnect standards Hardware Management Standards Storage Management Standards The well-managed system The need for standardized management is driven by IT customers who want to manage all their systems - standalone, rack mount bricks, blades, and storage - using the same tools. This requires a focus on the intersection of open management standards in the server and storage areas.

4. SNIA and DMTF • SNIA is a vendor-neutral trade organization and ALSO a standards body: • Fast-tracking of standard proposals through INCITS/ANSI • SMI_S v1.0.2 is ANSI INCITS 388-2004 • On-going standard projects include: • IP Storage • Shared Storage Model • Storage Management • Storage Security • Data Management • SNIA contributes to the development of the DMTF CIM standard • Many object and schema changes/extensions in the CIM Specification are the result of SNIA Change Requests • SNIA Technical Working Groups are working to extend the DMTF Common Models to achieve a comprehensive Storage Management Specification (SMI-S)

5. SNIA Storage Management Initiative • Storage Management Initiative (SMI) and the Storage Management Initiative Specification (SMI-S) • Represents the efforts of the SNIA teams driving towards the first common and interoperable management standard for storage networks • Entirely based on CIM and WEBM • SMI-S enhances CIM and WEBM by • Introducing “profiles” that precisely define what classes and fields are required, and how the CIM classes interact • Defining Profiles for array, fabric, hosts, tape library, virtualization, and volume managers. • Defining other necessary components to ensure interoperability – transport, security, discovery, installation, upgrade • SMI-S Status • Version 1.0.2 commercial, 1.1 final, 1.2 out for review - http://www.snia.org/smi/home) • Tested during SNWs and at plugfests • SNIA Colorado SMI-S Interoperability Lab • Test program in place to certify SMI-S compliance (SNIA-CTP) • SMI-S Certification test suites – provider and client side

6. Notes on Commercial CIM Implementations • WMI is a Windows-based implementation of the DMTF Web-Based Enterprise Management (WBEM) initiative, and is fully compliant with the DMTF CIM version 2.0 management schema definitions. But… • Using Microsoft DCOM for communications transport • Using Microsoft Active Directory and Security systems • IBM AIX, Sun Solaris, Linux WEBM implementations use different CIM implementations – some Java, some C++ • Pretty much they don’t talk.

7. HiCommand Storage Services Managerpowered by AppIQ • Hitachi Data Systems HiCommand Storage Services Manager is a SMI-S based Storage Management system • Designed to SMI-S, uses CIM-based object model as the abstraction layer (CIMIQ-X) • Uses SMI-S providers where available • Wraps proprietary APIs in CIM/SMI-S where no SMI-S is available • Can consume from (be a client to) both SMI-S and CIM providers • Communicates with both WEBM and WMI using appropriate transports

8. QoS:Oracle QoS: Exchange QoS: FileServers QoS:Sybase Dynamic Link Manager Protection Manager Rapid Recovery SQL & Exchange Business Application Modules Replication Monitor Chargeback PathProvisioning Global Reporter BackupServicesManager Tiered Storage Manager Tuning Manager • Thunder, Lightning and USP Interfaces • Real time performance agents • User definable polling • Array asset reporting and correlation Storage Operation Modules Storage Services Manager • Visualization / Topology • Reporting • Event Management • Path Management • Capacity Monitoring & Planning • Performance Monitoring & Forecasting CIM / SMI-S+ Model Array Specific and Unstructured Model Common Platform CIMOM 3rd Party CIMOMs Non Standard CIMOM Non Standard Device Manager Storage Array: Services Array Services Configuration Reporting API:CIM, VDS, SMI-S 1.1, EVMS Provisioning • Performance Monitoring • Cache Allocation • Volume Migration & Port Bandwidth Allocation Replication • Universal Replicator • Partitioning Manager • Volume Manager Hitachi Enhanced Heterogeneous Hitachi HiCommand® Suite Architecture

9. HiCommand Storage Services Manager - Multiple CIMOM Architecture Business Application Modules …. QoS for SQL QoS for Oracle QoS for Exchange QoS for File Servers QoS for Sybase …. Storage Operations Modules Chargeback PathProvisioning Addt’l Storage Ops Modules Platform Services + HSSM Base Features HiCommand Storage Services Manager CIM Client CIM-Built SMI-S+ Management Platform xmlCIM over HTTP Java RMI Proprietary Device Integration Platform CIMOM Multiple CIMOMs CIMOM CIMOM CIMOM CIM Provider CIM Provider CIM Providers Proprietary Interfaces Proprietary Interfaces …. …. Managed Array Managed Switch Application Host Managed Device Managed Device Managed Device

10. HiCommand Storage Services Manager consuming from CIM provider vs. SMI-S provider • Host information (With SMI-S CIM extension) • Host model • IP address • OS type and version • Physical memory • Number of processors • DNS name • HBA cards, HBA WWN, HBA vendor, HBA model, HBA serial • # HBA ports, port connection to switch port, switch port WWN, port speed, target storage ports • Persistent bindings • Volumes under host mgmt, mount point, disks, volume management software type and version • Multi-pathing software type and version, meta devices, volumes, type of multipathing, subpaths and status • Volume Management • Events • Asset management • ReportingMonitoringPolicies  Host information (with WMI only) • HBA cards • HBA ports • WWNs

11. Data Management Background - View of Data Lifecycle Relocation Creation Relocation HardwareTrouble Hardware Replacement Archiving Hardware Replacement Deletion Data Lifecycle Application Archive Software Erasure Migration Migration 完全消去 Primary Storage (High-end) Secondary Storage (Mid-range) Tertiary Storage (Low cost) Tertiary Storage (Low cost) Migration Production Data Archive Data Archive Data Archive Data Secondary Storage (Mid-range) Set read-only w/ retention time Replication Migration Production Data Backup Storage(Low cost) Backup Storage(Low cost) Recovery Replica Replica Optimized Volume Placement

12. SNIA Data Management Initiative • SNIA Data Management Forum is working in these areas • Information Lifecycle Management • Data Protection Initiative • Long Term Archive and Compliance Storage Initiative • ILM definition and vision • Information Lifecycle Management is comprised of the policies, processes, practices, and tools used to align the business value of information with the most appropriate and cost effective IT infrastructure from the time information is conceived through it’s final disposition. • Information is aligned with business requirements through management policies and service levels associated with applications, metadata, and data. • ILM’s goal - Storage Management Interface (SMI) • A new set of management practices • A new set of data-centric standards based on SNIA’s SMI-S • Currently SMI-S defines a set of access modes to a StorageExtent and replication functions in CopyServices • More is needed & being worked on to cover additional considerations in overall data lifecycle. This will take a while …

13. Standardized management is one key Hitachi TagmaStore™ Universal Storage Platform 3rd Party Enterprise Storage Hitachi Lightning 9900™ V Series 3rd Party Mid-range Thunder 9500 V Series Hitachi Thunder 9500™ V Series with SATA Performance characteristics Tiered Storage Solutions $$ There is a clear and immediate cost savings potential by implementing Tiered Storage Environments Data Classification is another

14. Application Optimised Storage Step 1: Data vs. Application Classification • Everyone agrees that proper Data Classification is a fundamental component in any Storage Tiering initiative. • However, if you attempt to classify every application and file in your environment today: • It will be laborious and may take years to complete • You will end up with too many classes and policies • It will be difficult to implement in a reasonable timeframe • Consider “Application Classification” instead • Select your top 3 to 5 business applications to start • Identify Applications with the highest ROI • Demonstrating results quickly will validate the project

16. Application Optimised Storage Step 1: Application Classification • There are at least 4 basic categories that classify any application: • Availability  Uptime requirements, often measured in 9’s • Performance  Response Time • Protection  Replication (Local and Remote) and Backup • Retention/Compliance  Archive and Locking capability • The output from these requirements will determine the classes of storage and associated Service Levels needed

17. Application Optimised Storage Step 2Service Level Definition (Examples) • Platinum Service or Class A: This should be provided to your most critical Business applications because it provides the highest level of Availability, Performance and Protection • Gold Service or Class B: High Availability, Acceptable Performance and Recoverability tolerance of 1 to 5 hours • Silver Service or Class C: Business Essential but not as critical • Low Cost drives (performance and availability) and Tape backup for recovery are acceptable

18. Application Optimised Storage Step 3:Infrastructure Selection • Key to Infrastructure Selection: • Efficient, optimized and scalable • lowest possible costs and risks to meet your service levels • FLEXIBLE and DYNAMIC • Business requirements are constantly changing and will drive application requirements throughout their lifecycle. • Data requiring High Performance and availability today, may not need it tomorrow, but may require it again at month end. • Dynamic Tiering in place you can further optimise applications • By tiering active vs. inactive data within applications. Having this flexibility, will allow you to react quickly, optimize performance and minimize backup windows and REDUCE COST.

19. Static Tier 1 Dynamic and Optimised Static Tier 2 Application A Application B Application C Application A Application B Application C Universal, Multi-Tier Storage Competition HDS HDS IBM API FC RAID 1 RAID Thunder SATA Lightning 146GB 72GB FC RAID 1 300GB DRU w/SATA 300GB 76GB A New Paradigm: Virtualisation makes your Infrastructure Agile and Flexible

20. Distributed Environment Standards • There are still numerous gaps in SMI-S & CIM • Current products supporting CIM usually are stovepiped on top of their own CIM stack (e.g. no cross shared directory, security, etc.) • The web services standards community (WW3, DMTF, Oasis) and the grid computing standards community (Globus) are standardizing on a common set of Internet based standards for distributed services (IPC, directory, security, data formats, events). These will be important in solving the stovepiping problem for both remote management and for commercial application support.

21. SMI-S and Data Lifecycle Management • Hitachi is committed to contributing extensively to both DMTF and SNIA • Hitachi agrees that extensions are required to cover additional considerations in the overall data lifecycle and had made proposals in several* of those areas: • additional extent protection modes* • a retention period defining how long the protection mode MUST stay in effect • the definition of behaviors and constraints related to retention periods • non-disruptive extent migration* • maintenance of protection modes through replication and recovery • reclamation services to implement storage extent shredding and reuse after migration and final data deletion*

22. Questions?