{"id":39250,"date":"2019-10-31T22:28:41","date_gmt":"2019-10-31T19:28:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/rezervnoe-kopirovanie-chast-7-vyvody\/"},"modified":"2019-10-31T22:28:41","modified_gmt":"2019-10-31T19:28:41","slug":"rezervnoe-kopirovanie-chast-7-vyvody","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/rezervnoe-kopirovanie-chast-7-vyvody","title":{"rendered":"Backup, partea 7: Concluzii","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Backup, partea 7: Concluzii\" src=\"\/wp-content\/uploads\/2019\/10\/475781030b157d85aa9e9a1dc7ea7c6b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Aceasta not\u0103 finalizeaz\u0103 ciclul despre backup. Se va discuta despre organizarea logic\u0103 a serverului dedicat (sau VPS), convenabil\u0103 pentru backup, precum \u0219i o op\u021biune pentru recuperarea rapid\u0103 a serverului dintr-o copie de siguran\u021b\u0103, f\u0103r\u0103 \u00eent\u00e2rzieri semnificative \u00een caz de urgen\u021b\u0103.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2 id=\"ishodnye-dannye\">Datele originale<\/h2>\n<p><\/p>\n<p>Un server dedicat are de obicei cel pu\u021bin dou\u0103 hard diskuri, folosite pentru organizarea unui array RAID de tip 1 (oglindire). Acest lucru este necesar pentru a continua func\u021bionarea serverului \u00een cazul \u00een care un disc se defecteaz\u0103. Dac\u0103 acesta este un server dedicat obi\u0219nuit, poate exista un controler RAID hardware separat, cu tehnologie activ\u0103 de caching pe SSD, astfel \u00eenc\u00e2t, pe l\u00e2ng\u0103 hard diskurile comune, poate fi conectat unul sau mai multe SSD-uri. Uneori, se ofer\u0103 servere dedicate care au doar SATADOM-uri (discuri mici, constructiv - un stick USB conectat la portul SATA), sau chiar un stick USB mic (8-16GB) conectat la un port intern special, iar datele sunt preluate de la un sistem de stocare conectat printr-o re\u021bea dedicat\u0103 de stocare (Ethernet 10G, FC etc.), \u0219i exist\u0103 servere dedicate care se boot-eaz\u0103 direct de pe sistemul de stocare. Aceste op\u021biuni nu le voi analiza, deoarece \u00een aceste cazuri, responsabilitatea pentru backup-ul serverului trece c\u0103tre specialistul care \u00eentre\u021bine sistemul de stocare; de obicei, exist\u0103 diferite tehnologii proprietare pentru crearea instantaneelor de stare, deduplicare integrat\u0103 \u0219i alte beneficii pentru administratorii de sistem, discutate \u00een p\u0103r\u021bile anterioare ale acestui ciclu. Volumul array-ului de discuri al unui server dedicat poate atinge c\u00e2teva zeci de terabytes, \u00een func\u021bie de num\u0103rul \u0219i dimensiunea discurilor conectate la server. \u00cen cazul VPS, volumele sunt mai mici: de obicei, nu mai mult de 100GB (de\u0219i pot fi \u0219i mai mari), iar tarifele pentru aceste VPS-uri pot fi chiar mai mari dec\u00e2t cele mai ieftine servere dedicate de la acela\u0219i provider. \u00cen mod obi\u0219nuit, un VPS are un singur disc, deoarece va fi conectat la un sistem de stocare (sau ceva hipercoperit). Uneori, un VPS poate avea mai multe discuri cu caracteristici diferite, pentru scopuri diferite:<\/p>\n<p><\/p>\n<ul>\n<li>mic sistem \u2014 pentru instalarea sistemului de operare;<\/li>\n<li>mare \u2014 pentru stocarea datelor utilizatorilor.<\/li>\n<\/ul>\n<p><\/p>\n<p>C\u00e2nd se reinstaleaz\u0103 sistemul prin intermediul panoului de control, discul cu datele utilizatorului nu este \u0219ters, \u00eens\u0103 cel de sistem este suprascris complet. De asemenea, \u00een cazul VPS, furnizorul poate oferi un buton care face o captur\u0103 a st\u0103rii VPS-ului (sau a discului), \u00eens\u0103 dac\u0103 se instaleaz\u0103 un sistem de operare propriu sau se uit\u0103 s\u0103 activeze serviciul necesar \u00een VPS, o parte din date poate fi totu\u0219i pierdut\u0103. \u00cen plus fa\u021b\u0103 de buton, de obicei, se ofer\u0103 un serviciu de stocare a datelor, care este de cele mai multe ori foarte limitat. \u00cen general, aceasta const\u0103 \u00eentr-un cont cu acces prin protocol FTP sau SFTP, uneori \u00eempreun\u0103 cu SSH, cu un shell restric\u021bionat (de exemplu, rbash) sau cu restric\u021bii \u00een execu\u021bia comenzilor prin authorized_keys (prin ForcedCommand). <\/p>\n<p><\/p>\n<p>Serverul dedicat este conectat la re\u021bea prin dou\u0103 porturi cu o vitez\u0103 de 1 Gbps, uneori acestea pot fi carduri de 10 Gbps. La VPS, interfa\u021ba de re\u021bea este, de obicei, una singur\u0103. De cele mai multe ori, centrele de date nu limiteaz\u0103 viteza re\u021belei \u00een interiorul centrului de date, dar limiteaz\u0103 viteza de acces la internet.<\/p>\n<p><\/p>\n<p>\u00cenc\u0103rc\u0103tura tipic\u0103 a unui server dedicat sau a unui VPS const\u0103 \u00een server web, baz\u0103 de date, server de aplica\u021bii. Uneori, pot fi instalate diferite servicii auxiliare, inclusiv pentru serverul web sau baza de date: motor de c\u0103utare, sistem de po\u0219t\u0103 etc.<\/p>\n<p><\/p>\n<p>Ca spa\u021biu pentru stocarea copiilor de siguran\u021b\u0103 este utilizat un server special preg\u0103tit, despre care se va scrie mai \u00een detaliu mai t\u00e2rziu.<\/p>\n<p><\/p>\n<h2 id=\"logicheskaya-organizaciya-diskovoy-sistemy\">Organizarea logic\u0103 a sistemului de fi\u0219iere<\/h2>\n<p><\/p>\n<p>Dac\u0103 exist\u0103 un controler RAID sau aceasta este o VPS cu un singur disc \u0219i nu exist\u0103 preferin\u021be speciale pentru func\u021bionarea subsistemului de discuri (de exemplu, un disc rapid separat pentru baza de date) \u2014 tot spa\u021biul liber se \u00eemparte astfel: se creeaz\u0103 o parti\u021bie, deasupra c\u0103reia se creeaz\u0103 un grup de volume LVM, \u00een care se creeaz\u0103 mai multe volume: 2 mici, de aceea\u0219i dimensiune, utilizate ca sistem de fi\u0219iere r\u0103d\u0103cin\u0103 (modificate alternativ la actualiz\u0103ri pentru a permite revenirea rapid\u0103, idee inspirat\u0103 de distribu\u021bia Calculate Linux), \u00eenc\u0103 unul \u2014 pentru parti\u021bia de swap, restul spa\u021biului liber se \u00eemparte \u00een volume mici, utilizate ca sistem de fi\u0219iere r\u0103d\u0103cin\u0103 pentru containerele complete, discurile pentru ma\u0219inile virtuale, sistemele de fi\u0219iere pentru conturile din \\\/home (fiecare cont av\u00e2nd propriul sistem de fi\u0219iere), sistemele de fi\u0219iere pentru containerele de aplica\u021bii.<\/p>\n<p><\/p>\n<p>Observa\u021bie important\u0103: volumele trebuie s\u0103 fie complet autonome, adic\u0103 nu trebuie s\u0103 depind\u0103 unele de altele, nici de sistemul de fi\u0219iere r\u0103d\u0103cin\u0103. \u00cen cazul ma\u0219inilor virtuale sau containerelor, acest aspect este respectat automat. Dac\u0103 este vorba despre containere de aplica\u021bii sau directoare home \u2014 ar trebui s\u0103 ne g\u00e2ndim la separarea fi\u0219ierelor de configurare ale serverului web \u0219i altor servicii \u00een a\u0219a fel \u00eenc\u00e2t s\u0103 elimin\u0103m maximum dependen\u021bele \u00eentre volume. De exemplu, fiecare site func\u021bioneaz\u0103 de la propriul utilizator, fi\u0219ierele de configurare ale site-ului se afl\u0103 \u00een directorul home al utilizatorului, \u00een set\u0103rile serverului web, fi\u0219ierele de configurare ale site-urilor sunt incluse nu prin \\\/etc\\\/nginx\\\/conf.d\\\/,<em>.conf, ci, de exemplu, \\\/home\\\/<\/em>\/configs\/nginx\/*.conf<\/p>\n<p><\/p>\n<p>Dac\u0103 sunt mai multe discuri \u2014 se poate crea un RAID software (\u0219i s\u0103-l configura\u021bi cu memorie cache pe SSD, dac\u0103 este nevoie \u0219i se pot face acest lucru), deasupra c\u0103ruia se poate construi LVM conform regulilor propuse mai sus. De asemenea, \u00een acest caz, se poate utiliza ZFS sau BtrFS, dar aici ar trebui s\u0103 ne g\u00e2ndim de mai multe ori: ambele necesit\u0103 o abordare mult mai serioas\u0103 fa\u021b\u0103 de resurse, mai mult, ZFS nu vine \u00eempreun\u0103 cu kernelul Linux.<\/p>\n<p><\/p>\n<p>Indiferent de schema folosit\u0103, este \u00eentotdeauna bine s\u0103 estim\u0103m aproximativ viteza de scriere a modific\u0103rilor pe discuri, dup\u0103 care s\u0103 calcul\u0103m dimensiunea spa\u021biului liber care va fi rezervat pentru crearea instantaneelor. De exemplu, dac\u0103 serverul nostru va scrie date cu o vitez\u0103 de 10 megabai\u021bi pe secund\u0103, iar dimensiunea total\u0103 a masei de date este de 10 terabai\u021bi \u2014 timpul de sincronizare poate ajunge la o zi (22 de ore \u2014 at\u00e2t va dura transmiterea acestui volum pe re\u021beaua de 1 Gbps) \u2014 ar trebui s\u0103 rezerv\u0103m aproximativ 800 GB. \u00cen realitate, cifra va fi mai mic\u0103, o putem \u00eemp\u0103r\u021bi f\u0103r\u0103 probleme la num\u0103rul de volume logice.<\/p>\n<p><\/p>\n<h2 id=\"ustroystvo-servera-hraneniya-rezervnyh-kopiy\">Dispozitivul serverului de stocare a copiilor de rezerv\u0103<\/h2>\n<p><\/p>\n<p>Principala diferen\u021b\u0103 a serverului pentru stocarea copiilor de rezerv\u0103 const\u0103 \u00een discuri mari, ieftine \u0219i relativ lente. Deoarece HDD-urile moderne au dep\u0103\u0219it deja pragul de 10TB pe un disc \u2014 este esen\u021bial\u0103 aplicarea sistemelor de fi\u0219iere sau RAID cu sume de control, deoarece \u00een timpul reconstruc\u021biei masei sau restaur\u0103rii sistemului de fi\u0219iere (c\u00e2teva zile!) ar putea s\u0103 cedeze al doilea disc din cauza unei sarcini mari. Pe discurile cu capacitate de p\u00e2n\u0103 la 1TB acest aspect nu a fost at\u00e2t de sensibil. Pentru simplificarea descrierii, presupun c\u0103 spa\u021biul pe disc este \u00eemp\u0103r\u021bit \u00een dou\u0103 p\u0103r\u021bi de aproximativ aceea\u0219i dimensiune (iar\u0103\u0219i, de exemplu, cu ajutorul LVM):<\/p>\n<p><\/p>\n<ul>\n<li>volumuri, corespunz\u0103toare pe serverele folosite pentru stocarea datelor utilizatorilor (pe acestea va fi desf\u0103\u0219urat\u0103 ultima copie de rezerv\u0103 realizat\u0103 pentru verificare);<\/li>\n<li>volumuri, folosite ca repozitorii BorgBackup (aici vor ajunge direct datele pentru copiile de rezerv\u0103).<\/li>\n<\/ul>\n<p><\/p>\n<p>Principiul de func\u021bionare const\u0103 \u00een crearea de volume separate pentru fiecare server sub repozitoriile BorgBackup, unde vor ajunge datele din serverele de produc\u021bie. Repozi\u021biile func\u021bioneaz\u0103 \u00een modul de ad\u0103ugare exclusiv\u0103, ceea ce exclude posibilitatea \u0219tergerii inten\u021bionate a datelor, iar prin deduplicare \u0219i cur\u0103\u021barea periodic\u0103 a repozitoriilor de copiile vechi de rezerv\u0103 (r\u0103m\u00e2n copiile anuale, lunare din ultimul an, s\u0103pt\u0103m\u00e2nale din ultima lun\u0103, zilnice din ultima s\u0103pt\u0103m\u00e2n\u0103, posibil \u2014 \u00een cazuri speciale \u2014 orare din ultima zi: \u00een total 24 + 7 + 4 + 12 + anuale \u2014 aproximativ 50 de copii pentru fiecare server).<br \/>\n\u00cen repositoarele BorgBackup nu se activeaz\u0103 modul de doar ad\u0103ugare, ci se folose\u0219te ForcedCommand \u00een .ssh\/authorized_keys de un fel similar:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">from=\"adresa serverului\",command=\"\/usr\/local\/bin\/borg serve --append-only --restrict-to-path \/home\/servername\/borgbackup\/\",no-pty,no-agent-forwarding,no-port-forwarding,no-X11-forwarding,no-user-rc AAAAA.......<\/code><\/pre>\n<p><\/p>\n<p>Pe calea specificat\u0103 se afl\u0103 un script wrapper deasupra borg, care, pe l\u00e2ng\u0103 lansarea binarului cu parametrii, ini\u021biaz\u0103 de asemenea procesul de restaurare a unei copii de rezerv\u0103 dup\u0103 terminarea capt\u0103rii datelor. Pentru aceasta, scriptul wrapper creeaz\u0103 un fi\u0219ier de semnalizare l\u00e2ng\u0103 repository-ul corespunz\u0103tor. Ultima copie de rezerv\u0103 realizat\u0103 este restaurat\u0103 automat pe volumul logic corespunz\u0103tor dup\u0103 finalizarea procesului de \u00eenc\u0103rcare a datelor.<\/p>\n<p><\/p>\n<p>Aceast\u0103 construc\u021bie permite cur\u0103\u021barea periodic\u0103 a copiilor de rezerv\u0103 inutile \u0219i, de asemenea, \u00eempiedic\u0103 serverele de produc\u021bie s\u0103 \u0219tearg\u0103 ceva pe serverul de stocare a copiilor de rezerv\u0103.<\/p>\n<p><\/p>\n<h2 id=\"process-rezervnogo-kopirovaniya\">Procesul de realizare a copiilor de rezerv\u0103<\/h2>\n<p><\/p>\n<p>Ini\u021biatorul procesului de copiere de rezerv\u0103 este serverul dedicat sau VPS-ul, deoarece acest sistem ofer\u0103 mai mult control asupra procesului de copiere de rezerv\u0103 din partea acestui server. \u00cen primul r\u00e2nd, se realizeaz\u0103 o captur\u0103 a st\u0103rii sistemului de fi\u0219iere r\u0103d\u0103cin\u0103 activ, care este montat\u0103 \u0219i \u00eencarcat\u0103 cu ajutorul BorgBackup pe serverul de stocare a copiilor de rezerv\u0103. Dup\u0103 terminarea capt\u0103rii datelor, captura este demontat\u0103 \u0219i \u0219tears\u0103.<\/p>\n<p><\/p>\n<p>\u00cen cazul \u00een care exist\u0103 o baz\u0103 de date mic\u0103 (de p\u00e2n\u0103 la 1 GB pentru fiecare site), se face un dump al bazei de date, care este salvat \u00een volumul logic corespunz\u0103tor, acolo unde se afl\u0103 celelalte date ale aceluia\u0219i site, dar \u00eentr-un mod \u00een care dump-ul s\u0103 nu fie accesibil prin serverul web. Dac\u0103 \u00eens\u0103 bazele de date sunt mari, ar trebui s\u0103 se configureze o salvare \"fierbinte\" a datelor, de exemplu, folosind xtrabackup pentru MySQL sau func\u021bionarea WAL cu archive_command \u00een PostgreSQL. \u00cen acest caz, baza de date va fi restaurat\u0103 separat de datele site-urilor.<\/p>\n<p><\/p>\n<p>Dac\u0103 se folosesc containere sau ma\u0219ini virtuale, ar trebui configurat qemu-guest-agent, CRIU sau alte tehnologii necesare. \u00cen celelalte cazuri, de obicei nu sunt necesare set\u0103ri suplimentare \u2014 pur \u0219i simplu cre\u0103m capturi ale volumelor logice, care sunt apoi procesate similar capturii st\u0103rii sistemului de fi\u0219iere r\u0103d\u0103cin\u0103. Dup\u0103 captarea datelor, capturile sunt \u0219terse.<\/p>\n<p><\/p>\n<p>Activitatea ulterioar\u0103 se desf\u0103\u0219oar\u0103 pe serverul de stocare a copiilor de rezerv\u0103:<\/p>\n<p><\/p>\n<ul>\n<li>se verific\u0103 ultima copie de rezerv\u0103 realizat\u0103 \u00een fiecare depozit<\/li>\n<li>se verific\u0103 existen\u021ba unui fi\u0219ier de etichetare care indic\u0103 faptul c\u0103 procesul de realizare a copiilor de rezerv\u0103 s-a finalizat<\/li>\n<li>se desf\u0103\u0219oar\u0103 desf\u0103\u0219urarea datelor pe volumul local corespunz\u0103tor<\/li>\n<li>se \u0219terge fi\u0219ierul de etichetare<\/li>\n<\/ul>\n<p><\/p>\n<h2 id=\"process-vosstanovleniya-rabotosposobnosti-servera\">Procesul de recuperare a func\u021bionalit\u0103\u021bii serverului<\/h2>\n<p><\/p>\n<p>Dac\u0103 serverul principal cedeaz\u0103, se activeaz\u0103 un server dedicat similar, care se \u00eencarc\u0103 dintr-o imagine standard. Cel mai probabil, \u00eenc\u0103rcarea se va face prin re\u021bea, \u00eens\u0103 tehnicianul din centrul de date care configureaz\u0103 serverul poate copia imediat aceast\u0103 imagine standard pe unul dintre discuri. \u00cenc\u0103rcarea are loc \u00een memoria RAM, dup\u0103 care se ini\u021biaz\u0103 procesul de recuperare:<\/p>\n<p><\/p>\n<ul>\n<li>se efectueaz\u0103 o solicitare pentru conectarea dispozitivului bloc la iscsinbd sau alt protocol similar de volum logic care con\u021bine sistemul de fi\u0219iere r\u0103d\u0103cin\u0103 al serverului avariat; deoarece sistemul de fi\u0219iere r\u0103d\u0103cin\u0103 trebuie s\u0103 fie mic \u2014 aceast\u0103 etap\u0103 trebuie s\u0103 se finalizeze \u00een c\u00e2teva minute. De asemenea, se restaureaz\u0103 bootloader-ul;<\/li>\n<li>se reconstruieste structura volumelor logice locale, se ata\u0219eaz\u0103 volumele logice de pe serverul de rezerv\u0103 utiliz\u00e2nd modulul kernel dm_clone: \u00eencepe recuperarea datelor, iar modific\u0103rile sunt \u00eenregistrate imediat pe discurile locale<\/li>\n<li>se porne\u0219te un container cu toate discurile fizice disponibile \u2014 func\u021bionalitatea serverului este restabilit\u0103 complet, dar cu performan\u021be reduse;<\/li>\n<li>dup\u0103 finalizarea sincroniz\u0103rii datelor, volumele logice de pe serverul de rezerv\u0103 sunt deconectate, containerul este oprit, iar serverul este repornit;<\/li>\n<\/ul>\n<p><\/p>\n<p>Dup\u0103 repornire, serverul va avea toate datele care existau \u00een momentul realiz\u0103rii copiilor de rezerv\u0103, precum \u0219i toate modific\u0103rile care au fost efectuate \u00een timpul procesului de recuperare.<\/p>\n<p>\n<b class=\"spoiler_title\">Alte articole din ciclu<\/b><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/449282\/\">Backup, partea 1: De ce este necesar backup-ul, revizuirea metodelor, tehnologiilor.<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/452630\/\">Backup, partea 2: Revizuirea \u0219i testarea instrumentelor de backup bazate pe rsync.<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/454420\/\">Backup, partea 3: Prezentare \u0219i testare a duplicity, duplicati<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/454734\/#first_unread\">Backup, partea 4: Revizuirea \u0219i testarea zbackup, restic, borgbackup<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/459550\/\">Backup, partea 5: Testarea Bacula \u0219i Veeam Backup pentru Linux<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/468963\/\">Backup: partea solicitat\u0103 de cititori: recenzia AMANDA, UrBackup, BackupPC<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/470802\/\">Backup, partea 6: Compara\u021bia uneltelor de backup<\/a><\/noindex><br \/>\nBackup, partea 7: Concluzii<\/p>\n<p><\/p>\n<p>V\u0103 invit s\u0103 discut\u0103m despre propunerea prezentat\u0103 \u00een comentarii, mul\u021bumesc pentru aten\u021bie!<\/p>\n<p>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/472776\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0414\u0430\u043d\u043d\u0430\u044f \u0437\u0430\u043c\u0435\u0442\u043a\u0430 \u0437\u0430\u0432\u0435\u0440\u0448\u0430\u0435\u0442 \u0446\u0438\u043a\u043b \u043e \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u043c \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438. \u0412 \u043d\u0435\u0439 \u043f\u043e\u0439\u0434\u0435\u0442 \u0440\u0435\u0447\u044c \u043e \u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0441\u0435\u0440\u0432\u0435\u0440\u0430 (\u0438\u043b\u0438 VPS), \u0443\u0434\u043e\u0431\u043d\u043e\u0439 \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0430 \u0442\u0430\u043a\u0436\u0435 \u0431\u0443\u0434\u0435\u0442 \u043f\u0440\u0435\u0434\u043b\u043e\u0436\u0435\u043d \u0432\u0430\u0440\u0438\u0430\u043d\u0442 \u0431\u044b\u0441\u0442\u0440\u043e\u0433\u043e \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u0438\u0437 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0439 \u043a\u043e\u043f\u0438\u0438 \u0431\u0435\u0437 \u043e\u0441\u043e\u0431\u044b\u0445 \u043f\u0440\u043e\u0441\u0442\u043e\u0435\u0432 \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u0430\u0432\u0430\u0440\u0438\u0438. \u0418\u0441\u0445\u043e\u0434\u043d\u044b\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0412\u044b\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u0439 \u0441\u0435\u0440\u0432\u0435\u0440 \u0447\u0430\u0449\u0435 \u0432\u0441\u0435\u0433\u043e \u0438\u043c\u0435\u0435\u0442 \u043c\u0438\u043d\u0438\u043c\u0443\u043c \u0434\u0432\u0430 \u0436\u0435\u0441\u0442\u043a\u0438\u0445 \u0434\u0438\u0441\u043a\u0430, \u0441\u043b\u0443\u0436\u0430\u0449\u0438\u0445 \u0434\u043b\u044f \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438 RAID \u043c\u0430\u0441\u0441\u0438\u0432\u0430 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":29456,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-39250","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=\"\u0414\u0430\u043d\u043d\u0430\u044f \u0437\u0430\u043c\u0435\u0442\u043a\u0430 \u0437\u0430\u0432\u0435\u0440\u0448\u0430\u0435\u0442 \u0446\u0438\u043a\u043b \u043e \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u043c.\" \/>\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\/ro\/blog\/administrirovanie\/rezervnoe-kopirovanie-chast-7-vyvody\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\u0420\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0435 \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435, \u0447\u0430\u0441\u0442\u044c 7: \u0412\u044b\u0432\u043e\u0434\u044b | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0414\u0430\u043d\u043d\u0430\u044f \u0437\u0430\u043c\u0435\u0442\u043a\u0430 \u0437\u0430\u0432\u0435\u0440\u0448\u0430\u0435\u0442 \u0446\u0438\u043a\u043b \u043e \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u043c.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/rezervnoe-kopirovanie-chast-7-vyvody\" \/>\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:28:41+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:28:41+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\udd47Backup, partea 7: Concluzii | ProHoster","description":"Aceast\u0103 not\u0103 \u00eencheie ciclul despre backup.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/rezervnoe-kopirovanie-chast-7-vyvody","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\u0420\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0435 \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435, \u0447\u0430\u0441\u0442\u044c 7: \u0412\u044b\u0432\u043e\u0434\u044b | ProHoster","og:description":"\u0414\u0430\u043d\u043d\u0430\u044f \u0437\u0430\u043c\u0435\u0442\u043a\u0430 \u0437\u0430\u0432\u0435\u0440\u0448\u0430\u0435\u0442 \u0446\u0438\u043a\u043b \u043e \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u043c.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/rezervnoe-kopirovanie-chast-7-vyvody","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:28:41+00:00","article:modified_time":"2019-10-31T19:28:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"39250","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-24 01:28:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:53:37","updated":"2026-01-24 01:28:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/39250","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=39250"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/39250\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/29456"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=39250"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=39250"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=39250"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}