{"id":54466,"date":"2019-12-27T00:00:00","date_gmt":"2019-12-26T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/znakomtes-novoe-reshenie-veeam-backup-for-aws"},"modified":"2020-02-18T14:02:28","modified_gmt":"2020-02-18T11:02:28","slug":"znakomtes-novoe-reshenie-veeam-backup-for-aws","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","title":{"rendered":"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>La \u00eenceputul lunii decembrie a fost lansat\u0103 o nou\u0103 solu\u021bie <b>Veeam Backup for AWS<\/b> pentru backup \u0219i recuperare a infrastructurilor cloud Amazon Elastic Compute Cloud (Amazon EC2). <\/p>\n<p>Cu ajutorul acestuia, se pot crea copii de siguran\u021b\u0103 pentru instan\u021bele EC2 \u0219i salva \u00een stocarea cloud Amazon Simple Storage Service (Amazon S3), precum \u0219i crea lan\u021buri de snapshot-uri EC2 \u00een format nativ. <\/p>\n<p>Pentru recuperarea datelor, Veeam Backup for AWS ofer\u0103 urm\u0103toarele op\u021biuni: <\/p>\n<ul>\n<li>Recuperarea complet\u0103 a instan\u021bei EC2<\/li>\n<li>Recuperarea volumelor instan\u021bei<\/li>\n<li>Recuperarea fi\u0219ierelor \u0219i folderelor din sistemul de operare al instan\u021bei<\/li>\n<\/ul>\n<p>\n\u00cen plus, deoarece solu\u021bia creeaz\u0103 copii de siguran\u021b\u0103 \u00een format Veeam, este posibil s\u0103 utiliza\u021bi Veeam Backup &amp; Replication pentru a salva copiile backup-urilor EC2 \u00een depozite on-premises, apoi s\u0103 efectua\u021bi migrarea datelor \u00eentre infrastructurile cloud, virtuale \u0219i on-premises. <\/p>\n<p>\u0218i, cu siguran\u021b\u0103, utilizatorii vor fi \u00eenc\u00e2nta\u021bi de disponibilitatea unei versiuni gratuite a noii solu\u021bii. Pentru a explora mai \u00een detaliu Veeam Backup for AWS, v\u0103 invit\u0103m s\u0103 citi\u021bi \u00een continuare.<\/p>\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/73914c365c4b7c876affe73517108875.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Func\u021bionalit\u0103\u021bi principale<\/h3>\n<p>\nPe l\u00e2ng\u0103 func\u021bionalit\u0103\u021bile deja men\u021bionate de automatizare a cre\u0103rii snapshot-urilor Amazon EBS \u0219i stoc\u0103rii backup-urilor \u00een cloud Amazon S3, solu\u021bia include:<\/p>\n<ul>\n<li>Autentificare multi-factor pentru administratorii de backup<\/li>\n<li>Protec\u021bie a datelor bazat\u0103 pe politici<\/li>\n<li>Suport pentru divizarea rolurilor IAM<\/li>\n<li>Suport pentru configura\u021bii cross-region<\/li>\n<li>Un algoritm \u00eencorporat de evaluare preliminar\u0103 a costurilor serviciilor, care ajut\u0103 la monitorizarea pl\u0103\u021bilor.<\/li>\n<\/ul>\n<p>\nA\u0219a cum s-a men\u021bionat deja, exist\u0103 o licen\u021b\u0103 gratuit\u0103, precum \u0219i BYOL (build your own license) \u0219i o licen\u021b\u0103 bazat\u0103 pe consum \u2014 fiecare poate alege op\u021biunea potrivit\u0103.<\/p>\n<h3>Etapele de lucru<\/h3>\n<p>\nDac\u0103 ar fi s\u0103 rezum\u0103m, principalele etape sunt:<\/p>\n<ol>\n<li>Verific\u0103m infrastructura noastr\u0103 \u00een raport cu cerin\u021bele sistemului descrise <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/system_requirements.html?ver=10\">aici<\/a><\/noindex>. <\/li>\n<li>Instal\u0103m Veeam Backup for AWS, conform instruc\u021biunilor de mai jos.<\/li>\n<li>Specifica\u021bi rolurile IAM. Acestea sunt necesare pentru accesul la resursele AWS implicate \u00een backup \u0219i recuperare:\n<ul>\n<li>Dac\u0103 inten\u021biona\u021bi s\u0103 face\u021bi backup pentru instan\u021bele EC2 \u00een cadrul acelea\u0219i cont AWS, pute\u021bi utiliza rolul <i>Default Backup Restore<\/i> \u2014 acesta este creat \u00een timpul instal\u0103rii Veeam Backup for AWS. Acest rol are permisiunile necesare pentru a accesa toate instan\u021bele EC2 \u0219i bucket-urile S3 din contul AWS \u00een care este implementat Veeam Backup for AWS (contul AWS ini\u021bial).<\/li>\n<li>Dac\u0103 inten\u021biona\u021bi s\u0103 face\u021bi backup sau s\u0103 restaura\u021bi datele instan\u021belor EC2 \u00eentre dou\u0103 conturi AWS diferite sau dori\u021bi s\u0103 utiliza\u021bi pentru fiecare opera\u021biune un rol IAM dedicat cu un set minim de permisiuni, va trebui s\u0103 crea\u021bi rolurile IAM necesare \u00een cadrul contului AWS ini\u021bial \u0219i apoi s\u0103 le ad\u0103uga\u021bi \u00een Veeam Backup for AWS. Despre aceasta se vorbe\u0219te detaliat \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/iam_roles_add.html?ver=10\">documentation<\/a><\/noindex>. <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Configur\u0103m infrastructura de backup, \u0219i anume:\n<ul>\n<li>Configur\u0103m depozitul S3.\n<p><i>Not\u0103:<\/i> Dac\u0103 sunte\u021bi pe cale s\u0103 utiliza\u021bi pentru protec\u021bia datelor nu backup-uri, ci instantanee create \u00een mod nativ, atunci acest punct poate fi s\u0103rit, deoarece depozitul S3 nu va fi necesar \u00een acest scenariu. \n <\/li>\n<li>Stabilim set\u0103rile de re\u021bea pentru componentele auxiliare <i>instan\u021bele worker<\/i>.<br \/>\n<i>Workerii<\/i> sunt instan\u021be EC2 auxiliare gestionate de OS Linux. Acestea sunt pornite doar pe perioada backup-ului (sau restaur\u0103rii) \u0219i \u00eendeplinesc rolul de proxy de backup. \u00cen set\u0103rile worker, va trebui s\u0103 specifica\u021bi Amazon VPC, subre\u021beaua \u0219i grupul de securitate la care aceste instan\u021be auxiliare se vor conecta. Despre toate acestea pute\u021bi citi <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/workers.html?ver=10\">aici<\/a><\/noindex>.\n <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Apoi, cre\u0103m o politic\u0103 pe baza c\u0103reia vor fi realizate backup-urile sau instantan\u021bele instan\u021belor EC2. Despre aceasta voi povesti pe scurt mai jos.<\/li>\n<li>Din backup poate fi efectuat\u0103 o restaurare \u2013 despre aceasta voi vorbi, de asemenea, pu\u021bin mai jos. <\/li>\n<\/ol>\n<p><\/p>\n<h3>Implementare \u0219i configurare<\/h3>\n<p>\nVeeam Backup for AWS este disponibil pe <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/marketplace\/pp\/B081VXF1Q9\">AWS Marketplace<\/a><\/noindex>. <\/p>\n<p>Implementarea solu\u021biei se realizeaz\u0103 astfel:<\/p>\n<ol>\n<li>Acces\u0103m AWS Marketplace cu contul AWS pe care inten\u021bion\u0103m s\u0103-l folosim pentru instalarea solu\u021biei.<\/li>\n<li>Deschidem pagina Veeam Backup for AWS, alegem edi\u021bia dorit\u0103 (pl\u0103tit\u0103 sau gratuit\u0103). Mai multe informa\u021bii despre edi\u021bii sunt prezentate <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/lic.html\">aici<\/a><\/noindex>.\n<ul>\n<li>Veeam Backup for AWS Free Edition<\/li>\n<li>Veeam Backup for AWS Paid Edition<\/li>\n<li>Veeam Backup for AWS BYOL Edition<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>\u00cen dreapta sus, facem clic pe <b>Continue to Subscribe<\/b>.\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/bee5554b53ed411789b31d178d4f4875.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Pe pagina de abonare, mergem la sec\u021biunea <b>Terms and Conditions<\/b> (termeni \u0219i condi\u021bii de utilizare) \u0219i acolo facem clic pe <b>Show Details<\/b>, apoi pe linkul <b>End User License Agreement<\/b> citit licen\u021ba de utilizare. <\/li>\n<li>Apoi, ap\u0103s\u0103m butonul <b>Continue to Configuration<\/b> \u0219i \u00eencepem configurarea.\n<\/li>\n<li>Pe pagina <b>Configure this software<\/b> definim set\u0103rile pentru instalare:\n<ul>\n<li>Din lista <b>Fulfillment Option<\/b> (op\u021biuni de implementare) alegem op\u021biunea pentru produsul nostru \u2014 <b>VB for AWS Deployment<\/b>.<\/li>\n<li>Din lista versiunilor <b>Software Version<\/b> alegem cea mai recent\u0103 versiune a Veeam Backup for AWS.<\/li>\n<li>Din lista regiunilor <b>Region<\/b> alegem regiunea AWS \u00een care va fi desf\u0103\u0219urat instan\u021ba EC2 cu Veeam Backup pentru AWS.<\/li>\n<\/ul>\n<p>\n<i>Not\u0103: <\/i>Mai multe informa\u021bii despre regiunile AWS pot fi citite <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/using-regions-availability-zones.html\">aici<\/a><\/noindex>.\n<\/li>\n<li>Apoi, ap\u0103s\u0103m butonul <b>Continu\u0103 c\u0103tre Lansare<\/b> pentru a continua la lansare.\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/9264144271e73d7ad8dcb303340ae4d3.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Pe pagina <b>Lanseaz\u0103 acest software<\/b> execut\u0103m ace\u0219ti pa\u0219i:\n<ul>\n<li>\u00cen sec\u021biune <b>Detalii de configurare<\/b> verific\u0103m dac\u0103 toate set\u0103rile sunt corect specificate.<\/li>\n<li>Din lista ac\u021biunilor <b>Alege\u021bi Ac\u021biunea<\/b> alegem <b>Lanseaz\u0103 CloudFormation<\/b>.<\/li>\n<li>Instalarea Veeam Backup pentru AWS se realizeaz\u0103 prin intermediul unei stive AWS CloudFormation.\n<p><i>Not\u0103: <\/i>Aici, o stiv\u0103 este un set de resurse cloud care pot fi gestionate ca o unitate separat\u0103: cl\u0103di\u021bi, elimina\u021bi, utiliza\u021bi pentru a lansa aplica\u021bii. Mai multe informa\u021bii pot fi g\u0103site \u00een documenta\u021bia AWS.<\/p>\n<p>Facem clic pe <b>Lanseaz\u0103<\/b> \u0219i lans\u0103m asistentul de creare a stivei <b>Asistent de creare a stivei<\/b>.<\/li>\n<\/ul>\n<p>\n<\/li>\n<\/ol>\n<p>\n<b class=\"spoiler_title\">Crearea stivei AWS CloudFormation<\/b>Crearea stivei AWS CloudFormation:<\/p>\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/834415111714f2143c701f704e3d624d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<ol>\n<li>La pasul <b>Specifica\u021bi \u0219ablonul<\/b> pute\u021bi l\u0103sa set\u0103rile \u0219ablonului stivei nealterate. \n<\/li>\n<li>La pasul <b>Specifica\u021bi detaliile stivei<\/b> introducem set\u0103rile pentru stiva noastr\u0103.\n<ul>\n<li>\u00cen c\u00e2mpul <b>Numele stivei<\/b> introducem un nume; se pot folosi litere mari \u0219i mici, cifre \u0219i cratime.<\/li>\n<li>\u00cen sec\u021biunea de set\u0103ri <b>Configurarea instan\u021bei<\/b>:<br \/>\n Din lista <b>Tipul de instan\u021b\u0103 pentru serverul Veeam Backup pentru AWS<\/b> trebuie s\u0103 alegem tipul de instan\u021b\u0103 EC2 pe care va fi instalat Veeam Backup pentru AWS (\u00een continuare vom numi acest <i>server Veeam Backup pentru AWS<\/i>). Este recomandat s\u0103 alege\u021bi tipul <i>t2.medium<\/i>.<br \/>\n Din lista <b>Pereche de chei pentru serverul Veeam Backup pentru AWS<\/b> trebuie s\u0103 selecta\u021bi o pereche de chei care va fi utilizat\u0103 pentru autentificare pe acest nou server. Dac\u0103 perechea de chei necesar\u0103 nu se afl\u0103 \u00een list\u0103, aceasta trebuie creat\u0103, a\u0219a cum este descris <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/ec2-key-pairs.html\">aici<\/a><\/noindex>. <br \/>\n Specifica\u021bi dac\u0103 trebuie s\u0103 activa\u021bi backup-ul automat pentru volumele EBS pentru serverul Veeam Backup pentru AWS (implicit este necesar, adic\u0103. <i>true<\/i>).<br \/>\n Specifica\u021bi dac\u0103 trebuie s\u0103 reporni\u021bi serverul Veeam Backup pentru AWS \u00een caz de defectare a software-ului.<br \/>\n Specifica\u021bi dac\u0103 trebuie s\u0103 reporni\u021bi serverul Veeam Backup pentru AWS \u00een caz de defectare a infrastructurii.\n<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>\u00cen sec\u021biunea de set\u0103ri de re\u021bea <b>Configurarea re\u021belei<\/b>:\n<ul>\n<li>Specifica\u021bi dac\u0103 trebuie s\u0103 crea\u021bi un adres\u0103 IP Elastic pentru serverul Veeam Backup pentru AWS. Mai multe informa\u021bii pot fi g\u0103site aici.<\/li>\n<li>\u00cen c\u00e2mpul <b>Adrese IP surs\u0103 permise pentru conexiunea SSH<\/b> specifica\u021bi intervalul adreselor IPv4 din care va fi permis accesul la serverul Veeam Backup pentru AWS prin SSH.<\/li>\n<li>\u00cen c\u00e2mpul <b>Adrese IP surs\u0103 permise pentru conexiunea HTTPS<\/b> specifica\u021bi intervalul adreselor IPv4 din care va fi permis accesul la interfa\u021ba web a Veeam Backup pentru AWS.<br \/>\n Intervalul adreselor IPv4 se specific\u0103 \u00een nota\u021bia CIDR (de exemplu, 12.23.34.0\/24). Pentru a permite accesul de pe toate adresele IPv4, se poate introduce 0.0.0.0\/0. (Cu toate acestea, aceast\u0103 op\u021biune nu este recomandat\u0103, deoarece reduce securitatea infrastructurii.)<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Pe baza adreselor IPv4 specificate, AWS CloudFormation creeaz\u0103 un grup de securitate pentru Veeam Backup for AWS, cu regulile corespunz\u0103toare pentru traficul de intrare prin SSH \u0219i HTTPS. (\u00cen mod implicit, pentru traficul de intrare prin SSH se folose\u0219te portul 22, iar pentru HTTPS \u2014 portul 443.) Dac\u0103 inten\u021biona\u021bi s\u0103 specifica\u021bi un alt grup de securitate pentru Veeam Backup for AWS \u00een timpul instal\u0103rii solu\u021biei, nu uita\u021bi s\u0103 ad\u0103uga\u021bi manual regulile corespunz\u0103toare \u00een acest grup \u0219i s\u0103 verifica\u021bi c\u0103 accesul la serviciile AWS este permis (a\u0219a cum este men\u021bionat \u00een sec\u021biunea Cerin\u021be a manualului de utilizare).<\/li>\n<li>\u00cen sec\u021biune <b>VPC \u0219i Subnet<\/b> trebuie s\u0103 selecta\u021bi Amazon Virtual Private Cloud (Amazon VPC) \u0219i subnetul la care va fi conectat serverul Veeam Backup for AWS.\n<\/li>\n<li>La pasul <b>Configureaz\u0103 op\u021biunile stivei<\/b> specifica\u021bi etichetele AWS, permisiunile pentru rolul IAM \u0219i alte set\u0103ri ale stivei.\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/31062236b5ddf46ab22cd69a18c2cf06.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>La pasul <b>Revizuie\u0219te<\/b> verifica\u021bi toate set\u0103rile, selecta\u021bi op\u021biunea <b>Recunosc c\u0103 AWS CloudFormation ar putea crea resurse IAM<\/b> \u0219i ap\u0103sa\u021bi <b>Creeaz\u0103 stiva<\/b>.<\/li>\n<\/ol>\n<p>Dup\u0103 instalare, deschidem consola web, introduc\u00e2nd \u00een browser DNS-ul sau adresa IP a instan\u021bei EC2 unde este instalat Veeam Backup for AWS, de exemplu:<br \/>\n<code>https:\/\/ec2-135-169-170-192.eu-central-1.compute.amazonaws.com<\/code><\/p>\n<p>\u00cen consol\u0103 sunt afi\u0219ate resursele pentru care este configurat\u0103 protec\u021bia datelor folosind Veeam Backup for AWS:<\/p>\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/eb7ed2550eb15398c8c0732e1c2b7f52.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSet\u0103rile necesare pentru infrastructur\u0103, roluri etc. sunt descrise detaliat \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/configuration.html?ver=10\">documentation<\/a><\/noindex>.<\/p>\n<h3>Politicile de backup<\/h3>\n<p>\nPentru a proteja instan\u021bele, cre\u0103m politici. <\/p>\n<p>Pentru diferite tipuri de obiecte se pot configura politici diferite: de exemplu, o politic\u0103 destinat\u0103 protec\u021biei aplica\u021biilor tier 3 (ce mai pu\u021bin critice), sau politici pentru aplica\u021biile tier 2 \u0219i tier 1. \u00cen set\u0103rile politicii specific\u0103m:<\/p>\n<ul>\n<li>Contul cu roluri IAM<\/li>\n<li>Regiuni \u2014 se pot selecta mai multe <\/li>\n<li>Ce se planific\u0103 a fi protejat \u2014 pot fi toate resursele (toate resursele) sau instan\u021be selectate sau (etichet\u0103ri)<\/li>\n<li>Resursele care trebuie excluse<\/li>\n<li>Set\u0103rile de snapshot, inclusiv dac\u0103 se utilizeaz\u0103 snapshot-uri \u0219i care ar trebui s\u0103 fie durata de p\u0103strare<\/li>\n<li>Set\u0103rile de backup: calea c\u0103tre repository, programul \u0219i durata de p\u0103strare<\/li>\n<li>Estimarea costului serviciilor (despre care vorbim mai jos)<\/li>\n<li>Set\u0103rile programului \u0219i notific\u0103rilor<\/li>\n<\/ul>\n<p><\/p>\n<h4>Estimarea costului serviciilor integrate<\/h4>\n<p>\n\u00cen solu\u021bia Veeam Backup for AWS este integrat\u0103 o estimare automat\u0103 a costului serviciilor \u2014 aceasta calculeaz\u0103 imediat care va fi costul serviciilor de backup conform politicii specifice. \u00cen calcul sunt incluse urm\u0103toarele metrici:<\/p>\n<ul>\n<li>Costul backup-ului<\/li>\n<li>Costul snapshot-ului<\/li>\n<li>Costul traficului este deosebit de important atunci c\u00e2nd depozitul se afl\u0103 \u00een afara regiunii \u00een care func\u021bioneaz\u0103 obiectele de infrastructur\u0103 (Amazon AWS percepe taxe pentru traficul din alte regiuni)<\/li>\n<li>Costul tranzac\u021biilor<\/li>\n<li>Costul total<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/d81df948587d769241c58887ed8769cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDatele pot fi exportate \u00eentr-un fi\u0219ier CSV sau XML.<\/p>\n<h3>Componente auxiliare \u2014 Workers<\/h3>\n<p>\nPentru a reduce costurile de trafic, se pot configura automatizarea cre\u0103rii de componente auxiliare \u2014 <b>workers<\/b> \u2014 \u00een aceea\u0219i regiune AWS unde se afl\u0103 obiectele protejate. Workers sunt activate automat doar \u00een perioada transferului de date din\/sau c\u0103tre Amazon S3 sau \u00een timpul recuper\u0103rii, iar dup\u0103 finalizarea opera\u021biunilor, acestea sunt oprite \u0219i \u0219terse.<\/p>\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/0926f91f39f09f77e4f4511d1a6d02f9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Backup<\/h3>\n<p>\nPentru opera\u021biunile de backup, Veeam Backup for AWS utilizeaz\u0103 instantanee native (vezi <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/EBSSnapshots.html\">Amazon EBS snapshots<\/a><\/noindex>). \u00cen procesul de backup, Veeam Backup for AWS folose\u0219te comenzi AWS CLI pentru a crea instantanee ale volumelor EBS ata\u0219ate instan\u021bei EC2. Apoi, \u00een func\u021bie de scenariul de backup ales de dumneavoastr\u0103, Veeam Backup for AWS va crea pentru instan\u021ba EC2 fie o serie de instantanee native, fie un backup la nivel de imagine.<\/p>\n<h4>Instantanee native<\/h4>\n<p>\nVeeam Backup for AWS creeaz\u0103 instantanee native ale instan\u021bei EC2 \u00een urm\u0103toarele moduri:<\/p>\n<ol>\n<li>Mai \u00eent\u00e2i, se fac instantanee ale volumelor EBS ata\u0219ate acestei instan\u021be.<\/li>\n<li>Instantaneelor EBS li se atribuie etichete AWS la momentul cre\u0103rii. Cheile \u0219i valorile acestor etichete con\u021bin meta-date criptate. Veeam Backup for AWS consider\u0103 instantanele EBS cu meta-date ca fiind instantanee native pentru instan\u021ba EC2.<\/li>\n<li>Dac\u0103 instan\u021ba EC2 a fost deja procesat\u0103 de o politic\u0103 de backup, atunci Veeam Backup for AWS verific\u0103 num\u0103rul punctelor de recuperare din seria de instantanee. Dac\u0103 acesta dep\u0103\u0219e\u0219te limita specificat\u0103 \u00een politic\u0103, atunci cel mai vechi punct este \u0219ters. <i>Not\u0103:<\/i> Politica de stocare \u0219i \u0219tergere automat\u0103 (retention) nu se aplic\u0103 instantaneelor create manual (se refer\u0103 exact la instantanele create separat). Aceste instantanee pot fi \u0219terse, a\u0219a cum este descris <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/backups_remove.html\">aici<\/a><\/noindex>. (Dac\u0103 \u201emanual\u201d se refer\u0103 la lansarea manual\u0103 a politicii \u00een afara programului, atunci pentru instantaneul creat \u00een acest mod, retention va func\u021biona.) <\/li>\n<\/ol>\n<p><\/p>\n<h4>Back-up-uri la nivel de imagine<\/h4>\n<p>\nIat\u0103 cum Veeam Backup for AWS realizeaz\u0103 backup-ul la nivel de imagine:<\/p>\n<ol>\n<li>Mai \u00eent\u00e2i, se fac instantanee ale volumelor EBS ata\u0219ate acestei instan\u021be.<\/li>\n<li>Veeam Backup for AWS folose\u0219te snapshot-uri EBS ca surse pentru backup. Dup\u0103 finalizarea procesului de backup, aceste snapshot-uri sunt \u0219terse.<\/li>\n<li>Apoi, \u00een regiunea AWS \u00een care se afl\u0103 acest instance, se lanseaz\u0103 un worker auxiliar, care ajut\u0103 la procesarea datelor instance-ului EC2.<\/li>\n<li>Din snapshot-urile temporare se creeaz\u0103 volume EBS \u0219i sunt ata\u0219ate la instance-ul worker.<\/li>\n<li>Se cite\u0219te datele din volumele EBS pe instance-ul worker, dup\u0103 care datele sunt transferate \u00een repository-ul S3, unde vor fi stocate \u00een format Veeam.<\/li>\n<li>\u00cen cadrul sesiunii incrementale, Veeam Backup for AWS cite\u0219te meta-datele backup-urilor din repository-ul S3 \u0219i le folose\u0219te pentru a identifica blocurile care s-au modificat de la sesiunea anterioar\u0103. <\/li>\n<li>C\u00e2nd backup-ul este complet, Veeam Backup for AWS \u0219terge snapshot-urile temporare EBS \u0219i instance-ul worker de pe Amazon EC2.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Recuperarea datelor<\/h3>\n<p>\nCu ajutorul Veeam Backup for AWS, se pot restaura datele dup\u0103 cum urmeaz\u0103:<\/p>\n<ul>\n<li>\u00cen loca\u021bia original\u0103, suprascriind instance-ul original. Toate datele de pe acest instance vor fi suprascrise cu cele stocate \u00een backup, iar configura\u021bia instance-ului va fi p\u0103strat\u0103.<\/li>\n<li>\u00centr-o nou\u0103 loca\u021bie, cre\u00e2nd un nou instance. \u00cen acest scenariu \u2014 dac\u0103 alege\u021bi restaurarea \u00eentr-o nou\u0103 loca\u021bie sau cu noi set\u0103ri \u2014 va fi necesar s\u0103 specifica\u021bi parametrii de configura\u021bie care vor fi aplica\u021bi instance-ului la finalizarea restaur\u0103rii:\n<ul>\n<li>Regiunea<\/li>\n<li>Set\u0103rile de criptare<\/li>\n<li>Numele \u0219i tipul instance-ului<\/li>\n<li>Set\u0103rile de re\u021bea: Virtual Private Cloud (VPC), subre\u021bea, grup de securitate<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><\/p>\n<h4>Restaurarea volumelor<\/h4>\n<p>Se suport\u0103, de asemenea, restaurarea volumelor instance-ului EC2 dintr-un snapshot sau dintr-un backup, \u00een loca\u021bia original\u0103 sau \u00eentr-o nou\u0103 loca\u021bie. \u00cen cazul celei din urm\u0103, pentru noua loca\u021bie, va trebui s\u0103 specifica\u021bi regiunea AWS, Zona de disponibilitate \u0219i al\u021bi parametri. <\/p>\n<p>\u00cen procesul de restaurare, se implic\u0103 de asemenea un worker. <\/p>\n<p>Procesul este sumarizat astfel (\u00een exemplul restaur\u0103rii din backup):<\/p>\n<ol>\n<li>Veeam Backup for AWS lanseaz\u0103 un worker \u00een regiunea AWS dorit\u0103, creeaz\u0103 cantitatea necesar\u0103 de volume EBS goale \u0219i le ata\u0219eaz\u0103 la instance-ul worker. <\/li>\n<li>Restaureaz\u0103 datele din backup pe aceste volume.<\/li>\n<li>Detaseaz\u0103 volumele EBS \u0219i le mut\u0103 \u00een loca\u021bia dorit\u0103 (original\u0103 sau alta regiune AWS), unde aceste volume sunt p\u0103strate ca separate. <\/li>\n<li>\u0218terge instance-ul worker la finalizarea opera\u021biunilor.<br \/>\n <i>Not\u0103:<\/i> Nu uita\u021bi c\u0103, dup\u0103 restaurarea volumului, acesta nu va fi ata\u0219at automat la instan\u021ba EC2 (va fi salvat pur \u0219i simplu \u00een loca\u021bia specificat\u0103 ca un volum EBS separat).<\/li>\n<\/ol>\n<p><\/p>\n<h4>Restaurare fi\u0219iere<\/h4>\n<p>\nPermite restaurarea fi\u0219ierelor individuale f\u0103r\u0103 a fi necesar\u0103 restaurarea \u00eentregii instan\u021be. <\/p>\n<p>C\u00e2nd ini\u021bia\u021bi restaurarea la nivel de fi\u0219iere, ob\u021bine\u021bi un URL (bazat pe numele DNS public al workerului), prin care pute\u021bi vizualiza \u00eentreaga structur\u0103 a fi\u0219ierelor pe sistemul de operare asociat, g\u0103si\u021bi fi\u0219ierele dorite \u0219i le desc\u0103rca\u021bi pe ma\u0219ina local\u0103. <br \/>\nDe asemenea, pentru asigurarea securit\u0103\u021bii, pute\u021bi verifica certificatul \u0219i amprenta acestuia, pentru a v\u0103 asigura c\u0103 nu exist\u0103 un atac MiTM.<\/p>\n<p><img decoding=\"async\" alt=\"\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/7205b4f5385ae0505ea287d689a9d6d9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Integrarea cu Veeam Backup &amp; Replication<\/h3>\n<p>\nDac\u0103 \u00een infrastructura dumneavoastr\u0103 este implementat Veeam Backup &amp; Replication, pute\u021bi configura restaurarea ma\u0219inilor sale \u00een cloud-ul Amazon EC2 folosind func\u021bionalitatea Direct Restore to AWS \u0219i apoi proteja aceste date cloud cu Veeam Backup for AWS. <br \/>\nDe asemenea, se suport\u0103 utilizarea Veeam Backup &amp; Replication cu repositoarele Amazon S3, care sunt create de Veeam Backup for AWS - pute\u021bi restaura copii de rezerv\u0103 ale instan\u021belor Amazon EC2 \u00een infrastructura on-premises.<\/p>\n<h3>Caracteristici ale versiunii gratuite<\/h3>\n<p>\nVersiunea gratuit\u0103 Veeam Backup for AWS permite backup-ul a p\u00e2n\u0103 la 10 instan\u021be EC2; restaurarea din copiile de rezerv\u0103 se efectueaz\u0103 f\u0103r\u0103 restric\u021bii. <br \/>\n<i>Not\u0103: <\/i>Recomandat s\u0103 folosi\u021bi <i>t2.medium<\/i>.<\/p>\n<p>Costul estimativ al resurselor este de 9.8 USD\/lun\u0103, baz\u00e2ndu-se pe utilizarea continu\u0103 cu urm\u0103toarele set\u0103ri implicite:<\/p>\n<ul>\n<li>EC2 - 1 instan\u021b\u0103 t3.micro<\/li>\n<li>EBS - 1 volum GP2 de 8 GB<\/li>\n<li>Configurare pentru repositoarele S3 - 50 GB stocare Standard S3, 13 000 cereri S3 PUT, 10 000 cereri S3 GET, utilizare S3 Select de 50 GB<\/li>\n<\/ul>\n<p><\/p>\n<h3>Linkuri utile<\/h3>\n<p>\nSolu\u021bia Veeam Backup for AWS pe <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/marketplace\/pp\/B081VXF1Q9\">AWS Marketplace<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/overview.html?ver=10\">Manualul utilizatorului<\/a><\/noindex> (\u00een limba englez\u0103).<br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/veeam\/blog\/481926\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u043d\u0430\u0447\u0430\u043b\u0435 \u0434\u0435\u043a\u0430\u0431\u0440\u044f \u0432\u044b\u0448\u043b\u043e \u0432 \u0441\u0432\u0435\u0442 \u043d\u043e\u0432\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 Veeam Backup for AWS \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440 Amazon Elastic Compute Cloud (Amazon EC2). \u0421 \u0435\u0433\u043e \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u043c\u043e\u0436\u043d\u043e \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u0442\u044c \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u0435 \u043a\u043e\u043f\u0438\u0438 \u0438\u043d\u0441\u0442\u0430\u043d\u0441\u043e\u0432 \u0415\u04212 \u0438 \u0441\u043e\u0445\u0440\u0430\u043d\u044f\u0442\u044c \u0438\u0445 \u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u043e\u043c \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 Amazon Simple Storage Service (Amazon S3), \u0442\u0430\u043a\u0436\u0435 \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u0442\u044c \u0446\u0435\u043f\u043e\u0447\u043a\u0438 \u0441\u043d\u0430\u043f\u0448\u043e\u0442\u043e\u0432 \u0415\u04212 \u0432 \u043d\u0430\u0442\u0438\u0432\u043d\u043e\u043c \u0444\u043e\u0440\u043c\u0430\u0442\u0435. \u0414\u043b\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-54466","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u043d\u0430\u0447\u0430\u043b\u0435 \u0434\u0435\u043a\u0430\u0431\u0440\u044f \u0432\u044b\u0448\u043b\u043e \u0432 \u0441\u0432\u0435\u0442 \u043d\u043e\u0432\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 Veeam Backup for AWS \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440 Amazon Elastic Compute Cloud (Amazon EC2).\" \/>\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\/znakomtes-novoe-reshenie-veeam-backup-for-aws\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\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\u0417\u043d\u0430\u043a\u043e\u043c\u044c\u0442\u0435\u0441\u044c: \u043d\u043e\u0432\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 Veeam Backup for AWS | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u043d\u0430\u0447\u0430\u043b\u0435 \u0434\u0435\u043a\u0430\u0431\u0440\u044f \u0432\u044b\u0448\u043b\u043e \u0432 \u0441\u0432\u0435\u0442 \u043d\u043e\u0432\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 Veeam Backup for AWS \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440 Amazon Elastic Compute Cloud (Amazon EC2).\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws\" \/>\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-12-26T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:02:28+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\udd47\u00cent\u00e2lni\u021bi: noua solu\u021bie Veeam Backup for AWS | ProHoster","description":"La \u00eenceputul lunii decembrie, a fost lansat\u0103 o nou\u0103 solu\u021bie Veeam Backup for AWS pentru backup \u0219i restaurare a infrastructurilor cloud Amazon Elastic Compute Cloud (Amazon EC2).","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","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\u0417\u043d\u0430\u043a\u043e\u043c\u044c\u0442\u0435\u0441\u044c: \u043d\u043e\u0432\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 Veeam Backup for AWS | ProHoster","og:description":"\u0412 \u043d\u0430\u0447\u0430\u043b\u0435 \u0434\u0435\u043a\u0430\u0431\u0440\u044f \u0432\u044b\u0448\u043b\u043e \u0432 \u0441\u0432\u0435\u0442 \u043d\u043e\u0432\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 Veeam Backup for AWS \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440 Amazon Elastic Compute Cloud (Amazon EC2).","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","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-12-26T21:00:00+00:00","article:modified_time":"2020-02-18T11:02:28+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"54466","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 11:28:21","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:05:06","updated":"2026-01-24 11:28:21","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\/54466","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=54466"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/54466\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=54466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=54466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=54466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}