{"id":95870,"date":"2020-10-04T13:41:59","date_gmt":"2020-10-04T11:41:59","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/pochemu-vazhno-proverit-po-na-vashej-shd-vysokoj-dostupnosti-999999"},"modified":"2020-10-04T13:41:59","modified_gmt":"2020-10-04T11:41:59","slug":"pochemu-vazhno-proverit-po-na-vashej-shd-vysokoj-dostupnosti-999999","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pochemu-vazhno-proverit-po-na-vashej-shd-vysokoj-dostupnosti-999999","title":{"rendered":"Pse \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kontrolloni softuerin n\u00eb sistemin tuaj t\u00eb ruajtjes me disponueshm\u00ebri t\u00eb lart\u00eb (99,9999%)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Pse<\/p>\n

Cila version e firmware-it \u00ebsht\u00eb m\u00eb \"e sakt\u00eb\" dhe \"funksionale\"? N\u00ebse sistemi i ruajtjes garanton disponueshm\u00ebri prej 99,9999%, a do t\u00eb thot\u00eb kjo q\u00eb do t\u00eb funksionoj\u00eb pa nd\u00ebrprer\u00eb edhe pa p\u00ebrdit\u00ebsuar softuerin? Apo, p\u00ebrkundrazi, p\u00ebr t\u00eb arritur maksimumin n\u00eb disponueshm\u00ebri, \u00ebsht\u00eb gjithmon\u00eb e nevojshme t\u00eb instalohet firmware-i m\u00eb i fundit? Ne do t\u00eb p\u00ebrpiqemi t\u00eb p\u00ebrgjigjemi n\u00eb k\u00ebto pyetje duke u mb\u00ebshtetur n\u00eb p\u00ebrvoj\u00ebn ton\u00eb.<\/p>\n

Nj\u00eb hyrje e shkurt\u00ebr<\/h3>\n

T\u00eb gjith\u00eb ne e kuptojm\u00eb se n\u00eb \u00e7do version t\u00eb softuerit, qoft\u00eb sistemi operativ apo drejtuesi p\u00ebr ndonj\u00eb pajisje, shpesh p\u00ebrfshihen mang\u00ebsi \/ gabime dhe karakteristika t\u00eb tjera \"t\u00eb ve\u00e7anta\", t\u00eb cilat mund t\u00eb \"shfaqen\" deri n\u00eb fund t\u00eb jet\u00ebs s\u00eb pajisjes, ose t\u00eb \"zbulohet\" vet\u00ebm n\u00eb kushte t\u00eb caktuara. Numri dhe r\u00ebnd\u00ebsia e k\u00ebtyre nuancave varet nga kompleksiteti (funksionaliteti) i softuerit dhe nga cil\u00ebsia e testimit gjat\u00eb zhvillimit t\u00eb tij. <\/p>\n

Shpesh p\u00ebrdoruesit mbeten n\u00eb \"firmware-in nga fabrika\" (e njohur si - \"funksionon, pra mos u prek\") ose gjithmon\u00eb instalojn\u00eb versionin m\u00eb t\u00eb fundit (n\u00eb kuptimin e tyre, e fundit do t\u00eb thot\u00eb m\u00eb funksional). Ne p\u00ebrdorim nj\u00eb qasje tjet\u00ebr - shohim sh\u00ebnimet e l\u00ebshimit p\u00ebr t\u00eb gjith\u00eb softuerin q\u00eb p\u00ebrdorim. n\u00eb cloud mClouds<\/a><\/noindex> pajisjen q\u00eb p\u00ebrdorim dhe zgjedhim me kujdes firmware-in e p\u00ebrshtatsh\u00ebm p\u00ebr secil\u00ebn nj\u00ebsi. <\/p>\n

N\u00eb k\u00ebt\u00eb p\u00ebrfundim kemi arritur, si\u00e7 thuhet, me p\u00ebrvoj\u00eb. Nga praktika jon\u00eb e p\u00ebrdorimit do t\u00eb shpjegojm\u00eb pse 99,9999 % e besueshm\u00ebris\u00eb s\u00eb premtuar p\u00ebr sistemin e ruajtjes nuk do t\u00eb thon\u00eb asgj\u00eb n\u00ebse nuk ndiqni n\u00eb koh\u00eb p\u00ebrdit\u00ebsimet dhe p\u00ebrshkrimet e softuerit. Rasti yn\u00eb \u00ebsht\u00eb i vlefsh\u00ebm p\u00ebr p\u00ebrdoruesit e sistemeve t\u00eb ruajtjes t\u00eb \u00e7do prodhuesi, sepse nj\u00eb situat\u00eb e till\u00eb mund t\u00eb ndodh\u00eb me pajisje t\u00eb \u00e7do marke.<\/p>\n

Zgjedhja e nj\u00eb sistemi t\u00eb ri t\u00eb ruajtjes s\u00eb t\u00eb dh\u00ebnave<\/h3>\n

N\u00eb fund t\u00eb vitit t\u00eb kaluar, n\u00eb infrastruktur\u00ebn ton\u00eb u shtua nj\u00eb sistem i interesant i ruajtjes s\u00eb t\u00eb dh\u00ebnave: modeli m\u00eb i vog\u00ebl nga linja IBM FlashSystem 5000, i cili n\u00eb momentin e blerjes u em\u00ebrua Storwize V5010e. Tani ai shitet me emrin FlashSystem 5010, por n\u00eb fakt \u00ebsht\u00eb e nj\u00ebjta baz\u00eb harduari me t\u00eb nj\u00ebjtin Spectrum Virtualize brenda. <\/p>\n

Prania e nj\u00eb sistemi t\u00eb vet\u00ebm menaxhimi \u00ebsht\u00eb, si\u00e7 ndodhet, dallimi kryesor i IBM FlashSystem. Tek modelet e seris\u00eb m\u00eb t\u00eb vog\u00ebl, ajo pothuajse nuk ndryshon nga modelet m\u00eb t\u00eb fuqishme. Zgjedhja e nj\u00eb modeli t\u00eb caktuar vet\u00ebm ofron baz\u00ebn harduerike p\u00ebrkat\u00ebse, karakteristikat e s\u00eb cil\u00ebs japin mund\u00ebsin\u00eb p\u00ebr t\u00eb p\u00ebrdorur k\u00ebt\u00eb ose at\u00eb funksionalitet ose t\u00eb sigurojn\u00eb nj\u00eb nivel m\u00eb t\u00eb lart\u00eb t\u00eb shkall\u00ebzueshm\u00ebris\u00eb. Softueri, n\u00eb k\u00ebt\u00eb rast, identifikon pjes\u00ebn harduerike dhe ofron funksionalitetin e nevojsh\u00ebm dhe t\u00eb mjaftuesh\u00ebm p\u00ebr k\u00ebt\u00eb platform\u00eb. <\/p>\n

\"PseIBM FlashSystem 5010<\/p>\n

Shkurtimisht p\u00ebr modelin ton\u00eb 5010. Kjo \u00ebsht\u00eb nj\u00eb sistem ruajtjeje t\u00eb dh\u00ebnash me blloqe, me dy kontrollues, i nivelit fillestar. Ai mb\u00ebshtet disqe NLSAS, SAS dhe SSD. Vendosja e NVMe n\u00eb t\u00eb nuk \u00ebsht\u00eb e disponueshme, pasi ky model i sistemit t\u00eb ruajtjes pozicionohet p\u00ebr zgjidhjen e detyrave q\u00eb nuk k\u00ebrkojn\u00eb performanc\u00ebn e disqeve NVMe.<\/p>\n

Sistemi i ruajtjes u ble p\u00ebr vendosjen e informacionit arkivor ose t\u00eb dh\u00ebnave q\u00eb nuk aksesohen shpesh. Prandaj, p\u00ebr ne ishte i mjaftuesh\u00ebm seti standard i funksioneve t\u00eb tij: tiering (Easy Tier), Thin Provision. Edhe performanca prej 1000\u20132000 IOPS n\u00eb disqet NLSAS na p\u00ebrshtatej plot\u00ebsisht. <\/p>\n

P\u00ebrvoja jon\u00eb \u2014 si nuk e p\u00ebrdit\u00ebsuam firmware-in n\u00eb koh\u00eb<\/h3>\n

Tani, konkretisht p\u00ebr vet\u00eb p\u00ebrdit\u00ebsimin e softuerit. N\u00eb momentin e blerjes, sistemi kishte tashm\u00eb nj\u00eb version disi t\u00eb vjet\u00ebruar t\u00eb softuerit Spectrum Virtualize, p\u00ebrkat\u00ebsisht, 8.2.1.3.<\/strong><\/p>\n

Kemi studiuar p\u00ebrshkrimin e firmware-eve dhe kemi planifikuar p\u00ebrdit\u00ebsimin deri n\u00eb 8.2.1.9<\/strong>. Po t\u00eb kishim qen\u00eb pak m\u00eb t\u00eb shpejt\u00eb, ky artikull nuk do t\u00eb ekzistonte \u2014 n\u00eb nj\u00eb firmware m\u00eb t\u00eb ri ky bug nuk do t\u00eb ishte shfaqur. Megjithat\u00eb, p\u00ebr arsye t\u00eb caktuara, p\u00ebrdit\u00ebsimi i k\u00ebtij sistemi u shty.<\/p>\n

Si rezultat, nj\u00eb vones\u00eb e vog\u00ebl n\u00eb p\u00ebrdit\u00ebsim \u00e7oi n\u00eb nj\u00eb situat\u00eb jasht\u00ebzakonisht t\u00eb pak\u00ebndshme, si\u00e7 p\u00ebrshkruhet n\u00eb lidhjen m\u00eb posht\u00eb: https:\/\/www.ibm.com\/support\/pages\/node\/6172341<\/u><\/a><\/noindex>. <\/p>\n

Po, n\u00eb firmware-in e atij versioni ishte pik\u00ebrisht aktual i ashtuquajturi APAR (Authorized Program Analysis Report) HU02104. Ai shfaqet n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb. N\u00ebn ngarkes\u00eb, n\u00eb rrethana t\u00eb caktuara, cache fillon t\u00eb mbushet tej mase; m\u00eb pas sistemi kalon n\u00eb modalitet mbrojt\u00ebs, n\u00eb t\u00eb cilin \u00e7aktivizon input\/output p\u00ebr Pool-in. N\u00eb rastin ton\u00eb, kjo u duk si \u00e7aktivizim i 3 disqeve p\u00ebr grupin RAID n\u00eb modalitetin RAID 6. \u00c7aktivizimi zgjat 6 minuta. M\u00eb pas, qasja te Volumet n\u00eb Pool rikthehet.<\/p>\n

N\u00ebse dikush nuk \u00ebsht\u00eb i njohur me struktur\u00ebn dhe em\u00ebrtimin e entiteteve logjike n\u00eb kontekstin e IBM Spectrum Virtualize, do ta shpjegoj shkurt tani.<\/p>\n

\"PseStruktura e elementeve logjike t\u00eb sistemit t\u00eb ruajtjes<\/p>\n

Disqet grupohen n\u00eb nj\u00ebsi q\u00eb quhen MDisk (Managed Disk). MDisk mund t\u00eb p\u00ebrfaq\u00ebsoj\u00eb nj\u00eb RAID klasik (0,1,10,5,6) ose nj\u00eb variant t\u00eb virtualizuar \u2013 DRAID (Distributed RAID). P\u00ebrdorimi i DRAID lejon rritjen e performanc\u00ebs s\u00eb array-t, pasi p\u00ebrdoren t\u00eb gjith\u00eb disqet e grupit, dhe ul koh\u00ebn e rebuild-it, sepse duhet t\u00eb rikthehen vet\u00ebm blloqe t\u00eb caktuara, jo t\u00eb gjitha t\u00eb dh\u00ebnat nga disku q\u00eb ka dal\u00eb jasht\u00eb funksionit.<\/p>\n

\"PseShp\u00ebrndarja e blloqeve t\u00eb t\u00eb dh\u00ebnave n\u00ebp\u00ebr disqe gjat\u00eb p\u00ebrdorimit t\u00eb Distributed RAID (DRAID) n\u00eb modalitetin RAID-5.<\/p>\n

Nd\u00ebrsa kjo skem\u00eb tregon logjik\u00ebn e funksionimit t\u00eb rebuild-it t\u00eb DRAID n\u00eb rast t\u00eb d\u00ebshtimit t\u00eb nj\u00eb disku:<\/p>\n

\"PseLogjika e funksionimit t\u00eb rebuild-it t\u00eb DRAID n\u00eb rast t\u00eb d\u00ebshtimit t\u00eb nj\u00eb disku<\/p>\n

M\u00eb pas, nj\u00eb ose disa MDisk formojn\u00eb t\u00eb ashtuquajturin Pool. Brenda t\u00eb nj\u00ebjtit pool, nuk rekomandohet p\u00ebrdorimi i MDisk me nivele t\u00eb ndryshme RAID\/DRAID mbi disqe t\u00eb t\u00eb nj\u00ebjtit lloj. Nuk do t\u00eb hyjm\u00eb shum\u00eb n\u00eb k\u00ebt\u00eb tem\u00eb, pasi planifikojm\u00eb ta trajtojm\u00eb n\u00eb nj\u00eb nga artikujt e ardhsh\u00ebm. Dhe, n\u00eb thelb, Pool ndahet n\u00eb Volumes, t\u00eb cilat prezantohen drejt hosteve p\u00ebrmes nj\u00ebrit ose tjetrit protokoll t\u00eb aksesit n\u00eb nivel blloku.<\/p>\n

K\u00ebshtu, si rezultat i situat\u00ebs s\u00eb p\u00ebrshkruar n\u00eb APAR HU02104<\/em>, p\u00ebr shkak t\u00eb d\u00ebshtimit logjik t\u00eb tre disqeve, MDisk pushoi s\u00eb funksionuari, gj\u00eb q\u00eb nga ana e vet shkaktoi nd\u00ebrprerjen e funksionimit t\u00eb Pool dhe Volumes p\u00ebrkat\u00ebse.<\/p>\n

Meqen\u00ebse k\u00ebto sisteme jan\u00eb mjaft \u201cinteligjente\u201d, ato mund t\u00eb lidhen me sistemin cloud t\u00eb monitorimit IBM Storage Insights, i cili, n\u00eb m\u00ebnyr\u00eb automatike, kur ndodh nj\u00eb defekt, d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb sh\u00ebrbimi te mb\u00ebshtetja e IBM. Krijohet nj\u00eb tiket\u00eb dhe specialist\u00ebt e IBM kryejn\u00eb diagnostikim n\u00eb distanc\u00eb dhe kontaktojn\u00eb p\u00ebrdoruesin e sistemit. <\/p>\n

Fal\u00eb k\u00ebsaj, \u00e7\u00ebshtja u zgjidh mjaft shpejt dhe nga sh\u00ebrbimi i mb\u00ebshtetjes mor\u00ebm nj\u00eb rekomandim t\u00eb menj\u00ebhersh\u00ebm p\u00ebr t\u00eb p\u00ebrdit\u00ebsuar sistemin ton\u00eb n\u00eb firmware-in 8.2.1.9, t\u00eb zgjedhur m\u00eb her\u00ebt prej nesh, ku n\u00eb at\u00eb koh\u00eb ky problem ishte tashm\u00eb i korrigjuar. K\u00ebt\u00eb e konfirmon Release Note p\u00ebrkat\u00ebs<\/u><\/a><\/noindex>.<\/u><\/p>\n

P\u00ebrfundimet dhe rekomandimet tona<\/h3>\n

Si thoni, \"gjith\u00e7ka e mir\u00eb p\u00ebrfundon mir\u00eb.\" Nj\u00eb gabim n\u00eb firmware nuk shkaktoi probleme t\u00eb r\u00ebnda \u2014 funksionimi i server\u00ebve u rikuperua n\u00eb koh\u00eb t\u00eb shkurt\u00ebr dhe pa humbje t\u00eb dh\u00ebnash. Disa klient\u00ebve iu desh t\u00eb rinisnin makinat virtuale, por n\u00eb p\u00ebrgjith\u00ebsi ishim t\u00eb p\u00ebrgatitur p\u00ebr pasoja m\u00eb t\u00eb r\u00ebnda, pasi \u00e7do dit\u00eb b\u00ebjm\u00eb kopje rezerv\u00eb t\u00eb t\u00eb gjitha elementeve t\u00eb infrastruktur\u00ebs dhe makinave t\u00eb klient\u00ebve. <\/p>\n

Mor\u00ebm konfirmimin se edhe sistemet e besueshme me 99,9999% disponueshm\u00ebri t\u00eb premtuar k\u00ebrkojn\u00eb v\u00ebmendje dhe mir\u00ebmbajtje n\u00eb koh\u00eb. Nisur nga kjo situat\u00eb, nxor\u00ebm disa p\u00ebrfundime dhe po ndajm\u00eb rekomandimet tona:<\/p>\n