{"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\/cs\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","title":{"rendered":"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Na za\u010d\u00e1tku prosince bylo uvedeno na trh nov\u00e9 \u0159e\u0161en\u00ed <b>Veeam Backup for AWS<\/b> pro z\u00e1lohov\u00e1n\u00ed a obnovu cloudov\u00fdch infrastruktur Amazon Elastic Compute Cloud (Amazon EC2). <\/p>\n<p>S jeho pomoc\u00ed lze vytv\u00e1\u0159et z\u00e1lohy instanc\u00ed EC2 a ukl\u00e1dat je do cloudov\u00e9ho \u00falo\u017ei\u0161t\u011b Amazon Simple Storage Service (Amazon S3), stejn\u011b jako vytv\u00e1\u0159et \u0159et\u011bzce snapshot\u016f EC2 v nativn\u00edm form\u00e1tu. <\/p>\n<p>Pro obnoven\u00ed dat nab\u00edz\u00ed Veeam Backup for AWS n\u00e1sleduj\u00edc\u00ed mo\u017enosti: <\/p>\n<ul>\n<li>Obnoven\u00ed cel\u00e9 instance EC2<\/li>\n<li>Obnoven\u00ed objem\u016f instance<\/li>\n<li>Obnoven\u00ed soubor\u016f a slo\u017eek z hostitelsk\u00e9ho opera\u010dn\u00edho syst\u00e9mu instance<\/li>\n<\/ul>\n<p>\nKrom\u011b toho, jeliko\u017e \u0159e\u0161en\u00ed vytv\u00e1\u0159\u00ed z\u00e1lohy ve form\u00e1tu Veeam, lze vyu\u017e\u00edt Veeam Backup &amp; Replication k uchov\u00e1n\u00ed kopi\u00ed z\u00e1loh EC2 v on-premises repozit\u00e1\u0159\u00edch a pot\u00e9 prov\u00e1d\u011bt migraci dat mezi cloudovou, virtu\u00e1ln\u00ed a on-premises infrastrukturou. <\/p>\n<p>A ur\u010dit\u011b pot\u011b\u0161\u00ed u\u017eivatele skute\u010dnost, \u017ee nov\u00e9 \u0159e\u0161en\u00ed m\u00e1 bezplatnou verzi. Pro podrobn\u011bj\u0161\u00ed sezn\u00e1men\u00ed s Veeam Backup for AWS v\u00e1s v\u00edt\u00e1me pod \u010dl\u00e1nkem.<\/p>\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed 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>Hlavn\u00ed funkce<\/h3>\n<p>\nKrom\u011b ji\u017e zm\u00edn\u011bn\u00fdch funkc\u00ed pro automatick\u00e9 vytv\u00e1\u0159en\u00ed snapshot\u016f Amazon EBS a ulo\u017een\u00ed z\u00e1loh v cloudu Amazon S3 obsahuje \u0159e\u0161en\u00ed tak\u00e9:<\/p>\n<ul>\n<li>V\u00edcef\u00e1zovou autentifikaci pro z\u00e1lohovac\u00ed administr\u00e1tory<\/li>\n<li>Ochranu dat na z\u00e1klad\u011b politik<\/li>\n<li>Podporu d\u011blen\u00ed rol\u00ed IAM<\/li>\n<li>Podporu kros-region\u00e1ln\u00edch konfigurac\u00ed<\/li>\n<li>Vestav\u011bn\u00fd algoritmus pro p\u0159edb\u011b\u017en\u00e9 vyhodnocen\u00ed n\u00e1klad\u016f na provoz slu\u017eeb, kter\u00fd pom\u00e1h\u00e1 \u0159\u00eddit platby.<\/li>\n<\/ul>\n<p>\nA jak ji\u017e bylo zm\u00edn\u011bno, existuje jak bezplatn\u00e1 licence, tak BYOL (vytvo\u0159te si vlastn\u00ed licenci) a licence zalo\u017een\u00e1 na spot\u0159eb\u011b zdroj\u016f \u2014 ka\u017ed\u00fd si m\u016f\u017ee vybrat to vhodn\u00e9.<\/p>\n<h3>Etapy pr\u00e1ce<\/h3>\n<p>\nPokud to shrneme, hlavn\u00ed etapy jsou n\u00e1sleduj\u00edc\u00ed:<\/p>\n<ol>\n<li>Kontrolujeme na\u0161i infrastrukturu na shodu se syst\u00e9mov\u00fdmi po\u017eadavky uveden\u00fdmi <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/system_requirements.html?ver=10\">zde<\/a><\/noindex>. <\/li>\n<li>Instalujeme Veeam Backup for AWS, jak je pops\u00e1no n\u00ed\u017ee.<\/li>\n<li>Uv\u00e1d\u00edme role IAM. Ty jsou pot\u0159ebn\u00e9 pro p\u0159\u00edstup k prost\u0159edk\u016fm AWS zapojen\u00fdm do z\u00e1lohov\u00e1n\u00ed a obnovy:\n<ul>\n<li>Pokud pl\u00e1nujete z\u00e1lohovat instance EC2 v r\u00e1mci jednoho \u00fa\u010dtu AWS, m\u016f\u017eete pou\u017e\u00edt roli <i>Default Backup Restore<\/i> \u2014 ta se vytv\u00e1\u0159\u00ed b\u011bhem instalace Veeam Backup for AWS. Tato role m\u00e1 pot\u0159ebn\u00e1 opr\u00e1vn\u011bn\u00ed pro p\u0159\u00edstup ke v\u0161em instanc\u00edm EC2 a bucket\u016fm S3 v r\u00e1mci \u00fa\u010dtu AWS, kde je nasazen Veeam Backup for AWS (p\u016fvodn\u00ed \u00fa\u010det AWS).<\/li>\n<li>Pokud pl\u00e1nujete z\u00e1lohovat nebo obnovovat data instanc\u00ed EC2 mezi dv\u011bma r\u016fzn\u00fdmi \u00fa\u010dty AWS, nebo chcete pro ka\u017edou operaci pou\u017e\u00edt vyhrazenou roli IAM s minim\u00e1ln\u00edm souborem pr\u00e1v, budete muset vytvo\u0159it pot\u0159ebn\u00e9 role IAM v p\u016fvodn\u00edm \u00fa\u010dtu AWS a pot\u00e9 je p\u0159idat do Veeam Backup for AWS. O tomto se podrobn\u011b hovo\u0159\u00ed v <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/iam_roles_add.html?ver=10\">dokumentaci<\/a><\/noindex>. <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Nastavujeme infrastrukturu z\u00e1lohov\u00e1n\u00ed, konkr\u00e9tn\u011b:\n<ul>\n<li>Konfigurujeme S3 \u00falo\u017ei\u0161t\u011b.\n<p><i>Pozn\u00e1mka:<\/i> Pokud hodl\u00e1te pou\u017e\u00edvat m\u00edsto z\u00e1loh nativn\u011b vytvo\u0159en\u00e9 snapshoty pro ochranu dat, tento krok m\u016f\u017eete p\u0159esko\u010dit, proto\u017ee S3 \u00falo\u017ei\u0161t\u011b v tomto sc\u00e9n\u00e1\u0159i nebude pot\u0159eba. \n <\/li>\n<li>Nastavujeme s\u00ed\u0165ov\u00e9 konfigurace pro pomocn\u00e9 komponenty <i>worker instances<\/i>.<br \/>\n<i>Workers<\/i> \u2014 to jsou pomocn\u00e9 instance EC2 b\u011b\u017e\u00edc\u00ed na syst\u00e9mu Linux. Spou\u0161t\u011bj\u00ed se pouze na dobu z\u00e1lohov\u00e1n\u00ed (nebo obnovy) a slou\u017e\u00ed jako z\u00e1lohovac\u00ed proxy. V nastaven\u00ed pracovn\u00edk\u016f bude pot\u0159eba uv\u00e9st Amazon VPC, pods\u00ed\u0165 a bezpe\u010dnostn\u00ed skupinu, ke kter\u00e9 se tyto pomocn\u00e9 instance p\u0159ipoj\u00ed. O tom v\u0161em si m\u016f\u017eete p\u0159e\u010d\u00edst <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/workers.html?ver=10\">tady<\/a><\/noindex>.\n <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Pot\u00e9 vytvo\u0159\u00edme politiku, na jej\u00edm\u017e z\u00e1klad\u011b budou vytv\u00e1\u0159eny z\u00e1lohy nebo snapshoty instanc\u00ed EC2. O tom stru\u010dn\u011b hovo\u0159\u00edm n\u00ed\u017ee.<\/li>\n<li>Z z\u00e1lohy je mo\u017en\u00e9 prov\u00e9st obnoven\u00ed \u2014 o tom tak\u00e9 trochu n\u00ed\u017ee. <\/li>\n<\/ol>\n<p><\/p>\n<h3>Nasazen\u00ed a konfigurace<\/h3>\n<p>\nVeeam Backup for AWS je dostupn\u00fd na <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/marketplace\/pp\/B081VXF1Q9\">AWS Marketplace<\/a><\/noindex>. <\/p>\n<p>Nasazen\u00ed \u0159e\u0161en\u00ed prob\u00edh\u00e1 takto:<\/p>\n<ol>\n<li>P\u0159ihlaste se do AWS Marketplace pod \u00fa\u010dtem AWS, kter\u00fd pl\u00e1nujeme pou\u017e\u00edt pro instalaci \u0159e\u0161en\u00ed.<\/li>\n<li>Otev\u0159ete str\u00e1nku Veeam Backup for AWS, vyberte po\u017eadovanou edici (placenou nebo bezplatnou). V\u00edce o edic\u00edch je naps\u00e1no <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/lic.html\">tady<\/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>Vpravo naho\u0159e klikn\u011bte na <b>Continue to Subscribe<\/b>.\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/bee5554b53ed411789b31d178d4f4875.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Na str\u00e1nce dokon\u010den\u00ed p\u0159edplatn\u00e9ho p\u0159ejd\u011bte do sekce <b>Terms and Conditions<\/b> (podm\u00ednky pou\u017eit\u00ed) a tam klikn\u011bte na <b>Show Details<\/b>, pot\u00e9 klikn\u011bte na odkaz <b>End User License Agreement<\/b> \u010dt\u011bte licen\u010dn\u00ed smlouvu. <\/li>\n<li>Pak klikn\u011bte na tla\u010d\u00edtko <b>Continue to Configuration<\/b> a p\u0159ejd\u011bte ke konfiguraci.\n<\/li>\n<li>Na str\u00e1nce <b>Configure this software<\/b> nastavte parametry pro instalaci:\n<ul>\n<li>Z nab\u00eddky <b>Fulfillment Option<\/b> (mo\u017enosti nasazen\u00ed) vyberte mo\u017enost pro n\u00e1\u0161 produkt \u2014 <b>VB for AWS Deployment<\/b>.<\/li>\n<li>Z nab\u00eddky verz\u00ed <b>Software Version<\/b> vyberte nejnov\u011bj\u0161\u00ed verzi Veeam Backup for AWS.<\/li>\n<li>Z seznamu region\u016f <b>Region<\/b> vybereme region AWS, ve kter\u00e9m bude nasazen instanc EC2 s Veeam Backup for AWS.<\/li>\n<\/ul>\n<p>\n<i>Pozn\u00e1mka: <\/i>V\u00edce o regionech AWS si m\u016f\u017eete p\u0159e\u010d\u00edst <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/using-regions-availability-zones.html\">tady<\/a><\/noindex>.\n<\/li>\n<li>Pak klikn\u011bte na tla\u010d\u00edtko <b>Pokra\u010dovat k spu\u0161t\u011bn\u00ed<\/b> pro p\u0159echod k spu\u0161t\u011bn\u00ed.\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/9264144271e73d7ad8dcb303340ae4d3.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Na str\u00e1nce <b>Spus\u0165te tento software<\/b> prov\u00e1d\u00edme tyto kroky:\n<ul>\n<li>V sekci <b>Podrobnosti o konfiguraci<\/b> zkontrolujeme, zda jsou v\u0161echna nastaven\u00ed spr\u00e1vn\u011b vypln\u011bna.<\/li>\n<li>Z seznamu akc\u00ed <b>Vyberte akci<\/b> vybereme <b>Spustit CloudFormation<\/b>.<\/li>\n<li>Instalace Veeam Backup for AWS prob\u00edh\u00e1 pomoc\u00ed stohu AWS CloudFormation.\n<p><i>Pozn\u00e1mka: <\/i>Zde je stoh - souhrn cloudov\u00fdch zdroj\u016f, kter\u00fdmi lze spravovat jako samostatnou jednotku: vytv\u00e1\u0159et, odstra\u0148ovat, pou\u017e\u00edvat k nasazov\u00e1n\u00ed aplikac\u00ed. V\u00edce m\u016f\u017eete p\u0159e\u010d\u00edst v dokumentaci k AWS.<\/p>\n<p>Klikneme <b>Spustit<\/b> a spust\u00edme pr\u016fvodce vytv\u00e1\u0159en\u00edm stohu <b>Pr\u016fvodce vytv\u00e1\u0159en\u00edm stohu<\/b>.<\/li>\n<\/ul>\n<p>\n<\/li>\n<\/ol>\n<p>\n<b class=\"spoiler_title\">Vytv\u00e1\u0159en\u00ed stohu AWS CloudFormation<\/b>Vytv\u00e1\u0159en\u00ed stohu AWS CloudFormation:<\/p>\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed 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>V kroku <b>Specifikujte \u0161ablonu<\/b> m\u016f\u017eete ponechat nastaven\u00ed \u0161ablony stohu v\u00fdchoz\u00ed. \n<\/li>\n<li>V kroku <b>Specifikujte podrobnosti o stohu<\/b> zad\u00e1v\u00e1me nastaven\u00ed pro n\u00e1\u0161 stoh.\n<ul>\n<li>V poli <b>N\u00e1zev stohu<\/b> zad\u00e1v\u00e1me n\u00e1zev; m\u016f\u017eete pou\u017e\u00edt velk\u00e1 i mal\u00e1 p\u00edsmena, \u010d\u00edslice a poml\u010dky.<\/li>\n<li>V sekci nastaven\u00ed <b>Konfigurace instance<\/b>:<br \/>\n Z nab\u00eddky <b>Typ instance pro server Veeam Backup for AWS<\/b> je t\u0159eba vybrat typ instance EC2, na kter\u00e9m bude nainstalov\u00e1n Veeam Backup for AWS (d\u00e1le budeme naz\u00fdvat <i>server Veeam Backup for AWS<\/i>). Doporu\u010duje se vybrat typ <i>t2.medium<\/i>.<br \/>\n Z nab\u00eddky <b>P\u00e1ra kl\u00ed\u010d\u016f pro server Veeam Backup for AWS<\/b> je t\u0159eba vybrat p\u00e1r kl\u00ed\u010d\u016f, kter\u00e9 budou pou\u017eity p\u0159i ov\u011b\u0159ov\u00e1n\u00ed na tomto nov\u00e9m serveru. Pokud po\u017eadovan\u00fd p\u00e1r kl\u00ed\u010d\u016f v seznamu nen\u00ed, je nutn\u00e9 ho vytvo\u0159it, jak je pops\u00e1no. <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/ec2-key-pairs.html\">zde<\/a><\/noindex>. <br \/>\n Uve\u010fte, zda m\u00e1 b\u00fdt aktivov\u00e1na automatick\u00e1 z\u00e1loha objem\u016f EBS pro server Veeam Backup for AWS (ve v\u00fdchoz\u00edm stavu je to pot\u0159eba, t.j. <i>true<\/i>).<br \/>\n Uve\u010fte, zda m\u00e1 b\u00fdt restartov\u00e1n server Veeam Backup for AWS v p\u0159\u00edpad\u011b selh\u00e1n\u00ed softwaru.<br \/>\n Uve\u010fte, zda m\u00e1 b\u00fdt restartov\u00e1n server Veeam Backup for AWS v p\u0159\u00edpad\u011b selh\u00e1n\u00ed infrastruktury.\n<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>V sekci nastaven\u00ed s\u00edt\u011b <b>Konfigurace s\u00edt\u011b<\/b>:\n<ul>\n<li>Uve\u010fte, zda m\u00e1 b\u00fdt vytvo\u0159en Elastic IP adresa pro server Veeam Backup for AWS. V\u00edce informac\u00ed najdete zde.<\/li>\n<li>V poli <b>Povolen\u00e9 IP adresy pro p\u0159ipojen\u00ed k SSH<\/b> uve\u010fte rozsah adres IPv4, ze kter\u00fdch bude povolen p\u0159\u00edstup k serveru Veeam Backup for AWS p\u0159es SSH.<\/li>\n<li>V poli <b>Povolen\u00e9 IP adresy pro p\u0159ipojen\u00ed k HTTPS<\/b> uve\u010fte rozsah adres IPv4, ze kter\u00fdch bude povolen p\u0159\u00edstup k webov\u00e9mu rozhran\u00ed Veeam Backup for AWS.<br \/>\n Rozsah IPv4 adres se uv\u00e1d\u00ed v notaci CIDR (nap\u0159\u00edklad 12.23.34.0\/24). Chcete-li povolit p\u0159\u00edstup ze v\u0161ech adres IPv4, m\u016f\u017eete zadat 0.0.0.0\/0. (Tato mo\u017enost v\u0161ak nen\u00ed doporu\u010dena, proto\u017ee sni\u017euje bezpe\u010dnost infrastruktury.)<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Na z\u00e1klad\u011b uveden\u00fdch IPv4 adres AWS CloudFormation vytvo\u0159\u00ed bezpe\u010dnostn\u00ed skupinu pro Veeam Backup for AWS, s odpov\u00eddaj\u00edc\u00edmi pravidly pro p\u0159\u00edchoz\u00ed provoz p\u0159es SSH a HTTPS. (Ve v\u00fdchoz\u00edm nastaven\u00ed je pro p\u0159\u00edchoz\u00ed provoz p\u0159es SSH pou\u017e\u00edv\u00e1n port 22 a pro HTTPS port 443.) Pokud pl\u00e1nujete b\u011bhem instalace \u0159e\u0161en\u00ed zadat jinou bezpe\u010dnostn\u00ed skupinu pro Veeam Backup for AWS, nezapome\u0148te ru\u010dn\u011b p\u0159idat odpov\u00eddaj\u00edc\u00ed pravidla do t\u00e9to skupiny a zkontrolovat, \u017ee m\u00e1 povolen\u00fd p\u0159\u00edstup k slu\u017eb\u00e1m AWS (uveden\u00fdm v \u010d\u00e1sti Po\u017eadavky u\u017eivatelsk\u00e9 p\u0159\u00edru\u010dky).<\/li>\n<li>V sekci <b>VPC a pods\u00ed\u0165<\/b> mus\u00edte vybrat Amazon Virtual Private Cloud (Amazon VPC) a pods\u00ed\u0165, ke kter\u00e9 bude p\u0159ipojen server Veeam Backup for AWS.\n<\/li>\n<li>V kroku <b>Nastavit mo\u017enosti stacku<\/b> uvedete tagy AWS, povolen\u00ed pro roli IAM a dal\u0161\u00ed nastaven\u00ed stacku.\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/31062236b5ddf46ab22cd69a18c2cf06.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>V kroku <b>Zkontrolovat<\/b> zkontrolujte v\u0161echna nastaven\u00ed, zvolte mo\u017enost <b>Uznav\u00e1m, \u017ee AWS CloudFormation m\u016f\u017ee vytvo\u0159it zdroje IAM<\/b> a klikn\u011bte na <b>Vytvo\u0159it stack<\/b>.<\/li>\n<\/ol>\n<p>Po instalaci otev\u0159eme webovou konzoli zad\u00e1n\u00edm DNS nebo IP adresy instance EC2, kde je nainstalov\u00e1n Veeam Backup for AWS, nap\u0159\u00edklad:<br \/>\n<code>https:\/\/ec2-135-169-170-192.eu-central-1.compute.amazonaws.com<\/code><\/p>\n<p>V konzoli jsou zobrazeny zdroje, pro kter\u00e9 je nastavena ochrana dat pomoc\u00ed Veeam Backup for AWS:<\/p>\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/eb7ed2550eb15398c8c0732e1c2b7f52.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPot\u0159ebn\u00e1 nastaven\u00ed infrastruktury, rol\u00ed atd. jsou podrobn\u011b pops\u00e1na v <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/configuration.html?ver=10\">dokumentaci<\/a><\/noindex>.<\/p>\n<h3>Politiky z\u00e1lohov\u00e1n\u00ed<\/h3>\n<p>\nPro ochranu instanc\u00ed vytv\u00e1\u0159\u00edme politiky. <\/p>\n<p>Pro r\u016fzn\u00e9 typy objekt\u016f lze nastavit r\u016fzn\u00e9 politiky: nap\u0159\u00edklad politika ur\u010den\u00e1 pro ochranu tier 3 aplikac\u00ed (nejm\u00e9n\u011b kritick\u00fdch), nebo politiky pro aplikace tier 2 a tier 1. V nastaven\u00edch politiky uv\u00e1d\u00edme:<\/p>\n<ul>\n<li>\u00da\u010det s rolemi IAM<\/li>\n<li>Regiony \u2014 lze vybrat v\u00edce <\/li>\n<li>Co se pl\u00e1nuje chr\u00e1nit \u2014 mohou to b\u00fdt v\u0161echny zdroje (v\u0161echny zdroje) nebo vybran\u00e9 instance nebo (tagy)<\/li>\n<li>Zdroje, kter\u00e9 je t\u0159eba vylou\u010dit<\/li>\n<li>Nastaven\u00ed snapshotu, v\u010detn\u011b toho, zda pou\u017e\u00edt snapshoty a jak\u00e1 by m\u011bla b\u00fdt doba uchov\u00e1v\u00e1n\u00ed<\/li>\n<li>Nastaven\u00ed z\u00e1lohy: cesta k repozit\u00e1\u0159i, rozvrh a doba uchov\u00e1v\u00e1n\u00ed<\/li>\n<li>Vyhodnocen\u00ed n\u00e1klad\u016f na slu\u017eby (o n\u00ed n\u00ed\u017ee)<\/li>\n<li>Nastaven\u00ed rozvrhu a upozorn\u011bn\u00ed<\/li>\n<\/ul>\n<p><\/p>\n<h4>Vestav\u011bn\u00e9 vyhodnocen\u00ed n\u00e1klad\u016f na slu\u017eby<\/h4>\n<p>\nV \u0159e\u0161en\u00ed Veeam Backup for AWS je vestav\u011bn\u00e9 automatick\u00e9 vyhodnocen\u00ed n\u00e1klad\u016f na slu\u017eby \u2014 d\u00edky n\u011bmu se okam\u017eit\u011b vypo\u010d\u00edt\u00e1, jak\u00e9 budou n\u00e1klady na slu\u017eby z\u00e1lohov\u00e1n\u00ed podle konkr\u00e9tn\u00ed politiky. Do v\u00fdpo\u010dtu jsou zahrnuty n\u00e1sleduj\u00edc\u00ed metriky:<\/p>\n<ul>\n<li>N\u00e1klady na z\u00e1lohu<\/li>\n<li>N\u00e1klady na snapshot<\/li>\n<li>N\u00e1klady na provoz dat jsou zvl\u00e1\u0161\u0165 d\u016fle\u017eit\u00e9, pokud je repozit\u00e1\u0159 um\u00edst\u011bn mimo region, kde funguj\u00ed infrastruktura (Amazon AWS \u00fa\u010dtuje provoz do jin\u00fdch region\u016f)<\/li>\n<li>N\u00e1klady na transakce<\/li>\n<li>Celkov\u00e9 n\u00e1klady<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/d81df948587d769241c58887ed8769cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nData lze exportovat do form\u00e1tu CSV nebo XML.<\/p>\n<h3>Pomocn\u00e9 komponenty \u2014 Workers<\/h3>\n<p>\nPro sn\u00ed\u017een\u00ed n\u00e1klad\u016f na provoz lze nastavit automatick\u00e9 vytv\u00e1\u0159en\u00ed pomocn\u00fdch komponent \u2014 <b>workers<\/b> \u2014 ve stejn\u00e9m regionu AWS, kde se nach\u00e1zej\u00ed chr\u00e1n\u011bn\u00e9 objekty. Workers se automaticky spou\u0161t\u011bj\u00ed pouze b\u011bhem p\u0159enosu dat do\/z cloudov\u00e9ho \u00falo\u017ei\u0161t\u011b Amazon S3 nebo b\u011bhem obnovy, a po dokon\u010den\u00ed operac\u00ed se vypnou a odstran\u00ed.<\/p>\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/0926f91f39f09f77e4f4511d1a6d02f9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Z\u00e1lohov\u00e1n\u00ed<\/h3>\n<p>\nPro operace z\u00e1lohov\u00e1n\u00ed vyu\u017e\u00edv\u00e1 Veeam Backup for AWS nativn\u00ed snapshoty (viz <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/EBSSnapshots.html\">Amazon EBS snapshots<\/a><\/noindex>). B\u011bhem z\u00e1lohov\u00e1n\u00ed pou\u017e\u00edv\u00e1 Veeam Backup for AWS p\u0159\u00edkazy AWS CLI k vytv\u00e1\u0159en\u00ed snapshot\u016f EBS svazk\u016f p\u0159ipojen\u00fdch k instanci EC2. Pot\u00e9, v z\u00e1vislosti na zvolen\u00e9m sc\u00e9n\u00e1\u0159i z\u00e1lohov\u00e1n\u00ed, vytvo\u0159\u00ed Veeam Backup for AWS pro instanci EC2 bu\u010f \u0159et\u011bzec nativn\u00edch snapshot\u016f, nebo z\u00e1lohu na \u00farovni obrazu.<\/p>\n<h4>Nativn\u00ed snapshoty<\/h4>\n<p>\nVeeam Backup for AWS vytv\u00e1\u0159\u00ed nativn\u00ed snapshoty instance EC2 n\u00e1sleduj\u00edc\u00edm zp\u016fsobem:<\/p>\n<ol>\n<li>Nejprve se po\u0159izuj\u00ed snapshoty svazk\u016f EBS p\u0159ipojen\u00fdch k t\u00e9to instanci.<\/li>\n<li>Snapshoty EBS p\u0159i jejich vytv\u00e1\u0159en\u00ed obdr\u017e\u00ed AWS tagy. Kl\u00ed\u010de a hodnoty t\u011bchto tag\u016f obsahuj\u00ed za\u0161ifrovan\u00e1 meta-data. Veeam Backup for AWS pova\u017euje snapshoty EBS s meta-daty za nativn\u00ed snapshoty pro instanci EC2.<\/li>\n<li>Pokud byla instance EC2 ji\u017e zpracov\u00e1na politikou z\u00e1lohov\u00e1n\u00ed, Veeam Backup for AWS zkontroluje po\u010det bod\u016f obnoven\u00ed v \u0159et\u011bzci snapshot\u016f. Pokud p\u0159ekra\u010duje maxim\u00e1ln\u00ed hodnotu uvedenou v politice, nejstar\u0161\u00ed bod je odstran\u011bn. <i>Pozn\u00e1mka:<\/i> Politika uchov\u00e1v\u00e1n\u00ed a automatick\u00e9ho odstra\u0148ov\u00e1n\u00ed (retenci\u00f3) se nevztahuje na snapshoty vytvo\u0159en\u00e9 ru\u010dn\u011b (mysl\u00edme t\u00edm p\u0159esn\u011b snapshoty vytvo\u0159en\u00e9 samostatn\u011b). Takov\u00e9 snapshoty je mo\u017en\u00e9 odstranit, jak je pops\u00e1no <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/backups_remove.html\">zde<\/a><\/noindex>. (Pokud pod 'ru\u010dn\u011b' rozum\u00edme ru\u010dn\u00ed spu\u0161t\u011bn\u00ed politiky mimo pl\u00e1n, tak pro takto vytvo\u0159en\u00fd snapshot se retenci\u00f3 uplatn\u00ed.) <\/li>\n<\/ol>\n<p><\/p>\n<h4>Z\u00e1lohy na \u00farovni obrazu<\/h4>\n<p>\nTakto Veeam Backup for AWS prov\u00e1d\u00ed z\u00e1lohov\u00e1n\u00ed na \u00farovni obrazu:<\/p>\n<ol>\n<li>Nejprve se po\u0159izuj\u00ed snapshoty svazk\u016f EBS p\u0159ipojen\u00fdch k t\u00e9to instanci.<\/li>\n<li>Veeam Backup pro AWS pou\u017e\u00edv\u00e1 sn\u00edmky EBS jako zdroje pro z\u00e1lohu. Po dokon\u010den\u00ed procesu z\u00e1lohov\u00e1n\u00ed se tyto sn\u00edmky odstra\u0148uj\u00ed.<\/li>\n<li>Pot\u00e9 se v regionu AWS, kde se nach\u00e1z\u00ed tento instance, spust\u00ed pomocn\u00fd worker, kter\u00fd pom\u00e1h\u00e1 zpracov\u00e1vat data instance EC2.<\/li>\n<li>Z do\u010dasn\u00fdch sn\u00edmk\u016f se vytv\u00e1\u0159ej\u00ed objemy EBS a p\u0159ipojuj\u00ed se k instanci worker.<\/li>\n<li>Prob\u00edh\u00e1 \u010dten\u00ed dat z objem\u016f EBS na instanci worker a pot\u00e9 se data p\u0159en\u00e1\u0161ej\u00ed do \u00falo\u017ei\u0161t\u011b S3, kde budou ulo\u017eena ve form\u00e1tu Veeam.<\/li>\n<li>B\u011bhem inkrement\u00e1ln\u00ed relace Veeam Backup pro AWS \u010dte metadata z\u00e1loh z \u00falo\u017ei\u0161t\u011b S3 a pou\u017e\u00edv\u00e1 je k identifikaci blok\u016f, kter\u00e9 se zm\u011bnily od posledn\u00ed relace. <\/li>\n<li>Jakmile je z\u00e1lohov\u00e1n\u00ed dokon\u010deno, Veeam Backup pro AWS odstran\u00ed do\u010dasn\u00e9 sn\u00edmky EBS a instanci worker na Amazon EC2.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Obnova dat<\/h3>\n<p>\nS pomoc\u00ed Veeam Backup pro AWS je mo\u017en\u00e9 obnovit data n\u00e1sleduj\u00edc\u00edmi zp\u016fsoby:<\/p>\n<ul>\n<li>Na p\u016fvodn\u00ed um\u00edst\u011bn\u00ed, p\u0159eps\u00e1n\u00edm p\u016fvodn\u00ed instance. V\u0161echna data na t\u00e9to instanci budou p\u0159eps\u00e1na t\u011bmi, kter\u00e1 jsou ulo\u017eena v z\u00e1loze, a konfigurace instance z\u016fst\u00e1v\u00e1 zachov\u00e1na.<\/li>\n<li>Na nov\u00e9 um\u00edst\u011bn\u00ed, vytvo\u0159en\u00edm nov\u00e9 instance. V tomto sc\u00e9n\u00e1\u0159i \u2013 pokud zvol\u00edte obnoven\u00ed na nov\u00e9 um\u00edst\u011bn\u00ed nebo s nov\u00fdmi nastaven\u00edmi \u2013 bude nutn\u00e9 uv\u00e9st parametry konfigurace, kter\u00e9 budou aplikov\u00e1ny na instanci po dokon\u010den\u00ed obnova:\n<ul>\n<li>Region<\/li>\n<li>Nastaven\u00ed \u0161ifrov\u00e1n\u00ed<\/li>\n<li>Jm\u00e9no a typ instance<\/li>\n<li>S\u00ed\u0165ov\u00e1 nastaven\u00ed: Virtual Private Cloud (VPC), pods\u00ed\u0165, bezpe\u010dnostn\u00ed skupina<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><\/p>\n<h4>Obnova objem\u016f<\/h4>\n<p>Tak\u00e9 je podporov\u00e1na obnova objem\u016f instance EC2 ze sn\u00edmku nebo z\u00e1lohy, na p\u016fvodn\u00ed nebo nov\u00e9 um\u00edst\u011bn\u00ed. V druh\u00e9m p\u0159\u00edpad\u011b je t\u0159eba pro nov\u00e9 um\u00edst\u011bn\u00ed uv\u00e9st region AWS, Availability Zone a dal\u0161\u00ed parametry. <\/p>\n<p>B\u011bhem obnovy je tak\u00e9 zapojen worker. <\/p>\n<p>Cel\u00fd proces v kr\u00e1tkosti vypad\u00e1 takto (na p\u0159\u00edklad\u011b obnovy ze z\u00e1lohy):<\/p>\n<ol>\n<li>Veeam Backup pro AWS spou\u0161t\u00ed worker v po\u017eadovan\u00e9m regionu AWS, vytv\u00e1\u0159\u00ed po\u017eadovan\u00fd po\u010det pr\u00e1zdn\u00fdch objem\u016f EBS a p\u0159ipojuje je k instanci worker. <\/li>\n<li>Obnovuje data ze z\u00e1lohy na tyto objemy.<\/li>\n<li>Prov\u00e1d\u00ed odpojen\u00ed objem\u016f EBS a p\u0159esun do po\u017eadovan\u00e9ho um\u00edst\u011bn\u00ed (p\u016fvodn\u00edho nebo jin\u00e9ho regionu AWS), kde jsou tyto objemy uchov\u00e1v\u00e1ny jako samostatn\u00e9. <\/li>\n<li>Po dokon\u010den\u00ed operac\u00ed se odstran\u00ed instance worker.<br \/>\n <i>Pozn\u00e1mka:<\/i> Nezapome\u0148te, \u017ee po obnoven\u00ed nebude svazek automaticky p\u0159ipojen k instanci EC2 (bude ulo\u017een na ur\u010den\u00e9 m\u00edsto jako samostatn\u00fd svazek EBS).<\/li>\n<\/ol>\n<p><\/p>\n<h4>Obnoven\u00ed soubor\u016f<\/h4>\n<p>\nUmo\u017e\u0148uje obnovit jednotliv\u00e9 soubory bez nutnosti obnovovat celou instanci. <\/p>\n<p>Kdy\u017e iniciujete obnoven\u00ed na \u00farovni soubor\u016f, z\u00edsk\u00e1te URL (na z\u00e1klad\u011b ve\u0159ejn\u00e9ho DNS n\u00e1zvu pracovn\u00edka), pomoc\u00ed kter\u00e9ho m\u016f\u017eete vid\u011bt celou strukturu soubor\u016f na hostitelsk\u00e9 OS, naj\u00edt po\u017eadovan\u00e9 soubory a st\u00e1hnout je na lok\u00e1ln\u00ed stroj. <br \/>\nTak\u00e9 pro zaji\u0161t\u011bn\u00ed bezpe\u010dnosti lze zkontrolovat certifik\u00e1t a jeho otisk, abyste si byli jisti, \u017ee nedoch\u00e1z\u00ed k \u00fatoku typu MiTM.<\/p>\n<p><img decoding=\"async\" alt=\"Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/7205b4f5385ae0505ea287d689a9d6d9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Integrace s Veeam Backup &amp; Replication<\/h3>\n<p>\nPokud je ve va\u0161\u00ed infrastruktu\u0159e nasazen Veeam Backup &amp; Replication, m\u016f\u017eete nastavit obnoven\u00ed stroj\u016f obsa\u017een\u00fdch v n\u011bm do cloudu Amazon EC2 pomoc\u00ed funkce Direct Restore to AWS a pot\u00e9 chr\u00e1nit tato cloudov\u00e1 data s Veeam Backup for AWS. <br \/>\nTak\u00e9 se podporuje pr\u00e1ce Veeam Backup &amp; Replication s \u00falo\u017ei\u0161ti Amazon S3, kter\u00e9 vytv\u00e1\u0159\u00ed Veeam Backup for AWS - lze obnovit z\u00e1lohy instanc\u00ed Amazon EC2 do on-premises infrastruktury.<\/p>\n<h3>Vlastnosti bezplatn\u00e9 verze<\/h3>\n<p>\nBezplatn\u00e1 verze Veeam Backup for AWS umo\u017e\u0148uje z\u00e1lohovat a\u017e 10 instanc\u00ed EC2; obnoven\u00ed ze z\u00e1loh se prov\u00e1d\u00ed bez omezen\u00ed. <br \/>\n<i>Pozn\u00e1mka: <\/i>Doporu\u010duje se pou\u017e\u00edt <i>t2.medium<\/i>.<\/p>\n<p>P\u0159ibli\u017en\u00e9 n\u00e1klady na zdroje - 9,8 USD\/m\u011bs\u00edc, vych\u00e1zej\u00edc\u00ed z celodenn\u00edho pou\u017e\u00edv\u00e1n\u00ed s n\u00e1sleduj\u00edc\u00edmi v\u00fdchoz\u00edmi nastaven\u00edmi:<\/p>\n<ul>\n<li>EC2 - 1 instance t3.micro<\/li>\n<li>EBS - 1 svazek GP2 o velikosti 8 GB<\/li>\n<li>Konfigurace pro \u00falo\u017ei\u0161t\u011b S3 - 50 GB Standard S3 storage, 13 000 S3 PUT po\u017eadavk\u016f, 10 000 S3 GET po\u017eadavk\u016f, 50 GB vyu\u017eit\u00ed S3 Select<\/li>\n<\/ul>\n<p><\/p>\n<h3>U\u017eite\u010dn\u00e9 odkazy<\/h3>\n<p>\n\u0158e\u0161en\u00ed Veeam Backup for AWS na <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\">U\u017eivatelsk\u00e1 p\u0159\u00edru\u010dka<\/a><\/noindex> (v angli\u010dtin\u011b).<br \/>\n<br \/>Zdroj: <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.3 - 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\/cs\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"cs_CZ\" \/>\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\/cs\/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\udd47Seznamte se: nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS | ProHoster","description":"Na za\u010d\u00e1tku prosince bylo uvedeno nov\u00e9 \u0159e\u0161en\u00ed Veeam Backup for AWS pro z\u00e1lohov\u00e1n\u00ed a obnovu cloudov\u00fdch infrastruktur Amazon Elastic Compute Cloud (Amazon EC2).","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/54466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=54466"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/54466\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=54466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=54466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=54466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}