實驗4存儲雙活容災解決方案應用實踐參考現(xiàn)網(wǎng)情況匯總

1、修訂開發(fā)/優(yōu)化者時間審核人開發(fā)類型（新開發(fā)/優(yōu)化）更新說明新開發(fā)課程編碼適用產(chǎn)品產(chǎn)品版本課程版本IEHCIE-StorageV3R6，V5R72.5M數(shù)據(jù)中心改造項目背景情況說明技術(shù)目錄1 引文42 現(xiàn)網(wǎng)信息43 應用系統(tǒng)現(xiàn)狀51 引文銷售 S 和售前支持 P 在和IT 團隊成員進行了一個會議，主要是了解的容災系統(tǒng)建設的現(xiàn)狀和存在的問題，并在會后把會議紀要和一些數(shù)據(jù)中心組網(wǎng)信息同步給項目成員。2 現(xiàn)網(wǎng)信息說明：本文所涉及的案例僅為樣例，實際操作中請以真實設備環(huán)境為準，具體配置步驟請參考對應的產(chǎn)品文檔。目前M業(yè)務系統(tǒng)包括業(yè)務交易、電子數(shù)據(jù)庫系統(tǒng)、辦公自動化系統(tǒng)等。其中，第一階段需要遷到新的容災保

2、護的業(yè)務如下表：應用系統(tǒng) IT 現(xiàn)狀（第一階段）4站點業(yè)務類型初始數(shù)據(jù)量規(guī)劃時間總?cè)萘可a(chǎn)站點資產(chǎn)財務4000GB3 年綜合數(shù)據(jù)庫2000GB3 年業(yè)務管理系統(tǒng)500GB3 年電子2500GB3 年OA1TB3 年桌面云測試系統(tǒng)1TB3 年3 應用系統(tǒng)現(xiàn)狀（1）業(yè)務系統(tǒng)涉及 M財務、資產(chǎn)、物資、檢修、運行等工作，部署方式為集中式部署，業(yè)務窗口時間為 7*24 小時。根據(jù)相關(guān)規(guī)定，數(shù)據(jù)不能丟失，業(yè)務中斷時間為 5 分鐘。資產(chǎn)財務管理的關(guān)聯(lián)系統(tǒng)是電子商務，系統(tǒng)之間有業(yè)務流程和。（2）電子庫包括綜合統(tǒng)計和網(wǎng)上等系統(tǒng)，并提供其他電子商務交易接口，涉及 M下屬所有ATM 機的數(shù)據(jù)上報和信息。數(shù)據(jù)不能丟失

3、，業(yè)務中斷最長 15 分鐘。（3）總行 OA 系統(tǒng)包括 OA 辦公、公文審批和內(nèi)網(wǎng)郵件等。XX 局 OA 系統(tǒng)為分布式部署(從一級到三級)。總部OA 系統(tǒng)與 XX 局下屬OA 系統(tǒng)之間主要為收發(fā)公文。最多 30 分鐘內(nèi)的數(shù)據(jù)丟失，可業(yè)務中斷時間最長 2 小時。（4）桌面云包括員工辦公虛擬機系統(tǒng)和 Homedir 文件。主要用于員工辦公，其中 Homedir 文件存放員工工作文檔。最多 30 分鐘內(nèi)的數(shù)據(jù)丟失，可業(yè)務中斷時間最長 2 小時。一部分測試系統(tǒng)使用的桌面云虛擬機不允許業(yè)務中斷和數(shù)據(jù)丟失。4 網(wǎng)絡系統(tǒng)現(xiàn)狀當前已建設同城災備中心，與生產(chǎn)中心距離約 30km。中間鏈路租用運營商 光纖鏈路，并

4、自購 4 臺 DWDM 設備，其中核在數(shù)據(jù)中心 A 使用兩臺 DWDM 設備實現(xiàn)冗余，數(shù)據(jù)中心 B 放置 2 臺 DWDM 設備,經(jīng)過測試，兩數(shù)據(jù)中心之間平均時延1ms。并租用運營商機房部署仲裁服務器，已經(jīng)通過以太網(wǎng)連通到數(shù)據(jù)中心 A 和數(shù)據(jù)中心 B，經(jīng)測試平均時延100ms。5M產(chǎn)品采購要求6AreaItemGeneral requirement3.1ArchitectureThe storage system must offer symmetric active/active mode with load balancing. Active storage controllers mus

5、t afford I/O operations simultaneously in parallel, symmetrical and load balance mode for any volume ( ) presented among hosts. Storage with Asymmetric Logica it Ac s (ALUA) architecture or Active/Passive controllers is not preferred.3.2ControllerThe storage system shoulde 4 controllers in one contr

6、oller enclosure occupied within rack space of 4U or less.3.3ScalabilityThe storage system should support up to 800 NVMe SSD.3.4Scale-outThe storage system should support scale-out to 16 controllers by adding new controllers without serviceerruption, the cluster mode should be Scale-out, but not Fede

7、ration mode, and the erconnect network should be high speed network such asPCIe ,IB,RDMA, but FC and 10GE will not be accepted.3.5Cache sizeThe storage system shalleeast 2048 GB DRAM cache for system memory and user data, protected by ECC.The use of cache expanthrough disks or SSD cards is not consi

8、dered.3.6ReliabilityEnt rise-class reliability, availability, and serviceability with High- end architecture, multiple storage controllers to allow for linear/near- linear scalability of performance and capacity and for fault tolerant operation.Servi are not errupted while three out of four controll

9、ers failure3.7RAIDThe Storage should support the RAID5, RAID 6 and higher data redundancy t is capable to tolerate simultaneous failure of three disks east.3.8Crosssite Active-ActiveThe two storage systems must operate in active-active cluster mode natively without any external gateway appliance.Sim

10、ultaneous reading and writingwo volumes of different storages, which are presented as a virtual volume to the hosts”, so t the host servican be maained unerrupted, evenheevent of a disaster at one of the sites.3.9Effective capacity guarantee serviceShould provide 65TB usable capacity or effective capa