{"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 sistemet tuaja t\u00eb ruajtjes me disponibilitet t\u00eb lart\u00eb (99,9999%)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Pse<\/p>\n

Cila \u00ebsht\u00eb versioni i firmware-it m\u00eb \"i sakt\u00eb\" dhe \"funksional\"? N\u00ebse sistemi i ruajtjes garanton q\u00ebndrueshm\u00ebri prej 99,9999%, a do t\u00eb thot\u00eb kjo q\u00eb do t\u00eb funksionoj\u00eb pa nd\u00ebrprerje edhe pa p\u00ebrmir\u00ebsime n\u00eb softuer? Apo, p\u00ebrkundrazi, p\u00ebr t\u00eb arritur q\u00ebndrueshm\u00ebrin\u00eb maksimale duhet gjithmon\u00eb t\u00eb vendosni versionin m\u00eb t\u00eb ri t\u00eb firmware-it? Do t\u00eb p\u00ebrpiqemi t\u00eb p\u00ebrgjigjemi p\u00ebr k\u00ebto pyetje, duke u mb\u00ebshtetur n\u00eb p\u00ebrvoj\u00ebn ton\u00eb.<\/p>\n

Nj\u00eb hyrje e vog\u00ebl<\/h3>\n

T\u00eb gjith\u00eb ne e kuptojm\u00eb se n\u00eb \u00e7do version t\u00eb softuerit, qoft\u00eb sistemi operacional ose nj\u00eb drejtuese p\u00ebr ndonj\u00eb pajisje, shpesh p\u00ebrmbahen mang\u00ebsi\/bagat dhe karakteristika t\u00eb tjera \"t\u00eb ve\u00e7anta\", t\u00eb cilat mund t\u00eb \"shfaqen\" p\u00ebrfundimisht gjat\u00eb jet\u00ebs s\u00eb pajisjes ose t\u00eb \"zbulohen\" vet\u00ebm n\u00ebn kushte t\u00eb caktuara. Numri dhe r\u00ebnd\u00ebsia e k\u00ebtyre detajeve varet nga kompleksiteti (funksionaliteti) i softuerit dhe nga cil\u00ebsia e testimeve gjat\u00eb zhvillimit t\u00eb tij. <\/p>\n

Shpesh, p\u00ebrdoruesit mbeten n\u00eb \"firmware-in e fabrik\u00ebs\" (e njohur \u2014 \"punon, pra mos e prek!\") ose gjithmon\u00eb vendosin versionin m\u00eb t\u00eb fundit (n\u00eb kuptimin e tyre, versioni m\u00eb i fundit do t\u00eb thot\u00eb m\u00eb funksional). Ne p\u00ebrdorim nj\u00eb qasje tjet\u00ebr \u2014 shikojm\u00eb sh\u00ebnimet e l\u00ebshimit p\u00ebr t\u00eb gjith\u00eb softuerin q\u00eb p\u00ebrdorim. n\u00eb mClouds<\/a><\/noindex> pajisjet dhe p\u00ebrzgjedhim me kujdes firmware-in e duhur p\u00ebr \u00e7do nj\u00ebsi pajisjeje. <\/p>\n

Kemi arritur n\u00eb k\u00ebt\u00eb p\u00ebrfundim p\u00ebrmes p\u00ebrvoj\u00ebs. Do t'ju tregojm\u00eb p\u00ebrvoj\u00ebn ton\u00eb p\u00ebrse 99,9999% e besueshm\u00ebris\u00eb s\u00eb sistemit t\u00eb ruajtjes nuk do t\u00eb thot\u00eb asgj\u00eb n\u00ebse nuk e ndjekni rregullisht p\u00ebrmir\u00ebsimin dhe p\u00ebrshkrimin e softuerit. Rasti yn\u00eb do t'i p\u00ebrgjigjet p\u00ebrdoruesve t\u00eb sistemeve t\u00eb ruajtjes nga \u00e7do prodhues, sepse nj\u00eb situat\u00eb e till\u00eb mund t\u00eb ndodh\u00eb me pajisje nga \u00e7do prodhues.<\/p>\n

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

N\u00eb fund t\u00eb vitit t\u00eb kaluar, infrastruktura jon\u00eb u pasurua me nj\u00eb sistem t\u00ebrheq\u00ebs t\u00eb dh\u00ebnash interesant: modeli m\u00eb i vog\u00ebl nga linja IBM FlashSystem 5000, i cili n\u00eb momentin e blerjes quhej Storwize V5010e. Tani ai shitet n\u00ebn emrin FlashSystem 5010, por n\u00eb fakt kjo \u00ebsht\u00eb e nj\u00ebjta baz\u00eb hardueri me t\u00eb nj\u00ebjtin Spectrum Virtualize brenda. <\/p>\n

Prania e nj\u00eb sistemi t\u00eb p\u00ebrbashk\u00ebt menaxhimi \u2014 \u00ebsht\u00eb, p\u00ebrve\u00e7 k\u00ebsaj, dallimi kryesor i IBM FlashSystem. N\u00eb modelet e seris\u00eb m\u00eb t\u00eb vog\u00ebl, ajo praktikisht nuk dallon nga modelet m\u00eb t\u00eb fuqishme. Zgjedhja e nj\u00eb modeli t\u00eb caktuar vet\u00ebm ofron baz\u00ebn p\u00ebrkat\u00ebse t\u00eb harduerit, karakteristikat e t\u00eb cilit lejojn\u00eb p\u00ebrdorimin e funksionaliteteve t\u00eb caktuara ose ofrojn\u00eb nj\u00eb nivel m\u00eb t\u00eb lart\u00eb t\u00eb shkall\u00ebzueshm\u00ebris\u00eb. Softueri identifikon harduerin 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

N\u00eb p\u00ebrmbledhje p\u00ebr modelin ton\u00eb 5010. Ky \u00ebsht\u00eb nj\u00eb sistem ruajtjeje t\u00eb dh\u00ebnash dy kontrollor\u00ebsh n\u00eb nivel fillestar. Ai mund t\u00eb vendos\u00eb disqe NLSAS, SAS, SSD. Vendosja e NVMe n\u00eb t\u00eb nuk \u00ebsht\u00eb e mundur, pasi ky model sistemi ruajtjeje \u00ebsht\u00eb pozicionuar p\u00ebr zgjidhjen e detyrave q\u00eb nuk k\u00ebrkojn\u00eb performanc\u00eb nga disqet NVMe.<\/p>\n

Sistemi i ruajtjes u ble p\u00ebr t\u00eb mbajtur informacionin arkiv dhe t\u00eb dh\u00ebnat q\u00eb nuk shihen shpesh. Prandaj, na mjaftonte grupi standard i funksionalitetit t\u00eb saj: tiering (Easy Tier), Thin Provision. Performanca mbi disqet NLSAS n\u00eb nivelin 1000-2000 IOPS ishte gjithashtu e pranueshme p\u00ebr ne. <\/p>\n

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

Tani t\u00eb kalojm\u00eb n\u00eb p\u00ebrmir\u00ebsimin e softuerit. N\u00eb momentin e blerjes, sistemi kishte nj\u00eb version t\u00eb pak\u00ebt t\u00eb vjet\u00ebr t\u00eb softuerit Spectrum Virtualize, konkretisht, 8.2.1.3.<\/strong><\/p>\n

Ne studiuam p\u00ebrshkrimin e firmware-it dhe planifikuam p\u00ebrmir\u00ebsimin deri n\u00eb 8.2.1.9<\/strong>. Sikur t\u00eb ishim pak m\u00eb t\u00eb shpejt\u00eb, kjo artikull nuk do t\u00eb ishte ekzistues \u2014 n\u00eb firmware m\u00eb t\u00eb fresk\u00ebt nuk do t\u00eb kishte ndodhur ky problem. Megjithat\u00eb, p\u00ebr disa arsye, p\u00ebrmir\u00ebsimi i k\u00ebsaj sistemi u vonua.<\/p>\n

Si rezultat, nj\u00eb vones\u00eb e vog\u00ebl n\u00eb p\u00ebrmir\u00ebsim \u00e7oi n\u00eb nj\u00eb situat\u00eb shum\u00eb t\u00eb pak\u00ebndshme, si\u00e7 \u00ebsht\u00eb p\u00ebrshkruar n\u00eb lidhjen: https:\/\/www.ibm.com\/support\/pages\/node\/6172341<\/u><\/a><\/noindex>. <\/p>\n

Po, n\u00eb firmware-in e asaj versioni p\u00ebrkat\u00ebs ishte aktuale raporti i njohur si 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, fillon t\u00eb mbushet cache, dhe m\u00eb pas sistemi kalon n\u00eb modin mbrojt\u00ebs, n\u00eb t\u00eb cilin \u00e7on n\u00eb ndikim t\u00eb hyrjeve\/daljeve p\u00ebr grupin (Pool). N\u00eb rastin ton\u00eb, v\u00ebrehej si shtypja e 3 disqeve p\u00ebr grupin RAID n\u00eb modin RAID 6. Nd\u00ebrprerja ndodhte p\u00ebr 6 minuta. M\u00eb pas, qasja n\u00eb v\u00ebllimet e Pool-it rikthehej.<\/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, tani do t\u00eb shpjegoj shkurtimisht.<\/p>\n

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

Disqet grumbullohen n\u00eb grupe, t\u00eb cilat quhen MDisk (Disk t\u00eb Menaxhuar). MDisk mund t\u00eb p\u00ebrfaq\u00ebsoj\u00eb RAID klasik (0,1,10,5,6) ose t\u00eb virtualizuar - DRAID (RAID i Distribuar). P\u00ebrdorimi i DRAID lejon rritjen e performanc\u00ebs s\u00eb grupit, pasi do t\u00eb p\u00ebrdoren t\u00eb gjith\u00eb disqet e grupit dhe do t\u00eb zvog\u00eblohet koha e rikonstruksionit, fal\u00eb faktit se do t\u00eb duhet t\u00eb rikuperohen vet\u00ebm blloqet e 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\u00eb disqe kur p\u00ebrdoret Distributed RAID (DRAID) n\u00eb m\u00ebnyr\u00ebn RAID-5.<\/p>\n

Dhe ky skem\u00eb tregon logjik\u00ebn e pun\u00ebs s\u00eb rikonstruksionit DRAID n\u00eb rast se nj\u00eb disk d\u00ebshtoi:<\/p>\n

\"PseLogjika e pun\u00ebs s\u00eb rikonstruksionit DRAID kur nj\u00eb disk d\u00ebshtoi<\/p>\n

Pastaj, nj\u00eb ose m\u00eb shum\u00eb MDisk formojn\u00eb at\u00eb q\u00eb quhet Pool. Brenda nj\u00eb pool nuk rekomandohet t\u00eb p\u00ebrdoren MDisk me nivele t\u00eb ndryshme RAID\/DRAID n\u00eb disqe t\u00eb nj\u00eb lloji. Nuk do t\u00eb thellohemi shum\u00eb n\u00eb k\u00ebt\u00eb, pasi planifikojm\u00eb t\u00eb flasim p\u00ebr t\u00eb n\u00eb nj\u00eb nga artikujt e ardhsh\u00ebm. N\u00eb t\u00eb v\u00ebrtet\u00eb, Pool ndahet n\u00eb Toma (Volumes), t\u00eb cilat prezantohen p\u00ebrmes nj\u00eb protokolli t\u00eb caktuar t\u00eb aksesit n\u00eb bllok n\u00eb drejtim t\u00eb hosteve.<\/p>\n

Pra, na ndodhi q\u00eb n\u00eb situat\u00ebn e p\u00ebrshkruar n\u00eb APAR HU02104<\/em>, p\u00ebr shkak t\u00eb nj\u00eb d\u00ebshtimi logjik t\u00eb tre disqeve, nj\u00eb MDisk t\u00eb cilin ndryshe e d\u00ebshtoi, duke \u00e7uar k\u00ebshtu n\u00eb d\u00ebshtimin e Pool dhe Tomave p\u00ebrkat\u00ebs.<\/p>\n

T\u00eb gjitha k\u00ebto sisteme jan\u00eb mjaft \"t\u00eb men\u00e7ura\", mund t\u00eb lidhen me sistemin cloud t\u00eb monitorimit IBM Storage Insights, i cili automatikisht, n\u00eb rast t\u00eb nj\u00eb d\u00ebshtimi, d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb p\u00ebr suport n\u00eb sh\u00ebrbimin e mb\u00ebshtetjes IBM. Krijohet nj\u00eb k\u00ebrkes\u00eb dhe specialist\u00ebt e IBM zhvillojn\u00eb diagnostikimin n\u00eb distanc\u00eb dhe kontaktojn\u00eb p\u00ebrdoruesin e sistemit. <\/p>\n

Fal\u00eb k\u00ebsaj, problemi u zgjidh mjaft shpejt dhe nga sh\u00ebrbimi i mb\u00ebshtetjes u mor nj\u00eb rekomandim t\u00eb shpejt\u00eb p\u00ebr t\u00eb rinovuar sistemin ton\u00eb n\u00eb versionin e zgjedhur m\u00eb her\u00ebt 8.2.1.9, n\u00eb t\u00eb cilin at\u00ebher\u00eb ky problem ishte tashm\u00eb zgjidhur. Kjo konfirmon sh\u00ebnimin p\u00ebrkat\u00ebs t\u00eb L\u00ebshimit<\/u><\/a><\/noindex>.<\/u><\/p>\n

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

Si thoni: \"e mira \u00ebsht\u00eb ajo q\u00eb mbaron mir\u00eb\". Problemi n\u00eb firmware nuk rezultoi n\u00eb probleme serioze - puna e server\u00ebve u rikuperua menj\u00ebher\u00eb dhe pa humbje t\u00eb t\u00eb dh\u00ebnave. Disa klient\u00eb ishin t\u00eb detyruar t\u00eb riparonin makinat virtuale, por n\u00eb t\u00ebr\u00ebsi ishim t\u00eb gatsh\u00ebm p\u00ebr pasojat m\u00eb negative, pasi \u00e7do dit\u00eb b\u00ebjm\u00eb kopje rezerv\u00eb t\u00eb gjith\u00eb elementeve t\u00eb infrastruktur\u00ebs dhe makinave t\u00eb klient\u00ebve. <\/p>\n

Kemi marr\u00eb konfirmim se edhe sistemet e besueshme me 99,9999% disponibilitet t\u00eb premtuar k\u00ebrkojn\u00eb kujdes dhe mb\u00ebshtetje n\u00eb koh\u00eb. N\u00eb baz\u00eb t\u00eb situat\u00ebs ne kemi b\u00ebr\u00eb disa p\u00ebrfundime dhe po ndajm\u00eb rekomandimet tona:<\/p>\n