《惠普HP大容量网络存储解决方案培训.ppt》由会员分享，可在线阅读，更多相关《惠普HP大容量网络存储解决方案培训.ppt（29页珍藏版）》请在三一办公上搜索。
1、惠普大容量存储解决方案,2008 Hewlett-Packard Development Company,L.P.,本文所含信息如有更改，恕不另行通知。,8000,PB,5000,4000,3000,存储的未来W W Disk Storage Systems Petabytes,2006-2010 ForecastPB18000,存储消耗加速增长,1600014000,20082010年的增长速度将超过50%,12000100006000400020000,May 2006 Forecast,2006,2007,2008,2009,2010,90008000,W W File and Bloc
2、k Disk Storage Systems,2005-2008,资料来源：2006年IDC调,70006000,Block basedFile based,向基于文件的存储转变,2008年，用户需要使用专门存储文件数据的磁盘存储块数据200010000,2005,2006,2007,2008,资料来源：2007年IDC调查报告,当前的业务模式需要新型基础设施,在线社区,照片共享与润色服务,借助技术应用的全球化以及速度更快、性能更高、价格更低的技术来实现,流媒体视频服务音乐与铃声服务,内容共享数字动画医疗影像分析安全监控系统,基因组研究,能源勘探,问题,宽带服务,手机,广播,生命科学,石油天然
3、气,企业,应用程序、相机和手机的文件容量越来越大越来越多的用户需要观看和共享视频广播和社区网站的用户数量呈指数级增长存储消耗正在以前所未有的速度增长2008年11月14日,6,星期五,实际环境中的大容量存储,问题,照片共享服务提供商,在线订购用户的数量呈指数级增长图像捕获技术飞速发展周期性用户活动流媒体技术提供商问题用户数量随时都会激增媒体技术飞速发展业务需求瞬息万变电信服务提供商机遇当前的基础设施已无法满足需求值得信赖且拥有用户基础的合作伙伴不断增加的收入来源惠普机密。仅供惠普及其渠道合作伙伴内部使用。,e,ta,ta,6,Previous Solutions Have Bottleneck
4、sCentralized ArchitecturesMetadata Server,M,da,DataData,Namespace ServerLock ManagerToken ManagerDoesnt Scale Most enterprise applicationworkloads are metadata intensiveSmall files,small I/Os,randomaccess,metadata operationsCentral component is a bottleneckDistributed Lock ManagersAny server can mod
5、ify anyportion of the file systemDoesnt ScaleInter-server messaging grows as(number of servers)2,Messaging overhead too highbeyond few(10)serversComplex failure modes2 April 2010,HP StorageWorks X9720Extreme Data Storage SystemIntegrated hardware/software solution,1.Software Proven in Content Rich E
6、nvironments,Integrated system management Simplified performance and capacity scaling Multiple access protocols NFS,CIFS,X9000,2.Performance Blocks Scale Performance,Up to 12.8 cores/U Starting at 3 blades,expand up to 16 blades Quad-core,half-height blades in c7000 Enclosure,3.Capacity Blocks Indust
7、ry Leading Density,Up to 12TB/U Starting at 82TB,expand to 656TB Scales in 82TB Capacity BlocksHP Restricted.HP and Channel Partner Internal Use.,MSA2000,MSA2000,MSA2000,8,X9320 Capacity/Performance,Capacity Couplet Disk Assignments,Performance Couplet Disk Assignments,SATA sparevdisk 1vdisk 1SATA s
8、parevdisk 2vdisk 2SATA sparevdisk 3vdisk 3SATA sparevdisk 4vdisk 4,vdisk 1vdisk 1vdisk 1vdisk 2vdisk 2vdisk 2vdisk 3vdisk 3vdisk 3vdisk 4vdisk 5vdisk 5,vdisk 1vdisk 1vdisk 1vdisk 2vdisk 2vdisk 3vdisk 4vdisk 4vdisk 4vdisk 5vdisk 5vdisk 5,vdisk 1vdisk 2vdisk 2vdisk 3vdisk 3vdisk 3vdisk 4vdisk 4vdisk 4
9、vdisk 5vdisk 5vdisk 5,SAS sparevdisk 1vdisk 1vdisk 3vdisk 3vdisk 3SAS sparevdisk 5vdisk 5vdisk 7vdisk 7vdisk 7,vdisk 1vdisk 1vdisk 1vdisk 3vdisk 3vdisk 3vdisk 5vdisk 5vdisk 5vdisk 7vdisk 7vdisk 7,vdisk 2vdisk 2vdisk 2vdisk 4vdisk 4vdisk 4vdisk 6vdisk 6vdisk 6vdisk 8vdisk 8vdisk 8,vdisk 2vdisk 2vdisk
10、 2vdisk 4vdisk 4vdisk 4vdisk 6vdisk 6vdisk 6vdisk 8vdisk 8vdisk 8,4 global hot spares4X 7+2 and 1X 6+2 RAID6 VDisksVDisk1,VDisk3 and VDisk5 assigned to Controller AVDisk2 and VDisk4 assigned to Controller B1 LUN per VDisk5 LUNs*(segments)per couplet2 April 2010,2 global hot spares6X 5+1 RAID5 and 2X
11、 4+1 RAID5 VDisksVDisks 1,3,5,7 assigned to Controller AVDisks 2,4,6,8 assigned to Controller B1 LUN per VDisk8 LUNs per couplet,MSA2000,Capacity Couplet Storage ConfigurationNo Snap ReserveIbrix File System 31TB Usable,Segment Server 1,Segment Server 2,Ibrix LVSegment6.5 TB(ext3)Ibrix vg6.9 TB LUNV
12、DISK11TB SATA DrivesRAID 69 Drives(7+2)Controller A,Ibrix LVSegment6.5 TB(ext3)Ibrix vg6.9 TB LUNVDISK21TB SATA DrivesRAID 69 Drives(7+2)Controller B,Ibrix LVSegment5.4 TB(ext3)Ibrix vg5.9 TB LUNVDISK31TB SATA DrivesRAID 68 Drives(6+2)Controller A,Ibrix LVSegment6.5 TB(ext3)Ibrix vg6.9 TB LUNVDISK41
13、TB SATA DrivesRAID 69 Drives(7+2)Controller A,Ibrix LVSegment6.5 TB(ext3)Ibrix vg6.9 TB LUNVDISK51TB SATA DrivesRAID 69 Drives(7+2)Controller B,Controller AController BNote:If Snapshots are desired,space must be reserved in the LUNs for snap pools prior to formatting the ext3vols,MSA2000,MSA2000,Per
14、formance Couplet StorageConfiguration No Snap ReserveIbrix File System 15TB Usable,Segment Server 1,Segment Server 2,Ibrix LVSegment1.5TB(ext3)Ibrix vg1.8 TB LUNVDISK1 450GBSAS HDDs RAID 5 5 Drives(4+1)Controller A,Ibrix LVSegment2 TB(ext3)Ibrix vg2.25 TB LUNVDISK2 450GBSAS HDDs RAID 5 5 Drives(5+1)
15、Controller B,Ibrix LVSegment2 TB(ext3)Ibrix vg2.25 TB LUNVDISK3 450GBSAS HDDs RAID 5 5 Drives(5+1)Controller A,Ibrix LVSegment2 TB(ext3)Ibrix vg2.25 TB LUNVDISK4 450GBSAS HDDs RAID 5 5 Drives(5+1)Controller B,Ibrix LVSegment1.5TB(ext3)Ibrix vg1.8 TB LUNVDISK1 450GBSAS HDDs RAID 5 5 Drives(4+1)Contro
16、ller A,Ibrix LVSegment2 TB(ext3)Ibrix vg2.25 TB LUNVDISK2 450GBSAS HDDs RAID 5 5 Drives(5+1)Controller B,Ibrix LVSegment2 TB(ext3)Ibrix vg2.25 TB LUNVDISK3 450GBSAS HDDs RAID 5 5 Drives(5+1)Controller A,Ibrix LVSegment2 TB(ext3)Ibrix vg2.25 TB LUNVDISK4 450GBSAS HDDs RAID 5 5 Drives(5+1)Controller B
17、,Controller AController B,Controller AController B,Note:If Snapshots are desired,space must be reserved in the LUNs for snap pools prior to formatting the ext3vols,Isilon,X9000 Network Storage SystemCompetition,Competing productsNetAppOntap 7G,Ontap 8(GX)IBMGPFS(SoFS),Competitoradvantages简单管理,市场认可,合
18、作伙伴众多NAS行业领跑者Brand recognition,scalable file system,feature set,Competitordisadvantages只在特殊领域，Cover范围不广贵HPC行业没有案例不适合Scale out 领域复杂IBM支持差SAN架构,11,2 April 2010,11,HP Product Announcement HP Restricted,Technical Concept,HP Restricted,2009 Hewlett-Packard Development Company,L.P.,The information contain
19、ed herein is subject to change without notice.,IBRIX Research and DevelopmentInnovation in data distribution and backupRecently AwardedU.S.Patents*Patent#7,464,125Checking the Validity of Blocks andBackup Duplicates of Blocks DuringBlock ReadsPatent#7,430,570Shadow Directory Structure in aDistribute
20、d Segmented File System,IBRIX FusionSegmented File System,Patent#7,406,484Storage Allocation in a DistributedSegmented File System,*Partial List,13,2 April 2010,The IBRIX Distribution Engine(IDE),Standard OS Stack,OS Stack w/IDE,ClientsClientsNetwork Drivers,Network DriversTCP/IPNFS/CIFSVFSAPI Layer
21、PFS,TCP/IPNFS/CIFSVFSAPI LayerIBRIXDistribution EngineAPI Layer,Device Drivers,IBRIX didnt reinvent thephysical file system.,Ext3Device Drivers,StorageStorage,14,2 April 2010,14,F1,F2,F3,Fn,S1,S2,S3,Sn,S2,F1,F2,F3,S1,Sn,Fn,S3,Non-hierarchical ArchitectureDirUS Patent#6,782,389,F1,F2,F3,Fn,S1,S2,Subd
22、irS3,S,Sn,1,Dir,S2,Extremely HighAggregatePerformancefrom a SingleDirectory(and Single File),1S2Sn,423100,F1F2F3Fn,S1SubdirSnS3,SegmentServers,Segments,15,2 April 2010,Allocation policyControls placement of new files RANDOM choose segment at random ROUNDROBIN cycle through permutation of segments DI
23、RECTORY place file on same segment as its parent directory NONE(for directories only)use same policy for files and directories AUTOMATIC choose a segment with the most free space STICKY use only one segmentThis policy is generally not recommended.Keep in mind that other policies willautomatically re
24、direct file creation and append operations away from segments thatbecome full.Preferred segments set of segments to place files on first if possible.LOCAL for segment server,choose a segment it owns,16,2 April 2010,The IBRIX Segmented ConceptTraditional file system design:monolithic metadata managem
25、ent,Block 0,Block n-1,Obsoleteboundaries(e.g.Cylinder Groups)Segmented File System“Distributed File Space”approachEach segment is almost a“mini”file system with its own set of metadataAllocation is generally localized within a segment,but may span segmentsDeterministically DistributedEach Segment ow
26、ned by exactly one Ibrix Engine,Segment,Owner mapping determined locally by each Ibrix engine,Flexible Segment control can migrate to balance load,17,2 April 2010,Distributed Inode SpaceEach Segment is a range of inodes Client can unilaterally determine two things by looking at the Inode numberof an
27、 entity:Which segment/server owns that entity What is the coordinate of that entity within that segment,Inode 0Inode 0,Inode 999 Inode 1000Inode 999 Inode 0,Inode 1999 Inode 2000Inode 999 Inode 0,Inode 2999Inode 999,Inode 9000Inode 0,Inode 9999Inode 999,File1 I_1500File2 I_2200,18,2 April 2010,Stora
28、ge topology bricks potential data paths,IBRIXclient 1,IBRIXclient 2,NFSclient 1,NFSclient 2,Segmentserver 1,Segmentserver 2,Segmentserver M-1,Segmentserver M,Ownssegment,SP,SP,SP,SP,A13,B24,file,A57,B68,Storage topology bricks IBRIX client read,IBRIXclient 1,IBRIX fileclient 2,NFSclient 1,NFSclient
29、2,Segmentserver 1SPA,Segment fileserver 2SPB,Segmentserver M-1SPA,Segmentserver MSPB,4,file,Storage topology bricks multipleIBRIX clients read same file,IBRIXclient 1,file,IBRIXclient 2,file,NFSclient 1,NFSclient 2,Segmentserver 1SPA,Segment fileserver 2SPB,Segmentserver M-1SPA,Segmentserver MSPB,4,
30、file,Storage topology bricks,IBRIXclient 1,IBRIXclient 2,NFS client read,fileNFSclient 1,NFSclient 2,Segmentserver 1SPA,Segment fileserver 2SPB,fileSegmentserver M-1SPA,Segmentserver MSPB,4,file,Storage topology bricks,NFS multiple-client read,file,file,file,IBRIXclient 1,IBRIXclient 2,NFSclient 1,N
31、FSclient 2,NFSclient 2,User networkCluster network,Segmentserver 1SPA,Segment fileserver 2SPB4file,fileSegmentserver M-1SPA,fileSegmentserver MSPB,Storage topology bricks,NFS cached reads,file,file,file,IBRIXclient 1,IBRIXclient 2,NFSclient 1,NFSclient 2,NFSclient 2,Segmentserver 1SP,Segment fileser
32、ver 2SP,fileSegmentserver M-1SP,fileSegmentserver MSP,A,B,A,B,4,file,Storage topology bricks,NFS SAN reads,file,file,file,IBRIXclient 1,IBRIXclient 2,NFSclient 1,NFSclient 2,NFSclient 2,Segmentserver 1,Segmentserver 2,fileSegmentserver M-1,fileSegmentserver M,SAN Fabric,SP,SP,SP,SP,A,B,A,B,4,file,Hi
33、gh AvailabilityResilient&Modular,S1,1,3,ApplicationIBRIXDistribution,192.168.1.1,47,6,Engine,High Availability Features:Server Failover 1:1,N:1,1:N Active/Active or Active/Passive Redundant Component Failover GbE,FC Ports HBAs,192.168.1.2192.168.1.3NFS Client Table192.168.1.3,S2S3,25368,89,IBRIX Man
34、agementStation,SegmentServers,9Segments,IBRIX Resiliency Model is basis for rolling software upgrade,26,2 April 2010,Supported Configurations MultiSite ReplicationMulti site Replication,Cascading sitereplication for 1-to-Many sitereplication,Site AIBRIX FS3,Site BFS3 ReplicaFS3 ReplicaSite CCascadin
35、g site replication,27,2 April 2010,Remote Replication Supported FeaturesSupported FeaturesContinuous Remote ReplicationParallel Replication-all servers usedFile based ReplicationFile System accessible on remote siteRecover from loss of WAN/LAN connectionPause/Resume feature,28,2 April 2010,Storage Tier LevelsFibre Channel Storage(Tier 1)Flash/SSD Storage(Tier 0)SATA Storage(Tier 2),29,2 April 2010,
