{"id":35801,"date":"2019-10-31T22:06:24","date_gmt":"2019-10-31T19:06:24","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-vybrat-shd-ne-vystreliv-sebe-v-nogu\/"},"modified":"2019-10-31T22:06:24","modified_gmt":"2019-10-31T19:06:24","slug":"kak-vybrat-shd-ne-vystreliv-sebe-v-nogu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vybrat-shd-ne-vystreliv-sebe-v-nogu","title":{"rendered":"Si si zgjidhni nj\u00eb SDC, pa e l\u00ebnduar veten","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<h2>Hyrje<\/h2>\n<p>\nKa ardhur koha p\u00ebr t\u00eb bler\u00eb nj\u00eb sistem ruajtjeje. Cilin t\u00eb zgjedh, k\u00eb t\u00eb d\u00ebgjoj? Vendi A tregon p\u00ebr vendorin B, dhe pastaj ka integruesin C, i cili flet t\u00eb kund\u00ebrt\u00ebn dhe rekomandon vendorin D. N\u00eb nj\u00eb situat\u00eb t\u00eb till\u00eb, edhe nj\u00eb arkitekt i p\u00ebrvoj\u00ebs n\u00eb sistemet e ruajtjes do t\u00eb shp\u00ebrqendrohet, ve\u00e7an\u00ebrisht me t\u00eb gjith\u00eb vendor\u00ebt e rinj dhe me modat e sotme si SDS dhe konvergjenca e hiper.<\/p>\n<p>Tani, si t\u00eb kuptojm\u00eb gjith\u00e7ka k\u00ebt\u00eb dhe t\u00eb mos p\u00ebrfundojm\u00eb si budallenj? Ne (<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/users\/antonvirtual\/\" class=\"user_link\">AntonVirtual<\/a><\/noindex> Anton Zhbankov dhe <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/users\/korp\/\" class=\"user_link\">korp<\/a><\/noindex> Evgeny Elizarov) do t\u00eb p\u00ebrpiqemi ta shpjegojm\u00eb k\u00ebt\u00eb n\u00eb gjuh\u00ebn ruse n\u00eb m\u00ebnyr\u00eb t\u00eb qart\u00eb.<br \/>\nArtikulli n\u00eb nj\u00eb far\u00eb mase \u00ebsht\u00eb nj\u00eb rip\u00ebrs\u00ebritje, dhe n\u00eb fakt \u00ebsht\u00eb nj\u00eb shtrirje e \u201c<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/321178\/\">Dizajnit t\u00eb Qendr\u00ebs s\u00eb Virtualizuar t\u00eb T\u00eb Dh\u00ebnave<\/a><\/noindex>\u201d n\u00eb lidhje me zgjedhjen e sistemeve t\u00eb ruajtjes s\u00eb t\u00eb dh\u00ebnave dhe shqyrtimin e teknologjive t\u00eb ruajtjes. Ne do t\u00eb shqyrtojm\u00eb shkurtimisht teorin\u00eb e p\u00ebrgjithshme, por rekomandojm\u00eb t\u00eb shikoni edhe artikullin e p\u00ebrmendur.<\/p>\n<h2>Pse<\/h2>\n<p>\nShpesh mund t\u00eb v\u00ebrehet situata kur nj\u00eb person i ri hyn n\u00eb forum ose n\u00eb nj\u00eb chat t\u00eb specializuar, si\u00e7 \u00ebsht\u00eb Storage Discussions, dhe b\u00ebn nj\u00eb pyetje: \u201cM\u00eb ofrohen dy mund\u00ebsi p\u00ebr sistemet e ruajtjes \u2014 ABC SuperStorage S600 dhe XYZ HyperOcean 666v4, \u00e7far\u00eb rekomandoni\u201d?<\/p>\n<p>Dhe fillon matja e cilit ka cil\u00ebsi dhe ve\u00e7ori t\u00eb realizimit t\u00eb frikshme dhe t\u00eb paqarta, t\u00eb cilat p\u00ebr nj\u00eb person t\u00eb pap\u00ebrgatitur jan\u00eb si dokumentet kineze. <br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nPra, pyetje kryesore dhe e para q\u00eb duhet t'i b\u00ebni vetes shum\u00eb para se t\u00eb filloni t\u00eb krahasoni specifikimet n\u00eb ofertat komerciale \u2014 PSE? Pse e nevojitet ky sistem ruajtjeje?<\/p>\n<p><img decoding=\"async\" alt=\"Si si zgjidhni nj\u00eb SDC, pa e l\u00ebnduar veten\" src=\"\/wp-content\/uploads\/2019\/06\/4e02a50a2420483c6c4939bf264dea2a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u00ebrgjigja do t\u00eb jet\u00eb befasuese, dhe shum\u00eb n\u00eb stilin e Tony Robbins \u2014 p\u00ebr t\u00eb ruajtur t\u00eb dh\u00ebnat. Faleminderit, kapiten! Megjithat\u00eb, ndonj\u00ebher\u00eb ne thellohemi aq shum\u00eb n\u00eb krahasimin e detajeve, sa harrojm\u00eb p\u00ebrse e b\u00ebjm\u00eb gjith\u00eb k\u00ebt\u00eb.<\/p>\n<p>Pra, detyra e sistemit t\u00eb ruajtjes s\u00eb t\u00eb dh\u00ebnave \u00ebsht\u00eb ruajtja dhe ofrimi i qasjes n\u00eb T\u00cb DH\u00cbNAT me nj\u00eb performanc\u00eb t\u00eb caktuar. Nga t\u00eb dh\u00ebnat do t\u00eb fillojm\u00eb.<\/p>\n<h2>T\u00eb dh\u00ebnat<\/h2>\n<p><\/p>\n<h3>Lloji i t\u00eb dh\u00ebnave<\/h3>\n<p>\n\u00c7far\u00eb t\u00eb dh\u00ebnash planifikojm\u00eb t\u00eb ruajm\u00eb? \u00cbsht\u00eb nj\u00eb pyetje shum\u00eb e r\u00ebnd\u00ebsishme q\u00eb mund t\u00eb p\u00ebrjashtoj\u00eb shum\u00eb sisteme ruajtjeje nga shqyrtimi. P\u00ebr shembull, planifikohet ruajtja e videove dhe fotografive. Menj\u00ebher\u00eb mund t\u00eb p\u00ebrjashtohen sistemet q\u00eb jan\u00eb t\u00eb dedikuara p\u00ebr aksesin e rast\u00ebsish\u00ebm me blloqe t\u00eb vogla, ose sistemet me karakteristika t\u00eb patentuara p\u00ebr kompresion \/ deduplication. K\u00ebto mund t\u00eb jen\u00eb sisteme t\u00eb shk\u00eblqyera, nuk duam t\u00eb themi ndonj\u00eb gj\u00eb t\u00eb keqe p\u00ebr to. Por n\u00eb k\u00ebt\u00eb rast, pikat e tyre t\u00eb forta do t\u00eb b\u00ebhen pika t\u00eb dob\u00ebta (video dhe foto nuk kompresohen) ose do t\u00eb rrisin ndjesh\u00ebm koston e sistemit.<\/p>\n<p>Dhe e kund\u00ebrta, n\u00ebse p\u00ebrdorimi i synuar \u00ebsht\u00eb nj\u00eb DB tranzaksional e ngarkuar, at\u00ebher\u00eb sistemet e shk\u00eblqyera t\u00eb rrjedh\u00ebs p\u00ebr multimedia, t\u00eb cilat mund t\u00eb japin gigabajt n\u00eb sekond\u00eb, do t\u00eb ishin nj\u00eb zgjedhje e keqe.<\/p>\n<h3>V\u00ebllimi i t\u00eb dh\u00ebnave<\/h3>\n<p>\nSa t\u00eb dh\u00ebna planifikojm\u00eb t\u00eb ruajm\u00eb? Sasia gjithmon\u00eb kthehet n\u00eb cil\u00ebsi, k\u00ebt\u00eb nuk duhet ta harrojm\u00eb kurr\u00eb, ve\u00e7an\u00ebrisht n\u00eb koh\u00ebn ton\u00eb t\u00eb rritjes eksponenciale t\u00eb v\u00ebllimit t\u00eb t\u00eb dh\u00ebnave. Sistemet e klas\u00ebs petabajt tani nuk jan\u00eb t\u00eb pazakonta, por sa m\u00eb shum\u00eb petabajt t\u00eb ket\u00eb, aq m\u00eb specifike b\u00ebhet sistemi, aq m\u00eb pak funksionaliteti i zakonsh\u00ebm i sistemeve me akses t\u00eb rast\u00ebsish\u00ebm t\u00eb vog\u00ebl e t\u00eb mes\u00ebm do t\u00eb jet\u00eb i disponuesh\u00ebm. Kjo ndodh sepse vet\u00ebm tabelat e statistikave t\u00eb aksesit p\u00ebr blloqet b\u00ebhen m\u00eb t\u00eb m\u00ebdha se v\u00ebllimi i disponuesh\u00ebm t\u00eb memories t\u00eb p\u00ebrkohshme n\u00eb kontrollet. Pavar\u00ebsisht nga kompresimi \/ tieringu. Le t\u00eb supozojm\u00eb se duam t\u00eb kalojm\u00eb n\u00eb nj\u00eb algorit\u00ebm kompresimi m\u00eb t\u00eb fuqish\u00ebm dhe t\u00eb kompresojm\u00eb 20 petabajt t\u00eb dh\u00ebnash. Sa do t\u00eb zgjas\u00eb: gjasht\u00eb muaj, nj\u00eb vit?<\/p>\n<p>N\u00eb an\u00ebn tjet\u00ebr, pse t\u00eb nd\u00ebrtojm\u00eb nj\u00eb sistem t\u00eb madh, n\u00ebse na nevojitet t\u00eb ruajm\u00eb dhe t\u00eb procesojm\u00eb vet\u00ebm 500 GB t\u00eb dh\u00ebnash? Pothuajse 500. SSD-t\u00eb e zakonshme (me DWPD t\u00eb ul\u00ebt) t\u00eb k\u00ebtij v\u00ebllimi kushtojn\u00eb vet\u00ebm pak. Pse t\u00eb nd\u00ebrtojm\u00eb nj\u00eb fabrik\u00eb Fiber Channel dhe t\u00eb blejm\u00eb nj\u00eb sistem ruajtjeje t\u00eb jasht\u00ebm t\u00eb klas\u00ebs s\u00eb lart\u00eb q\u00eb kushton si nj\u00eb ur\u00eb prej hekuri?<\/p>\n<p>Cili p\u00ebrqindje e p\u00ebrgjithshme e t\u00eb dh\u00ebnave t\u00eb nxehta? Sa e pabarabart\u00eb \u00ebsht\u00eb ngarkesa sipas sasis\u00eb s\u00eb t\u00eb dh\u00ebnave? K\u00ebtu teknologjia e ruajtjes me shum\u00eb nivele ose Flash Cache mund t\u00eb ndihmoj\u00eb shum\u00eb, n\u00ebse sasia e t\u00eb dh\u00ebnave t\u00eb nxehta \u00ebsht\u00eb shum\u00eb e vog\u00ebl n\u00eb krahasim me totalin. Ose p\u00ebrkundrazi, n\u00eb rast t\u00eb nj\u00eb ngarkese t\u00eb barabart\u00eb n\u00eb t\u00eb gjith\u00eb volumet, e cila \u00ebsht\u00eb e zakonshme n\u00eb sistemet e transmetimit (monitorimi video, disa sisteme analitik\u00eb) teknologjit\u00eb e tilla nuk do t\u00eb ofrojn\u00eb asgj\u00eb, dhe vet\u00ebm do t\u00eb rrisin kostot \/ kompleksitetin e sistemit.<\/p>\n<h3>IS<\/h3>\n<p>\nAn\u00ebs tjet\u00ebr e t\u00eb dh\u00ebnave \u00ebsht\u00eb nj\u00eb sistem informatik q\u00eb p\u00ebrdor k\u00ebto t\u00eb dh\u00ebna. IS ka nj\u00eb grup k\u00ebrkesash q\u00eb trash\u00ebgohen nga t\u00eb dh\u00ebnat. M\u00eb shum\u00eb rreth IS shih te \u201cDizajni i Qendr\u00ebs s\u00eb Dh\u00ebnave t\u00eb Virtualizuara\u201d.<\/p>\n<h4>K\u00ebrkesat p\u00ebr q\u00ebndrueshm\u00ebri \/ disponueshm\u00ebri<\/h4>\n<p>K\u00ebrkesat p\u00ebr q\u00ebndrueshm\u00ebri \/ disponueshm\u00ebri t\u00eb t\u00eb dh\u00ebnave trash\u00ebgohen nga IS q\u00eb i p\u00ebrdor ato dhe shprehen n\u00eb tre numra \u2014 <b>RPO<\/b>, <b>RTO<\/b>, <b>disponueshm\u00ebrin\u00eb<\/b>.<\/p>\n<p><b>Disponueshm\u00ebria <\/b> \u2014 pjesa p\u00ebr nj\u00eb periudh\u00eb t\u00eb caktuar kohore, gjat\u00eb s\u00eb cil\u00ebs t\u00eb dh\u00ebnat jan\u00eb t\u00eb disponueshme p\u00ebr t'u p\u00ebrdorur. Kjo zakonisht shprehet n\u00eb numrin e 9. P\u00ebr shembull, dy n\u00ebnat n\u00eb vit do t\u00eb thot\u00eb q\u00eb disponueshm\u00ebria \u00ebsht\u00eb 99%, ose ndryshe lejohet 95 or\u00eb munges\u00eb n\u00eb vit. Treshe 9 \u2014 9.5 or\u00eb n\u00eb vit.<\/p>\n<p>RPO \/ RTO \u2014 k\u00ebto jan\u00eb tregues jo t\u00eb p\u00ebrmbledhura, por p\u00ebr \u00e7do incident (fatkeq\u00ebsi), ndryshe nga disponueshm\u00ebria.<\/p>\n<p><b>RPO <\/b> \u2014 sasia e t\u00eb dh\u00ebnave t\u00eb humbura gjat\u00eb nj\u00eb fatkeq\u00ebsie (n\u00eb or\u00eb). P\u00ebr shembull, n\u00ebse b\u00ebhet kopjim rezerv\u00eb \u00e7do dit\u00eb, at\u00ebher\u00eb RPO = 24 or\u00eb. P.sh., n\u00eb rast t\u00eb nj\u00eb fatkeq\u00ebsie dhe humbjes totale t\u00eb SHT, mund t\u00eb humben t\u00eb dh\u00ebna deri n\u00eb 24 or\u00eb (q\u00eb prej kopjimit t\u00eb rezerv\u00ebs). Bazuar n\u00eb RPO-n\u00eb e caktuar p\u00ebr IS, p\u00ebr shembull, do t\u00eb hartohet nj\u00eb rregullore p\u00ebr kopjimet rezerv\u00eb. Gjithashtu, nga RPO, mund t\u00eb kuptohet sa e nevojshme \u00ebsht\u00eb replikimi i t\u00eb dh\u00ebnave n\u00eb m\u00ebnyr\u00eb sinkrone \/ asinkrone.<\/p>\n<p><b>RTO<\/b> \u2014 koha e rikuperimit t\u00eb sh\u00ebrbimit (qasje n\u00eb t\u00eb dh\u00ebna) pas nj\u00eb fatkeq\u00ebsie. Bazuar n\u00eb vler\u00ebn e caktuar RTO mund t\u00eb kuptojm\u00eb n\u00ebse nevojitet nj\u00eb metrokaster, ose mjafton replikimi nj\u00eban\u00ebsh. A \u00ebsht\u00eb e nevojshme nj\u00eb SHT e klas\u00ebs hi-end me shum\u00eb kontrollues \u2014 gjithashtu.<\/p>\n<p><img decoding=\"async\" alt=\"Si si zgjidhni nj\u00eb SDC, pa e l\u00ebnduar veten\" src=\"\/wp-content\/uploads\/2019\/06\/327166acf29e390fa7454fe66bc4e409.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h4>K\u00ebrkesat p\u00ebr performanc\u00eb<\/h4>\n<p>\nMegjith\u00ebse kjo \u00ebsht\u00eb nj\u00eb pyetje mjaft e qart\u00eb, me t\u00eb ndodhin shumica e v\u00ebshtir\u00ebsive. N\u00eb var\u00ebsi t\u00eb faktit n\u00ebse ju tashm\u00eb keni ndonj\u00eb infrastruktur\u00eb apo jo dhe se si do t\u00eb nd\u00ebrtohen rrug\u00ebt p\u00ebr mbledhjen e statistikave t\u00eb nevojshme.<\/p>\n<p>N\u00ebse keni nj\u00eb sistem t\u00eb ruajtes s\u00eb t\u00eb dh\u00ebnave dhe jeni duke k\u00ebrkuar nj\u00eb z\u00ebvend\u00ebsues ose d\u00ebshironi t\u00eb blini nj\u00eb tjet\u00ebr p\u00ebr t\u00eb zgjeruar kapacitetin. K\u00ebtu \u00ebsht\u00eb e thjesht\u00eb. Ju e kuptoni se cilat sh\u00ebrbime keni aktualisht dhe cilat planifikoni t\u00eb implementoni n\u00eb t\u00eb ardhmen e af\u00ebrt. Duke u mb\u00ebshtetur n\u00eb sh\u00ebrbimet aktuale, keni mund\u00ebsin\u00eb t\u00eb mblidhni t\u00eb dh\u00ebna p\u00ebr performanc\u00ebn. Duhet t\u00eb p\u00ebrcaktoni numrin aktual t\u00eb IOPS dhe vonesat e tani - si jan\u00eb k\u00ebto tregues dhe a mjaftojn\u00eb p\u00ebr nevojat tuaja? K\u00ebt\u00eb e b\u00ebni si n\u00eb sistemin e ruajtes s\u00eb t\u00eb dh\u00ebnave, ashtu edhe nga ana e hosteve q\u00eb lidhen me t\u00eb.<\/p>\n<p>Por, duhet t\u00eb shikoni jo vet\u00ebm ngarkes\u00ebn aktuale, por p\u00ebr nj\u00eb periudh\u00eb (m\u00eb mir\u00eb nj\u00eb muaj). Shihni se cilat jan\u00eb pikat maksimale n\u00eb or\u00ebt e dit\u00ebs, \u00e7far\u00eb ngarkese krijon kopjimi rezerv\u00eb, etj. N\u00ebse sistemi juaj i ruajtes s\u00eb t\u00eb dh\u00ebnave ose softueri i tij nuk ju jep nj\u00eb gam\u00eb t\u00eb plot\u00eb t\u00eb k\u00ebtyre t\u00eb dh\u00ebnave, mund t\u00eb p\u00ebrdorni RRDtool falas, q\u00eb di t\u00eb punoj\u00eb me shumic\u00ebn e sistemeve m\u00eb t\u00eb njohura t\u00eb ruajtes s\u00eb t\u00eb dh\u00ebnave dhe switch-eve dhe mund t\u00eb ofroj\u00eb statistika t\u00eb detajuara p\u00ebr performanc\u00ebn. Gjithashtu, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb monitoroni ngarkes\u00ebn edhe n\u00eb hostet q\u00eb punojn\u00eb me k\u00ebt\u00eb sistem ruajtjeje, p\u00ebr makina virtuale specifike ose \u00e7far\u00ebdo q\u00eb po punon n\u00eb k\u00ebt\u00eb host.<\/p>\n<p><img decoding=\"async\" alt=\"Si si zgjidhni nj\u00eb SDC, pa e l\u00ebnduar veten\" src=\"\/wp-content\/uploads\/2019\/06\/a0db9ec82e8ab5282e7af5d50e02f281.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nMerita ve\u00e7an\u00ebrisht e p\u00ebrmendshme \u00ebsht\u00eb se n\u00ebse vonesat n\u00eb volum dhe datastorin q\u00eb ndodhet n\u00eb k\u00ebt\u00eb volum dallohen ndjesh\u00ebm - duhet t\u00eb vini re rrjetin tuaj SAN, ka mund\u00ebsi t\u00eb lart\u00eb q\u00eb ka probleme, dhe para se t\u00eb blini nj\u00eb sistem t\u00eb ri, duhet t\u00eb merret me k\u00ebt\u00eb \u00e7\u00ebshtje, pasi ka nj\u00eb mund\u00ebsi shum\u00eb t\u00eb madhe p\u00ebr t\u00eb rritur performanc\u00ebn e sistemit aktual.<\/p>\n<p>Ju po nd\u00ebrtoni infrastruktur\u00eb nga e para, ose po blini nj\u00eb sistem p\u00ebr ndonj\u00eb sh\u00ebrbim t\u00eb ri, p\u00ebr t\u00eb cilin nuk keni njohuri p\u00ebr ngarkesat. K\u00ebtu ka disa mund\u00ebsi: flisni me koleg\u00ebt n\u00eb burimet p\u00ebrkat\u00ebse, p\u00ebr t\u00eb p\u00ebrpiquar t\u00eb merrni informacion dhe t\u00eb parashikoni ngarkes\u00ebn, kontaktoni me nj\u00eb integrues, i cili ka p\u00ebrvoj\u00eb n\u00eb implementimin e sh\u00ebrbimeve t\u00eb tilla dhe q\u00eb mund t\u00eb llogaris\u00eb ngarkes\u00ebn p\u00ebr ju. Dhe opsioni i tret\u00eb (zakonisht m\u00eb i komplikuari, ve\u00e7an\u00ebrisht n\u00ebse kjo p\u00ebrfshin aplikacione t\u00eb krijuara vet\u00eb ose t\u00eb pazakonta) \u00ebsht\u00eb t\u00eb p\u00ebrpiqeni t\u00eb zbuloni k\u00ebrkesat p\u00ebr performanc\u00eb nga zhvilluesit e sistemit.<\/p>\n<p>Dhe, v\u00ebmendje, opsioni m\u00eb i sakt\u00eb nga pik\u00ebpamja e p\u00ebrdorimit praktik \u00ebsht\u00eb nj\u00eb pilot n\u00eb pajisjet aktuale, ose pajisje e siguruar p\u00ebr testim nga ofruesi \/ integratori.<\/p>\n<h4>K\u00ebrkesat e ve\u00e7anta<\/h4>\n<p>\nK\u00ebrkesat e ve\u00e7anta jan\u00eb gjith\u00e7ka q\u00eb nuk bie n\u00ebn k\u00ebrkesat p\u00ebr performanc\u00ebn, q\u00ebndrueshm\u00ebrin\u00eb dhe funksionalitetin n\u00eb p\u00ebrpunimin dhe ofrimin e t\u00eb dh\u00ebnave.<\/p>\n<p>Nj\u00eb nga k\u00ebrkesat m\u00eb t\u00eb thjeshta p\u00ebr sistemin e ruajtjes s\u00eb t\u00eb dh\u00ebnave mund t\u00eb quhet \"media informacioni t\u00eb shk\u00ebputshme\". Menj\u00ebher\u00eb b\u00ebhet e qart\u00eb se ky sistem ruajtjeje duhet t\u00eb p\u00ebrfshij\u00eb nj\u00eb bibliotek\u00eb kasetash ose thjesht nj\u00eb streamer, n\u00eb t\u00eb cilin ruhet nj\u00eb kopje rezerv\u00eb. Pas k\u00ebsaj, nj\u00eb person i trajnuar posa\u00e7\u00ebrisht n\u00ebnshkruan kaset\u00ebn dhe krenarisht e \u00e7on at\u00eb n\u00eb nj\u00eb sht\u00ebpi t\u00eb siguris\u00eb.<br \/>\nNj\u00eb shembull tjet\u00ebr i k\u00ebrkes\u00ebs s\u00eb ve\u00e7ant\u00eb \u00ebsht\u00eb p\u00ebrfundimi i mbrojtur nga goditjet.<\/p>\n<h2>Ku<\/h2>\n<p>\nPjesa tjet\u00ebr e r\u00ebnd\u00ebsishme n\u00eb zgjedhjen e k\u00ebtij ose atij sistemi t\u00eb ruajtjes s\u00eb t\u00eb dh\u00ebnave \u00ebsht\u00eb informacioni se KU do t\u00eb vendoset ky sistem. Duke filluar nga gjeografia ose kushtet klimatike, deri te stafi.<\/p>\n<h3>Klienti<\/h3>\n<p>\nP\u00ebr k\u00eb \u00ebsht\u00eb planifikuar ky sistem i ruajtjes s\u00eb t\u00eb dh\u00ebnave? Pyetja ka disa baza t\u00eb tjera:<\/p>\n<p><b>Klienti shtet\u00ebror \/ komercial.<\/b><br \/>\nKlienti komercial nuk ka asnj\u00eb kufizim dhe nuk ka detyrim t\u00eb organizoj\u00eb tender\u00eb, p\u00ebrve\u00e7 rregullave t\u00eb tij t\u00eb brendshme. <\/p>\n<p>Klienti shtet\u00ebror \u00ebsht\u00eb nj\u00eb tjet\u00ebr rast. Ligji 44-FZ dhe leht\u00ebsit\u00eb e tjera me tender\u00ebt dhe specifikimet teknike q\u00eb mund t\u00eb kontestohen.<\/p>\n<p><b>Klienti n\u00ebn sanksione<\/b><br \/>\nK\u00ebtu pyetja \u00ebsht\u00eb shum\u00eb e thjesht\u00eb - zgjedhja kufizohet vet\u00ebm n\u00eb ofertat e disponueshme p\u00ebr k\u00ebt\u00eb klient.<\/p>\n<p><b>Rregullat e brendshme \/ ofruesit e lejuar p\u00ebr blerje \/ modelet<\/b><br \/>\nPyetja gjithashtu \u00ebsht\u00eb jasht\u00ebzakonisht e thjesht\u00eb, por duhet mbajtur mend.<\/p>\n<h3>Ku fizikisht<\/h3>\n<p>\nN\u00eb k\u00ebt\u00eb pjes\u00eb shqyrtojm\u00eb t\u00eb gjitha \u00e7\u00ebshtjet me gjeografin\u00eb, kanalet e komunikimit dhe mikroklim\u00ebn n\u00eb ambientin e vendosjes.<\/p>\n<h4>Stafi<\/h4>\n<p>\nKush do t\u00eb punoj\u00eb me k\u00ebt\u00eb sistem t\u00eb ruajtjes s\u00eb t\u00eb dh\u00ebnave? Kjo \u00ebsht\u00eb po aq e r\u00ebnd\u00ebsishme sa ajo q\u00eb sistemi i ruajtjes s\u00eb t\u00eb dh\u00ebnave mund t\u00eb b\u00ebj\u00eb.<br \/>\nPavar\u00ebsisht se sa e perspektivshme, e mrekullueshme dhe e shk\u00eblqyer \u00ebsht\u00eb nj\u00eb sistem ruajtjeje t\u00eb dh\u00ebnash nga ofruesi A, nuk ka shum\u00eb kuptim ta vendos\u00ebsh at\u00eb n\u00ebse stafi di vet\u00ebm t\u00eb punoj\u00eb me ofruesin B, dhe nuk planifikohet blerja e m\u00ebtejshme dhe bashk\u00ebpunimi i vazhduesh\u00ebm me A.<\/p>\n<p>Dhe sigurisht, ana tjet\u00ebr e \u00e7\u00ebshtjes \u00ebsht\u00eb sa i qassh\u00ebm \u00ebsht\u00eb stafi i kualifikuar n\u00eb k\u00ebt\u00eb vendgjiografi, si brenda kompanis\u00eb ashtu edhe n\u00eb tregun potencial t\u00eb pun\u00ebs. P\u00ebr rajonet, ka nj\u00eb r\u00ebnd\u00ebsi t\u00eb madhe zgjedhja e STH-ve me nd\u00ebrfaqe t\u00eb thjeshta ose me mund\u00ebsi menaxhimi t\u00eb centralizuar n\u00eb distanc\u00eb. Ndryshe, n\u00eb nj\u00eb moment, mund t\u00eb b\u00ebhet mjaft e dhimbshme. Interneti \u00ebsht\u00eb plot histori se si nj\u00eb punonj\u00ebs i ri, nj\u00eb student i djesh\u00ebm, ka konfiguruar di\u00e7ka q\u00eb e ka bllokuar t\u00ebr\u00eb kompanin\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"Si si zgjidhni nj\u00eb SDC, pa e l\u00ebnduar veten\" src=\"\/wp-content\/uploads\/2019\/06\/5feeb5b13119c87d6b516d160d801129.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h4>Mjedisi<\/h4>\n<p>\nPo ashtu, nj\u00eb \u00e7\u00ebshtje mjaft e r\u00ebnd\u00ebsishme \u00ebsht\u00eb n\u00eb cilin ambient do t\u00eb punoj\u00eb ky STH. <\/p>\n<ul>\n<li>Si \u00ebsht\u00eb furnizimi me energji \/ ftohja?<\/li>\n<li>Cila \u00ebsht\u00eb lidhja?<\/li>\n<li>Ku do t\u00eb montohen?<\/li>\n<li>Etj.<\/li>\n<\/ul>\n<p>\nShpesh k\u00ebto pyetje merren si t\u00eb kuptueshme dhe nuk shqyrtohen shum\u00eb, por ndonj\u00ebher\u00eb ato mund t\u00eb p\u00ebrmbysin gjith\u00e7ka n\u00eb m\u00ebnyr\u00ebn e duhur.<\/p>\n<h2>\u00c7far\u00eb?<\/h2>\n<p><\/p>\n<h3>Furnizuesi<\/h3>\n<p>\nSot (mes viti 2019), tregu rus i STH-ve mund t\u00eb ndahet n\u00eb pes\u00eb kategori t\u00eb kusht\u00ebzuara:<\/p>\n<ol>\n<li>Divizioni m\u00eb i lart\u00eb \u2014 kompani t\u00eb njohura me nj\u00eb linj\u00eb t\u00eb gjer\u00eb nga raftet m\u00eb t\u00eb thjeshta t\u00eb disqeve deri te hi-end (HPE, DellEMC, Hitachi, NetApp, IBM \/ Lenovo)<\/li>\n<li>Divizioni i dyt\u00eb \u2014 kompani me nj\u00eb linj\u00eb t\u00eb kufizuar, lojtar\u00eb t\u00eb ni\u015f\u00ebzuar, furnizues t\u00eb r\u00ebnd\u00ebsish\u00ebm t\u00eb SDS ose start-up-et prometheiane (Fujitsu, Datacore, Infinidat, Huawei, Pure etj.)<\/li>\n<li>Divizioni i tret\u00eb \u2014 zgjidhje t\u00eb ni\u015f\u00ebzuara n\u00eb rangun low end, SDS t\u00eb lira, produkte t\u00eb p\u00ebrbashk\u00ebta mbi ceph dhe projekte t\u00eb tjera t\u00eb hapura (Infortrend, Starwind etj.)<\/li>\n<li>Segmenti SOHO \u2014 STH t\u00eb vogla dhe jasht\u00ebzakonisht t\u00eb vogla n\u00eb nivelin e sht\u00ebpis\u00eb \/ zyr\u00ebs s\u00eb vog\u00ebl (Synology, QNAP etj.)<\/li>\n<li>STH t\u00eb importuara \u2014 p\u00ebrfshijn\u00eb si pajisjet e divizionit t\u00eb par\u00eb me etiketa t\u00eb ripara, ashtu edhe p\u00ebrfaq\u00ebsues t\u00eb rrall\u00eb t\u00eb divizionit t\u00eb dyt\u00eb (RAIDIX, do t'u japim atyre nj\u00eb bonus t\u00eb dyt\u00eb), por n\u00eb t\u00ebr\u00ebsi \u00ebsht\u00eb divizioni i tret\u00eb (Aerodisk, Baum, Depo etj.)<\/li>\n<\/ol>\n<p>\nNdarja \u00ebsht\u00eb mjaft e kusht\u00ebzuar dhe nuk do t\u00eb thot\u00eb aspak se segmenti i tret\u00eb ose SOHO \u00ebsht\u00eb i dob\u00ebt dhe nuk mund t\u00eb p\u00ebrdoret. N\u00eb projekte specifike me nj\u00eb grup t\u00eb qart\u00eb t\u00eb t\u00eb dh\u00ebnave dhe profilin e ngarkes\u00ebs, ata mund t\u00eb funksionojn\u00eb shum\u00eb mir\u00eb, duke tejkaluar edhe divizionin e par\u00eb n\u00eb raportin \u00e7mim \/ cil\u00ebsi. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme fillimisht t\u00eb vendosni objektivat, perspektivat e rritjes, funksionalitetin e k\u00ebrkuar \u2014 dhe at\u00ebher\u00eb Synology do t'ju sh\u00ebrbej\u00eb besnik\u00ebrisht, duke b\u00ebr\u00eb q\u00eb flok\u00ebt tuaj t\u00eb b\u00ebhen t\u00eb but\u00eb dhe t\u00eb fryra.<\/p>\n<p>Nj\u00eb nga faktor\u00ebt e r\u00ebnd\u00ebsish\u00ebm n\u00eb p\u00ebrzgjedhjen e ofruesit \u00ebsht\u00eb ambienti aktual. Sa dhe \u00e7far\u00eb S\u0138D (Sistemet e Ruajtjes s\u00eb t\u00eb Dh\u00ebnave) keni, me cilat S\u0138D mund t\u00eb punojn\u00eb inxhinier\u00ebt. Ju nevojitet nj\u00eb ofrues tjet\u00ebr, nj\u00eb pik\u00eb kontakti tjet\u00ebr, do ta migroni gradualisht gjith\u00eb ngarkes\u00ebn nga ofruesi A te ofruesi B?<\/p>\n<p>Nuk duhet t\u00eb krijoni entitete m\u00eb shum\u00eb se sa e nevojshme.<\/p>\n<h3>iSCSI \/ FC \/ File<\/h3>\n<p>\nN\u00eb lidhje me protokollet e qasjes, nuk ka nj\u00eb mendim t\u00eb nj\u00ebtrajtsh\u00ebm mes inxhinier\u00ebve, dhe debatet duken m\u00eb shum\u00eb si diskurse teologjike sesa inxhinierike. Por n\u00eb p\u00ebrgjith\u00ebsi, mund t\u00eb theksohen disa pika:<\/p>\n<p><b>FCoE<\/b> m\u00eb shum\u00eb \u00ebsht\u00eb i vdekur sesa i gjall\u00eb.<\/p>\n<p><b>FC vs iSCSI<\/b>. Nj\u00eb nga avantazhet kryesore t\u00eb FC n\u00eb 2019 ndaj S\u0138D IP, fabrika e dedikuar p\u00ebr qasje n\u00eb t\u00eb dh\u00ebna, anashkalon rrjetin e dedikuar IP. Nuk ka avantazhe globale t\u00eb FC ndaj rrjeteve IP dhe mbi IP mund t\u00eb nd\u00ebrtohen S\u0138D t\u00eb \u00e7do niveli ngarkese, deri n\u00eb sisteme p\u00ebr SGBD t\u00eb r\u00ebnda p\u00ebr ABS t\u00eb nj\u00eb banke t\u00eb madhe. Nga ana tjet\u00ebr, vdekja e FC \u00ebsht\u00eb parashikuar p\u00ebr disa vite, por gjithmon\u00eb ka di\u00e7ka q\u00eb e pengon. Sot, p\u00ebr shembull, disa lojtar\u00eb n\u00eb tregun e S\u0138D po zhvillojn\u00eb aktivisht standardin NVMEoF. N\u00ebse ai do t\u00eb ndihmoj\u00eb n\u00eb ndarjen e fatit t\u00eb FCoE \u2014 vet\u00ebm koha do ta tregoj\u00eb.<\/p>\n<p><b>Qasja n\u00eb skedar<\/b> po ashtu nuk \u00ebsht\u00eb di\u00e7ka q\u00eb nuk meriton v\u00ebmendje. NFS \/ CIFS p\u00ebrformojn\u00eb shk\u00eblqyesh\u00ebm n\u00eb ambientet produktive dhe, me projektimin e duhur, nuk kan\u00eb m\u00eb shum\u00eb ankesa se protokollet bllokuese.<\/p>\n<h3>Hibrid \/ All Flash Array<\/h3>\n<p>\nS\u0138D klasike jan\u00eb t\u00eb dy llojeve:<\/p>\n<ol>\n<li>AFA (All Flash Array) \u2014 sisteme t\u00eb optimizuara p\u00ebr p\u00ebrdorimin e SSD.<\/li>\n<li>Hibrid \u2014 q\u00eb lejojn\u00eb p\u00ebrdorimin e HDD dhe SSD ose kombinimin e tyre.<\/li>\n<\/ol>\n<p>\nDallimi kryesor \u00ebsht\u00eb teknologjit\u00eb mb\u00ebshtet\u00ebse p\u00ebr efikasitetin e ruajtjes dhe nivelin maksimal t\u00eb performanc\u00ebs (shifrat e larta IOPS dhe vonesat e ul\u00ebta). T\u00eb dy sistemet (n\u00eb shumic\u00ebn e modeleve t\u00eb tyre, p\u00ebrve\u00e7 segmenteve low-end) mund t\u00eb funksionojn\u00eb si pajisje blloku, ashtu edhe si skedar\u00eb. Nga niveli i sistemit varet gjithashtu funksionaliteti i mb\u00ebshtetur, dhe p\u00ebr modelet m\u00eb t\u00eb ul\u00ebta, ai shpesh her\u00eb \u00ebsht\u00eb reduktuar n\u00eb nivelin minimal. Kjo \u00ebsht\u00eb di\u00e7ka p\u00ebr t\u00eb cil\u00ebn duhet t\u00eb keni parasysh kur studioni karakteristikat e nj\u00eb modeli t\u00eb caktuar, dhe jo thjesht mund\u00ebsit\u00eb e gjith\u00eb linj\u00ebs n\u00eb p\u00ebrgjith\u00ebsi. Sigurisht, nga niveli i sistemit varet gjithashtu karakteristikat e tij teknike, si procesori, kapaciteti i memories, cache, numri dhe llojet e porteve etj. Nga ana e menaxhimit, AFA dallon nga sistemet hibride (disk) vet\u00ebm n\u00eb \u00e7\u00ebshtjet e realizimit t\u00eb mekanizmave t\u00eb pun\u00ebs me SSD, dhe madje n\u00ebse e p\u00ebrdorni SSD n\u00eb nj\u00eb sistem hibrid, kjo nuk do t\u00eb thot\u00eb se do t\u00eb arrini nj\u00eb nivel performance n\u00eb nivelin e sistemit AFA. N\u00eb shumic\u00ebn e rasteve, mekanizmat inline p\u00ebr ruajtje efikase n\u00eb sistemet hibride jan\u00eb t\u00eb \u00e7aktivizuar, dhe aktivizimi i tyre \u00e7on n\u00eb humbje t\u00eb performanc\u00ebs.<\/p>\n<h3>Sistemet e specializuara t\u00eb ruajtjes<\/h3>\n<p>\nP\u00ebrve\u00e7 sistemeve t\u00eb ruajtjes s\u00eb p\u00ebrgjithshme, t\u00eb orientuara kryesisht p\u00ebr p\u00ebrpunimin e t\u00eb dh\u00ebnave n\u00eb koh\u00eb reale, ekzistojn\u00eb sisteme t\u00eb specializuara t\u00eb ruajtjes me parime ky\u00e7e, t\u00eb ndryshme nga ato t\u00eb zakonshmet (vonesa e ul\u00ebt, shum\u00eb IOPS):<\/p>\n<p><b>Media. <\/b><\/p>\n<p>K\u00ebto sisteme jan\u00eb t\u00eb destinuara p\u00ebr ruajtjen dhe p\u00ebrpunimin e skedar\u00ebve mediatik\u00eb, t\u00eb cil\u00ebt karakterizohen nga nj\u00eb madh\u00ebsi e madhe. P\u00ebrkat\u00ebsisht, vonesa b\u00ebhet praktikisht e par\u00ebnd\u00ebsishme, nd\u00ebrsa fokusimi kalon n\u00eb aft\u00ebsin\u00eb p\u00ebr t\u00eb d\u00ebrguar dhe pranuar t\u00eb dh\u00ebna me nj\u00eb gjer\u00ebsi t\u00eb madhe t\u00eb kanalit n\u00eb shum\u00eb rrjedha paralele.<\/p>\n<p><b>Sistemet e ruajtjes s\u00eb deduplikimit p\u00ebr kopje rezerv\u00eb.<\/b><\/p>\n<p>Duke pasur parasysh se kopjet rezerv\u00eb zakonisht dallohen nga nj\u00ebra-tjetra (kopja mesatare rezerv\u00eb ndryshon nga ajo e djeshme n\u00eb 1-2%), ky klas i sistemeve paketon shum\u00eb efektivisht t\u00eb dh\u00ebnat q\u00eb ruhen n\u00eb nj\u00eb num\u00ebr t\u00eb vog\u00ebl fizik t\u00eb mbajt\u00ebsve. P\u00ebr shembull, n\u00eb disa raste, koeficient\u00ebt e kompresimit t\u00eb t\u00eb dh\u00ebnave mund t\u00eb arrijn\u00eb 200 ndaj 1.<\/p>\n<p><b>Sistemet e ruajtjes objektive.<\/b><\/p>\n<p>N\u00eb k\u00ebto SHT nuk ka volume me akses bllokues dhe ndarje skedar\u00ebsh si zakonisht, por m\u00eb shum\u00eb ngjajn\u00eb me nj\u00eb baz\u00eb t\u00eb madhe t\u00eb dh\u00ebnash. Aksesi n\u00eb nj\u00eb objekt t\u00eb ruajtur n\u00eb nj\u00eb sistem t\u00eb till\u00eb b\u00ebhet p\u00ebrmes nj\u00eb identifikatori unik, ose p\u00ebrmes metadatat (p.sh. t\u00eb gjitha objektet n\u00eb formatin JPEG, me dat\u00eb krijimi midis XX-XX-XXXX dhe YY-YY-YYYY).<\/p>\n<p><b>Sistemet e p\u00ebrputhshm\u00ebris\u00eb<\/b>. <\/p>\n<p>Nuk jan\u00eb aq t\u00eb zakonshme n\u00eb Rusi sot, por duhet t'i p\u00ebrmendim. Q\u00ebllimi i k\u00ebtyre SHT-ve \u00ebsht\u00eb ruajtja e garantuar e t\u00eb dh\u00ebnave p\u00ebr t\u00eb p\u00ebrmbushur politikat e siguris\u00eb ose k\u00ebrkesat e rregullator\u00ebve. N\u00eb disa sisteme (p.sh. EMC Centera) \u00ebsht\u00eb realizuar funksioni i ndalimit t\u00eb fshirjes s\u00eb t\u00eb dh\u00ebnave - sa her\u00eb q\u00eb \u00e7el\u00ebsi kthehet dhe sistemi kalon n\u00eb k\u00ebt\u00eb mod, as administrator\u00ebt, as askush tjet\u00ebr fizikisht nuk mund t\u00eb fshijn\u00eb t\u00eb dh\u00ebnat e regjistruara tashm\u00eb.<\/p>\n<h3>Teknologjit\u00eb e mark\u00ebs<\/h3>\n<p><\/p>\n<h4>Flash cache<\/h4>\n<p>\nFlash Cache \u00ebsht\u00eb termi i p\u00ebrgjithsh\u00ebm p\u00ebr t\u00eb gjitha teknologjit\u00eb e mark\u00ebs q\u00eb p\u00ebrdorin memorjen flash si nj\u00eb cache t\u00eb nivelit t\u00eb dyt\u00eb. Kur p\u00ebrdoret Flash Cache, SHT zakonisht llogaritet p\u00ebr t\u00eb p\u00ebrballuar ngarkes\u00ebn e vendosur nga disk\u00ebt magnetik\u00eb, nd\u00ebrsa ngarkesa pike e mb\u00ebshtet nga cache.<\/p>\n<p>N\u00eb k\u00ebt\u00eb rast \u00ebsht\u00eb e nevojshme t\u00eb kuptohet profili i ngarkes\u00ebs dhe shkalla e lokalizimit t\u00eb k\u00ebrkesave p\u00ebr blloqet e ruajtjes. Flash cache \u00ebsht\u00eb teknologji p\u00ebr ngarkesa me lokalizim t\u00eb lart\u00eb t\u00eb k\u00ebrkesave, dhe thuajse nuk aplikohet p\u00ebr volume t\u00eb ngarkuar nj\u00eblloj (si p\u00ebr shembull n\u00eb sistemet analitike). <\/p>\n<p>N\u00eb treg jan\u00eb p\u00ebr t\u00eb dy implementimet e Flash Cache:<\/p>\n<ul>\n<li>Read Only. N\u00eb k\u00ebt\u00eb rast, cache p\u00ebrdoret vet\u00ebm p\u00ebr t\u00eb dh\u00ebna n\u00eb lexim, nd\u00ebrsa shkrimi ndodh menj\u00ebher\u00eb n\u00eb disqe. Disa prodhues, si p.sh. NetApp, besojn\u00eb se shkrimi n\u00eb SHT-t\u00eb e tyre ndodh optimalisht dhe cache nuk ndihmon n\u00eb aspak.<\/li>\n<li>Read\/Write. Jo vet\u00ebm leximet por edhe shkrimet e cache-ohen, duke mund\u00ebsuar buferimin e fluksit dhe uljen e ndikimit t\u00eb RAID Penalty, dhe si pasoj\u00eb rrit performanc\u00ebn totale p\u00ebr SHT-t\u00eb me mekanizma shkrimi jo aq optimal.<\/li>\n<\/ul>\n<p><\/p>\n<h4>Tiering<\/h4>\n<p>\nRuajtja me shum\u00eb nivele (tiering) \u00ebsht\u00eb teknologjia q\u00eb bashkon n\u00eb nj\u00eb grup disqesh nivele me performanc\u00eb t\u00eb ndryshme, si p.sh. SSD dhe HDD. N\u00eb rastin e nj\u00eb shp\u00ebrndarjeje t\u00eb theksuar t\u00eb qasjes n\u00eb blloqet e t\u00eb dh\u00ebnave, sistemi do t\u00eb jet\u00eb n\u00eb gjendje t\u00eb balancoj\u00eb automatikisht blloqet e t\u00eb dh\u00ebnave, duke transferuar ato t\u00eb ngarkuara n\u00eb nivele me performanc\u00eb t\u00eb lart\u00eb, dhe ato t\u00eb ftohta, p\u00ebrkundrazi, n\u00eb nivele m\u00eb t\u00eb ngadalta.<\/p>\n<p>Sistemet hibride t\u00eb klas\u00ebs s\u00eb ul\u00ebt dhe mesme p\u00ebrdorin ruajtje n\u00eb nivele me l\u00ebvizjen e t\u00eb dh\u00ebnave midis niveleve sipas nj\u00eb orari. N\u00eb k\u00ebt\u00eb rast, madh\u00ebsia e bllokut t\u00eb ruajtjes n\u00eb nivele n\u00eb modelet m\u00eb t\u00eb mira \u00ebsht\u00eb 256 MB. K\u00ebto karakteristika nuk lejojn\u00eb q\u00eb teknologjia e ruajtjes n\u00eb nivele t\u00eb konsiderohet teknologji p\u00ebr t\u00eb rritur performanc\u00ebn, si\u00e7 gabimisht mendon shum\u00eb. Ruajtja n\u00eb nivele n\u00eb sistemet e klas\u00ebs s\u00eb ul\u00ebt dhe mesme \u00ebsht\u00eb nj\u00eb teknologji p\u00ebr optimizimin e kostos s\u00eb ruajtjes p\u00ebr sistemet me ngarkesa t\u00eb dukshme jo t\u00eb barabarta.<\/p>\n<h4>Snapshot<\/h4>\n<p>\nPavar se sa do t\u00eb flasim p\u00ebr besueshm\u00ebrin\u00eb e sistemit t\u00eb ruajtjes, ekzistojn\u00eb shum\u00eb mund\u00ebsi p\u00ebr t\u00eb humbur t\u00eb dh\u00ebna, t\u00eb pa lidhura me problemet harduerike. K\u00ebto mund t\u00eb jen\u00eb viruse, haker\u00eb ose \u00e7do fshirje\/mbetje t\u00eb paq\u00ebllimshme t\u00eb t\u00eb dh\u00ebnave. P\u00ebr k\u00ebt\u00eb arsye, kopjimi i t\u00eb dh\u00ebnave produktive \u00ebsht\u00eb nj\u00eb pjes\u00eb e pandashme e pun\u00ebs s\u00eb inxhinierit. <\/p>\n<p>Snapsoti \u00ebsht\u00eb nj\u00eb imazh i volumit n\u00eb nj\u00eb moment t\u00eb caktuar. Gjat\u00eb pun\u00ebs me shumic\u00ebn e sistemeve, si virtualizimi, Baza e t\u00eb Dh\u00ebnave, etj., na nevojitet t\u00eb krijojm\u00eb nj\u00eb imazh t\u00eb till\u00eb nga i cili do t\u00eb kopjojm\u00eb t\u00eb dh\u00ebnat n\u00eb nj\u00eb kopje rezerv\u00eb, nd\u00ebrkoh\u00eb q\u00eb sistemet tona do t\u00eb mund t\u00eb vazhdojn\u00eb t\u00eb punojn\u00eb normalisht me k\u00ebt\u00eb volum. Por duhet t\u00eb kujtojm\u00eb - jo t\u00eb gjitha snapsotet jan\u00eb t\u00eb nj\u00ebjta n\u00eb p\u00ebrdorim. Furnizues t\u00eb ndrysh\u00ebm kan\u00eb qasje t\u00eb ndryshme lidhur me krijimin e snapsoteve, t\u00eb lidhura me arkitektur\u00ebn e tyre.<\/p>\n<p><b>CoW (Copy-On-Write)<\/b>. Kur p\u00ebrpiqemi t\u00eb shkruajm\u00eb nj\u00eb bllok t\u00eb dh\u00ebnash, p\u00ebrmbajtja e tij origjinale kopjohet n\u00eb nj\u00eb zon\u00eb t\u00eb ve\u00e7ant\u00eb, pas s\u00eb cil\u00ebs shkrimi kalon normalisht. K\u00ebshtu parandalojm\u00eb d\u00ebmtimin e t\u00eb dh\u00ebnave brenda snapsotit. Natyrisht, t\u00eb gjitha k\u00ebto \"manipulime parazite\" me t\u00eb dh\u00ebnat shkaktojn\u00eb ngarkes\u00eb shtes\u00eb n\u00eb sistemin e ruajtjes dhe p\u00ebr k\u00ebt\u00eb arsye furnizuesit me implementime t\u00eb tilla nuk rekomandojn\u00eb p\u00ebrdorimin e m\u00eb shum\u00eb se dhjet\u00eb snapsoteve, dhe n\u00eb volumin me ngarkes\u00eb t\u00eb lart\u00eb, t\u00eb mos i p\u00ebrdorin fare.<\/p>\n<p><b>RoW (Redirect-on-Write)<\/b>. N\u00eb k\u00ebt\u00eb rast, volumi origjinal ngjitet natyrsh\u00ebm, dhe kur p\u00ebrpiqet t\u00eb shkruaj\u00eb nj\u00eb bllok t\u00eb dh\u00ebnash, sistemi i ruajtjes shkruan t\u00eb dh\u00ebnat n\u00eb nj\u00eb zon\u00eb t\u00eb ve\u00e7ant\u00eb n\u00eb hap\u00ebsir\u00ebn e lir\u00eb, duke ndryshuar lokacionin e k\u00ebtij blloku n\u00eb tabel\u00ebn e metadatas. Kjo lejon reduktimin e numrit t\u00eb operacioneve t\u00eb rip\u00ebrs\u00ebritjes, \u00e7ka n\u00eb p\u00ebrfundim e neutralizon r\u00ebnien e performanc\u00ebs dhe heq kufizimet mbi snapsotet dhe numrin e tyre.<\/p>\n<p>Snapsotet gjithashtu ndahen n\u00eb dy tipe n\u00eb lidhje me aplikacionet:<\/p>\n<p><b>Application consistent<\/b>. N\u00eb momentin e krijimit t\u00eb snapsotit, sistemi i ruajtjes aktivizon agjentin n\u00eb sistemin operativ t\u00eb p\u00ebrdoruesit, i cili detyron q\u00eb t\u00eb kesh burimet e diskut t\u00eb shkarkuara nga memorja n\u00eb disk dhe e detyron aplikacionin ta b\u00ebj\u00eb k\u00ebt\u00eb. N\u00eb k\u00ebt\u00eb rast, kur rikuperohet nga snapsoti, t\u00eb dh\u00ebnat do t\u00eb jen\u00eb t\u00eb q\u00ebndrueshme.<\/p>\n<p><b>Crash consistent<\/b>N\u00eb k\u00ebt\u00eb rast, asgj\u00eb e till\u00eb nuk ndodh dhe snapshot-i krijohet ashtu si\u00e7 \u00ebsht\u00eb. N\u00eb rast t\u00eb rikthimit nga nj\u00eb snapshot t\u00eb till\u00eb, pamja \u00ebsht\u00eb identike sikur t\u00eb ishte ndalur papritur energjia dhe \u00ebsht\u00eb e mundur nj\u00eb humbje e caktuar t\u00eb t\u00eb dh\u00ebnave, t\u00eb cilat ishin ngulur n\u00eb cache dhe nuk arrit\u00ebn kurr\u00eb n\u00eb disk. Snapshot-et e tilla jan\u00eb m\u00eb t\u00eb lehta n\u00eb zbatim dhe nuk shkaktojn\u00eb r\u00ebnie t\u00eb performanc\u00ebs n\u00eb aplikacione, por jan\u00eb m\u00eb pak t\u00eb besueshme. <\/p>\n<p>Pse nevojiten snapshot-et n\u00eb sistemet e ruajtjes s\u00eb t\u00eb dh\u00ebnave? <\/p>\n<ul>\n<li>Backup-i pa agjent direkt nga S\u00c7D<\/li>\n<li>Krijimi i mjediseve testuese mbi t\u00eb dh\u00ebna reale<\/li>\n<li>N\u00eb rastin e S\u00c7D-ve t\u00eb skedar\u00ebve, mund t\u00eb p\u00ebrdoret p\u00ebr t\u00eb krijuar mjedise VDI duke p\u00ebrdorur snapshot-et e S\u00c7D-s\u00eb n\u00eb vend t\u00eb hipervizorit<\/li>\n<li>Sigurimi i RPO-ve t\u00eb ul\u00ebta duke krijuar snapshot-e n\u00eb nj\u00eb program me nj\u00eb frekuenc\u00eb shum\u00eb m\u00eb t\u00eb lart\u00eb se frekuenca e backup-it<\/li>\n<\/ul>\n<p><\/p>\n<h4>Kloni<\/h4>\n<p>\nKlonimi i volumit funksionon sipas nj\u00eb principi analog me snapshot-et, por sh\u00ebrben jo thjesht p\u00ebr t\u00eb lexuar t\u00eb dh\u00ebnat, por p\u00ebr t\u00eb punuar plot\u00ebsisht me to. Ne kemi mund\u00ebsin\u00eb t\u00eb marrim nj\u00eb kopje t\u00eb sakt\u00eb t\u00eb volumit ton\u00eb, me t\u00eb gjitha t\u00eb dh\u00ebnat e tij, pa krijuar nj\u00eb kopje fizike, \u00e7ka do t\u00eb ndihmoj\u00eb n\u00eb ruajtjen e hap\u00ebsir\u00ebs. Zakonisht, klonimi i volumeve p\u00ebrdoret ose n\u00eb Test &amp; Dev ose n\u00ebse d\u00ebshironi t\u00eb verifikoni funksionimin e disa p\u00ebrdit\u00ebsimeve n\u00eb sistemin tuaj t\u00eb informacionit. Klonimi do t\u00eb lejoj\u00eb q\u00eb kjo t\u00eb b\u00ebhet maksimalisht shpejt dhe ekonomikisht n\u00eb aspektin e burimeve diskore, pasi do t\u00eb shkruhen vet\u00ebm blloqet e dh\u00ebnave t\u00eb ndryshuara.<\/p>\n<h4>Replikimi \/ regjistrimi<\/h4>\n<p>\nReplikimi \u00ebsht\u00eb nj\u00eb mekaniz\u00ebm p\u00ebr krijimin e nj\u00eb kopje t\u00eb t\u00eb dh\u00ebnave n\u00eb nj\u00eb S\u00c7D tjet\u00ebr fizike. Zakonisht ekziston nj\u00eb teknologji mark\u00eb p\u00ebr \u00e7do furnizues, e cila funksionon vet\u00ebm brenda linj\u00ebs s\u00eb tij t\u00eb produkteve. Por gjithashtu ka zgjidhje t\u00eb jashtme, p\u00ebrfshir\u00eb ato q\u00eb punojn\u00eb n\u00eb nivelin e hipervizorit, si p\u00ebr shembull VMware vSphere Replikimi.<\/p>\n<p>Funksionaliteti i teknologjive t\u00eb mark\u00ebs dhe leht\u00ebsia e p\u00ebrdorimit t\u00eb tyre zakonisht jan\u00eb shum\u00eb superiore ndaj atyre universale, por jan\u00eb jo t\u00eb aplikueshme kur, p\u00ebr shembull, nevojitet t\u00eb b\u00ebhet nj\u00eb replik\u00eb nga NetApp n\u00eb HP MSA.<\/p>\n<p>Replikimi ndahet n\u00eb dy n\u00ebnkat\u00ebsh:<\/p>\n<p><b>Sinkron<\/b>. N\u00eb rastin e replikimit sinkron, operacioni i shkruar transmetohet menj\u00ebher\u00eb n\u00eb sistemin e dyt\u00eb t\u00eb ruajtjes dhe nuk konfirmohet deri sa sistemi i larg\u00ebt t\u00eb konfirmoj\u00eb. Kjo rrit vones\u00ebn e aksesit, por na jep nj\u00eb kopje t\u00eb sakt\u00eb refleksive t\u00eb t\u00eb dh\u00ebnave. Kjo do t\u00eb thot\u00eb q\u00eb RPO = 0 n\u00eb rast t\u00eb humbjes s\u00eb sistemit kryesor t\u00eb ruajtjes. <\/p>\n<p><b>Asinkron<\/b>. Operacionet e shkruara kryhen vet\u00ebm n\u00eb sistemin kryesor t\u00eb ruajtjes dhe konfirmohen menj\u00ebher\u00eb, duke u grumbulluar n\u00eb nj\u00eb tuf\u00eb p\u00ebr transferim n\u00eb sistemin e larg\u00ebt t\u00eb ruajtjes. Ky lloj replikimi \u00ebsht\u00eb i aplikuesh\u00ebm p\u00ebr t\u00eb dh\u00ebna m\u00eb pak t\u00eb vlefshme, ose p\u00ebr kanale me kapacitet t\u00eb ul\u00ebt ose me vonesa t\u00eb larta (karakteristike p\u00ebr distanca mbi 100 km). Prandaj, RPO = frekuenca e d\u00ebrgimit t\u00eb tufave.<\/p>\n<p>Shpesh, s\u00eb bashku me replikimin ekziston nj\u00eb mekaniz\u00ebm <b>t\u00eb regjistrimit<\/b> t\u00eb operacioneve diskore. N\u00eb k\u00ebt\u00eb rast, rezervuar nj\u00eb zon\u00eb t\u00eb ve\u00e7ant\u00eb p\u00ebr regjistrim dhe ruhen operacionet e shkruara n\u00eb nj\u00eb thell\u00ebsi t\u00eb caktuar n\u00eb koh\u00eb, ose t\u00eb kufizuara n\u00eb volumin e regjistrit. P\u00ebr disa teknologji mark\u00eb, si\u00e7 \u00ebsht\u00eb EMC RecoverPoint, ekziston integrimi me softuerin sistemor, i cili lejon lidhjen e sh\u00ebnimeve t\u00eb caktuara me regjistrin. Fal\u00eb k\u00ebsaj, \u00ebsht\u00eb e mundur q\u00eb t\u00eb rikthehet gjendja e volumit (ose t\u00eb krijohet nj\u00eb kopje) jo thjesht n\u00eb 23 Prill n\u00eb or\u00ebn 11:59:13, por n\u00eb momentin q\u00eb i paraprinte \u201cDROP ALL TABLES; COMMIT\u201d.<\/p>\n<h4>Metro cluster<\/h4>\n<p>\nMetro cluster \u00ebsht\u00eb nj\u00eb teknologji q\u00eb lejon krijimin e nj\u00eb replikimi sinkron dykah\u00ebsor midis dy sistemeve t\u00eb ruajtjes n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb nga jasht duket si nj\u00eb sistem i vet\u00ebm i ruajtjes. P\u00ebrdoret p\u00ebr t\u00eb krijuar klaster\u00eb me deg\u00eb gjeografikisht t\u00eb shp\u00ebrndara n\u00eb distanca metro (m\u00eb pak se 100 km).<\/p>\n<p>Me nj\u00eb shembull t\u00eb p\u00ebrdorimit n\u00eb ambientin e virtualizimit, metroklusteri lejon krijimin e nj\u00eb datastori me makinat virtuale, t\u00eb aksesueshme p\u00ebr shkrim menj\u00ebher\u00eb nga dy qendra t\u00eb t\u00eb dh\u00ebnave. N\u00eb k\u00ebt\u00eb rast, krijohet nj\u00eb klaster n\u00eb nivelin e hipervizor\u00ebve, i p\u00ebrb\u00ebr\u00eb nga hostname n\u00eb qendra t\u00eb ndryshme fizike t\u00eb t\u00eb dh\u00ebnave, t\u00eb lidhura me k\u00ebt\u00eb datastor. Kjo lejon<\/p>\n<ul>\n<li>Automatizimi i plot\u00eb i procesit t\u00eb rikuperimit pas vdekjes s\u00eb nj\u00eb nga qendrav\u00eb t\u00eb t\u00eb dh\u00ebnave. Pa ndihma t\u00eb tjera, t\u00eb gjitha VM-t\u00eb q\u00eb funksiononin n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave t\u00eb vdekur do t\u00eb rilidhen automatikisht n\u00eb at\u00eb q\u00eb ka mbetur. RTO = koha e pritjes s\u00eb klasterit t\u00eb aksesit t\u00eb lart\u00eb (15 sekonda p\u00ebr VMware) + koha e ngarkimit t\u00eb sistemit operativ dhe fillimit t\u00eb sh\u00ebrbimeve.<\/li>\n<li>Shmangia e katastrofave. N\u00ebse jan\u00eb t\u00eb planifikuara punime n\u00eb energjin\u00eb elektrike n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave 1, at\u00ebher\u00eb ne paraprakisht, para fillimit t\u00eb punimeve, kemi mund\u00ebsin\u00eb t\u00eb migrojm\u00eb t\u00eb gjith\u00eb ngarkes\u00ebn e r\u00ebnd\u00ebsishme n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave 2 n\u00eb vazhdim.<\/li>\n<\/ul>\n<p><\/p>\n<h4>Virtualizimi<\/h4>\n<p>\nVirtualizimi i SXYD-s\u00eb \u00ebsht\u00eb p\u00ebrdorimi teknik i volumeneve nga SXYD t\u00eb tjera si disqe. Virtualizatori i SXYD-s\u00eb mund t\u00eb kaloj\u00eb thjesht volumin e huaj tek konsumatori si t\u00eb vetin, duke e pasqyruar n\u00eb nj\u00eb SXYD tjet\u00ebr, ose madje t\u00eb krijoj\u00eb RAID nga volumin e jasht\u00ebm.<br \/>\nP\u00ebrfaq\u00ebsuesit klasik\u00eb n\u00eb klas\u00ebn e virtualizimit t\u00eb SXYD-s\u00eb jan\u00eb EMC VPLEX dhe IBM SVC. Natyrisht, SXYD me funksion virtualizimi \u2014 NetApp, Hitachi, IBM \/ Lenovo Storwize.<\/p>\n<p>Pse mund t\u00eb jet\u00eb e nevojshme?<\/p>\n<ul>\n<li>Rezervimi n\u00eb nivelin e SXYD-s\u00eb. Krijohet nj\u00eb pasqyr\u00eb midis volumeneve, ku nj\u00eb gjysm\u00eb mund t\u00eb jet\u00eb n\u00eb HP 3Par, nd\u00ebrsa tjetra n\u00eb NetApp. Dhe virtualizatori nga EMC.<\/li>\n<li>Migrimi i t\u00eb dh\u00ebnave me minimun downtime midis SXYD-ve t\u00eb prodhuesve t\u00eb ndrysh\u00ebm. Supozoni q\u00eb t\u00eb dh\u00ebnat duhet t\u00eb migrohen nga nj\u00eb 3Par i vjet\u00ebr, i cili do t\u00eb hidhet, n\u00eb nj\u00eb t\u00eb re Dell. N\u00eb k\u00ebt\u00eb rast, konsumator\u00ebt fiksohen nga 3Par, volumet kalojn\u00eb n\u00ebn VPLEX dhe prezantohen s\u00ebrish tek konsumator\u00ebt. Duke qen\u00eb se asnj\u00eb bit n\u00eb volum nuk \u00ebsht\u00eb ndryshuar, puna vazhdon. N\u00eb sfond, fillon procesi i pasqyrosjes s\u00eb volumit n\u00eb Dell-in e ri, dhe pas p\u00ebrfundimit pasqyra \u00e7ahen dhe 3Par fiket. <\/li>\n<li>Organizimi i metrokaster\u00ebve.<\/li>\n<\/ul>\n<p><\/p>\n<h4>Kompresimi \/ deduplicimi<\/h4>\n<p>\nKompresimi dhe deduplicimi jan\u00eb teknologjit\u00eb q\u00eb ju lejojn\u00eb t\u00eb kurseni hap\u00ebsir\u00eb disk n\u00eb SXYD-n\u00eb tuaj. Duhet p\u00ebrmendur aq shpejt se jo t\u00eb dh\u00ebna t\u00eb gjitha jan\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr kompresim dhe\/ose deduplicim n\u00eb princip, megjithat\u00eb disa lloje t\u00eb dh\u00ebnash p\u00ebrpunohen dhe deduplikohet m\u00eb mir\u00eb, nd\u00ebrsa t\u00eb tjera \u2014 p\u00ebrkundrazi. <\/p>\n<p>Kompresimi dhe deduplicimi jan\u00eb dy lloje:<\/p>\n<p><b>Inline<\/b> \u2014 kompresimi dhe deduplikohet e blloqeve t\u00eb dh\u00ebnash ndodh para se t\u00eb shkruhen k\u00ebto t\u00eb dh\u00ebna n\u00eb disk. K\u00ebshtu, sistemi llogarit vet\u00ebm hash-in e bllokut dhe e krahasohet me tabel\u00ebn e blloqeve q\u00eb tashm\u00eb ekzistojn\u00eb. S\u00eb pari, kjo kryhet m\u00eb shpejt sesa thjesht shkruani n\u00eb disk, s\u00eb dyti, ne nuk shpenzojm\u00eb hap\u00ebsir\u00eb t\u00eb tep\u00ebrt n\u00eb disk.<\/p>\n<p><b>Post<\/b> \u2014 kur k\u00ebto operacione kryhen tashm\u00eb mbi t\u00eb dh\u00ebnat e shkruara, t\u00eb cilat ndodhen n\u00eb disqe. P\u00ebrkat\u00ebsisht, t\u00eb dh\u00ebnat fillimisht shkruhen n\u00eb disk, dhe vet\u00ebm m\u00eb pas, llogaritet hash-i dhe ndodhi heqja e bllok\u00ebve t\u00eb tep\u00ebrt dhe \u00e7lirimi i burimeve t\u00eb diskut.<\/p>\n<p>Duhet th\u00ebn\u00eb se shumica e ofruesve p\u00ebrdorin t\u00eb dy llojet, \u00e7ka lejon optimizimin e k\u00ebtyre proceseve dhe p\u00ebr rrjedhoj\u00eb rritjen e efikasitetit t\u00eb tyre. Shumica e ofruesve t\u00eb ruajtjes s\u00eb dh\u00ebnash kan\u00eb n\u00eb dispozicion mjete q\u00eb lejojn\u00eb analizimin e grupeve tuaja t\u00eb dh\u00ebnash. K\u00ebto mjete, punojn\u00eb sipas logjik\u00ebs q\u00eb \u00ebsht\u00eb zbatuar edhe n\u00eb ruajtjen e dh\u00ebnave, ndaj niveli i vler\u00ebsimit t\u00eb efikasitetit do t\u00eb p\u00ebrputhet. Gjithashtu, nuk duhet harruar se shum\u00eb ofrues kan\u00eb programe garancie efikasiteti, q\u00eb premtojn\u00eb se niveli nuk do t\u00eb jet\u00eb m\u00eb i ul\u00ebt se ai i deklaruar p\u00ebr nj\u00eb (apo t\u00eb gjitha) llojet e dh\u00ebnave. Dhe nuk duhet injoruar ky program, pasi duke llogaritur sistemin sipas nevojave tuaja, duke marr\u00eb parasysh koeficientin e efikasitetit t\u00eb sistemit t\u00eb caktuar, mund t\u00eb kurseni n\u00eb volum. Gjithashtu duhet marr\u00eb parasysh se k\u00ebto plane jan\u00eb t\u00eb dizajnuara p\u00ebr sistemet AFA, por duke bler\u00eb nj\u00eb volum m\u00eb t\u00eb vog\u00ebl SSD sesa HDD n\u00eb sistemet klasike, kjo do t\u00eb mund\u00ebsoj\u00eb uljen e kostos, dhe n\u00ebse jo t\u00eb arrij\u00eb koston e sistemit disk, at\u00ebher\u00eb shum\u00eb af\u00ebr saj.<\/p>\n<h3>Modeli<\/h3>\n<p>\nDhe k\u00ebtu arrijm\u00eb te pyetja e sakt\u00eb. <\/p>\n<p>\u201cM\u00eb ofrohen dy opsione p\u00ebr ruajtjen e dh\u00ebnave \u2014 ABC SuperStorage S600 dhe XYZ HyperOcean 666v4, \u00e7far\u00eb do t\u00eb m\u00eb k\u00ebshillonit?\u201d<\/p>\n<p>Shnd\u00ebrrohet n\u00eb \u201cM\u00eb ofrohen dy opsione p\u00ebr ruajtjen e dh\u00ebnave \u2014 ABC SuperStorage S600 dhe XYZ HyperOcean 666v4, \u00e7far\u00eb do t\u00eb m\u00eb k\u00ebshillonit?<\/p>\n<p>Ngarkesa e targetuar jan\u00eb makinat virtuale t\u00eb p\u00ebrziera VMware me ciklet prodhim \/ testim \/ zhvillim. Testi = prodhimi. 150 TB p\u00ebr \u00e7do nj\u00ebsis\u00eb me performanc\u00eb maksimale 80,000 IOPS me bllok 8kb 50% qasje t\u00eb rast\u00ebsishme 80\/20 lexim-shkruar. 300 TB p\u00ebr zhvillim, 50,000 IOPS \u00ebsht\u00eb e mjaftueshme, 80 aksese rast\u00ebsore, 80 shkruar.<\/p>\n<p>Prodhimi supozohet n\u00eb metrokluster RPO = 15 minuta RTO = 1 or\u00eb, zhvillimi n\u00eb replikim asinkron RPO = 3 or\u00eb, testi n\u00eb nj\u00eb lokacion.<\/p>\n<p>Do t\u00eb ket\u00eb 50TB t\u00eb DB-s\u00eb, do t\u00eb ishte mir\u00eb p\u00ebr ta t\u00eb kishte regjistrim.<\/p>\n<p>Kemi server\u00eb Dell kudo, magazinat e vjetra Hitachi, q\u00eb po e kan\u00eb t\u00eb v\u00ebshtir\u00eb, planifikojm\u00eb nj\u00eb rritje prej 50% t\u00eb ngarkes\u00ebs n\u00eb volum dhe performanc\u00eb.<\/p>\n<p>Si\u00e7 thon\u00eb, n\u00eb nj\u00eb pyetje t\u00eb formuluar mir\u00eb \u00ebsht\u00eb 80% e p\u00ebrgjigjes.<\/p>\n<h2>Informacione shtes\u00eb<\/h2>\n<p>\n\u00c7far\u00eb duhet t\u00eb shqyrtohet m\u00eb tej sipas autor\u00ebve<\/p>\n<h3>Libra<\/h3>\n<p><\/p>\n<ul>\n<li>Oliefer dhe Olifer \u201cRrjetet kompjuterike\u201d. Libri do t'ju ndihmoj\u00eb t\u00eb sistematizoni dhe ndoshta t\u00eb kuptoni m\u00eb mir\u00eb se si funksionon mjedisi i transmetimit t\u00eb t\u00eb dh\u00ebnave p\u00ebr sistemet IP \/ Ethernet t\u00eb ruajtjes.<\/li>\n<li>\u201cEMC Informacioni p\u00ebr Ruajtjen dhe Menaxhimin\u201d. Nj\u00eb lib\u00ebr i shk\u00eblqyer mbi bazat e magazinimit, pse, si dhe p\u00ebrse.<\/li>\n<\/ul>\n<p><\/p>\n<h4>Forumet dhe bisedat<\/h4>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/t.me\/storagediscussions\">Diskutimet mbi Ruajtjen<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/t.me\/nutanix_russia\">Nutanix \/ Klubi i Diskutimeve IT Ruse <\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/t.me\/vmugru\">Grupi i P\u00ebrdoruesve t\u00eb VMware n\u00eb Rusi <\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/t.me\/RussianBackupUserGroup\">Grupi i P\u00ebrdoruesve t\u00eb Kthimit n\u00eb Rusi<\/a><\/noindex> <\/li>\n<\/ul>\n<p><\/p>\n<h3>Rekomandime t\u00eb p\u00ebrgjithshme<\/h3>\n<p><\/p>\n<h4>\u00c7mimet<\/h4>\n<p>\nTani, sa i p\u00ebrket \u00e7mimeve - n\u00eb p\u00ebrgjith\u00ebsi \u00e7mimet e magazinave, n\u00ebse i hasim, zakonisht jan\u00eb \u00e7mimi list\u00eb, nga i cili \u00e7do klient merr zbritje individuale. Shuma e zbritjes formohet nga shum\u00eb parametra, k\u00ebshtu q\u00eb t\u00eb parashikosh se \u00e7far\u00eb \u00e7mimi p\u00ebrfundimtar do t\u00eb marr\u00eb pik\u00ebrisht kompania juaj, pa pyetje p\u00ebr distributorin \u00ebsht\u00eb thjesht e pamundur. Por koh\u00ebt e fundit, modelet e ulta kan\u00eb filluar t\u00eb shfaqen n\u00eb dyqane kompjuterike normale, si, p\u00ebr shembull, <noindex><a rel=\"nofollow\" href=\"http:\/\/nix.ru\">nix.ru<\/a><\/noindex> ose <noindex><a rel=\"nofollow\" href=\"http:\/\/xcom-shop.ru\">xcom-shop.ru<\/a><\/noindex>. N\u00eb to mund t\u00eb blini menj\u00ebher\u00eb sistemin q\u00eb ju intereson me nj\u00eb \u00e7mim t\u00eb fixuar, si \u00e7do komponent kompjuterik.<\/p>\n<p>Por dua t\u00eb theksoj menj\u00ebher\u00eb se krahasimi i drejtp\u00ebrdrejt\u00eb sipas TB\/$ nuk \u00ebsht\u00eb i sakt\u00eb. N\u00ebse qasemi nga kjo pik\u00ebpamje, zgjidhja m\u00eb e lir\u00eb do t\u00eb ishte nj\u00eb JBOD i thjesht\u00eb + serveri, q\u00eb nuk do t\u00eb ofronte as fleksibilitetin, as besueshm\u00ebrin\u00eb q\u00eb ofron nj\u00eb magazin\u00eb e plot\u00eb me dy kontroler\u00eb. Kjo nuk do t\u00eb thot\u00eb se JBOD \u00ebsht\u00eb di\u00e7ka e keqe, thjesht duhet, p\u00ebrs\u00ebri, t\u00eb kuptoni shum\u00eb qart\u00eb se si dhe p\u00ebr cilat q\u00ebllime do ta p\u00ebrdorni k\u00ebt\u00eb zgjidhje. Shpesh d\u00ebgjohet se n\u00eb JBOD nuk ka asgj\u00eb q\u00eb mund t\u00eb d\u00ebshtoj\u00eb, pasi ka vet\u00ebm nj\u00eb blekplejn. Sidoqoft\u00eb, edhe blekplejn\u00ebt ndonj\u00ebher\u00eb d\u00ebshtojn\u00eb. \u00c7do gj\u00eb d\u00ebmtohet her\u00ebt a von\u00eb.<\/p>\n<h4>P\u00ebrve\u00e7 k\u00ebsaj<\/h4>\n<p>\nKrahasimi i sistemeve midis tyre duhet t\u00eb b\u00ebhet jo vet\u00ebm sipas \u00e7mimit, ose jo vet\u00ebm sipas performanc\u00ebs, por sipas nj\u00eb kumpule t\u00eb gjitha treguesve.<\/p>\n<p>Bleni HDD vet\u00ebm n\u00ebse jeni t\u00eb sigurt se ju nevojiten HDD. P\u00ebr ngarkesa t\u00eb ulta dhe lloje t\u00eb dh\u00ebnash t\u00eb pa kompresuara, ndryshe, duhet t\u00eb shikoni programet e garancis\u00eb s\u00eb efikasitetit t\u00eb ruajtjes n\u00eb SSD, t\u00eb cilat tani i ka shumica e ofruesve (dhe ato v\u00ebrtet funksionojn\u00eb, madje edhe n\u00eb Rusi), por k\u00ebtu gjith\u00e7ka varet nga aplikacionet dhe t\u00eb dh\u00ebnat q\u00eb do t\u00eb vendosen n\u00eb k\u00ebt\u00eb SAN.<\/p>\n<p>Mos ndiqni koston e ul\u00ebt. Ndonj\u00ebher\u00eb n\u00ebn k\u00ebt\u00eb fshihet shum\u00eb problematika, nj\u00eb nga t\u00eb cilat Evgeniy Elizarov e p\u00ebrshkroi n\u00eb artikujt e tij rreth <noindex><a rel=\"nofollow\" href=\"http:\/\/blog.korphome.ru\/tag\/infortrend\/\">Infortrend<\/a><\/noindex>. Dhe se, n\u00eb fund t\u00eb fundit, kjo kosto e ul\u00ebt mund t'ju dal\u00eb juve kosto. Mos harroni \u2014 \"i kurti paguan dy her\u00eb\".<br \/>\n<br \/>Burimi: habr.com<\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041f\u0440\u0438\u0448\u043b\u0430 \u043f\u043e\u0440\u0430 \u043f\u043e\u043a\u0443\u043f\u0430\u0442\u044c \u0421\u0425\u0414. \u041a\u0430\u043a\u0443\u044e \u0432\u0437\u044f\u0442\u044c, \u043a\u043e\u0433\u043e \u0441\u043b\u0443\u0448\u0430\u0442\u044c? \u0412\u0435\u043d\u0434\u043e\u0440 \u0410 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043f\u0440\u043e \u0432\u0435\u043d\u0434\u043e\u0440\u0430 B, \u0430 \u0435\u0449\u0435 \u0435\u0441\u0442\u044c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0442\u043e\u0440 C, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u043d\u043e\u0435 \u0438 \u0441\u043e\u0432\u0435\u0442\u0443\u0435\u0442 \u0432\u0435\u043d\u0434\u043e\u0440\u0430 D. \u0412 \u0442\u0430\u043a\u043e\u0439 \u0441\u0438\u0442\u0443\u0430\u0446\u0438\u0438 \u0438 \u0443 \u043e\u043f\u044b\u0442\u043d\u043e\u0433\u043e \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u043e\u0440\u0430 \u043f\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0433\u043e\u043b\u043e\u0432\u0430 \u043f\u043e\u0439\u0434\u0435\u0442 \u043a\u0440\u0443\u0433\u043e\u043c, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0441\u043e \u0432\u0441\u0435\u043c\u0438 \u043d\u043e\u0432\u044b\u043c\u0438 \u0432\u0435\u043d\u0434\u043e\u0440\u0430\u043c\u0438 \u0438 \u043c\u043e\u0434\u043d\u044b\u043c\u0438 \u0441\u0435\u0433\u043e\u0434\u043d\u044f SDS \u0438 \u0433\u0438\u043f\u0435\u0440\u043a\u043e\u043d\u0432\u0435\u0440\u0433\u0435\u043d\u0446\u0438\u0435\u0439. \u0418\u0442\u0430\u043a, \u043a\u0430\u043a \u0436\u0435 \u0432\u043e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26807,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35801","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041f\u0440\u0438\u0448\u043b\u0430 \u043f\u043e\u0440\u0430 \u043f\u043e\u043a\u0443\u043f\u0430\u0442\u044c \u0421\u0425\u0414. \u041a\u0430\u043a\u0443\u044e \u0432\u0437\u044f\u0442\u044c, \u043a\u043e\u0433\u043e \u0441\u043b\u0443\u0448\u0430\u0442\u044c? \u0412\u0435\u043d\u0434\u043e\u0440 \u0410 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043f\u0440\u043e \u0432\u0435\u043d\u0434\u043e\u0440\u0430 B, \u0430 \u0435\u0449\u0435 \u0435\u0441\u0442\u044c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0442\u043e\u0440 C, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u043d\u043e\u0435 \u0438 \u0441\u043e\u0432\u0435\u0442\u0443\u0435\u0442 \u0432\u0435\u043d\u0434\u043e\u0440\u0430 D.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vybrat-shd-ne-vystreliv-sebe-v-nogu\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041a\u0430\u043a \u0432\u044b\u0431\u0440\u0430\u0442\u044c \u0421\u0425\u0414, \u043d\u0435 \u0432\u044b\u0441\u0442\u0440\u0435\u043b\u0438\u0432 \u0441\u0435\u0431\u0435 \u0432 \u043d\u043e\u0433\u0443 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041f\u0440\u0438\u0448\u043b\u0430 \u043f\u043e\u0440\u0430 \u043f\u043e\u043a\u0443\u043f\u0430\u0442\u044c \u0421\u0425\u0414. \u041a\u0430\u043a\u0443\u044e \u0432\u0437\u044f\u0442\u044c, \u043a\u043e\u0433\u043e \u0441\u043b\u0443\u0448\u0430\u0442\u044c? \u0412\u0435\u043d\u0434\u043e\u0440 \u0410 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043f\u0440\u043e \u0432\u0435\u043d\u0434\u043e\u0440\u0430 B, \u0430 \u0435\u0449\u0435 \u0435\u0441\u0442\u044c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0442\u043e\u0440 C, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u043d\u043e\u0435 \u0438 \u0441\u043e\u0432\u0435\u0442\u0443\u0435\u0442 \u0432\u0435\u043d\u0434\u043e\u0440\u0430 D.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vybrat-shd-ne-vystreliv-sebe-v-nogu\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:06:24+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:06:24+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Si t\u00eb zgjidhni SAN, pa ia hedhur vetes n\u00eb k\u00ebmb\u00eb | ProHoster","description":"Hyrje Ka ardhur koha t\u00eb blini SAN. Cilin t\u00eb zgjidhni, k\u00eb d\u00ebgjoni? Ofruesi A flet p\u00ebr ofruesin B, dhe p\u00ebr m\u00eb tep\u00ebr, ka integruesin C, q\u00eb thot\u00eb t\u00eb kund\u00ebrt\u00ebn dhe sugjeron ofruesin D.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vybrat-shd-ne-vystreliv-sebe-v-nogu","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041a\u0430\u043a \u0432\u044b\u0431\u0440\u0430\u0442\u044c \u0421\u0425\u0414, \u043d\u0435 \u0432\u044b\u0441\u0442\u0440\u0435\u043b\u0438\u0432 \u0441\u0435\u0431\u0435 \u0432 \u043d\u043e\u0433\u0443 | ProHoster","og:description":"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041f\u0440\u0438\u0448\u043b\u0430 \u043f\u043e\u0440\u0430 \u043f\u043e\u043a\u0443\u043f\u0430\u0442\u044c \u0421\u0425\u0414. \u041a\u0430\u043a\u0443\u044e \u0432\u0437\u044f\u0442\u044c, \u043a\u043e\u0433\u043e \u0441\u043b\u0443\u0448\u0430\u0442\u044c? \u0412\u0435\u043d\u0434\u043e\u0440 \u0410 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043f\u0440\u043e \u0432\u0435\u043d\u0434\u043e\u0440\u0430 B, \u0430 \u0435\u0449\u0435 \u0435\u0441\u0442\u044c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0442\u043e\u0440 C, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u043d\u043e\u0435 \u0438 \u0441\u043e\u0432\u0435\u0442\u0443\u0435\u0442 \u0432\u0435\u043d\u0434\u043e\u0440\u0430 D.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vybrat-shd-ne-vystreliv-sebe-v-nogu","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:06:24+00:00","article:modified_time":"2019-10-31T19:06:24+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35801","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-22 00:48:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:55:27","updated":"2026-01-22 00:48:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35801","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=35801"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35801\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/26807"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=35801"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=35801"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=35801"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}