Presentation is loading. Please wait.

Presentation is loading. Please wait.

1© Hitachi Data Systems Corporation 2013. All Rights Reserved. W HAT ’ S N EW IN HCP 6.0 Eamon O Neill, HCP Product Management May 15-17, 2013.

Similar presentations


Presentation on theme: "1© Hitachi Data Systems Corporation 2013. All Rights Reserved. W HAT ’ S N EW IN HCP 6.0 Eamon O Neill, HCP Product Management May 15-17, 2013."— Presentation transcript:

1 1© Hitachi Data Systems Corporation All Rights Reserved. W HAT ’ S N EW IN HCP 6.0 Eamon O Neill, HCP Product Management May 15-17, 2013

2 2Hitachi Data Systems – Confidential. Not for redistribution. HDS C ONFIDENTIAL AND P ROPRIETARY The documents and other material available on Hitachi's corporate website may contain forward-looking statements which reflect management's current views with respect to certain future events and financial performance. Words such as "anticipate," "believe," "expect," "estimate," "intend," "plan," "project" and similar expressions which indicate future events and trends identify forward-looking statements. Actual results may differ materially from those projected or implied in the forward-looking statements and from historical trends. Further, certain forward-looking statements are based upon assumptions of future events which may not prove to be accurate. In addition to the risks and uncertainties discussed in Hitachi's SEC filings, the following factors could cause actual results to differ materially from those projected or implied in any forward-looking statements :rapid technological change, particularly in the Information & Telecommunication Systems segment and Electronic Devices segment; uncertainty as to Hitachi's ability to continue to develop products and to market products that incorporate new technology on a timely and cost-effective basis and achieve market acceptance; fluctuations in product demand and industry capacity, particularly in the Information & Telecommunication Systems segment, Electronic Devices segment and Digital Media & Consumer Products segment; increasing commoditization of information technology products, and intensifying price competition in the market for such products; fluctuations in rates of exchange for the yen and other currencies in which Hitachi makes significant sales or in which Hitachi's assets and liabilities are denominated, particularly between the yen and the U.S. dollar; uncertainty as to Hitachi's access to liquidity or long-term financing, particularly in the context of restrictions on availability of credit prevailing in Japan; uncertainty as to Hitachi's ability to implement measures to reduce the potential negative impact of fluctuations in product demand and/or exchange rates; general economic conditions and the regulatory and trade environment of Hitachi's major markets, particularly, the United States, Japan and elsewhere in Asia, including, without limitation, continued stagnation or deterioration of the Japanese economy, or direct or indirect restriction by other nations of imports; uncertainty as to Hitachi's access to, or protection for, certain intellectual property rights, particularly those related to electronics and data processing technologies; Hitachi's dependence on alliances with other corporations in designing or developing certain products; and the market prices of equity securities in Japan, declines in which may result in write-downs of equity securities Hitachi holds.

3 3Hitachi Data Systems – Confidential. Not for redistribution. HCP 6.0: COMPELLING ADVANCEMENTS IN DATA ANALYSIS, IN VIRTUALIZATION, AND IN CLOUD TOPOLOGIES Virtual Network Management System Metadata Custom Metadata File Multiple Custom Metadata Annotations  Revolutionary enhancement: Structured Custom Metadata analogous to Relational DBMS schema. New Custom Metadata Properties do for unstructured data what SQL did for structured data – can perform specific queries that are data context and type aware.  Other exciting features around… API compatibility

4 4Hitachi Data Systems – Confidential. Not for redistribution. HCP 6.0 F EATURES BY T HEME  Big Data / Intelligent Objects ‒ Structured Custom Metadata (Content Properties) ‒ Multiple custom metadata annotations ‒ Metadata Only ‒ Custom metadata language support – Chinese  Cloud ‒ Amazon S3 compatible API ‒ Tier to external  Carrier Class / Operational Efficiency ‒ Dual outbound links ‒ Virtual Network Management ‒ Link Aggregation ‒ VMware edition of HCP leveraging VMware HA ‒ Customer Branding ‒ Nodes with higher per- server storage density

5 5 S TRUCTURED C USTOM M ETADATA BRINGING STRUCTURE TO UNSTRUCTURED CONTENT

6 6Hitachi Data Systems – Confidential. Not for redistribution. S TRUCTURED C USTOM M ETADATA – PRIMARY USE CASE M AKING C USTOM METADATA QUERIES CONTEXT AWARE Retrieve movies with “Quentin Tarantino” HCP 5 custom metadata query Unstructured - can only find text Is Quentin Tarantino an actor or a director? Unstructured - can only find text Is Quentin Tarantino an actor or a director?

7 7Hitachi Data Systems – Confidential. Not for redistribution. S TRUCTURED C USTOM M ETADATA – PRIMARY USE CASE HCP 6 custom metadata queries Context aware: can find Quentin Tarantino as actor but not as director Structured. Custom Metadata no longer considered a text string – XML (below) is split into separately indexed properties: actor and director Context aware: can find Quentin Tarantino as actor but not as director Structured. Custom Metadata no longer considered a text string – XML (below) is split into separately indexed properties: actor and director Quentin Tarantino Quentin Tarantino Retrieve movies with “Quentin Tarantino” as actor only Retrieve movies with “Quentin Tarantino” as director only Retrieve movies with “Quentin Tarantino” as actor and director

8 8Hitachi Data Systems – Confidential. Not for redistribution. S TRUCTURED C USTOM M ETADATA – ANALOGOUS TO RDBMS SCHEMA Define if attribute indexed Define attribute type Oracle SQL schema definition similar to HCP Content Property definition

9 9Hitachi Data Systems – Confidential. Not for redistribution. S OPHISTICATED CONTENT PROPERTIES C USTOM METADATA QUERIES NOW UNDERSTAND RANGE AND TYPE Retrieve other images for same patient where image date within range November – December, 2007 With HCP 5, had to know exact date HCP 6: range queries possible With HCP 5, had to know exact date HCP 6: range queries possible

10 10Hitachi Data Systems – Confidential. Not for redistribution. S TRUCTURED C USTOM M ETADATA Q UERY – ANALOGOUS TO RDBMS QUERY MQE exposes content properties Structured queries with MQE API and Search Console

11 11Hitachi Data Systems – Confidential. Not for redistribution. S TRUCTURE ENABLES MORE SOPHISTICATED APPLICATIONS WITH HCP, E. G. E -D ISCOVERY After s are archived with HDIM, can retrieve a specific message

12 12 M ULTIPLE CUSTOM M ETADATA A NNOTATIONS..

13 13Hitachi Data Systems – Confidential. Not for redistribution. M ULTIPLE M ETADATA A NNOTATIONS – PRIMARY USE CASE LU GA Land Usage Analysis ED Elevation Deviation Data WT Water Table Variations PD Population Density Distribution Government Agency Listing Note: Each annotation shown was generated by separate programs that analyzed the image. Object

14 14Hitachi Data Systems – Confidential. Not for redistribution. Custom Metadata System Metadata M ULTIPLE M ETADATA A NNOTATIONS – E XAMPLE System Metadata  Filename: NZ JPG  Created: January 4, 2012  Last modified: March 23, 2012 H CP 5 OBJECT File File + Metadata = Object File Class = Image Custom Metadata  Subject: Family reunion  Place Taken: Wellington  Category: Travel

15 15Hitachi Data Systems – Confidential. Not for redistribution. M ULTIPLE M ETADATA A NNOTATIONS – E XAMPLE CONTINUED System Metadata  Filename: NZ JPG  Created: January 4, 2012  Last modified: March 23, 2012 H CP 6 OBJECT File + Metadata = Object File Class = Image Custom Metadata Annotation 1  Protection: National Landmark  Location: Castlepoint, Wellington, New Zealand  Type: Caisson System Metadata Custom Metadata File Custom Metadata Annotation 2  Construction year: 1913  Management: Remote  Height: 23 m

16 16 M ETADATA O NLY

17 17 DATACENTER M ETADATA O NLY - E FFICIENT S TORAGE U TILIZATION W ITH M ULTIPLE S ITES Replication Link  Object Replicated  Data Portion Removed - Metadata Stays  Smaller Storage Required Content still accessed via primary HCP

18 18Hitachi Data Systems – Confidential. Not for redistribution. M ETADATA O NLY B ENEFITS  Transparent: Client applications do not have to re-configure access to the data; URLs unchanged even when reading from replica.  Complete offering for Right-sized Edge: ‒ Now have efficient storage of objects at the non HQ data centers. Presents HTTP APIs to apps at the edge. ‒ Complements HDI, which enables efficient storage of files at edge. Presents CIFS and NFS API to apps at the edge.  Differential Data Management: Create different policy for each namespace – some applications may keep data nearby, some not. Visibility into data bytes saved.

19 19 HS3 AMAZON S3 COMPATIBLE API

20 20Hitachi Data Systems – Confidential. Not for redistribution. A MAZON S3 COMPATIBLE API EXPANDS ACCESS TO HCP  Products that send data to Amazon S3 can now also send data to HCP without requiring an HDS specific integration. For example… DragonDisk

21 21Hitachi Data Systems – Confidential. Not for redistribution. A MAZON S3 COMPATIBLE API WITH NEW DATACENTER TOPOLOGIES  Hybrid: Enterprise can run internal apps that write data, externally to Amazon S3 or other Public Utility clouds, to HC3 or Hosted Provider clouds, and internally to on- premise HCP cloud, without modification of code. Application

22 22Hitachi Data Systems – Confidential. Not for redistribution. A MAZON S3 COMPATIBLE API TOOLS Cyberduck s3fs Many other tools: Lorem ipsum dolor sit amet consectetur adipisicing elit Move content between namespaces Copy content from filesystem Copy content from other clouds Create namespace Add custom metadata  Ecosystem: Hundreds of apps already integrated with Amazon S3 API, and hence automatically integrated with new HCP API. Large community of developers building S3 compatible tools. For example, CloudBerry can do management and data movement with HCP.

23 23Hitachi Data Systems – Confidential. Not for redistribution. NFSCIFSWebDAVSMTPHCP RESTAmazon S3 N EW S3 COMPATIBLE API COMPLEMENTS EXISTING ACCESS METHODS

24 24 V IRTUAL NETWORK MANAGEMENT

25 25Hitachi Data Systems – Confidential. Not for redistribution. V IRTUAL NETWORK MANAGEMENT U SE C ASES  The default: a single untagged network. No change after upgrade from 5.0. admindata Tenants and Cluster Management

26 26Hitachi Data Systems – Confidential. Not for redistribution. V IRTUAL NETWORK MANAGEMENT U SE C ASES  The default: a single untagged network. No change after upgrade from 5.0.  The HCP is connected to one VLAN (A) for all network traffic. admindata vlan: A Tenants and Cluster Management

27 27Hitachi Data Systems – Confidential. Not for redistribution. V IRTUAL NETWORK MANAGEMENT U SE C ASES  The default: a single untagged network. No change after upgrade from 5.0.  The HCP is connected to one VLAN (A) for all network traffic.  All cluster management is done over a separated VLAN (M). May include tenant management. vlan: A vlan: M admindata Cluster Management Tenants

28 28Hitachi Data Systems – Confidential. Not for redistribution. V IRTUAL NETWORK MANAGEMENT U SE C ASES  The default: a single untagged network. No change after upgrade from 5.0.  The HCP is connected to one VLAN (A) for all network traffic.  All cluster management is done over a separated VLAN (M). May include tenant management.  Each tenant is connected to individual networks VLAN (A), (B) and (C) for data and tenant administration. vlan: A vlan: C vlan: B admindata vlan: M Cluster Management Tenants

29 29Hitachi Data Systems – Confidential. Not for redistribution. V IRTUAL NETWORK MANAGEMENT U SE C ASES  The default: a single untagged network. No change after upgrade from 5.0.  The HCP is connected to one VLAN (A) for all network traffic.  All cluster management is done over a separated VLAN (M). May include tenant management.  Each tenant is connected to individual networks VLAN (A), (B) and (C) for data and tenant administration.  Multiple tenants can share the same network. vlan: Avlan: B admindata vlan: M Cluster Management Tenants

30 30Hitachi Data Systems – Confidential. Not for redistribution. V IRTUAL NETWORK MANAGEMENT U SE C ASES  The default: a single untagged network. No change after upgrade from 5.0.  The HCP is connected to one VLAN (A) for all network traffic.  All cluster management is done over a separated VLAN (M). May include tenant management.  Each tenant is connected to individual networks VLAN (A), (B) and (C) for data and tenant administration.  Multiple tenants can share the same network.  One tenant may have separate network for data and one for tenant management. vlan: C admindata vlan: M vlan: A vlan: B Cluster Management Tenant

31 31Hitachi Data Systems – Confidential. Not for redistribution. V IRTUAL NETWORK MANAGEMENT U SE C ASES  The default: a single untagged network. No change after upgrade from 5.0.  The HCP is connected to one VLAN (A) for all network traffic.  All cluster management is done over a separated VLAN (M). May include tenant management.  Each tenant is connected to individual networks VLAN (A), (B) and (C) for data and tenant administration.  Multiple tenants can share the same network.  One tenant may have separate network for data and one for tenant management.  Replication traffic over a separate network. admindata vlan: R Replication Tenants and Cluster Management

32 32 DUAL OUTBOUND REPLICATION LINKS

33 33Hitachi Data Systems – Confidential. Not for redistribution. Application B Replicating tenant Nonreplicating tenant Replicating namespace Nonreplicating namespace Locally created tenants Replicated tenantsReplication link Tenant-1 Tenant-2 Tenant-3 Tenant-1 Tenant-2 D UAL OUTBOUND REPLICATION LINKS – PRIMARY USE CASE App 1 App 2  Bidirectional Replication topology with disaster recovery support  No SPOF

34 34Hitachi Data Systems – Confidential. Not for redistribution. D UAL OUTBOUND REPLICATION LINKS – E XAMPLE 2  Example topology 2: Chain is more performant and easier to manage but less available because SPOF Replicating tenant Nonreplicating tenant Replicating namespace Nonreplicating namespace Locally created tenants Replicated tenantsReplication link

35 35 C USTOMER B RANDING Custom logo Custom tenant screen heading name

36 36 HIGH AVAILABILITY AND INCREASED UTILIZATION – VMWARE EDITION OF HCP  Utilization increased: HCP delivered as software- only. Deploy on your existing hardware.  Availability: HCP integrated with VMware HA functionality – automatic failover among nodes and storage

37 37 T IER TO EXTERNAL

38 38Hitachi Data Systems – Confidential. Not for redistribution. T IER TO E XTERNAL – STORE CONTENT OUTSIDE OF HCP  Reduce storage costs by moving rarely accessed content from active-archive tier to cheaper cold-storage tier Wide range of external media or clouds Tier data portion of an object but keep metadata portion

39 39Hitachi Data Systems – Confidential. Not for redistribution. T IER TO E XTERNAL – SHINE A LIGHT ON DARK DATA  Historically when content moved to low-cost tier it became dark ‒ Could no longer be queried ‒ Retrieval: ‒ Long SLA ‒ Changed access: method and address

40 40Hitachi Data Systems – Confidential. Not for redistribution.  HCP tiered content not dark -Available for analytics; MQE query still works -Retrieval: Faster SLA Transparent to client application T IER TO E XTERNAL – SHINE A LIGHT ON DARK DATA

41 41Hitachi Data Systems – Confidential. Not for redistribution. T IER TO E XTERNAL DEMO - C ONTENT DOES NOT APPEAR TIERED

42 42Hitachi Data Systems – Confidential. Not for redistribution. T IER TO E XTERNAL … NFS … NFS Tape Library LTO-6 and LTO-5 … and other brands … that can be extended to a tier to tape solution with the help of partners

43 43Hitachi Data Systems – Confidential. Not for redistribution. T WEENER LAYERS ARE NOT API INTEGRATED

44 44Hitachi Data Systems – Confidential. Not for redistribution. N OT BACKUP / DR USE CASE X Don’t think of the final stage as Tape. Think of it…

45 45 CONFIDENTIAL – For use by Hitachi Data Systems employees and other audiences under NDA only. … AS A T IER  System ‒ Lower performance disk  Topology ‒ Placement on other HCP systems in a networked topology; but retaining meta data.  External ‒ Outside the HCP topology; but retaining meta data. HCP HAS AN INTELLIGENT FRAMEWORK FOR DATA PLACEMENT Active Archive Spindown Metadata Only External

46 46Hitachi Data Systems – Confidential. Not for redistribution. T AKING FOCUS FROM TAPE – REMINDER OF BUILT - IN HCP DATA PROTECTION  Use of proven RAID-6 protection  HCP MDPL-2: 2 copies of all metadata  Customer configurable redundant local object copies (2,3, or 4)  Content validation via hashes and Automatic Object Repair  HCP Replication – offsite copies with automated Repair from Replica  HCP Object Versioning – protection from accidental deletes and changes Why HCP objects need no backup – active data protection designed in Equals: Unparalleled data protection and reduced backup burden

47 47Hitachi Data Systems – Confidential. Not for redistribution. C HINESE METADATA CAN NOW BE SEARCHED - MQE LANGUAGE SUPPORT 元数据

48 48Hitachi Data Systems – Confidential. Not for redistribution.  Network (SAN/LAN) ‒ Hitachi FiVE-EX HBA in CR 210H: 8 Gb/s throughput ‒ Link aggregation for front-end network: Potential to double single node throughput with multiple clients  Server Offerings ‒ CR220S: 6-pack upgrade. Double the capacity of HCP 300 systems without adding additional servers ‒ CR210H: HCP 500 now has 1U option, 16 GB instead of 12 GB  RAID Flash Backup unit to last 5 years HARDWARE ENHANCEMENTS

49 49 Q UESTIONS AND DISCUSSION

50 50 T HANK YOU


Download ppt "1© Hitachi Data Systems Corporation 2013. All Rights Reserved. W HAT ’ S N EW IN HCP 6.0 Eamon O Neill, HCP Product Management May 15-17, 2013."

Similar presentations


Ads by Google