{"id":38746,"date":"2019-10-31T22:25:40","date_gmt":"2019-10-31T19:25:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/rezervnoe-kopirovanie-chast-6-sravnenie-sredstv-rezervnogo-kopirovaniya\/"},"modified":"2019-10-31T22:25:40","modified_gmt":"2019-10-31T19:25:40","slug":"rezervnoe-kopirovanie-chast-6-sravnenie-sredstv-rezervnogo-kopirovaniya","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/rezervnoe-kopirovanie-chast-6-sravnenie-sredstv-rezervnogo-kopirovaniya","title":{"rendered":"Kopjimi i rezervave, pjesa 6: Krahasimi i mjeteve p\u00ebr kopje rezerv\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Kopjimi
\nN\u00eb k\u00ebt\u00eb artikull do t\u00eb b\u00ebhet nj\u00eb krahasim i mjeteve t\u00eb kopjimit, por s\u00eb pari \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptohet se si ato p\u00ebrballen shpejt dhe mir\u00eb me rikuperimin e t\u00eb dh\u00ebnave nga kopjet rezerv\u00eb.
\nP\u00ebr thjesht\u00ebsi krahasimi do t\u00eb shqyrtohet rikuperimi nga nj\u00eb kopje rezerv\u00eb e plot\u00eb, sidomos sepse ky mod i pun\u00ebs mb\u00ebshtetet nga t\u00eb gjith\u00eb kandidat\u00ebt. P\u00ebr thjesht\u00ebsi, numrat jan\u00eb marr\u00eb t\u00eb mesatarizuar (mesatarja aritmetike nga disa ekzekutime). Rezultatet do t\u00eb p\u00ebrmblidhen n\u00eb nj\u00eb tabel\u00eb, n\u00eb t\u00eb cil\u00ebn do t\u00eb ket\u00eb gjithashtu informacion mbi mund\u00ebsit\u00eb: prania e nj\u00eb nd\u00ebrfaqeje n\u00eb web, thjesht\u00ebsia n\u00eb konfigurim dhe p\u00ebrdorim, aft\u00ebsia p\u00ebr automatizim, si dhe mund\u00ebsi t\u00eb tjera shtes\u00eb (p\u00ebr shembull, kontrolli i integritetit t\u00eb t\u00eb dh\u00ebnave) etj. Grafik\u00ebt do t\u00eb tregojn\u00eb ngarkes\u00ebn e serverit, ku t\u00eb dh\u00ebnat do t\u00eb aplikohen (jo serveri p\u00ebr ruajtjen e kopjeve rezerv\u00eb).
\n<\/a><\/noindex><\/p>\n

Rikuperimi i t\u00eb dh\u00ebnave<\/h2>\n

\nSi pik\u00eb referimi do t\u00eb p\u00ebrdoren rsync dhe tar, pasi pik\u00ebrisht mbi to zakonisht mb\u00ebshteten<\/a><\/noindex> skritpat m\u00eb t\u00eb thjeshta p\u00ebr marrjen e kopjeve rezerv\u00eb.<\/p>\n

Rsync<\/i> e p\u00ebrfundoi setin e t\u00eb dh\u00ebnave testuese p\u00ebr 4 minuta dhe 28 sekonda, duke treguar <\/p>\n

k\u00ebt\u00eb ngarkes\u00eb<\/b>\"Kopjimi
\n
\nProcedura e rikuperimit u p\u00ebrball me kufizimin e sistemit t\u00eb disave t\u00eb diskut t\u00eb serverit t\u00eb ruajtjes s\u00eb kopjeve rezerv\u00eb (grafik\u00ebt zigzag). Gjithashtu, ngarkesa e nj\u00eb b\u00ebrthame \u00ebsht\u00eb e dukshme pa probleme t\u00eb ve\u00e7anta (iowait i ul\u00ebt dhe softirq \u2014 pa probleme me diskun dhe rrjetin p\u00ebrkat\u00ebs). Duke qen\u00eb se dy programet e tjera, dmth. rdiff-backup dhe rsnapshot, jan\u00eb t\u00eb bazuara n\u00eb rsync, si dhe ofrojn\u00eb rsync si metod\u00eb rikuperimi, ato do t\u00eb ken\u00eb nj\u00eb profil ngarkese dhe koh\u00eb rikuperimi t\u00eb ngjashme.<\/p>\n

Tar<\/i> u p\u00ebrfundua pak m\u00eb shpejt, p\u00ebr <\/p>\n

2 minuta dhe 43 sekonda:<\/b>\"Kopjimi
\n
\nNgarkesa e plot\u00eb e sistemit ishte m\u00eb e lart\u00eb n\u00eb mesatarisht 20% p\u00ebr shkak t\u00eb rritjes s\u00eb softirq \u2014 rritja e kostove t\u00eb operimit t\u00eb sistemit t\u00eb rrjetit.<\/p>\n

N\u00ebse arkivi do t\u00eb kompresohej p\u00ebr m\u00eb tej, koha e rikuperimit rritet n\u00eb 3 minuta 19 sekonda me
\nk\u00ebt\u00eb ngarkes\u00eb n\u00eb serverin kryesor (\u00e7montimi n\u00eb an\u00ebn e serverit kryesor):<\/b>\"Kopjimi
\n
\nProcesi i shp\u00ebrndarjes merr t\u00eb dy b\u00ebrthamat e procesorit, pasi punon me dy procese. N\u00eb p\u00ebrgjith\u00ebsi \u2014 rezultat i pritur. Nj\u00eb rezultat i krahasuesh\u00ebm (3 minuta dhe 20 sekonda) u arrit gjithashtu kur u fillua gzip n\u00eb an\u00ebn e serverit me kopjet rezerv\u00eb, ngarkesa e p\u00ebrdorimit n\u00eb serverin kryesor ishte mjaft e ngjashme me fillimin e tar pa kompresorin gzip (shih grafikun e m\u00ebparsh\u00ebm).<\/p>\n

N\u00eb rdiff-backup<\/i> mund t\u00eb sinkronizoni kopjen rezerv\u00eb m\u00eb t\u00eb fundit me rsync t\u00eb zakonsh\u00ebm (rezultatet do t\u00eb jen\u00eb t\u00eb ngjashme), por kopjet m\u00eb t\u00eb vjetra duhet ende t\u00eb rikuperohen me programin rdiff-backup, i cili p\u00ebrfundoi rikuperimin p\u00ebr 17 minuta dhe 17 sekonda, duke treguar <\/p>\n

ngarkes\u00ebn e till\u00eb:<\/b>\"Kopjimi
\n
\nNdoshta k\u00ebshtu ishte menduar, t\u00eb pakt\u00ebn p\u00ebr t\u00eb kufizuar shpejt\u00ebsin\u00eb autor\u00ebt sugjerojn\u00eb nj\u00eb zgjidhje t\u00eb till\u00eb<\/a><\/noindex>. Procesi i rikuperimit t\u00eb kopjeve rezerv\u00eb merr pak m\u00eb pak se gjysma e nj\u00eb b\u00ebrthame, me performanc\u00eb proporcionalisht t\u00eb krahasueshme (dmth. 2-5 her\u00eb m\u00eb ngadal\u00eb) p\u00ebr disk dhe rrjet me rsync.<\/p>\n

Rsnapshot<\/i> p\u00ebr rikuperim ofron p\u00ebrdorimin e rsync t\u00eb zakonsh\u00ebm, k\u00ebshtu q\u00eb rezultatet e tij do t\u00eb jen\u00eb t\u00eb ngjashme. N\u00eb p\u00ebrgjith\u00ebsi, k\u00ebshtu ndodhi.<\/p>\n

Burp<\/i> p\u00ebr detyr\u00ebn e rikuperimit t\u00eb kopjes rezerv\u00eb u angazhua p\u00ebr 7 minuta dhe 2 sekonda me
\nngarkes\u00ebn e till\u00eb:<\/b>\"Kopjimi
\n
\nPunoi mjaft shpejt, dhe, t\u00eb pakt\u00ebn, shum\u00eb m\u00eb komode se rsync i past\u00ebr: nuk \u00ebsht\u00eb e nevojshme t\u00eb mbash mend ndonj\u00eb flamur, nj\u00eb nd\u00ebrfaqe cli e thjesht\u00eb dhe intuitiv, mb\u00ebshtetje e integruar p\u00ebr kopje t\u00eb shumta, \u2014 p\u00ebr t\u00eb v\u00ebrtet\u00eb dy her\u00eb m\u00eb ngadal\u00eb. N\u00ebse t\u00eb dh\u00ebnat duhet t\u00eb rikuperohen nga kopja rezerv\u00eb m\u00eb e fundit e b\u00ebr\u00eb \u2014 mund t\u00eb p\u00ebrdorni rsync, me disa rezervata t\u00eb vogla.<\/p>\n

Programi i ngjash\u00ebm BackupPC<\/i> n\u00eb aktivizimin e modit t\u00eb transmetimit rsync, p\u00ebrfundoi rikuperimin p\u00ebr <\/p>\n

7 minuta dhe 42 sekonda:<\/b>\"Kopjimi
\n
\nPor n\u00eb modin e transmetimit t\u00eb t\u00eb dh\u00ebnave me tar BackupPC p\u00ebrfundoi m\u00eb ngadal\u00eb: p\u00ebr 12 minuta dhe 15 sekonda, ngarkesa e procesorit n\u00eb k\u00ebt\u00eb rast ishte gjithashtu m\u00eb e ul\u00ebt <\/p>\n

p\u00ebr nj\u00eb dhe nj\u00eb gjysm\u00eb her\u00eb:<\/b>\"Kopjimi
\n
\nDuplicity<\/i> pa shifrimin tregoi rezultate pak m\u00eb t\u00eb mira, duke arritur t\u00eb rikuperoj\u00eb nj\u00eb kopje rezerv\u00eb p\u00ebr 10 minuta dhe 58 sekonda. N\u00ebse aktivizohet shifrimi me gpg, koha e rikuperimit rritet n\u00eb 15 minuta dhe 3 sekonda. Gjithashtu, kur krijoni nj\u00eb depo p\u00ebr ruajtjen e kopjeve, mund t\u00eb p\u00ebrcaktoni madh\u00ebsin\u00eb e arkiv\u00ebs q\u00eb do t\u00eb p\u00ebrdoret gjat\u00eb ndarjes s\u00eb fluxit t\u00eb t\u00eb dh\u00ebnave t\u00eb hyrjes. N\u00eb p\u00ebrgjith\u00ebsi, n\u00eb disk\u00ebt e zakonsh\u00ebm t\u00eb ngurt\u00eb, gjithashtu p\u00ebr shkak t\u00eb modit nj\u00ebpotencial, nuk ka ndonj\u00eb diferenc\u00eb t\u00eb madhe. Ajo, ndoshta, do t\u00eb shfaqet me madh\u00ebsi t\u00eb ndryshme bllokesh, kur p\u00ebrdoren magazinat hibride. Ngarkesa n\u00eb serverin kryesor gjat\u00eb rikuperimit ishte e till\u00eb:<\/p>\n

pa shifrimin<\/b>\"Kopjimi
\n
\nme shifrimin<\/b>\"Kopjimi
\n
\nDuplicati<\/i> tregoi shpejt\u00ebsi rikuperimi t\u00eb krahasueshme, duke arritur p\u00ebr 13 minuta dhe 45 sekonda. Rreth 5 minuta iu desh\u00ebn p\u00ebr verifikimin e sakt\u00ebsis\u00eb s\u00eb t\u00eb dh\u00ebnave t\u00eb rikuperuara (n\u00eb total rreth 19 minuta). Ngarkesa gjat\u00eb k\u00ebsaj ishte <\/p>\n

mjaft e lart\u00eb:<\/b>\"Kopjimi
\n
\nKur shifrimi aes u aktivizua me mjete t\u00eb brendshme, koha e rikuperimit ishte 21 minuta 40 sekonda, p\u00ebr m\u00eb shum\u00eb, ngarkesa n\u00eb procesor ishte maksimale (t\u00eb dy b\u00ebrthamat!) gjat\u00eb rikuperimit; gjat\u00eb verifikimit t\u00eb t\u00eb dh\u00ebnave ishte aktiv vet\u00ebm nj\u00eb nyj\u00eb, q\u00eb zinte nj\u00eb b\u00ebrtham\u00eb t\u00eb procesorit. Verifikimi i t\u00eb dh\u00ebnave pas rikuperimit zgjati t\u00eb nj\u00ebjt\u00ebn 5 minuta (n\u00eb total pothuajse 27 minuta).<\/p>\n

Rezultati<\/b>\"Kopjimi
\n
\nPak m\u00eb shpejt duplicati arriti t\u00eb menaxhoj\u00eb rikuperimin duke p\u00ebrdorur nj\u00eb program t\u00eb jasht\u00ebm gpg p\u00ebr shifrimin, por n\u00eb p\u00ebrgjith\u00ebsi diferencat nga moda e m\u00ebparshme jan\u00eb minimale. Koha e pun\u00ebs ishte 16 minuta 30 sekonda, me verifikimin e t\u00eb dh\u00ebnave n\u00eb 6 minuta. Ngarkesa ishte <\/p>\n

e till\u00eb:<\/b>\"Kopjimi
\n
\nAMANDA<\/i>, q\u00eb p\u00ebrdor tar, arriti p\u00ebr 2 minuta 49 sekonda, q\u00eb, n\u00eb thelb, \u00ebsht\u00eb shum\u00eb af\u00ebr tar-it t\u00eb zakonsh\u00ebm. Ngarkesa n\u00eb sistem n\u00eb p\u00ebrgjith\u00ebsi <\/p>\n

\u00ebsht\u00eb e nj\u00ebjt\u00eb:<\/b>\"Kopjimi
\n
\nGjat\u00eb rikuperimit t\u00eb kopj\u00ebs rezerv\u00eb me mjete zbackup<\/i> u arrit\u00ebn rezultatet e m\u00ebposhtme:<\/p>\n

shifrimi, kompaktimi lzma<\/b>\"Kopjimi
\n
\nKoha e pun\u00ebs 11 minuta dhe 8 sekonda<\/p>\n

shifrimi aes, kompaktimi lzma<\/b>\"Kopjimi
\n
\nKoha e pun\u00ebs 14 minuta<\/p>\n

shifrimi aes, kompaktimi lzo<\/b>\"Kopjimi
\n
\nKoha e pun\u00ebs 6 minuta, 19 sekonda<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, nuk \u00ebsht\u00eb keq. T\u00eb gjitha varet nga shpejt\u00ebsia e CPU-s\u00eb n\u00eb serverin e kopjimit, e cila duket qart\u00eb nga koha e funksionimit t\u00eb programit me kompresor\u00eb t\u00eb ndrysh\u00ebm. Nga ana e serverit t\u00eb kopjimit \u00ebsht\u00eb aktivizuar tar-i i zakonsh\u00ebm, k\u00ebshtu q\u00eb n\u00ebse e krahasojm\u00eb me t\u00eb \u2014 riparimi funksionon 3 her\u00eb m\u00eb ngadal\u00eb. Ndoshta, duhet t\u00eb verifikojm\u00eb pun\u00ebn n\u00eb modin shum\u00ebth\u00ebrmues, me num\u00ebr m\u00eb t\u00eb madh se dy.<\/p>\n

BorgBackup<\/i> n\u00eb modin pa enkriptim u p\u00ebrball me pak m\u00eb ngadal\u00eb se tar, p\u00ebr 2 minuta e 45 sekonda, megjithat\u00eb, n\u00eb krahasim me tar, u shfaq mund\u00ebsia e deduplikimit t\u00eb depozit\u00ebs. Ngarkesa n\u00eb k\u00ebt\u00eb rast doli <\/p>\n

e till\u00eb:<\/b>\"Kopjimi
\n
\nN\u00ebse aktivizoni enkriptimin mbi blake, shpejt\u00ebsia e riparimit t\u00eb kopjimit ngadal\u00ebsohet pak. Koha e riparimit n\u00eb k\u00ebt\u00eb mod \u00ebsht\u00eb 3 minuta e 19 sekonda, dhe ngarkesa doli <\/p>\n

e till\u00eb:<\/b>\"Kopjimi
\n
\nEnkriptimi aes funksionon pak m\u00eb ngadal\u00eb, koha e riparimit \u00ebsht\u00eb 3 minuta e 23 sekonda, ngarkesa nuk u <\/p>\n

ndryshua ndjesh\u00ebm:<\/b>\"Kopjimi
\n
\nDuke qen\u00eb se Borg mund t\u00eb punoj\u00eb n\u00eb modin shum\u00ebth\u00ebrmues \u2014 ngarkesa e CPU-s\u00eb \u00ebsht\u00eb maksimale, nd\u00ebrsa me aktivizimin e funksioneve shtes\u00eb, koha e pun\u00ebs rritet. N\u00eb dukje, ia vlen t\u00eb studiohet \u043c\u043d\u043e\u0433\u043e\u043f\u043e\u0442\u043e\u0447\u043d\u0456\u0441\u0442\u044c igore ngjash\u00ebm me zbackup.<\/p>\n

Restic<\/i> u p\u00ebrball me riparimin pak m\u00eb ngadal\u00eb, koha e pun\u00ebs ishte 4 minuta e 28 sekonda. Ngarkesa n\u00eb k\u00ebt\u00eb rast dukej <\/p>\n

e till\u00eb:<\/b>\"Kopjimi
\n
\nDuket se procesi i riparimit punon n\u00eb disa thesare, por efikasiteti nuk \u00ebsht\u00eb aq i lart\u00eb sa BorgBackup, por \u00ebsht\u00eb krahasues n\u00eb koh\u00eb me rsync-n e zakonsh\u00ebm.<\/p>\n

Me ndihm\u00ebn e UrBackup<\/i> arriti t\u00eb riparoj\u00eb t\u00eb dh\u00ebnat n\u00eb 8 minuta e 19 sekonda, ngarkesa n\u00eb k\u00ebt\u00eb rast ishte <\/p>\n

e till\u00eb:<\/b>\"Kopjimi
\n
\nEdhe k\u00ebshtu duket se ngarkesa nuk \u00ebsht\u00eb shum\u00eb e lart\u00eb, madje m\u00eb e ul\u00ebt se ajo e tar. Disa her\u00eb ka shp\u00ebrthime, por jo m\u00eb shum\u00eb se ngarkesa e nj\u00eb b\u00ebrthame.<\/p>\n

Zgjedhja dhe justifikimi i kritereve p\u00ebr krahasim<\/h2>\n

\nSi\u00e7 u tha n\u00eb nj\u00eb nga artikujt e m\u00ebparsh\u00ebm, sistemi i kopjimit duhet t\u00eb p\u00ebrmbush\u00eb k\u00ebto kritere:<\/p>\n