{"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\/sq\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","title":{"rendered":"Njihuni me zgjidhjen e re Veeam Backup for AWS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>N\u00eb fillim t\u00eb dhjetorit doli n\u00eb treg nj\u00eb zgjidhje e re <b>Veeam Backup for AWS<\/b> p\u00ebr kopjimin dhe rikuperimin e infrastrukturave t\u00eb cloud-it Amazon Elastic Compute Cloud (Amazon EC2). <\/p>\n<p>Me ndihm\u00ebn e saj, mund t\u00eb krijoni kopje rezerv\u00eb t\u00eb instanceve EC2 dhe t'i ruani ato n\u00eb hap\u00ebsir\u00ebn e magazinimit t\u00eb cloud-it Amazon Simple Storage Service (Amazon S3), si dhe t\u00eb krijoni rrjeta snapshots EC2 n\u00eb formatin e natyrsh\u00ebm. <\/p>\n<p>P\u00ebr rikuperimin e t\u00eb dh\u00ebnave, Veeam Backup for AWS ofron opsionet e m\u00ebposhtme: <\/p>\n<ul>\n<li>Rikuperimin e plot\u00eb t\u00eb nj\u00eb instance EC2<\/li>\n<li>Rikuperimin e volumin t\u00eb nj\u00eb instance<\/li>\n<li>Rikuperimin e skedar\u00ebve dhe dosjeve t\u00eb sistemit operativ t\u00eb instanc\u00ebs<\/li>\n<\/ul>\n<p>\nP\u00ebrve\u00e7 k\u00ebsaj, p\u00ebr shkak se zgjidhja krijon kopje rezerv\u00eb n\u00eb formatin Veeam, mund t\u00eb angazhohet Veeam Backup &amp; Replication p\u00ebr t\u00eb ruajtur kopje t\u00eb kopjeve rezerv\u00eb t\u00eb EC2 n\u00eb depozita on-premises dhe m\u00eb pas t\u00eb kryhen migrime t\u00eb t\u00eb dh\u00ebnave midis infrastrukturave cloud, virtuale dhe on-premises. <\/p>\n<p>Dhe, padyshim, p\u00ebrdoruesit do t\u00eb g\u00ebzohen nga prania e nj\u00eb versioni falas t\u00eb zgjidhjes s\u00eb re. P\u00ebr nj\u00eb njohje m\u00eb t\u00eb detajuar me Veeam Backup for AWS, ju mir\u00ebpritur n\u00ebn k\u00ebt\u00eb seksion.<\/p>\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re 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>P\u00ebrgjegj\u00ebsi kryesore<\/h3>\n<p>\nP\u00ebrve\u00e7 mund\u00ebsive tashm\u00eb t\u00eb p\u00ebrmendura p\u00ebr krijimin automatik t\u00eb snapshots Amazon EBS dhe ruajtjen e kopjeve n\u00eb Amazon S3 cloud, zgjidhja implementon:<\/p>\n<ul>\n<li>Autentifikimi me shum\u00eb faktor\u00eb p\u00ebr administrator\u00ebt e kopjave rezerv\u00eb<\/li>\n<li>Mbrojtja e t\u00eb dh\u00ebnave n\u00eb baz\u00eb t\u00eb politikave<\/li>\n<li>Mb\u00ebshtetje p\u00ebr ndarjen e roleve IAM<\/li>\n<li>Mb\u00ebshtetje p\u00ebr konfigurime nd\u00ebr-rajonale<\/li>\n<li>Algoritmi i ngulitur i vler\u00ebsimit paraprak t\u00eb kostove t\u00eb sh\u00ebrbimeve q\u00eb ndihmon n\u00eb kontrollin e pages\u00ebs.<\/li>\n<\/ul>\n<p>\nDhe ashtu si\u00e7 u p\u00ebrmend m\u00eb par\u00eb, ka nj\u00eb licenc\u00eb falas, BYOL (nd\u00ebrto licenc\u00ebn t\u00ebnde), dhe nj\u00eb licenc\u00eb t\u00eb bazuar n\u00eb p\u00ebrdorimin e burimeve \u2014 secili mund t\u00eb zgjedh\u00eb at\u00eb q\u00eb i p\u00ebrshtatet.<\/p>\n<h3>Hapat e pun\u00ebs<\/h3>\n<p>\nN\u00ebse flasim shkurt, hapat kryesor\u00eb jan\u00eb si m\u00eb posht\u00eb:<\/p>\n<ol>\n<li>Kontrollojm\u00eb infrastruktur\u00ebn ton\u00eb p\u00ebr p\u00ebrputhshm\u00ebrin\u00eb me k\u00ebrkesat sistemike q\u00eb jan\u00eb p\u00ebrshkruar <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/system_requirements.html?ver=10\">k\u00ebtu<\/a><\/noindex>. <\/li>\n<li>Instalojm\u00eb Veeam Backup p\u00ebr AWS, si\u00e7 p\u00ebrshkruhet m\u00eb posht\u00eb.<\/li>\n<li>Specifikojm\u00eb rolet IAM. Ato jan\u00eb t\u00eb nevojshme p\u00ebr qasje n\u00eb burimet AWS q\u00eb jan\u00eb t\u00eb angazhuara n\u00eb kopjimin dhe rikuperimin:\n<ul>\n<li>N\u00ebse planifikoni t\u00eb b\u00ebni kopje rezerv\u00eb instancash EC2 brenda nj\u00eb llogarie AWS, mund t\u00eb p\u00ebrdorni rolin <i>Default Backup Restore<\/i> \u2014 ai krijohet gjat\u00eb instalimit t\u00eb Veeam Backup p\u00ebr AWS. Ky rol ka t\u00eb drejtat e nevojshme p\u00ebr qasje n\u00eb t\u00eb gjitha instancat EC2 dhe kov\u00ebt S3 brenda llogaris\u00eb AWS, ku \u00ebsht\u00eb nd\u00ebrtuar Veeam Backup p\u00ebr AWS (llogaria fillestare AWS).<\/li>\n<li>N\u00ebse po planifikoni t\u00eb b\u00ebni kopje t\u00eb dh\u00ebnash ose t\u00eb rikuperoni t\u00eb dh\u00ebnat e instancave EC2 midis dy llogarive t\u00eb ndryshme AWS ose d\u00ebshironi t\u00eb p\u00ebrdorni nj\u00eb rol t\u00eb dedikuar IAM me setin minimal t\u00eb t\u00eb drejtave p\u00ebr \u00e7do operacion, do t\u00eb duhet t\u00eb krijoni rolet e nevojshme IAM brenda llogaris\u00eb fillestare AWS dhe pastaj t'i shtoni ato n\u00eb Veeam Backup for AWS. Kjo \u00ebsht\u00eb shpjeguar n\u00eb detaje n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/iam_roles_add.html?ver=10\">dokumentacion<\/a><\/noindex>. <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Po konfiguroni infrastruktur\u00ebn e kopjimeve rezerv\u00eb, konkretisht:\n<ul>\n<li>Po konfigurojm\u00eb depo S3.\n<p><i>Sh\u00ebnim:<\/i> N\u00ebse do t\u00eb p\u00ebrdorni snapshot-e t\u00eb krijuara natyrsh\u00ebm p\u00ebr mbrojtjen e t\u00eb dh\u00ebnave dhe jo kopje rezerv\u00eb, at\u00ebher\u00eb k\u00ebt\u00eb pjes\u00eb mund ta kaloni, pasi depo S3 nuk do t\u00eb nevojitet n\u00eb k\u00ebt\u00eb skenar. \n <\/li>\n<li>Po p\u00ebrcaktojm\u00eb cil\u00ebsimet e rrjetit p\u00ebr komponent\u00ebt ndihm\u00ebs <i>worker instances<\/i>.<br \/>\n<i>Workers<\/i> jan\u00eb instanca ndihm\u00ebse EC2 n\u00ebn sistemin operativ Linux. Ato aktivizohen vet\u00ebm gjat\u00eb procesit t\u00eb kopjimit (ose rikuperimit) dhe sh\u00ebrbejn\u00eb si bkp-proxy. N\u00eb cil\u00ebsimet e pun\u00ebtor\u00ebve do t\u00eb duhet t\u00eb p\u00ebrcaktoni Amazon VPC, n\u00ebnrrjetin dhe grupin e siguris\u00eb, me t\u00eb cilat do t\u00eb lidhen k\u00ebto instanca ndihm\u00ebse. M\u00eb shum\u00eb rreth k\u00ebtyre mund t\u00eb lexoni <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/workers.html?ver=10\">k\u00ebtu<\/a><\/noindex>.\n <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Pastaj krijojm\u00eb nj\u00eb politik\u00eb mbi t\u00eb cil\u00ebn do t\u00eb krijohen kopje rezerv\u00eb ose snapshote t\u00eb instancave EC2. P\u00ebr k\u00ebt\u00eb do t\u00eb flas shkurtimisht m\u00eb posht\u00eb.<\/li>\n<li>Nga kopja rezerv\u00eb mund t\u00eb kryhet nj\u00eb rikuperim \u2014 p\u00ebr k\u00ebt\u00eb gjithashtu pak m\u00eb posht\u00eb. <\/li>\n<\/ol>\n<p><\/p>\n<h3>Zhvillimi dhe konfigurimi<\/h3>\n<p>\nVeeam Backup p\u00ebr AWS \u00ebsht\u00eb i disponuesh\u00ebm n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/marketplace\/pp\/B081VXF1Q9\">AWS Marketplace<\/a><\/noindex>. <\/p>\n<p>Zhvillimi i zgjidhjes kryhet k\u00ebshtu:<\/p>\n<ol>\n<li>Hyni n\u00eb AWS Marketplace me llogarin\u00eb AWS, t\u00eb cil\u00ebn planifikoni t\u00eb p\u00ebrdorni p\u00ebr instalimin e zgjidhjes.<\/li>\n<li>Hapni faqen Veeam Backup p\u00ebr AWS, zgjidhni redaktimin q\u00eb na nevojitet (tashti ose falas). M\u00eb shum\u00eb detaje rreth redaksive jan\u00eb shkruar <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/lic.html\">k\u00ebtu<\/a><\/noindex>.\n<ul>\n<li>Veeam Backup p\u00ebr AWS Free Edition<\/li>\n<li>Veeam Backup p\u00ebr AWS Paid Edition<\/li>\n<li>Veeam Backup p\u00ebr AWS BYOL Edition<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>N\u00eb t\u00eb djatht\u00ebn lart klikoni <b>Continue to Subscribe<\/b>.\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/bee5554b53ed411789b31d178d4f4875.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>N\u00eb faqen e regjistrimit shkojm\u00eb te seksioni <b>Terms and Conditions<\/b> (kushtet e p\u00ebrdorimit) dhe atje klikoni <b>Show Details<\/b>, m\u00eb pas n\u00eb lidhjen <b>End User License Agreement<\/b> lexojm\u00eb marr\u00ebveshjen e licenc\u00ebs. <\/li>\n<li>M\u00eb pas, klikojm\u00eb butonin <b>Continue to Configuration<\/b> dhe fillojm\u00eb konfigurimin.\n<\/li>\n<li>N\u00eb faqe <b>Configure this software<\/b> p\u00ebrshkruajm\u00eb cil\u00ebsimet p\u00ebr instalimin:\n<ul>\n<li>Nga lista <b>Fulfillment Option<\/b> (opsionet e zhvillimit) zgjidhni opsionin p\u00ebr produktin ton\u00eb \u2014 <b>VB p\u00ebr AWS Deployment<\/b>.<\/li>\n<li>Nga lista e versioneve <b>Software Version<\/b> zgjidhni versionin m\u00eb t\u00eb ri t\u00eb Veeam Backup p\u00ebr AWS.<\/li>\n<li>Nga lista e rajoneve <b>Region<\/b> zgjidhni rajonin AWS ku do t\u00eb derdhet instanca EC2 me Veeam Backup p\u00ebr AWS.<\/li>\n<\/ul>\n<p>\n<i>Sh\u00ebnim: <\/i>M\u00eb shum\u00eb rreth rajoneve AWS mund t\u00eb lexoni <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/using-regions-availability-zones.html\">k\u00ebtu<\/a><\/noindex>.\n<\/li>\n<li>M\u00eb pas, klikojm\u00eb butonin <b>Vazhdo p\u00ebr t\u00eb Nisur<\/b> p\u00ebr t\u00eb kaluar n\u00eb nisje.\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/9264144271e73d7ad8dcb303340ae4d3.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>N\u00eb faqe <b>Nisni k\u00ebt\u00eb software<\/b> kryejm\u00eb k\u00ebto hapa:\n<ul>\n<li>N\u00eb seksionin <b>Detajet e Konfigurimit<\/b> verifikojm\u00eb n\u00ebse t\u00eb gjitha cil\u00ebsimet jan\u00eb sakt\u00ebsisht t\u00eb nxjerra.<\/li>\n<li>Nga lista e veprimeve <b>Zgjidhni Veprimin<\/b> zgjedhim <b>Nis CloudFormation<\/b>.<\/li>\n<li>Instalimi i Veeam Backup p\u00ebr AWS b\u00ebhet p\u00ebrmes stakut AWS CloudFormation.\n<p><i>Sh\u00ebnim: <\/i>K\u00ebtu staku \u00ebsht\u00eb nj\u00eb grup burimesh cloud q\u00eb mund t\u00eb menaxhohen si nj\u00eb nj\u00ebsie t\u00eb vetme: krijoni, fshini, p\u00ebrdorni p\u00ebr t\u00eb nisur aplikacione. M\u00eb shum\u00eb mund t\u00eb lexoni n\u00eb dokumentacionin e AWS.<\/p>\n<p>Klikoni <b>Nisni<\/b> dhe nisni mjetin p\u00ebr krijimin e stakut <b>Mjeti p\u00ebr krijimin e stakut<\/b>.<\/li>\n<\/ul>\n<p>\n<\/li>\n<\/ol>\n<p>\n<b class=\"spoiler_title\">Krijimi i stakut AWS CloudFormation<\/b>Krijimi i stakut AWS CloudFormation:<\/p>\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re 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>N\u00eb hap <b>Specifikoni modelin<\/b> mund t\u00eb lini cil\u00ebsimet e modelit t\u00eb stakut si\u00e7 jan\u00eb. \n<\/li>\n<li>N\u00eb hap <b>Specifikoni detajet e stakut<\/b> nxirni cil\u00ebsimet p\u00ebr stakun ton\u00eb.\n<ul>\n<li>N\u00eb fush\u00ebn <b>Emri i stakut<\/b> jepni nj\u00eb em\u00ebr; mund t\u00eb p\u00ebrdorni shkronja t\u00eb madha dhe t\u00eb vogla, numra dhe copa.<\/li>\n<li>N\u00eb seksionin e cil\u00ebsimeve <b>Konfigurimi i Instanc\u00ebs<\/b>:<br \/>\n Nga lista <b>Tipi i instanc\u00ebs p\u00ebr serverin Veeam Backup p\u00ebr AWS<\/b> duhet t\u00eb zgjidhni tipin e instanc\u00ebs EC2, n\u00eb t\u00eb cilin do t\u00eb instalohet Veeam Backup p\u00ebr AWS (m\u00eb pas do ta quajm\u00eb <i>serveri Veeam Backup p\u00ebr AWS<\/i>). Rekomandohet t\u00eb zgjidhni tipin <i>t2.medium<\/i>.<br \/>\n Nga lista <b>\u00c7ift \u00c7el\u00ebsash p\u00ebr Serverin Veeam Backup p\u00ebr AWS<\/b> duhet t\u00eb zgjidhni nj\u00eb \u00e7ift \u00e7el\u00ebsash q\u00eb do t\u00eb p\u00ebrdoren p\u00ebr autentifikimin n\u00eb k\u00ebt\u00eb server t\u00eb ri. N\u00ebse \u00e7el\u00ebsi i k\u00ebrkuar nuk \u00ebsht\u00eb n\u00eb list\u00eb, duhet ta krijoni sipas p\u00ebrshkrimit <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/ec2-key-pairs.html\">k\u00ebtu<\/a><\/noindex>. <br \/>\n Specifikoni n\u00ebse duhet t\u00eb p\u00ebrfshihet nj\u00eb kopje e automatizuar e v\u00ebllimeve EBS p\u00ebr serverin Veeam Backup for AWS (m\u00ebnyra default \u00ebsht\u00eb po, do thot\u00eb) <i>e v\u00ebrtet\u00eb<\/i>).<br \/>\n Specifikoni n\u00ebse duhet t\u00eb rindezni serverin Veeam Backup for AWS n\u00eb rast t\u00eb d\u00ebshtimit t\u00eb softuerit.<br \/>\n Specifikoni n\u00ebse duhet t\u00eb rindezni serverin Veeam Backup for AWS n\u00eb rast t\u00eb d\u00ebshtimit t\u00eb infrastruktur\u00ebs.\n<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>N\u00eb seksionin e konfigurimit t\u00eb rrjetit <b>Konfigurimi i Rrjetit<\/b>:\n<ul>\n<li>Specifikoni n\u00ebse nevojitet krijimi i nj\u00eb adrese Elastic IP p\u00ebr serverin Veeam Backup for AWS. M\u00eb shum\u00eb detaje mund t\u00eb gjenden k\u00ebtu.<\/li>\n<li>N\u00eb fush\u00ebn <b>IP Adresat e Lejuara p\u00ebr lidhjen me SSH<\/b> specifikoni intervalin e adresave IPv4 nga t\u00eb cilat do t\u00eb lejohet akses n\u00eb serverin Veeam Backup for AWS p\u00ebrmes SSH.<\/li>\n<li>N\u00eb fush\u00ebn <b>IP Adresat e Lejuara p\u00ebr lidhjen me HTTPS<\/b> specifikoni intervalin e adresave IPv4 nga t\u00eb cilat do t\u00eb lejohet akses n\u00eb nd\u00ebrfaqen web t\u00eb Veeam Backup for AWS.<br \/>\n Intervali i adresave IPv4 sh\u00ebnohet n\u00eb notacionin CIDR (p\u00ebr shembull, 12.23.34.0\/24). P\u00ebr t\u00eb lejuar aksesin nga t\u00eb gjitha adresat IPv4, mund t\u00eb vendosni 0.0.0.0\/0. (Megjithat\u00eb, kjo mund\u00ebsi nuk rekomandohet, pasi zvog\u00eblon sigurin\u00eb e infrastruktur\u00ebs.)<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Bazuar n\u00eb adresat IPv4 t\u00eb dh\u00ebna, AWS CloudFormation krijon nj\u00eb grup sigurie p\u00ebr Veeam Backup for AWS, me rregulla p\u00ebr trafikun e ardhsh\u00ebm p\u00ebr SSH dhe HTTPS. (S\u00eb pari, p\u00ebr trafikun e ardhsh\u00ebm p\u00ebr SSH p\u00ebrdoret porta 22, nd\u00ebrsa p\u00ebr HTTPS - porta 443.) N\u00ebse planifikoni t\u00eb specifikoni nj\u00eb grup tjet\u00ebr sigurie p\u00ebr Veeam Backup for AWS gjat\u00eb instalimit, sigurohuni t\u00eb shtoni manualisht rregullat e nevojshme n\u00eb k\u00ebt\u00eb grup dhe kontrolloni q\u00eb t\u00eb jet\u00eb lejuar qasja n\u00eb sh\u00ebrbimet AWS (t\u00eb specifikuara n\u00eb seksionin K\u00ebrkesat t\u00eb udh\u00ebzimeve t\u00eb p\u00ebrdoruesit).<\/li>\n<li>N\u00eb seksionin <b>VPC dhe Subnet<\/b> duhet t\u00eb zgjidhni Amazon Virtual Private Cloud (Amazon VPC) dhe subnet-in, me t\u00eb cilin do t\u00eb lidhet serveri Veeam Backup for AWS.\n<\/li>\n<li>N\u00eb hap <b>Konfiguro opsionet e grumbullit<\/b> specifikoni etiketat AWS, lejet p\u00ebr rolin IAM dhe cil\u00ebsime t\u00eb tjera t\u00eb grumbullit.\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/31062236b5ddf46ab22cd69a18c2cf06.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>N\u00eb hap <b>Rishiko<\/b> kontrolloni t\u00eb gjitha cil\u00ebsimet, zgjidhni opsionin <b>E pranoj se AWS CloudFormation mund t\u00eb krijoj\u00eb burime IAM<\/b> dhe klikoni <b>Krijo grumbull<\/b>.<\/li>\n<\/ol>\n<p>Pas instalimit, hapni konsol\u00ebn e web-it duke shkruar n\u00eb shfletues DNS-n\u00eb ose adres\u00ebn IP t\u00eb instanc\u00ebs EC2, ku \u00ebsht\u00eb instaluar Veeam Backup for AWS, p\u00ebr shembull:<br \/>\n<code>https:\/\/ec2-135-169-170-192.eu-central-1.compute.amazonaws.com<\/code><\/p>\n<p>Konsola tregon burimet p\u00ebr t\u00eb cilat \u00ebsht\u00eb konfiguruar mbrojtja e t\u00eb dh\u00ebnave me Veeam Backup for AWS:<\/p>\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/eb7ed2550eb15398c8c0732e1c2b7f52.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nCil\u00ebsimet e nevojshme t\u00eb infrastruktur\u00ebs, rolet, etj. jan\u00eb p\u00ebrshkruar n\u00eb detaje n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/configuration.html?ver=10\">dokumentacion<\/a><\/noindex>.<\/p>\n<h3>Politikat e backup-it<\/h3>\n<p>\nP\u00ebr mbrojtjen e instancave krijojm\u00eb politika. <\/p>\n<p>P\u00ebr lloje t\u00eb ndryshme objektesh mund t\u00eb konfiguroni politika t\u00eb ndryshme: p\u00ebr shembull, politika e destinuar p\u00ebr mbrojtjen e aplikacioneve tier 3 (m\u00eb pak kritike), ose politikat p\u00ebr aplikacionet tier 2 dhe tier 1. N\u00eb cil\u00ebsimet e politik\u00ebs specifikoni:<\/p>\n<ul>\n<li>Llogarin\u00eb me role IAM<\/li>\n<li>Rajonet \u2014 mund t\u00eb zgjidhni disa <\/li>\n<li>\u00c7far\u00eb planifikohet t\u00eb mbrohet \u2014 mund t\u00eb jen\u00eb t\u00eb gjitha burimet (all resources) ose instanca t\u00eb zgjedhura ose (etiketat)<\/li>\n<li>Burimet q\u00eb duhet t\u00eb p\u00ebrjashtohen<\/li>\n<li>Cil\u00ebsimet e snapshots, p\u00ebrfshir\u00eb n\u00ebse duhet t\u00eb p\u00ebrdoren snapshots dhe cila duhet t\u00eb jet\u00eb koh\u00ebzgjatja e ruajtjes<\/li>\n<li>Cil\u00ebsimet e kopjes s\u00eb siguris\u00eb: rruga n\u00eb depo, orar dhe koh\u00ebzgjatja e ruajtjes<\/li>\n<li>Vler\u00ebsimin e kostove t\u00eb sh\u00ebrbimeve (p\u00ebr k\u00ebt\u00eb m\u00eb posht\u00eb)<\/li>\n<li>Cil\u00ebsimet e orarit dhe njoftimeve<\/li>\n<\/ul>\n<p><\/p>\n<h4>Vler\u00ebsim i integruar i kostove t\u00eb sh\u00ebrbimeve<\/h4>\n<p>\nN\u00eb zgjidhjen Veeam Backup for AWS \u00ebsht\u00eb e integruar nj\u00eb vler\u00ebsim automatik i kostove t\u00eb sh\u00ebrbimeve \u2014 p\u00ebrmes saj llogaritet menj\u00ebher\u00eb se \u00e7far\u00eb do t\u00eb jet\u00eb kostoja e sh\u00ebrbimeve t\u00eb kopjimit sipas politik\u00ebs specifike. N\u00eb llogaritje p\u00ebrfshihen metrika t\u00eb m\u00ebtejshme:<\/p>\n<ul>\n<li>Kostoja e kopjimit<\/li>\n<li>Kostoja e snapshots<\/li>\n<li>Kostoja e trafikimit \u00ebsht\u00eb ve\u00e7an\u00ebrisht e r\u00ebnd\u00ebsishme n\u00ebse repositori ndodhet jasht\u00eb rajonit ku funksionojn\u00eb objektet e infrastruktur\u00ebs (Amazon AWS llogarit trafikimin n\u00eb rajone t\u00eb tjera).<\/li>\n<li>Kostoja e transaksioneve<\/li>\n<li>Kostoja totale<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/d81df948587d769241c58887ed8769cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nT\u00eb dh\u00ebnat mund t\u00eb eksportohen n\u00eb nj\u00eb skedar CSV ose XML.<\/p>\n<h3>Komponent\u00ebt ndihm\u00ebs \u2014 Workers<\/h3>\n<p>\nP\u00ebr t\u00eb zvog\u00ebluar shpenzimet p\u00ebr trafik, \u00ebsht\u00eb e mundur t\u00eb konfiguroni krijimin automatik t\u00eb komponent\u00ebve ndihm\u00ebs \u2014 <b>workers<\/b> \u2014 n\u00eb t\u00eb nj\u00ebjtin rajon AWS ku ndodhen objektet e mbrojtura. Workers aktivizohen automatikisht vet\u00ebm gjat\u00eb transmetimit t\u00eb t\u00eb dh\u00ebnave nga\/n\u00eb cloud Amazon S3 ose gjat\u00eb rikuperimit, dhe pas p\u00ebrfundimit t\u00eb operacioneve, ata fik\u00ebn dhe fshihen.<\/p>\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/0926f91f39f09f77e4f4511d1a6d02f9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Kopjimi<\/h3>\n<p>\nP\u00ebr operacionet e rezervimit, Veeam Backup p\u00ebr AWS p\u00ebrfshin snapshot-et native (shih. <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/EBSSnapshots.html\">Amazon EBS snapshots<\/a><\/noindex>). Gjat\u00eb backup-it, Veeam Backup p\u00ebr AWS p\u00ebrdor komandat AWS CLI p\u00ebr t\u00eb krijuar snapshot-et e volumeve EBS t\u00eb bashkangjitura n\u00eb instanc\u00ebn EC2. M\u00eb pas, var\u00ebsisht nga skenari i rezervimit q\u00eb keni zgjedhur, Veeam Backup p\u00ebr AWS do t\u00eb krijoj\u00eb p\u00ebr instanc\u00ebn EC2 ose nj\u00eb zinxhir snapshot-esh native ose nj\u00eb backup n\u00eb nivel figure.<\/p>\n<h4>Snapshot-et native<\/h4>\n<p>\nVeeam Backup for AWS krijon snapshot natyror t\u00eb instanc\u00ebs EC2 n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb:<\/p>\n<ol>\n<li>S\u00eb pari, merret snapshot i volumeve EBS t\u00eb bashk\u00ebngjitur me k\u00ebt\u00eb instanc\u00eb.<\/li>\n<li>Snapshotet EBS marrin etiketat AWS gjat\u00eb krijimit. \u00c7el\u00ebsat dhe vlerat e k\u00ebtyre etiketimeve p\u00ebrmbajn\u00eb metadata t\u00eb enkriptuara. Veeam Backup for AWS i konsideron snapshotet EBS me metadata si snapshot natyror p\u00ebr instanc\u00ebn EC2.<\/li>\n<li>N\u00ebse instanca EC2 tashm\u00eb \u00ebsht\u00eb procesuar nga politika e backup-it, at\u00ebher\u00eb Veeam Backup for AWS kontrollon numrin e pikave t\u00eb rikuperimit n\u00eb zinxhirin e snapshot-eve. N\u00ebse ai tejkalon kufirin e caktuar n\u00eb politik\u00eb, pika m\u00eb e vjet\u00ebr fshihet. <i>Sh\u00ebnim:<\/i> Politika e ruajtjes dhe fshirjes automatike (retention) nuk zbatohet p\u00ebr snapshotet e krijuara manualisht (n\u00eb kuptimin e plot\u00eb t\u00eb snapshot-eve t\u00eb krijuara ve\u00e7mas). Snapshotet e tilla mund t\u00eb fshihen si\u00e7 \u00ebsht\u00eb p\u00ebrshkruar <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/backups_remove.html\">k\u00ebtu<\/a><\/noindex>. (N\u00ebse n\u00ebnkuptohet si \"me dor\u00eb\" ekzekutimi manual i politik\u00ebs jasht\u00eb orarit, at\u00ebher\u00eb p\u00ebr nj\u00eb snapshot t\u00eb krijuar n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, retention do t\u00eb aplikohen.) <\/li>\n<\/ol>\n<p><\/p>\n<h4>Backupet n\u00eb nivel imazhi<\/h4>\n<p>\nJa se si Veeam Backup for AWS kryen backup n\u00eb nivel imazhi:<\/p>\n<ol>\n<li>S\u00eb pari, merret snapshot i volumeve EBS t\u00eb bashk\u00ebngjitur me k\u00ebt\u00eb instanc\u00eb.<\/li>\n<li>Veeam Backup p\u00ebr AWS p\u00ebrdor snapshot-et EBS si burime p\u00ebr backup. Pasi procesi i kopjimit t\u00eb dh\u00ebnave t\u00eb p\u00ebrfundoj\u00eb, k\u00ebto snapshot-e fshihen.<\/li>\n<li>M\u00eb pas, n\u00eb regionin AWS ku ndodhet ky instanc\u00eb, fillon nj\u00eb worker ndihm\u00ebs q\u00eb ndihmon n\u00eb procesimin e t\u00eb dh\u00ebnave t\u00eb instanc\u00ebs EC2.<\/li>\n<li>Nga snapshot-et e p\u00ebrkohshme krijohen volumet EBS dhe bashkohen me instanc\u00ebn worker.<\/li>\n<li>Lexohen t\u00eb dh\u00ebnat nga volumet EBS n\u00eb instanc\u00ebn worker, pastaj t\u00eb dh\u00ebnat d\u00ebrgohen n\u00eb repository S3, ku do t\u00eb ruhet n\u00eb formatin Veeam.<\/li>\n<li>N\u00eb sesionin inkremental, Veeam Backup p\u00ebr AWS lexon metadat e kopjeve nga repository S3 dhe i p\u00ebrdor ato p\u00ebr t\u00eb identifikuar blloqet q\u00eb jan\u00eb ndryshuar q\u00eb nga sesioni i m\u00ebparsh\u00ebm. <\/li>\n<li>Kur kopjimi i dh\u00ebnave p\u00ebrfundon, Veeam Backup p\u00ebr AWS fshin snapshot-et e p\u00ebrkohshme EBS dhe instanc\u00ebn worker nga Amazon EC2.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Rigjenerimi i t\u00eb dh\u00ebnave<\/h3>\n<p>\nMe ndihm\u00ebn e Veeam Backup p\u00ebr AWS, mund t\u00eb rikuperoni t\u00eb dh\u00ebnat n\u00eb m\u00ebnyrat e m\u00ebposhtme:<\/p>\n<ul>\n<li>N\u00eb vendndodhjen origjinale, duke e rishkruar instanc\u00ebn origjinale. T\u00eb gjitha t\u00eb dh\u00ebnat n\u00eb k\u00ebt\u00eb instanc\u00eb do t\u00eb z\u00ebvend\u00ebsohen me ato q\u00eb ruhen n\u00eb backup, nd\u00ebrsa konfigurimi i instanc\u00ebs ruhet.<\/li>\n<li>N\u00eb nj\u00eb vendndodhje t\u00eb re, duke krijuar nj\u00eb instanc\u00eb t\u00eb re. N\u00eb k\u00ebt\u00eb skenar - n\u00ebse zgjidhni rikuperimin n\u00eb nj\u00eb vendndodhje t\u00eb re ose me cil\u00ebsime t\u00eb reja - do t\u00eb duhet t\u00eb specifikoni parametrat e konfigurimit q\u00eb do t\u00eb aplikohen n\u00eb instanc\u00eb pas p\u00ebrfundimit t\u00eb rikuperimit:\n<ul>\n<li>Rajoni<\/li>\n<li>Cil\u00ebsimet e enkriptimit<\/li>\n<li>Emri dhe lloji i instanc\u00ebs<\/li>\n<li>Cil\u00ebsimet e rrjetit: Virtual Private Cloud (VPC), n\u00ebnshtresa, grupi i siguris\u00eb<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><\/p>\n<h4>Rikuperimi i volumeve<\/h4>\n<p>Rikuperimi i volumeve t\u00eb instanc\u00ebs EC2 nga nj\u00eb snapshot ose nga nj\u00eb kopje e backup-it \u00ebsht\u00eb gjithashtu i mb\u00ebshtetur, n\u00eb vendndodhjen origjinale ose n\u00eb nj\u00eb t\u00eb re. N\u00eb rastin e dyt\u00eb, p\u00ebr vendndodhjen e re duhet t\u00eb specifikoni rajonin AWS, Zon\u00ebn e Disponueshm\u00ebris\u00eb dhe parametrat e tjer\u00eb. <\/p>\n<p>Gjat\u00eb procesit t\u00eb rikuperimit, nj\u00eb worker \u00ebsht\u00eb gjithashtu i angazhuar. <\/p>\n<p>Procesi vet\u00eb p\u00ebrshkruhet shkurtimisht k\u00ebshtu (n\u00eb shembullin e rikuperimit nga backup):<\/p>\n<ol>\n<li>Veeam Backup for AWS nis nj\u00eb worker n\u00eb rajonin e duhur AWS, krijon numrin e nevojsh\u00ebm t\u00eb volumeve t\u00eb zbraz\u00ebt EBS dhe i bashk\u00ebngjitet atyre instanc\u00ebs s\u00eb worker. <\/li>\n<li>Rikuperon t\u00eb dh\u00ebnat nga backup n\u00eb k\u00ebto volume.<\/li>\n<li>Kryen shk\u00ebputjen e volumeve EBS dhe transferimin n\u00eb vendndodhjen e k\u00ebrkuar (origjinale ose nj\u00eb regjion tjet\u00ebr AWS), ku k\u00ebto volume ruhet si t\u00eb ve\u00e7anta. <\/li>\n<li>Fshin instanc\u00ebn worker pas p\u00ebrfundimit t\u00eb operacioneve.<br \/>\n <i>Sh\u00ebnim:<\/i> Mos harroni se, pas rikuperimit, volumi nuk do t\u00eb lidhet automatikisht me instanc\u00ebn EC2 (do t\u00eb ruhet thjesht n\u00eb vendndodhjen e specifikuar si nj\u00eb volum t\u00eb ve\u00e7ant\u00eb EBS).<\/li>\n<\/ol>\n<p><\/p>\n<h4>Rikuperimi i skedar\u00ebve<\/h4>\n<p>\nLejon rikuperimin e skedar\u00ebve t\u00eb ve\u00e7ant\u00eb pa pasur nevoj\u00eb t\u00eb rikuperoni t\u00ebr\u00eb instanc\u00ebn. <\/p>\n<p>Kur t\u00eb inicioni rikuperimin n\u00eb nivel skedari, do t\u00eb merrni nj\u00eb URL (n\u00eb baz\u00eb t\u00eb emrit DNS publik t\u00eb pun\u00ebtorit), p\u00ebrmes s\u00eb cil\u00ebs mund t\u00eb shihni gjith\u00eb struktur\u00ebn e skedar\u00ebve n\u00eb OS-n\u00eb e hostit, t\u00eb gjeni skedar\u00ebt e nevojsh\u00ebm dhe t'i shkarkoni ata n\u00eb makin\u00ebn tuaj lokale. <br \/>\nPo ashtu, p\u00ebr t\u00eb siguruar sigurin\u00eb, mund t\u00eb kontrolloni certifikat\u00ebn dhe gjurm\u00ebn e saj, p\u00ebr t\u00eb siguruar q\u00eb nuk ka MiTM.<\/p>\n<p><img decoding=\"async\" alt=\"Njihuni me zgjidhjen e re Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/7205b4f5385ae0505ea287d689a9d6d9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Integrimi me Veeam Backup &amp; Replication<\/h3>\n<p>\nN\u00ebse n\u00eb infrastruktur\u00ebn tuaj \u00ebsht\u00eb vendosur Veeam Backup &amp; Replication, mund t\u00eb konfiguroni rikuperimin e makinave q\u00eb i p\u00ebrkasin atij n\u00eb cloudin Amazon EC2 duke p\u00ebrdorur funksionalitetin Direct Restore to AWS, dhe m\u00eb pas t\u00eb mbroni k\u00ebto t\u00eb dh\u00ebna n\u00eb cloud me Veeam Backup for AWS. <br \/>\nPo ashtu, mb\u00ebshtetet funksionimi i Veeam Backup &amp; Replication me depozitat Amazon S3, t\u00eb cilat krijon Veeam Backup for AWS - mund t\u00eb rikuperoni kopjet rezerv\u00eb t\u00eb instancave Amazon EC2 n\u00eb infrastruktur\u00ebn on-premises.<\/p>\n<h3>Karakteristikat e versionit falas<\/h3>\n<p>\nVersioni falas i Veeam Backup for AWS lejon t\u00eb b\u00ebni backup deri n\u00eb 10 instanca EC2; rikthimi nga kopjet rezerv\u00eb b\u00ebhet pa kufizime. <br \/>\n<i>Sh\u00ebnim: <\/i>Rekomandohet t\u00eb p\u00ebrdoret <i>t2.medium<\/i>.<\/p>\n<p>Kostoja approximate e burimeve \u00ebsht\u00eb 9.8 USD\/muaj, duke u bazuar n\u00eb p\u00ebrdorimin 24 or\u00eb me konfigurimin default si m\u00eb posht\u00eb:<\/p>\n<ul>\n<li>EC2 \u2014 1 instanc\u00eb t3.micro<\/li>\n<li>EBS \u2014 1 volum GP2 me kapacitet 8 GB<\/li>\n<li>Konfigurimi p\u00ebr depozitimin S3 \u2014 50 GB Standard S3 storage, 13 000 S3 PUT requests, 10 000 S3 GET requests, 50 GB S3 Select usage<\/li>\n<\/ul>\n<p><\/p>\n<h3>Linqe t\u00eb dobishme<\/h3>\n<p>\nZgjidhja Veeam Backup for AWS n\u00eb <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\">Udh\u00ebzuesi i p\u00ebrdoruesit<\/a><\/noindex> (n\u00eb anglisht).<br \/>\n<br \/>Burimi: <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 4.9.10 - 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). \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\" \/>\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\/znakomtes-novoe-reshenie-veeam-backup-for-aws\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\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\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). \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\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/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\udd47Njoftohuni: zgjidhja e re Veeam Backup for AWS | ProHoster","description":"N\u00eb fillim t\u00eb dhjetorit doli n\u00eb treg zgjidhja e re Veeam Backup for AWS p\u00ebr backup dhe rikthim t\u00eb infrastrukturave cloud t\u00eb Amazon Elastic Compute Cloud (Amazon EC2). Me t\u00eb, mund t\u00eb krijoni kopje rezerv\u00eb t\u00eb instancave EC2 dhe t\u2019i ruani ato n\u00eb ruajtjen cloud t\u00eb Amazon Simple Storage Service (Amazon S3), si dhe t\u00eb krijoni zinxhir\u00eb snapshots EC2 n\u00eb formatin natyror. P\u00ebr","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","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\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). \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","og:url":"https:\/\/prohoster.info\/sq\/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"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/54466","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=54466"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/54466\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=54466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=54466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=54466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}