惠普HP大容量网络存储解决方案培训.ppt

惠普大容量存储 解决方案, 2008 hewlett-packard development company, l.p.,本文所含信息如有更改，恕不另行通知。,8000,pb,5000,4000,3000,存储的未来 w w disk storage systems petabytes, 2006-2010 forecast pb 18000,存储消耗加速增长,16000 14000,20082010年的增长速度将超过50%,12000 10000 6000 4000 2000 0,may 2006 forecast,2006,2007,2008,2009,2010,9000 8000,w w file and block disk storage systems, 2005-2008,资料来源： 2006年idc调,7000 6000,block based file based,向基于文件的存储转变,2008年，用户需要使用专门存储文 件数据的磁盘存储块数据 2000 1000 0,2005,2006,2007,2008,资料来源： 2007年idc调查报告,当前的业务模式需要新型基础设施,在线社区,照片共享与润色服 务,借助 技术应用的全球化 以及速度更快、性 能更高、价格更低 的技术来实现,流媒体视频服务 音乐与铃声服务,内容共享 数字动画 医疗影像分析 安全监控系统,基因组研究,能源勘探,问题,宽带服务,手机,广播,生命科学,石油天然 气,企业,应用程序、相机和手机的文件容量越来越大 越来越多的用户需要观看和共享视频 广播和社区网站的用户数量呈指数级增长 存储消耗正在以前所未有的速度增长 2008年11月14日,6,星期五,实际环境中的大容量存储,问题,照片共享服务提供商,在线订购用户的数量呈指数级增长 图像捕获技术飞速发展 周期性用户活动 流媒体技术提供商 问题 用户数量随时都会激增 媒体技术飞速发展 业务需求瞬息万变 电信服务提供商 机遇 当前的基础设施已无法满足需求 值得信赖且拥有用户基础的合作伙伴 不断增加的收入来源 惠普机密。仅供惠普及其渠道合作伙伴内部使用。,e,ta,ta,6,previous solutions have bottlenecks centralized architectures metadata server,m,da,data data,namespace server lock manager token manager doesnt scale most enterprise application workloads are metadata intensive small files, small i/os, random access, metadata operations central component is a bottleneck distributed lock managers any server can modify any portion of the file system doesnt scale inter-server messaging grows as (number of servers)2,messaging overhead too high beyond few (10) servers complex failure modes 2 april 2010,hp storageworks x9720 extreme data storage system integrated hardware/software solution,1. software proven in content rich environments, 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 industry leading density, up to 12tb/u starting at 82tb, expand to 656tb scales in 82tb capacity blocks hp restricted. hp and channel partner internal use.,msa2000,msa2000,msa2000,8,x9320 capacity/performance,capacity couplet disk assignments,performance couplet disk assignments,sata spare vdisk 1 vdisk 1 sata spare vdisk 2 vdisk 2 sata spare vdisk 3 vdisk 3 sata spare vdisk 4 vdisk 4,vdisk 1 vdisk 1 vdisk 1 vdisk 2 vdisk 2 vdisk 2 vdisk 3 vdisk 3 vdisk 3 vdisk 4 vdisk 5 vdisk 5,vdisk 1 vdisk 1 vdisk 1 vdisk 2 vdisk 2 vdisk 3 vdisk 4 vdisk 4 vdisk 4 vdisk 5 vdisk 5 vdisk 5,vdisk 1 vdisk 2 vdisk 2 vdisk 3 vdisk 3 vdisk 3 vdisk 4 vdisk 4 vdisk 4 vdisk 5 vdisk 5 vdisk 5,sas spare vdisk 1 vdisk 1 vdisk 3 vdisk 3 vdisk 3 sas spare vdisk 5 vdisk 5 vdisk 7 vdisk 7 vdisk 7,vdisk 1 vdisk 1 vdisk 1 vdisk 3 vdisk 3 vdisk 3 vdisk 5 vdisk 5 vdisk 5 vdisk 7 vdisk 7 vdisk 7,vdisk 2 vdisk 2 vdisk 2 vdisk 4 vdisk 4 vdisk 4 vdisk 6 vdisk 6 vdisk 6 vdisk 8 vdisk 8 vdisk 8,vdisk 2 vdisk 2 vdisk 2 vdisk 4 vdisk 4 vdisk 4 vdisk 6 vdisk 6 vdisk 6 vdisk 8 vdisk 8 vdisk 8,4 global hot spares 4x 7+2 and 1x 6+2 raid6 vdisks vdisk1, vdisk3 and vdisk5 assigned to controller a vdisk2 and vdisk4 assigned to controller b 1 lun per vdisk 5 luns *(segments) per couplet 2 april 2010,2 global hot spares 6x 5+1 raid5 and 2x 4+1 raid5 vdisks vdisks 1, 3, 5, 7 assigned to controller a vdisks 2, 4, 6, 8 assigned to controller b 1 lun per vdisk 8 luns per couplet,msa2000,capacity couplet storage configuration no snap reserve ibrix file system 31tb usable,segment server 1,segment server 2,ibrix lv segment 6.5 tb (ext3) ibrix vg 6.9 tb lun vdisk1 1tb sata drives raid 6 9 drives (7+2) controller a,ibrix lv segment 6.5 tb (ext3) ibrix vg 6.9 tb lun vdisk2 1tb sata drives raid 6 9 drives (7+2) controller b,ibrix lv segment 5.4 tb (ext3) ibrix vg 5.9 tb lun vdisk3 1tb sata drives raid 6 8 drives (6+2) controller a,ibrix lv segment 6.5 tb (ext3) ibrix vg 6.9 tb lun vdisk4 1tb sata drives raid 6 9 drives (7+2) controller a,ibrix lv segment 6.5 tb (ext3) ibrix vg 6.9 tb lun vdisk5 1tb sata drives raid 6 9 drives (7+2) controller b,controller a controller b note: if snapshots are desired, space must be reserved in the luns for snap pools prior to formatting the ext3 vols,msa2000,msa2000,performance couplet storage configuration no snap reserve ibrix file system 15tb usable,segment server 1,segment server 2,ibrix lv segment 1.5tb (ext3) ibrix vg 1.8 tb lun vdisk1 450gb sas hdds raid 5 5 drives (4+1) controller a,ibrix lv segment 2 tb (ext3) ibrix vg 2.25 tb lun vdisk2 450gb sas hdds raid 5 5 drives (5+1) controller b,ibrix lv segment 2 tb (ext3) ibrix vg 2.25 tb lun vdisk3 450gb sas hdds raid 5 5 drives (5+1) controller a,ibrix lv segment 2 tb (ext3) ibrix vg 2.25 tb lun vdisk4 450gb sas hdds raid 5 5 drives (5+1) controller b,ibrix lv segment 1.5tb (ext3) ibrix vg 1.8 tb lun vdisk1 450gb sas hdds raid 5 5 drives (4+1) controller a,ibrix lv segment 2 tb (ext3) ibrix vg 2.25 tb lun vdisk2 450gb sas hdds raid 5 5 drives (5+1) controller b,ibrix lv segment 2 tb (ext3) ibrix vg 2.25 tb lun vdisk3 450gb sas hdds raid 5 5 drives (5+1) controller a,ibrix lv segment 2 tb (ext3) ibrix vg 2.25 tb lun vdisk4 450gb sas hdds raid 5 5 drives (5+1) controller b,controller a controller b,controller a controller b,note: if snapshots are desired, space must be reserved in the luns for snap pools prior to formatting the ext3 vols,isilon,x9000 network storage system competition,competing products netapp ontap 7g, ontap 8 (gx) ibm gpfs (sofs),competitor advantages 简单管理, 市场认可, 合 作伙伴众多 nas行业领跑者 brand recognition, scalable file system, feature set,competitor disadvantages 只在特殊领域，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 contained herein is subject to change without notice.,ibrix research and development innovation in data distribution and backup recently awarded u.s. patents* patent #7,464,125 checking the validity of blocks and backup duplicates of blocks during block reads patent #7,430,570 shadow directory structure in a distributed segmented file system,ibrix fusion segmented file system,patent #7,406,484 storage allocation in a distributed segmented file system,*partial list,13,2 april 2010,the ibrix distribution engine (ide),standard os stack,os stack w/ide,clients clients network drivers,network drivers tcp / ip nfs / cifs vfs api layer pfs,tcp / ip nfs / cifs vfs api layer ibrix distribution engine api layer,device drivers,ibrix didnt reinvent the physical file system.,ext3 device drivers,storage storage,14,2 april 2010,14,f1,f2,f3,fn,s1,s2,s3,sn,s2,f1,f2,f3,s1,sn,fn,s3,non-hierarchical architecture dir us patent # 6,782,389,f1,f2,f3,fn,s1,s2,subdir s3, s,sn,1,dir,s2,extremely high aggregate performance from a single directory (and single file),1 s 2 s n,4 2 3 100,f1 f2 f3 fn,s1 subdir sn s3,segment servers,segments,15,2 april 2010,allocation policy controls placement of new files random choose segment at random roundrobin cycle through permutation of segments directory 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 segment this policy is generally not recommended. keep in mind that other policies will automatically redirect file creation and append operations away from segments that become 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 concept traditional file system design: monolithic metadata management,block 0,block n-1,obsolete boundaries (e.g. cylinder groups) segmented file system “distributed file space” approach each segment is almost a “mini” file system with its own set of metadata allocation is generally localized within a segment, but may span segments deterministically distributed each segment owned 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 space each segment is a range of inodes client can unilaterally determine two things by looking at the inode number of an entity: which segment/server owns that entity what is the coordinate of that entity within that segment,inode 0 inode 0,inode 999 inode 1000 inode 999 inode 0,inode 1999 inode 2000 inode 999 inode 0,inode 2999 inode 999,inode 9000 inode 0,inode 9999 inode 999,file1 i_1500 file2 i_2200 ,18,2 april 2010,storage topology bricks potential data paths,ibrix client 1,ibrix client 2,nfs client 1,nfs client 2,segment server 1,segment server 2,segment server m-1,segment server m,owns segment,sp,sp,sp,sp,a 1 3,b 2 4,file,a 5 7,b 6 8,storage topology bricks ibrix client read,ibrix client 1,ibrix file client 2,nfs client 1,nfs client 2,segment server 1 sp a,segment file server 2 sp b, ,segment server m-1 sp a,segment server m sp b,4,file,storage topology bricks multiple ibrix clients read same file,ibrix client 1,file,ibrix client 2,file,nfs client 1,nfs client 2,segment server 1 sp a,segment file server 2 sp b, ,segment server m-1 sp a,segment server m sp b,4,file,storage topology bricks ,ibrix client 1,ibrix client 2,nfs client read ,file nfs client 1,nfs client 2,segment server 1 sp a,segment file server 2 sp b, ,file segment server m-1 sp a,segment server m sp b,4,file,storage topology bricks ,nfs multiple-client read,file,file,file,ibrix client 1,ibrix client 2,nfs client 1,nfs client 2,nfs client 2,user network cluster network,segment server 1 sp a,segment file server 2 sp b 4 file,file segment server m-1 sp a,file segment server m sp b,storage topology bricks ,nfs cached reads,file,file,file,ibrix client 1,ibrix client 2,nfs client 1,nfs client 2,nfs client 2,segment server 1 sp,segment file server 2 sp,file segment server m-1 sp,file segment server m sp,a,b,a,b,4,file,storage topology bricks ,nfs san reads,file,file,file,ibrix client 1,ibrix client 2,nfs client 1,nfs client 2,nfs client 2,segment server 1,segment server 2,file segm