{"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\/et\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","title":{"rendered":"Tutvuge: uus lahendus Veeam Backup for AWS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Detsemberi alguses ilmus uus lahendus <b>Veeam Backup for AWS<\/b> Amazon Elastic Compute Cloud (Amazon EC2) pilvi infrastruktuuri varundamiseks ja taastamiseks. <\/p>\n<p>Selle abil on v\u00f5imalik luua EC2 instantside varukoopiaid ja salvestada need Amazon Simple Storage Service (Amazon S3) pilvehoiustesse, samuti luua EC2-snapshootide ahelad natiivses formas. <\/p>\n<p>Andmete taastamiseks pakub Veeam Backup for AWS j\u00e4rgmisi v\u00f5imalusi: <\/p>\n<ul>\n<li>EC2 instansi t\u00e4ielik taastamine<\/li>\n<li>Instansi mahute taastamine<\/li>\n<li>Failide ja kaustade taastamine instansi k\u00fclgkasutaja OS-ist<\/li>\n<\/ul>\n<p>\nLisaks, kuna lahendus loob varukoopiaid Veeam formaadis, saab kasutada Veeam Backup &amp; Replication, et salvestada EC2 varukoopiate koopiaid kohalikku hoidlasse ja seej\u00e4rel teostada andmete migratsiooni pilve-, virtuaalsete ja kohalikku infrastruktuuri vahel. <\/p>\n<p>Ja kindlasti r\u00f5\u00f5mustab kasutajaid uus lahendus, millel on tasuta versioon. Rohkemate detailide jaoks Veeam Backup for AWS kohta palun tutvuge allpool.<\/p>\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus 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\u00f5hiomadused<\/h3>\n<p>\nLisaks juba mainitud v\u00f5imalustele Amazon EBS automaatsete snapshootide loomise ja varukoopiate salvestamise kohta pilves Amazon S3, on lahenduses rakendatud:<\/p>\n<ul>\n<li>Mitme faktorilise autentimise v\u00f5imalus varundusadministraatoritele<\/li>\n<li>Andmete kaitse poliitikate alusel<\/li>\n<li>IAM rollide jagamise tugi<\/li>\n<li>Rist-looduslike konfiguratsioonide tugi<\/li>\n<li>Sisse ehitatud teenuste t\u00f6\u00f6 kulude eelhindamise algoritm, mis aitab j\u00e4lgida tasu.<\/li>\n<\/ul>\n<p>\nNoh ja nagu juba mainitud, on olemas ka tasuta litsents, BYOL (build your own license) ja ressursitarbimise p\u00f5hine litsents \u2014 iga\u00fchel on v\u00f5imalus valida sobiv.<\/p>\n<h3>T\u00f6\u00f6etapid<\/h3>\n<p>\nL\u00fchidalt \u00f6eldes, peamised etapid on j\u00e4rgmised:<\/p>\n<ol>\n<li>Kontrollime meie infrastruktuuri s\u00fcsteemin\u00f5uete osas, nagu on kirjeldatud <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/system_requirements.html?ver=10\">siin<\/a><\/noindex>. <\/li>\n<li>Installime Veeam Backup for AWS, nagu on allpool kirjeldatud.<\/li>\n<li>M\u00e4\u00e4rame IAM rollid. Need on vajalikud AWS ressurssidele juurdep\u00e4\u00e4suks, mis on seotud varundamise ja taastamisega:\n<ul>\n<li>Kui plaanite varundada EC2 instantsid \u00fche AWS konto piires, v\u00f5ite kasutada rolli <i>Default Backup Restore<\/i> \u2014 see luuakse Veeam Backup for AWS installimise k\u00e4igus. Sellel rollil on vajalikud \u00f5igused k\u00f5igile EC2 instantsidele ja S3 bakettidele AWS konto piires, kus Veeam Backup for AWS on seadistatud (algne AWS konto).<\/li>\n<li>Kui plaanite EC2 instantside varundamist v\u00f5i andmete taastamist kahe erineva AWS konto vahel v\u00f5i soovite kasutada iga operatsiooni jaoks eraldi IAM rolli minimaalsete \u00f5igustega, tuleb luua vajalikud IAM rollid algse AWS konto piires ja lisada need seej\u00e4rel Veeam Backup for AWS-i. Seda k\u00e4sitletakse \u00fcksikasjalikult <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/iam_roles_add.html?ver=10\">dokumentatsioon<\/a><\/noindex>. <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Seadistame varundusinfra, nimelt:\n<ul>\n<li>Konfigureerime S3-hoidla.\n<p><i>M\u00e4rkus:<\/i> Kui kavatsete andmete kaitsmiseks kasutada mitte varukoopiaid, vaid natiivsetena loodud snapshot'e, siis seda sammu v\u00f5ib vahele j\u00e4tta, kuna S3-hoidlat antud stsenaariumis ei vajata. \n <\/li>\n<li>Seame v\u00f5rgu seadistused abikomponentide jaoks <i>worker instances<\/i>.<br \/>\n<i>Workers<\/i> \u2014 need on Linuxi OS-iga EC2 abistavad instantsid. Need k\u00e4ivitatakse ainult varundamise (v\u00f5i taastamise) ajaks ja t\u00e4idavad varundusproksi rolli. Worker'i seadetes peab m\u00e4\u00e4rama Amazon VPC, alamv\u00f5rgu ja turvagruppi, millega need abistavad instantsid \u00fchenduvad. K\u00f5ige kohta saab lugeda <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/workers.html?ver=10\">siit<\/a><\/noindex>.\n <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Seej\u00e4rel loome poliitika, mille alusel tehakse varukoopiad v\u00f5i snapshot'id EC2 instantsidest. Sellest r\u00e4\u00e4gin l\u00fchidalt allpool.<\/li>\n<li>Varukoopiast on v\u00f5imalik taastada \u2014 sellest r\u00e4\u00e4gin ka veidi allpool. <\/li>\n<\/ol>\n<p><\/p>\n<h3>Paigaldamine ja seadistamine<\/h3>\n<p>\nVeeam Backup for AWS on saadaval <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/marketplace\/pp\/B081VXF1Q9\">AWS Marketplace'is<\/a><\/noindex>. <\/p>\n<p>Lahenduse paigaldamine toimub j\u00e4rgmiselt:<\/p>\n<ol>\n<li>Logige AWS Marketplace'i sisse AWS konto kaudu, mida plaanite lahenduse paigaldamiseks kasutada.<\/li>\n<li>Avage Veeam Backup for AWS leht, valige vajalik v\u00e4ljaanne (tasuline v\u00f5i tasuta). Toodete v\u00e4ljaannete kohta on rohkem teavet <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/lic.html\">siit<\/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>\u00dcleval paremas nurgas kl\u00f5psake <b>Continue to Subscribe<\/b>.\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/bee5554b53ed411789b31d178d4f4875.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Tellimuse vormimise lehe peaosas minge jaotisse <b>Terms and Conditions<\/b> (kasutustingimused) ja seal kl\u00f5psake <b>Show Details<\/b>, seej\u00e4rel lingil <b>End User License Agreement<\/b> loe litsentsilepingut. <\/li>\n<li>Seej\u00e4rel kl\u00f5psake nuppu <b>Continue to Configuration<\/b> ja alustage seadistamist.\n<\/li>\n<li>Lehek\u00fcljel <b>Configure this software<\/b> seadistame paigaldamise jaoks:\n<ul>\n<li>Nimekirjast <b>Fulfillment Option<\/b> (paigaldamisv\u00f5imalused) valige oma toote valik \u2014 <b>VB for AWS Deployment<\/b>.<\/li>\n<li>Versioonide loendist <b>Software Version<\/b> valige uusim Veeam Backup for AWS versioon.<\/li>\n<li>Regioonide nimekirjast <b>Region<\/b> valime AWS piirkonna, kus EC2 instants Veeam Backup for AWS k\u00e4ivitada.<\/li>\n<\/ul>\n<p>\n<i>M\u00e4rkus: <\/i>Rohkem AWS piirkondade kohta saab lugeda <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/using-regions-availability-zones.html\">siit<\/a><\/noindex>.\n<\/li>\n<li>Seej\u00e4rel kl\u00f5psake nuppu <b>J\u00e4tka k\u00e4ivitamist<\/b> k\u00e4ivitamiseks.\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/9264144271e73d7ad8dcb303340ae4d3.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Lehek\u00fcljel <b>K\u00e4ivita tarkvara<\/b> teeme j\u00e4rgmisi samme:\n<ul>\n<li>Jaotises <b>Konfiguratsiooni \u00fcksikasjad<\/b> kontrollime, kas k\u00f5ik seaded on \u00f5igesti m\u00e4\u00e4ratud.<\/li>\n<li>Tegevuste loendist <b>Vali tegevus<\/b> valime <b>K\u00e4ivita CloudFormation<\/b>.<\/li>\n<li>Veeam Backup for AWS installimine toimub AWS CloudFormation kihi abil.\n<p><i>M\u00e4rkus: <\/i>Siin on kiht kogum pilveressursse, mida saab hallata \u00fche \u00fchikuna: luua, kustutada, kasutada rakenduste k\u00e4ivitamiseks. Rohkem saab lugeda AWS dokumentatsioonist.<\/p>\n<p>Kl\u00f5psame <b>K\u00e4ivita.<\/b> ja k\u00e4ivitame kihi loomise wizard'i <b>Loo kihi wizard<\/b>.<\/li>\n<\/ul>\n<p>\n<\/li>\n<\/ol>\n<p>\n<b class=\"spoiler_title\">AWS CloudFormation kihi loomine<\/b>AWS CloudFormation kihi loomine:<\/p>\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus 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>Sammul <b>M\u00e4\u00e4ra mall<\/b> v\u00f5ib j\u00e4tta kihi malli seaded vaikimisi. \n<\/li>\n<li>Sammul <b>M\u00e4\u00e4ra kihi \u00fcksikasjad<\/b> sisestame oma kihi seaded.\n<ul>\n<li>V\u00e4ljal <b>Kihi nimi<\/b> sisestame nime; v\u00f5ib kasutada suuri ja v\u00e4ikeseid t\u00e4hti, numbreid ja sidekriipse.<\/li>\n<li>Seadete sektsioonis <b>Instantsi konfiguratsioon<\/b>:<br \/>\n Nimekirjast <b>Instantsi t\u00fc\u00fcp Veeam Backup for AWS serverile<\/b> peame valima EC2 instantsi t\u00fc\u00fcbi, kuhu Veeam Backup for AWS paigaldatakse (edaspidi nimetame seda <i>Veeam Backup for AWS server<\/i>). Soovitav on valida t\u00fc\u00fcp <i>t2.medium<\/i>.<br \/>\n Nimekirjast <b>V\u00f5tmepaar Veeam Backup for AWS serverile<\/b> peame valima v\u00f5tmepaari, mida kasutatakse sellel uuel serveril autentimiseks. Kui vajaminevat v\u00f5tmepaari loetelus pole, tuleb see luua, nagu on kirjeldatud <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/ec2-key-pairs.html\">siin<\/a><\/noindex>. <br \/>\n M\u00e4\u00e4rake, kas Veeam Backup for AWS serverile EBS mahtude automaatne varundamine on vajalik (vaikimisi on see vajalik, st <i>true<\/i>).<br \/>\n M\u00e4\u00e4rake, kas Veeam Backup for AWS serverit tuleb taask\u00e4ivitada, kui tarkvara t\u00f5rke korral.<br \/>\n M\u00e4\u00e4rake, kas Veeam Backup for AWS serverit tuleb taask\u00e4ivitada, kui infrastruktuuri t\u00f5rke korral.\n<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>V\u00f5rgu seadete sektsioonis <b>V\u00f5rgu konfiguratsioon<\/b>:\n<ul>\n<li>M\u00e4\u00e4rake, kas on vajalik luua Elastic IP-aadress Veeam Backup for AWS serverile. Rohkem info kohta siit.<\/li>\n<li>V\u00e4ljal <b>Lubatud allika IP-aadressid SSH-\u00fchenduseks<\/b> m\u00e4\u00e4rake IPv4 aadresside vahemik, millest on lubatud p\u00e4\u00e4seda Veeam Backup for AWS serverisse SSH kaudu.<\/li>\n<li>V\u00e4ljal <b>Lubatud allika IP-aadressid HTTPS-\u00fchenduseks<\/b> m\u00e4\u00e4rake IPv4 aadresside vahemik, millest on lubatud p\u00e4\u00e4seda Veeam Backup for AWS veebiliidesele.<br \/>\n IPv4 aadresside vahemik m\u00e4\u00e4ratakse CIDR notatsiooni j\u00e4rgi (n\u00e4iteks 12.23.34.0\/24). K\u00f5igi IPv4 aadresside juurdep\u00e4\u00e4su lubamiseks v\u00f5ib sisestada 0.0.0.0\/0. (Siiski ei soovitata sellist varianti, kuna see v\u00e4hendab infrastruktuuri turvalisust.)<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>AWS CloudFormation loob antud IPv4-aadresside p\u00f5hjal Veeam Backup for AWS jaoks turvagruppi koos sobivate reeglitega SSH ja HTTPS sisendi jaoks. (Vaikimisi kasutatakse SSH jaoks sisendi porti 22 ja HTTPS jaoks porti 443.) Kui raamistikku installides kavatsete Veeam Backup for AWS jaoks m\u00e4\u00e4rata teise turvagruppi, siis \u00e4rge unustage sellele grupile k\u00e4sitsi vastavaid reegleid lisada ja kontrollida, et AWS teenustele oleks juurdep\u00e4\u00e4s lubatud (nagu on toodud kasutajajuhendi n\u00f5uete jaotises).<\/li>\n<li>Jaotises <b>VPC ja alamside<\/b> tuleb valida Amazon Virtual Private Cloud (Amazon VPC) ja alamside, millega server Veeam Backup for AWS \u00fchendatakse.\n<\/li>\n<li>Sammul <b>Konfigureeri virna valikud<\/b> m\u00e4\u00e4rake AWS sildid, IAM rolli \u00f5igused ja muud virna seaded.\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/31062236b5ddf46ab22cd69a18c2cf06.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Sammul <b>Vaadake \u00fcle<\/b> kontrollige k\u00f5iki seadeid, valige valik <b>N\u00f5ustun, et AWS CloudFormation v\u00f5ib luua IAM ressursse<\/b> ja kl\u00f5psake <b>Loo virn<\/b>.<\/li>\n<\/ol>\n<p>P\u00e4rast installimist avame veebikonsooli, sisestades brauserisse EC2 instantsi DNS v\u00f5i IP-aadressi, kus on installitud Veeam Backup for AWS, n\u00e4iteks:<br \/>\n<code>https:\/\/ec2-135-169-170-192.eu-central-1.compute.amazonaws.com<\/code><\/p>\n<p>Konsoolis kuvatakse ressursid, mille jaoks on seadistatud andmekaitse Veeam Backup for AWS abil:<\/p>\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/eb7ed2550eb15398c8c0732e1c2b7f52.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nInfrastruktuuri, rollide jms vajalikud seaded on podrobne kirjeldatud <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/configuration.html?ver=10\">dokumentatsioon<\/a><\/noindex>.<\/p>\n<h3>Varunduspoliitika<\/h3>\n<p>\nLoome instantside kaitsmiseks poliitikaid. <\/p>\n<p>Erinevate objektit\u00fc\u00fcpide jaoks saab seadistada erinevaid poliitikaid: n\u00e4iteks poliitika, mis on m\u00f5eldud tier 3 rakenduste (v\u00e4hem kriitilised) kaitsmiseks, v\u00f5i poliitikad tier 2 ja tier 1 rakenduste jaoks. Poliitika seadetes m\u00e4\u00e4rame:<\/p>\n<ul>\n<li>Konto IAM rollidega<\/li>\n<li>Regioonid \u2014 saab valida mitmeid <\/li>\n<li>Mida plaanitakse kaitsta \u2014 need v\u00f5ivad olla k\u00f5ik ressursid (k\u00f5ik ressursid) v\u00f5i valitud instantsid v\u00f5i (sildid)<\/li>\n<li>Ressursid, mis tuleb v\u00e4lja j\u00e4tta<\/li>\n<li>Snapshots'i seaded, sealhulgas kas kasutada snapshots'id ja kui kaua tuleb s\u00e4ilitada<\/li>\n<li>Varundamise seaded: tee repotis, ajakava ja s\u00e4ilitusaeg<\/li>\n<li>Teenuste maksumuse hindamine (koos sellest allpool)<\/li>\n<li>Ajakava ja teavitamise seaded<\/li>\n<\/ul>\n<p><\/p>\n<h4>Sisemine teenuste maksumuse hindamine<\/h4>\n<p>\nVeeam Backup for AWS lahenduses on sisseehitatud automaatne teenuste maksumuse hindamine \u2014 selle kaudu arvutatakse koheselt, kui palju maksavad varundusteenused vastavalt konkreetsele poliitikale. Arvesse v\u00f5etakse j\u00e4rgmised m\u00f5\u00f5dikud:<\/p>\n<ul>\n<li>Varundamise maksumus<\/li>\n<li>Snapshots'i maksumus<\/li>\n<li>Andmete liiklusmaksumus on eriti oluline, kui hoidis asub piirkonnast v\u00e4ljaspool, kus infrastruktuuri objektid t\u00f6\u00f6tavad (Amazon AWS arvestab liikluse maksustust teistesse piirkondadesse).<\/li>\n<li>Tehingute maksumus<\/li>\n<li>Kogumaksumus<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/d81df948587d769241c58887ed8769cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAndmeid saab eksportida CSV- v\u00f5i XML-faili.<\/p>\n<h3>Abikomponendid \u2014 Workers<\/h3>\n<p>\nLiikluskulude v\u00e4hendamiseks saab seadistada abikomponentide automaatse loomise \u2014 <b>workers<\/b> \u2014 samas AWS-i piirkonnas, kus on kaitstud objektid. Workers k\u00e4ivitatakse automaatselt ainult andmete edastamise ajaks Amazon S3-sse v\u00f5i taastamise ajaks ja p\u00e4rast toimingute l\u00f5petamist nad v\u00e4lja l\u00fclitatakse ja kustutatakse.<\/p>\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/0926f91f39f09f77e4f4511d1a6d02f9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Varundamine<\/h3>\n<p>\nVeeam Backup for AWS kasutab varundamiseks natiivseid snapshots'e (vt. <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/EBSSnapshots.html\">Amazon EBS snapshots<\/a><\/noindex>). Veeam Backup for AWS kasutab EBS-volume'i snapshots'ide loomise jaoks AWS CLI k\u00e4ske, mis on \u00fchendatud EC2 instantsiga. Seej\u00e4rel, s\u00f5ltuvalt teie valitud varundamisstsenaariumist, loob Veeam Backup for AWS neist EC2 instantsi jaoks kas natiivsete snapshots'ide ahela v\u00f5i pilditaseme varukoopia.<\/p>\n<h4>Natiivsed snapshots<\/h4>\n<p>\nVeeam Backup for AWS loob natiivsed snapshots EC2 instantsist j\u00e4rgmiselt:<\/p>\n<ol>\n<li>Esiteks koostatakse snapshots EBS-volume'ist, mis on seotud antud instantsiga.<\/li>\n<li>Snapshots EBS-l m\u00e4\u00e4ratakse loomisel AWS-i sildid. Nende siltide v\u00f5tmed ja v\u00e4\u00e4rtused sisaldavad kr\u00fcptitud metaandmeid. Veeam Backup for AWS k\u00e4sitleb metaandmetega EBS snapshots'e natiivsete snapshots'ina EC2 instantsi jaoks.<\/li>\n<li>Kui EC2 instants on juba varundamispolitiikaga t\u00f6\u00f6deldud, kontrollib Veeam Backup for AWS snapshots'ide ahela taastumispunktide arvu. Kui see \u00fcletab poliitikas m\u00e4rgitud piirm\u00e4\u00e4ra, eemaldatakse k\u00f5ige vanem punkt. <i>M\u00e4rkus:<\/i> Salvestamise ja automaatse kustutamise poliitika (retensioon) ei kehti k\u00e4sitsi loodud snapshots'ide kohta (r\u00e4\u00e4kides just nendest snapshots'idest, mis on loodud eraldi). Selliseid snapshots'e saab kustutada, nagu on kirjeldatud <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/backups_remove.html\">siin<\/a><\/noindex>. (Kui \u00abk\u00e4si\u00bb t\u00e4hendab poliitika k\u00e4sitsi k\u00e4ivitamist v\u00e4ljaspool ajakava, siis sellisel viisil loodud snapshots'i puhul t\u00f6\u00f6tas retensioon v\u00e4lja.) <\/li>\n<\/ol>\n<p><\/p>\n<h4>Pilditaseme varukoopiad<\/h4>\n<p>\nNii viib Veeam Backup for AWS l\u00e4bi pilditaseme varundamise:<\/p>\n<ol>\n<li>Esmalt koostatakse snapshots EBS-volume'ist, mis on seotud antud instantsiga.<\/li>\n<li>Veeam Backup for AWS kasutab EBS-i snapshot'e varundamise l\u00e4htepunktidena. P\u00e4rast varundamisprotsessi l\u00f5petamist need snapshot'id kustutatakse.<\/li>\n<li>Seej\u00e4rel algatatakse AWS-i regioonis, kus antud instance asub, abiline worker, mis aitab EC2 instance'i andmeid t\u00f6\u00f6delda.<\/li>\n<li>Ajutistest snapshot'itest luuakse EBS-i mahud ja need kinnitatakse worker instance'ile.<\/li>\n<li>Andmeid loetakse EBS-i mahtudest worker instance'il, seej\u00e4rel edastatakse andmed S3-repositooriumisse, kus need s\u00e4ilitatakse Veeami formaadis.<\/li>\n<li>Incrementaalse seansi k\u00e4igus Veeam Backup for AWS loeb varunduste metaandmeid S3-repositooriumist ja kasutab neid, et tuvastada plokid, mis on muutunud alates eelmisest sessioonist. <\/li>\n<li>Kui varundamine on l\u00f5petatud, eemaldab Veeam Backup for AWS ajutised EBS-i snapshot'id ja worker instance'i Amazon EC2-st.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Andmete taastamine<\/h3>\n<p>\nVeeam Backup for AWS-i abil on andmete taastamine v\u00f5imalik j\u00e4rgmistel viisidel:<\/p>\n<ul>\n<li>Algse asukohta, asendades algse instance'i. K\u00f5ik andmed sellel instance'il asendatakse varunduses talletatuga, samas kui instance'i konfiguratsioon s\u00e4ilib.<\/li>\n<li>Uude asukohta, luues uue instance'i. Tootmisprotsessis \u2013 kui valite taastamise uude asukohta v\u00f5i uute seadistustega \u2013 tuleb m\u00e4\u00e4rata konfiguratsiooni parameetrid, mis rakenduvad instance'ile taastamise l\u00f5puleviimisel:\n<ul>\n<li>Piirkond<\/li>\n<li>\u0160ifreerimise seaded<\/li>\n<li>Instance'i nimi ja t\u00fc\u00fcp<\/li>\n<li>V\u00f5rguseaded: Virtuaalne Privaatne Pilv (VPC), alamv\u00f5rk, turvagrupp<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><\/p>\n<h4>Mahutite taastamine<\/h4>\n<p>Toetatakse ka EC2 instance'i mahtude taastamist snapshot'ist v\u00f5i varundusest, algsesse v\u00f5i uude asukohta. Teisel juhul tuleb uue asukoha jaoks m\u00e4rkida AWS-i regioon, k\u00e4ttesaadavuse tsoon ja muud parameetrid. <\/p>\n<p>Taastamisprotsessis kasutatakse samuti worker'it. <\/p>\n<p>Protsess n\u00e4eb l\u00fchidalt v\u00e4lja j\u00e4rgmiselt (varundusest taastamise n\u00e4itel):<\/p>\n<ol>\n<li>Veeam Backup for AWS k\u00e4ivitab worker'i vajalikus AWS-i regioonis, loob vajalikul hulgal t\u00fchje EBS-i mahte ja kinnitab need worker instance'ile. <\/li>\n<li>Taastab andmed varundusest nendele mahtudele.<\/li>\n<li>Rakendab EBS-i mahutite lahti\u00fchendamise ja viimise soovitud asukohta (algne v\u00f5i m\u00f5ni teine AWS-i regioon), kus need mahud s\u00e4ilitatakse eraldi. <\/li>\n<li>Kustutab worker instance'i operatsioonide l\u00f5petamisel.<br \/>\n <i>M\u00e4rkus:<\/i> \u00c4rge unustage, et p\u00e4rast ketta taastamist ei liidetakse see automaatselt EC2 instantsiga (see salvestatakse lihtsalt m\u00e4\u00e4ratud asukohta eraldi EBS kettana).<\/li>\n<\/ol>\n<p><\/p>\n<h4>Failide taastamine<\/h4>\n<p>\nLubab taastada eraldi faile ilma, et peaks tervet instantsi t\u00e4ielikult taastama. <\/p>\n<p>Kui k\u00e4ivitate failitaseme taastamise, siis saate URL-i (avaliku DNS-nime p\u00f5hjal workerist), millega n\u00e4ete kogu failistruktuuri veebiserveris, leidke sealt vajalikud failid ja laadige need oma kohalikku masinasse. <br \/>\nSamuti on turvalisuse tagamiseks v\u00f5imalik kontrollida sertifikaati ja selle s\u00f5rmej\u00e4lge, et veenduda MiTM-i puudumises.<\/p>\n<p><img decoding=\"async\" alt=\"Tutvuge: uus lahendus Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/7205b4f5385ae0505ea287d689a9d6d9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Integreerimine Veeam Backup &amp; Replicationiga<\/h3>\n<p>\nKui teie infrastruktuuris on k\u00e4imas Veeam Backup &amp; Replication, saate seadistada tulevate masinate taastamise Amazon EC2 pilve funktsiooni Direct Restore to AWS abil ning seej\u00e4rel kaitsta neid pilveteenuseid Veeam Backup for AWSiga. <br \/>\nSamuti toetab Veeam Backup &amp; Replication Amazon S3 repositooriume, mille loob Veeam Backup for AWS \u2014 saate taastada Amazon EC2 instantside varukoopiad kohalikku infrastruktuuri.<\/p>\n<h3>Tasuta versiooni omadused<\/h3>\n<p>\nTasuta versioon Veeam Backup for AWS v\u00f5imaldab varundada kuni 10 EC2 instantsi; varukoopiatest taastamine toimub ilma piiranguteta. <br \/>\n<i>M\u00e4rkus: <\/i>Soovitatav kasutada <i>t2.medium<\/i>.<\/p>\n<p>Hinnanguline ressursside maksumus \u2014 9,8 USD \/ kuu, tuginedes 24\/7 kasutamisele j\u00e4rgmiste vaikeseadete p\u00f5hjal:<\/p>\n<ul>\n<li>EC2 \u2014 1 instants t3.micro<\/li>\n<li>EBS \u2014 1 GP2 ketas, mille maht on 8 GB<\/li>\n<li>S3 repositooriumi konfiguratsioon \u2014 50 GB Standard S3 salvestust, 13 000 S3 PUT taotlust, 10 000 S3 GET taotlust, 50 GB S3 Select kasutust<\/li>\n<\/ul>\n<p><\/p>\n<h3>Kasulikud lingid<\/h3>\n<p>\nVeeam Backup for AWS lahendus on <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/marketplace\/pp\/B081VXF1Q9\">AWS Marketplace'is<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/overview.html?ver=10\">Kasutajate juhend<\/a><\/noindex> (inglise keeles).<br \/>\n<br \/>Allikas: <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.1.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\/et\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\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\/et\/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\udd47Tutvuge: uus lahendus Veeam Backup for AWS | ProHoster","description":"Detsembri alguses tuli turule uus lahendus Veeam Backup for AWS Amazon Elastic Compute Cloud (Amazon EC2) pilve infrastruktuuride varundamiseks ja taastamiseks.","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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\/et\/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\/et\/wp-json\/wp\/v2\/posts\/54466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=54466"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/54466\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=54466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=54466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=54466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}