{"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":"Backup, pjesa 6: Krahasimi i mjeteve t\u00eb backup-it","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Backup,
\nN\u00eb k\u00ebt\u00eb artikull do t\u00eb b\u00ebhet nj\u00eb krahasim i mjeteve p\u00ebr krijimin e kopjeve rezerv\u00eb, por s\u00eb pari \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb dim\u00eb 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 merret n\u00eb konsiderat\u00eb rikuperimi nga nj\u00eb kopje rezerv\u00eb e plot\u00eb, sidomos pasi ky modalitet \u00ebsht\u00eb mb\u00ebshtetur nga t\u00eb gjith\u00eb kandidat\u00ebt. P\u00ebr thjesht\u00ebsi, numrat jan\u00eb marr\u00eb si mesatar\u00eb (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 informacion edhe p\u00ebr mund\u00ebsit\u00eb: prania e nd\u00ebrfaqes n\u00eb web, thjesht\u00ebsia n\u00eb konfigurim dhe p\u00ebrdorim, aft\u00ebsia p\u00ebr automatizim, prania e mund\u00ebsive t\u00eb ndryshme shtes\u00eb (p.sh., kontrolli i integritetit t\u00eb t\u00eb dh\u00ebnave) etj. Grafikat do t\u00eb tregojn\u00eb ngarkes\u00ebn e serverit, ku t\u00eb dh\u00ebnat do t\u00eb aplikohen (jo serverin p\u00ebr ruajtjen e kopjeve rezerv\u00eb).
\n<\/a><\/noindex><\/p>\n

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

\nSi pik\u00eb reference do t\u00eb p\u00ebrdoren rsync dhe tar, pasi n\u00eb t\u00eb cilat zakonisht mb\u00ebshteten<\/a><\/noindex> skriptet m\u00eb t\u00eb thjeshta p\u00ebr krijimin e kopjeve rezerv\u00eb.<\/p>\n

Rsync<\/i> ka p\u00ebrfunduar testin me grupin e t\u00eb dh\u00ebnave p\u00ebr 4 minuta dhe 28 sekonda, duke treguar <\/p>\n

k\u00ebto ngarkesa<\/b>\"Backup,
\n
\nProcessi i rikuperimit u shp\u00ebrb\u00eb n\u00eb kufizimin e n\u00ebn\u00ebs disk t\u00eb serverit t\u00eb ruajtjes s\u00eb kopjeve rezerv\u00eb (grafik\u00ebt me thik\u00eb). Po ashtu, \u00ebsht\u00eb e qart\u00eb ngarkesa e nj\u00eb b\u00ebrtham\u00eb pa ndonj\u00eb problem t\u00eb ve\u00e7ant\u00eb (iowait i ul\u00ebt dhe softirq \u2014 nuk ka probleme me diskun dhe rrjetin p\u00ebrkat\u00ebs). Duke qen\u00eb se dy programet e tjera, konkretisht rdiff-backup dhe rsnapshot, jan\u00eb t\u00eb bazuara n\u00eb rsync dhe ofrojn\u00eb si mjet rikuperimi rsyncin e zakonsh\u00ebm, ato do t\u00eb ken\u00eb nj\u00eb profil ngarkese dhe nj\u00eb koh\u00eb rikuperimi t\u00eb ngjashme.<\/p>\n

Tar<\/i> e p\u00ebrfundoi pak m\u00eb shpejt, p\u00ebr <\/p>\n

2 minuta dhe 43 sekonda:<\/b>\"Backup,
\n
\nNgarkesa e plot\u00eb e sistemit ishte m\u00eb e lart\u00eb mesatarisht me 20% p\u00ebr shkak t\u00eb rritjes s\u00eb softirq \u2014 rriten shpenzimet n\u00eb funksionimin e n\u00ebn\u00ebs rrjet.<\/p>\n

N\u00ebse arkivi kompresohet edhe m\u00eb tej, koha e rikuperimit rritet n\u00eb 3 minuta 19 sekonda me
\nk\u00ebt\u00eb ngarkes\u00eb n\u00eb serverin kryesor (shk\u00ebputja n\u00eb an\u00ebn e serverit kryesor):<\/b>\"Backup,
\n
\nProcesi i deshifrimit merr t\u00eb dy b\u00ebrthamat e procesorit, pasi kryhen dy procese. N\u00eb p\u00ebrgjith\u00ebsi, ky \u00ebsht\u00eb nj\u00eb rezultat i pritur. Nj\u00eb rezultat i ngjash\u00ebm (3 minuta dhe 20 sekonda) u arrit gjithashtu duke ekzekutuar gzip n\u00eb server me kopje rezerv\u00eb, dhe ngarkesa n\u00eb serverin kryesor ishte shum\u00eb e ngjashme me ekzekutimin e tar pa kompresorin gzip (shiko grafikun e m\u00ebparsh\u00ebm).<\/p>\n

N\u00eb rdiff-backup<\/i> mund t\u00eb sinkronizoni kopjen e fundit t\u00eb b\u00ebr\u00eb 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 e b\u00ebri rikuperimin p\u00ebr 17 minuta dhe 17 sekonda, duke treguar <\/p>\n

k\u00ebt\u00eb ngarkes\u00eb:<\/b>\"Backup,
\n
\nNdoshta k\u00ebshtu \u00ebsht\u00eb menduar, p\u00ebr \u00e7do rast p\u00ebr t\u00eb limituar shpejt\u00ebsin\u00eb autor\u00ebt propozojn\u00eb nj\u00eb zgjidhje t\u00eb till\u00eb<\/a><\/noindex>. Procesi i rikuperimit t\u00eb kopjes rezerv\u00eb merr pak m\u00eb pak se nj\u00eb e gjysm\u00eb b\u00ebrthame, me nj\u00eb performanc\u00eb proporcionale t\u00eb ngjashme (kjo do t\u00eb thot\u00eb 2-5 her\u00eb m\u00eb e ngadalshme) mbi disk dhe rrjet me rsync.<\/p>\n

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

Burp<\/i> u p\u00ebrball\u00eb me detyr\u00ebn e rikuperimit t\u00eb kopj\u00ebs rezerv\u00eb p\u00ebr 7 minuta dhe 2 sekonda me
\nt\u00eb till\u00eb ngarkese:<\/b>\"Backup,
\n
\nFunksionoi mjaft shpejt dhe, s\u00eb paku, shum\u00eb m\u00eb komod se rsync i past\u00ebr: nuk \u00ebsht\u00eb e nevojshme t\u00eb mbash mend ndonj\u00eb flag, nd\u00ebrfaqe CLI e thjesht\u00eb dhe intuitive, mb\u00ebshtetje e nd\u00ebrtuar p\u00ebr shum\u00eb kopje, - megjithat\u00eb dy her\u00eb m\u00eb e ngadalshme. N\u00ebse t\u00eb dh\u00ebnat duhet t\u00eb rikuperohen nga kopja e fundit e b\u00ebr\u00eb - mund t\u00eb p\u00ebrdoret rsync, me disa rezerva t\u00eb vogla.<\/p>\n

Programi BackupPC<\/i> tregoi af\u00ebrsisht t\u00eb nj\u00ebjt\u00ebn shpejt\u00ebsi dhe ngarkes\u00eb duke aktivizuar modin e transmetimit rsync, duke rikuperuar kopjen n\u00eb <\/p>\n

7 minuta dhe 42 sekonda:<\/b>\"Backup,
\n
\nNd\u00ebrsa n\u00eb modin e transmetimit t\u00eb t\u00eb dh\u00ebnave me tar, BackupPC e realizoi m\u00eb ngadal\u00eb: brenda 12 minutave dhe 15 sekondash, ngarkesa e procesorit gjat\u00eb k\u00ebtij procesi ishte gjithsej m\u00eb e ul\u00ebt <\/p>\n

n\u00eb nj\u00eb gjysm\u00eb here:<\/b>\"Backup,
\n
\nDuplicity<\/i> pa pa qart\u00eb m\u00eb t\u00eb mira, duke e b\u00ebr\u00eb rivendosjen e kopj\u00ebs brenda 10 minutash e 58 sekondash. N\u00ebse aktivizohet enkriptimi me gpg, koha e rivendosjes rritet n\u00eb 15 minuta e 3 sekonda. Po ashtu, kur krijoni nj\u00eb depo p\u00ebr ruajtjen e kopjave, mund t\u00eb p\u00ebrcaktoni madh\u00ebsin\u00eb e arkivit 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 hard disk\u00ebt e zakonsh\u00ebm, po ashtu p\u00ebr shkak t\u00eb m\u00ebnyr\u00ebs nj\u00ebkanal\u00ebshe t\u00eb funksionimit, nuk ka ndonj\u00eb dallim t\u00eb ve\u00e7ant\u00eb. Mund\u00ebsia ndoshta do t\u00eb shfaqet me madh\u00ebsi t\u00eb ndryshme bllokesh, kur p\u00ebrdoren ruajtje hibride. Ngarkesa n\u00eb serverin kryesor gjat\u00eb rivendosjes ishte e till\u00eb:<\/p>\n

pa enkriptim<\/b>\"Backup,
\n
\nme enkriptim<\/b>\"Backup,
\n
\nDuplicati<\/i> tregon nj\u00eb shpejt\u00ebsi rivendosjeje t\u00eb ngjashme, duke u p\u00ebrballur brenda 13 minutash e 45 sekondash. Rreth 5 minuta mori verifikimi i sakt\u00ebsis\u00eb s\u00eb t\u00eb dh\u00ebnave t\u00eb rikuperuara (n\u00eb total rreth 19 minuta). Ngarkesa n\u00eb k\u00ebt\u00eb rast ishte <\/p>\n

mjaft e lart\u00eb:<\/b>\"Backup,
\n
\nKur aktivizuam enkriptimin aes me mjete t\u00eb brendshme, koha e rikuperimit ishte 21 minuta e 40 sekonda, me ngarkes\u00eb maksimale t\u00eb procesorit (t\u00eb dy b\u00ebrthamat!) gjat\u00eb rikuperimit; gjat\u00eb kontrollit t\u00eb t\u00eb dh\u00ebnave ishte aktiv vet\u00ebm nj\u00eb proces, duke z\u00ebn\u00eb nj\u00eb b\u00ebrtham\u00eb procesori. Kontrolli i t\u00eb dh\u00ebnave pas rikuperimit zgjati t\u00eb nj\u00ebjtat 5 minuta (n\u00eb total af\u00ebrsisht 27 minuta).<\/p>\n

Rezultati<\/b>\"Backup,
\n
\nPak m\u00eb shpejt dublikuar p\u00ebrfundoi rikuperimin duke p\u00ebrdorur nj\u00eb program t\u00eb jasht\u00ebm gpg p\u00ebr enkriptim, por n\u00eb p\u00ebrgjith\u00ebsi dallimet nga moda e m\u00ebparshme jan\u00eb minimale. Koha e pun\u00ebs ishte 16 minuta e 30 sekonda, me kontrollin e t\u00eb dh\u00ebnave n\u00eb 6 minuta. Ngarkesa ishte <\/p>\n

ashtu:<\/b>\"Backup,
\n
\nAMANDA<\/i>, e cila p\u00ebrdor tar, p\u00ebrfundoi p\u00ebr 2 minuta e 49 sekonda, e cila, n\u00eb parim, \u00ebsht\u00eb shum\u00eb af\u00ebr tar-it t\u00eb zakonsh\u00ebm. Ngarkesa n\u00eb sistem n\u00eb parim <\/p>\n

\u00ebsht\u00eb e nj\u00ebjt\u00eb:<\/b>\"Backup,
\n
\nGjat\u00eb rikuperimit t\u00eb kopjes rezerv\u00eb me mjete zbackup<\/i> k\u00ebto rezultate u arrit\u00ebn:<\/p>\n

enkriptime, kompresim lzma<\/b>\"Backup,
\n
\nKoha e pun\u00ebs 11 minuta e 8 sekonda<\/p>\n

enkriptime aes, kompresim lzma<\/b>\"Backup,
\n
\nKoha e pun\u00ebs 14 minuta<\/p>\n

enkriptime aes, kompresim lz0<\/b>\"Backup,
\n
\nKoha e pun\u00ebs 6 minuta, 19 sekonda<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, nuk \u00ebsht\u00eb keq. E gjith\u00eb kjo varet nga shpejt\u00ebsia e procesorit n\u00eb serverin e kopjimit, e cila \u00ebsht\u00eb e dukshme n\u00eb koh\u00ebn e funksionimit t\u00eb programit me kompresor\u00eb t\u00eb ndrysh\u00ebm. Nga ana e serverit t\u00eb kopjimit \u00ebsht\u00eb ekzekutuar tar-i i zakonsh\u00ebm, k\u00ebshtu q\u00eb n\u00ebse e krahasojm\u00eb me t\u00eb \u2014 rikuperimi punon 3 her\u00eb m\u00eb ngadal\u00eb. Ndoshta duhet t\u00eb kontrolloni funksionimin n\u00eb m\u00ebnyr\u00eb shum\u00ebthith\u00ebse, me numrin e rrymave m\u00eb shum\u00eb se dy.<\/p>\n

BorgBackup<\/i> n\u00eb m\u00ebnyr\u00ebn pa enkriptim rezultoi t\u00eb jet\u00eb pak m\u00eb i ngadalsh\u00ebm se tar, p\u00ebr 2 minuta e 45 sekonda, megjithat\u00eb, ndryshe nga tar-i i nj\u00ebjt\u00eb, u shfaq mund\u00ebsia e deduplikimit t\u00eb depozit\u00ebs. Ngarkesa n\u00eb k\u00ebt\u00eb rast ishte <\/p>\n

e till\u00eb:<\/b>\"Backup,
\n
\nN\u00ebse aktivizoni enkriptimin duke p\u00ebrdorur blake, at\u00ebher\u00eb shpejt\u00ebsia e rikuperimit t\u00eb kopjimeve ngadal\u00ebsohet pak. Koha e rikuperimit n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb \u00ebsht\u00eb 3 minuta e 19 sekonda, nd\u00ebrsa ngarkesa rezultoi <\/p>\n

e till\u00eb:<\/b>\"Backup,
\n
\nEnkriptimi aes punon pak m\u00eb ngadal\u00eb, koha e rikuperimit \u00ebsht\u00eb 3 minuta e 23 sekonda, ngarkesa nuk ka ndryshuar shum\u00eb: <\/p>\n

nuk e \u00ebsht\u00eb ndar\u00eb:<\/b>\"Backup,
\n
\nDuke Borg mund t\u00eb funksionoj\u00eb n\u00eb m\u00ebnyr\u00eb shum\u00ebth\u00ebshe \u2014 ngarkesa e procesorit \u00ebsht\u00eb maksimale, nd\u00ebrsa gjat\u00eb aktivizimit t\u00eb funksioneve shtes\u00eb vet\u00ebm rritet koha e dyt\u00eb. Me sa duket, duhet t\u00eb hetojm\u00eb shum\u00ebth\u00ebshm\u00ebrin\u00eb e funksionimit t\u00eb ngjash\u00ebm me zbackup.<\/p>\n

Restic<\/i> u rikuperua pak m\u00eb ngadal\u00eb, koha e funksionimit ishte 4 minuta 28 sekonda. Ngarkesa dukej <\/p>\n

ashtu:<\/b>\"Backup,
\n
\nMe sa duket, procesi i rikuperimit funksionon n\u00eb disa tema, por efikasiteti nuk \u00ebsht\u00eb aq i lart\u00eb sa ai i BorgBackup, por \u00ebsht\u00eb krahasues me koh\u00ebn e zakonshme t\u00eb rsync.<\/p>\n

Me UrBackup<\/i> arriti t\u00eb rikuperoj\u00eb t\u00eb dh\u00ebnat p\u00ebr 8 minuta dhe 19 sekonda, ngarkesa ishte <\/p>\n

ashtu:<\/b>\"Backup,
\n
\nEdhe nj\u00ebher\u00eb tregohet se ngarkesa nuk \u00ebsht\u00eb shum\u00eb e lart\u00eb, madje edhe m\u00eb e ul\u00ebt se ajo e tar. Her\u00eb pas here ka shp\u00ebrthime, por jo m\u00eb shum\u00eb se ngarkesa e nj\u00eb b\u00ebrthame.<\/p>\n

Zgjedhja dhe arsyetimi 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\u00ebrputhet me kriteret e m\u00ebposhtme:<\/p>\n