{"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\/az\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","title":{"rendered":"Tan\u0131\u015f\u0131n: Veeam Backup for AWS'in yeni \u00e7\u00f6z\u00fcm\u00fc","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Aral\u0131k ay\u0131n\u0131n ba\u015flar\u0131nda yeni bir \u00e7\u00f6z\u00fcm piyasaya \u00e7\u0131kt\u0131 <b>Veeam Backup for AWS<\/b> Amazon Elastic Compute Cloud (Amazon EC2) bulut altyap\u0131lar\u0131n\u0131n yedeklenmesi ve geri y\u00fcklenmesi i\u00e7in. <\/p>\n<p>Bu sayede EC2 \u00f6rneklerinin yedeklerini olu\u015fturabilir ve bunlar\u0131 Amazon Simple Storage Service (Amazon S3) bulut depolamada saklayabilirsiniz; ayr\u0131ca EC2 i\u00e7in yerel formatta anl\u0131k g\u00f6r\u00fcnt\u00fc zincirleri olu\u015fturabilirsiniz. <\/p>\n<p>Verileri geri y\u00fcklemek i\u00e7in Veeam Backup for AWS a\u015fa\u011f\u0131daki se\u00e7enekleri sunar: <\/p>\n<ul>\n<li>EC2 \u00f6rne\u011finin tamamen geri y\u00fcklenmesi<\/li>\n<li>\u00d6rne\u011fin depolama alanlar\u0131n\u0131n geri y\u00fcklenmesi<\/li>\n<li>\u00d6rne\u011fin misafir i\u015fletim sistemindeki dosyalar\u0131n ve klas\u00f6rlerin geri y\u00fcklenmesi<\/li>\n<\/ul>\n<p>\nAyr\u0131ca, \u00e7\u00f6z\u00fcm Veeam format\u0131nda yedekler olu\u015fturdu\u011fundan, EC2 yedeklerinin on-premises depolara kaydedilmesi i\u00e7in Veeam Backup &amp; Replication kullan\u0131labilir ve ard\u0131ndan verilerin bulut, sanal ve on-premises altyap\u0131lar\u0131 aras\u0131nda ta\u015f\u0131nmas\u0131 sa\u011flanabilir. <\/p>\n<p>Ve \u015f\u00fcphesiz, yeni \u00e7\u00f6z\u00fcm\u00fcn \u00fccretsiz versiyonunun olmas\u0131 kullan\u0131c\u0131lar\u0131 memnun edecek. Veeam Backup for AWS ile daha ayr\u0131nt\u0131l\u0131 tan\u0131\u015fmak i\u00e7in ho\u015f geldiniz.<\/p>\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" 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>Temel \u00d6zellikler<\/h3>\n<p>\nAmazon EBS anl\u0131k g\u00f6r\u00fcnt\u00fclerinin otomatik olarak al\u0131nmas\u0131 ve yedeklerin Amazon S3'te saklanmas\u0131 d\u0131\u015f\u0131nda, \u00e7\u00f6z\u00fcme dahil olanlar:<\/p>\n<ul>\n<li>Yedek y\u00f6neticileri i\u00e7in \u00e7ok fakt\u00f6rl\u00fc kimlik do\u011frulama<\/li>\n<li>Politikalara dayal\u0131 veri korumas\u0131<\/li>\n<li>IAM rol ayr\u0131\u015ft\u0131rma deste\u011fi<\/li>\n<li>K\u00fcresel b\u00f6lgeler aras\u0131 yap\u0131land\u0131rma deste\u011fi<\/li>\n<li>Hizmetlerin \u00e7al\u0131\u015fma maliyetlerini \u00f6nceden de\u011ferlendiren entegre bir algoritma, \u00f6demeleri kontrol etmeye yard\u0131mc\u0131 olur.<\/li>\n<\/ul>\n<p>\nVe daha \u00f6nce belirtildi\u011fi gibi, hem \u00fccretsiz lisans, hem de BYOL (kendi lisans\u0131n\u0131z\u0131 olu\u015fturun), hem de kaynak t\u00fcketimine dayal\u0131 lisans var \u2014 herkes ihtiyac\u0131na uygun olan\u0131 se\u00e7ebilir.<\/p>\n<h3>\u00c7al\u0131\u015fma A\u015famalar\u0131<\/h3>\n<p>\nK\u0131saca, ana a\u015famalar \u015f\u00f6yle:<\/p>\n<ol>\n<li>Altyap\u0131m\u0131z\u0131n sistem gereksinimlerine uygunlu\u011funu kontrol ediyoruz, <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/system_requirements.html?ver=10\">burada<\/a><\/noindex>. <\/li>\n<li>A\u015fa\u011f\u0131da a\u00e7\u0131kland\u0131\u011f\u0131 gibi Veeam Backup for AWS'i kuruyoruz.<\/li>\n<li>IAM rollerini belirtiyoruz. Bu roller, yedekleme ve geri y\u00fckleme i\u015flemlerinde kullan\u0131lan AWS kaynaklar\u0131na eri\u015fim i\u00e7in gereklidir:\n<ul>\n<li>E\u011fer EC2 \u00f6rneklerini tek bir AWS hesab\u0131nda yedeklemeyi planl\u0131yorsan\u0131z, a\u015fa\u011f\u0131daki rol\u00fc kullanabilirsiniz: <i>Default Backup Restore<\/i> \u2014 Veeam Backup for AWS kurulumu s\u0131ras\u0131nda olu\u015fturulur. Bu rol, Veeam Backup for AWS'in da\u011f\u0131t\u0131ld\u0131\u011f\u0131 AWS hesab\u0131nda t\u00fcm EC2 \u00f6rneklerine ve S3 kovalar\u0131na eri\u015fim hakk\u0131na sahiptir.<\/li>\n<li>E\u011fer EC2 \u00f6rneklerinin yedeklerini ya da verilerini iki farkl\u0131 AWS hesab\u0131 aras\u0131nda yedeklemek veya her i\u015flem i\u00e7in asgari haklara sahip \u00f6zel bir IAM rol\u00fc kullanmak istiyorsan\u0131z, gerekli IAM rollerini ba\u015flang\u0131\u00e7ta kullan\u0131lan AWS hesab\u0131nda olu\u015fturman\u0131z ve ard\u0131ndan bunlar\u0131 Veeam Backup for AWS'e eklemeniz gerekir. Bu konu, detayl\u0131 olarak a\u00e7\u0131klanmaktad\u0131r. <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/iam_roles_add.html?ver=10\">s\u0259n\u0259d<\/a><\/noindex>. <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Yedekleme altyap\u0131s\u0131n\u0131 ayarl\u0131yoruz, yani:\n<ul>\n<li>S3 deposunu yap\u0131land\u0131r\u0131yoruz.\n<p><i>Qeyd:<\/i> M\u0259lumatlar\u0131 qorumaq \u00fc\u00e7\u00fcn ehtiyat n\u00fcsx\u0259l\u0259r \u0259v\u0259zin\u0259 natiz formada yarad\u0131lan snapshot-lardan istifad\u0259 etm\u0259yi planla\u015fd\u0131r\u0131rs\u0131n\u0131zsa, bu madd\u0259ni ke\u00e7\u0259 bil\u0259rsiniz, \u00e7\u00fcnki S3-repo bu ssenari \u00fc\u00e7\u00fcn t\u0259l\u0259b olunmayacaq. \n <\/li>\n<li>K\u00f6m\u0259k\u00e7i komponentl\u0259r \u00fc\u00e7\u00fcn \u015f\u0259b\u0259k\u0259 parametrl\u0259rini t\u0259yin edirik <i>worker instances<\/i>.<br \/>\n<i>Workers<\/i> \u2014 Linux \u0259m\u0259liyyat sistemini idar\u0259 ed\u0259n EC2-nin k\u00f6m\u0259k\u00e7i instanslar\u0131d\u0131r. Onlar yaln\u0131z ehtiyat n\u00fcsx\u0259si (v\u0259 ya b\u0259rpa) d\u00f6vr\u00fcnd\u0259 i\u015f\u0259 sal\u0131n\u0131r v\u0259 ehtiyat proxy-si rolunu oynay\u0131rlar. Worker parametrl\u0259rind\u0259 Amazon VPC, alt\u015f\u0259b\u0259k\u0259 v\u0259 bu k\u00f6m\u0259k\u00e7i instanslar \u00fc\u00e7\u00fcn qo\u015fulacaq t\u0259hl\u00fck\u0259sizlik qrupu g\u00f6st\u0259rilm\u0259lidir. Bununla ba\u011fl\u0131 daha \u0259trafl\u0131 m\u0259lumat ala bil\u0259rsiniz <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/workers.html?ver=10\">burada<\/a><\/noindex>.\n <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Sonra EC2 instanslar\u0131n\u0131n ehtiyat n\u00fcsx\u0259l\u0259ri v\u0259 ya snapshot-lar\u0131 yarad\u0131laca\u011f\u0131 siyas\u0259ti qururuq. Bununla ba\u011fl\u0131 q\u0131saca a\u015fa\u011f\u0131da dan\u0131\u015faca\u011fam.<\/li>\n<li>Ehtiyat n\u00fcsx\u0259sind\u0259n b\u0259rpa etm\u0259k m\u00fcmk\u00fcnd\u00fcr \u2014 bununla ba\u011fl\u0131 da bir az a\u015fa\u011f\u0131da. <\/li>\n<\/ol>\n<p><\/p>\n<h3>\u0130nki\u015faf etdirm\u0259k v\u0259 qura\u015fd\u0131rmaq<\/h3>\n<p>\nVeeam Backup for AWS <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/marketplace\/pp\/B081VXF1Q9\">AWS Marketplace<\/a><\/noindex>. <\/p>\n<p>H\u0259llin inki\u015faf etdirilm\u0259si bel\u0259 h\u0259yata ke\u00e7irilir:<\/p>\n<ol>\n<li>\u0130st\u0259diyimiz h\u0259lli qura\u015fd\u0131rmaq \u00fc\u00e7\u00fcn istifad\u0259 etm\u0259yi planlad\u0131\u011f\u0131m\u0131z AWS hesab\u0131 il\u0259 AWS Marketplace-\u0259 daxil oluruq.<\/li>\n<li>Veeam Backup for AWS s\u0259hif\u0259sini a\u00e7\u0131r\u0131q, laz\u0131m olan redaksiyan\u0131 (\u00f6d\u0259ni\u015fli v\u0259 ya pulsuz) se\u00e7irik. Redaksiyalar haqq\u0131nda daha \u0259trafl\u0131 m\u0259lumat var <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/lic.html\">burada<\/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>Sa\u011f yuxar\u0131da <b>Continue to Subscribe<\/b>.\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" src=\"\/wp-content\/uploads\/2019\/12\/bee5554b53ed411789b31d178d4f4875.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Abun\u0259lik formala\u015fd\u0131rma s\u0259hif\u0259sind\u0259 <b>Terms and Conditions<\/b> (istifad\u0259 \u015f\u0259rtl\u0259ri) b\u00f6lm\u0259sin\u0259 ke\u00e7ib orada bas\u0131r\u0131q <b>Show Details<\/b>, sonra <b>End User License Agreement<\/b> lisensiya m\u00fcqavil\u0259sini oxuyuruq. <\/li>\n<li>Sonra <b>Continue to Configuration<\/b> v\u0259 konfiqurasiyaya ba\u015flay\u0131r\u0131q.\n<\/li>\n<li>S\u0259hif\u0259d\u0259 <b>Configure this software<\/b> qura\u015fd\u0131rma parametrl\u0259rini t\u0259yin edirik:\n<ul>\n<li>Siyah\u0131dan <b>Fulfillment Option<\/b> (inki\u015faf variantlar\u0131) m\u0259hsulumuz \u00fc\u00e7\u00fcn variant se\u00e7irik \u2014 <b>VB for AWS Deployment<\/b>.<\/li>\n<li>Versiyalar siyah\u0131s\u0131ndan <b>Software Version<\/b> Veeam Backup for AWS-in \u0259n son versiyas\u0131n\u0131 se\u00e7irik.<\/li>\n<li>Region <b>AWS b\u00f6lg\u0259sini se\u00e7irik, burada Veeam Backup for AWS il\u0259 EC2 instans\u0131 yarad\u0131lacaq.<\/b> AWS b\u00f6lg\u0259l\u0259ri haqq\u0131nda daha \u0259trafl\u0131 m\u0259lumat ala bil\u0259rsiniz<\/li>\n<\/ul>\n<p>\n<i>Qeyd: <\/i>Continue to Launch <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/using-regions-availability-zones.html\">burada<\/a><\/noindex>.\n<\/li>\n<li>Sonra <b>i\u015fl\u0259tm\u0259y\u0259 ke\u00e7m\u0259k \u00fc\u00e7\u00fcn.<\/b> Launch this software\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" src=\"\/wp-content\/uploads\/2019\/12\/9264144271e73d7ad8dcb303340ae4d3.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>S\u0259hif\u0259d\u0259 <b>a\u015fa\u011f\u0131dak\u0131 add\u0131mlar\u0131 icra edirik:<\/b> Configuration Details\n<ul>\n<li>B\u00f6lm\u0259sind\u0259 <b>b\u00fct\u00fcn parametrl\u0259rin d\u00fczg\u00fcn oldu\u011funu yoxlay\u0131r\u0131q.<\/b> X\u0259tl\u0259rin siyah\u0131s\u0131ndan<\/li>\n<li>Choose Action <b>Launch CloudFormation<\/b> se\u00e7irik <b>Veeam Backup for AWS qurulmas\u0131 AWS CloudFormation y\u0131\u011f\u0131n\u0131ndan istifad\u0259 etm\u0259kl\u0259 h\u0259yata ke\u00e7irilir.<\/b>.<\/li>\n<li>Burada y\u0131\u011f\u0131n \u2014 ayr\u0131 bir vahid kimi idar\u0259 edil\u0259 bil\u0259n bulud resurslar\u0131n\u0131n toplusudur: yaratmaq, silm\u0259k, t\u0259tbiql\u0259ri ba\u015flatmaq \u00fc\u00e7\u00fcn istifad\u0259 etm\u0259k. Bununla ba\u011fl\u0131 daha \u0259trafl\u0131 m\u0259lumat ala bil\u0259rsiniz.\n<p><i>Qeyd: <\/i>v\u0259 y\u0131\u011f\u0131n yarad\u0131lmas\u0131 ustas\u0131n\u0131 i\u015f\u0259 sal\u0131r\u0131q<\/p>\n<p>Basin <b>Ba\u015flat<\/b> Create stack wizard <b>AWS CloudFormation y\u0131\u011f\u0131n\u0131n\u0131n yarad\u0131lmas\u0131<\/b>.<\/li>\n<\/ul>\n<p>\n<\/li>\n<\/ol>\n<p>\n<b class=\"spoiler_title\">AWS CloudFormation y\u0131\u011f\u0131n\u0131n\u0131n yarad\u0131lmas\u0131:<\/b>Specify template<\/p>\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" src=\"\/wp-content\/uploads\/2019\/12\/834415111714f2143c701f704e3d624d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<ol>\n<li>Add\u0131mda <b>y\u0131\u011f\u0131n \u015fablonunun parametrl\u0259rini standart olaraq saxlaya bil\u0259rsiniz.<\/b> Specify stack details \n<\/li>\n<li>Add\u0131mda <b>y\u0131\u011f\u0131n\u0131m\u0131z \u00fc\u00e7\u00fcn parametrl\u0259ri daxil edirik.<\/b> Stack name\n<ul>\n<li>Bo\u015fluqda <b>ad daxil edirik; b\u00f6y\u00fck v\u0259 ki\u00e7ik h\u0259rfl\u0259r, r\u0259q\u0259ml\u0259r v\u0259 tirel\u0259rd\u0259n istifad\u0259 ed\u0259 bil\u0259rsiniz.<\/b> Parametrl\u0259r b\u00f6lm\u0259sind\u0259<\/li>\n<li>Instance Configuration <b>Veeam Backup for AWS serveri \u00fc\u00e7\u00fcn instansiya tipi se\u00e7irik.<\/b>:<br \/>\n Siyah\u0131dan <b>Instance type for Veeam Backup for AWS server<\/b> EC2 instans\u0131n\u0131n n\u00f6v\u00fcn\u00fc se\u00e7m\u0259k laz\u0131md\u0131r, Veeam Backup for AWS burada qura\u015fd\u0131r\u0131lacaq (daha sonra biz onu <i>Veeam Backup for AWS serveri<\/i>). N\u00f6vl\u0259rd\u0259n se\u00e7m\u0259k t\u00f6vsiy\u0259 olunur <i>t2.medium<\/i>.<br \/>\n Siyah\u0131dan <b>Veeam Backup for AWS Serveri \u00fc\u00e7\u00fcn A\u00e7ar C\u00fct\u00fc<\/b> Yeni serverd\u0259 autentifikasiya \u00fc\u00e7\u00fcn istifad\u0259 olunacaq a\u00e7ar c\u00fct\u00fcn\u00fc se\u00e7m\u0259k laz\u0131md\u0131r. \u018fg\u0259r siyah\u0131da laz\u0131m olan a\u00e7ar c\u00fct\u00fc yoxdursa, onu yaratmaq laz\u0131md\u0131r, nec\u0259 ki, <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/ec2-key-pairs.html\">burada<\/a><\/noindex>. <br \/>\n Veeam Backup for AWS serveri \u00fc\u00e7\u00fcn EBS h\u0259cml\u0259rinin avtomatik ehtiyat n\u00fcsx\u0259sini \u00e7\u0131xarma\u011f\u0131n daxil edilm\u0259sini ist\u0259diyinizi bildirin (standart olaraq daxil edilir, y\u0259ni <i>true<\/i>).<br \/>\n Veeam Backup for AWS serverini proqram t\u0259minat\u0131nda nasazl\u0131q ba\u015f verdikd\u0259 yenid\u0259n ba\u015flatma\u011f\u0131 ist\u0259diyinizi bildirin.<br \/>\n Veeam Backup for AWS serverini infrastrukturda nasazl\u0131q ba\u015f verdikd\u0259 yenid\u0259n ba\u015flatma\u011f\u0131 ist\u0259diyinizi bildirin.\n<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>\u015e\u0259b\u0259k\u0259 parametrl\u0259ri b\u00f6lm\u0259sind\u0259 <b>\u015e\u0259b\u0259k\u0259 Konfiqurasiyas\u0131<\/b>:\n<ul>\n<li>Veeam Backup for AWS serveri \u00fc\u00e7\u00fcn Elastic IP \u00fcnvan\u0131 yarad\u0131lmas\u0131na ehtiyac olub-olmad\u0131\u011f\u0131n\u0131 bildirin. \u018ftrafl\u0131 burada bax\u0131n.<\/li>\n<li>Bo\u015fluqda <b>SSH ba\u011flant\u0131s\u0131 \u00fc\u00e7\u00fcn icaz\u0259 veril\u0259n M\u0259nb\u0259 IP \u00dcnvanlar\u0131<\/b> Veeam Backup for AWS serverin\u0259 SSH vasit\u0259sil\u0259 giri\u015f\u0259 icaz\u0259 veril\u0259n IPv4 \u00fcnvanlar\u0131 aral\u0131\u011f\u0131n\u0131 g\u00f6st\u0259rin.<\/li>\n<li>Bo\u015fluqda <b>HTTPS ba\u011flant\u0131s\u0131 \u00fc\u00e7\u00fcn icaz\u0259 veril\u0259n M\u0259nb\u0259 IP \u00dcnvanlar\u0131<\/b> Veeam Backup for AWS veb-interfeysin\u0259 giri\u015f\u0259 icaz\u0259 veril\u0259n IPv4 \u00fcnvanlar\u0131 aral\u0131\u011f\u0131n\u0131 g\u00f6st\u0259rin.<br \/>\n IPv4 \u00fcnvanlar\u0131 CIDR notasiyas\u0131nda g\u00f6st\u0259rilir (m\u0259s\u0259l\u0259n, 12.23.34.0\/24). B\u00fct\u00fcn IPv4 \u00fcnvanlar\u0131ndan giri\u015fi icaz\u0259 verm\u0259k \u00fc\u00e7\u00fcn 0.0.0.0\/0 yazmaq olar. (Ancaq bu variant t\u00f6vsiy\u0259 edilmir, \u00e7\u00fcnki infrastrukturun t\u0259hl\u00fck\u0259sizliyini azald\u0131r.)<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>G\u00f6st\u0259ril\u0259n IPv4 \u00fcnvanlar\u0131na \u0259saslanaraq AWS CloudFormation Veeam Backup for AWS \u00fc\u00e7\u00fcn SSH v\u0259 HTTPS vasit\u0259sil\u0259 daxil olan trafik \u00fc\u00e7\u00fcn m\u00fcvafiq qaydalar\u0131 olan t\u0259hl\u00fck\u0259sizlik qrupunu yarad\u0131r. (Standart olaraq, SSH \u00fc\u00e7\u00fcn daxil olan trafik \u00fc\u00e7\u00fcn 22-ci port, HTTPS \u00fc\u00e7\u00fcn is\u0259 443-c\u00fc port istifad\u0259 olunur.) \u018fg\u0259r h\u0259llin qura\u015fd\u0131r\u0131lmas\u0131 zaman\u0131 Veeam Backup for AWS \u00fc\u00e7\u00fcn f\u0259rqli bir t\u0259hl\u00fck\u0259sizlik qrupu g\u00f6st\u0259rm\u0259k niyy\u0259tind\u0259sinizs\u0259, bu qrupa m\u00fcvafiq qaydalar\u0131 \u0259ll\u0259 \u0259lav\u0259 etm\u0259yi unutmay\u0131n v\u0259 AWS xidm\u0259tl\u0259rin\u0259 giri\u015fin icaz\u0259 verildiyini yoxlay\u0131n (istifad\u0259\u00e7i r\u0259hb\u0259rliyinin T\u0259l\u0259bl\u0259r b\u00f6lm\u0259sind\u0259 g\u00f6st\u0259rilir).<\/li>\n<li>clients.conf <b>VPC v\u0259 Alt \u015e\u0259b\u0259k\u0259<\/b> Veeam Backup for AWS serverinin qo\u015fulaca\u011f\u0131 Amazon Virtual Private Cloud (Amazon VPC) v\u0259 alt \u015f\u0259b\u0259k\u0259ni se\u00e7m\u0259k laz\u0131md\u0131r.\n<\/li>\n<li>Add\u0131mda <b>Qura\u015fd\u0131rma se\u00e7iml\u0259rini konfiqurasiya edin<\/b> AWS etiketl\u0259rini, IAM roluna icaz\u0259l\u0259ri v\u0259 dig\u0259r qura\u015fd\u0131rma parametrl\u0259rini g\u00f6st\u0259rin.\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" src=\"\/wp-content\/uploads\/2019\/12\/31062236b5ddf46ab22cd69a18c2cf06.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>Add\u0131mda <b>Yoxlay\u0131n<\/b> b\u00fct\u00fcn parametrl\u0259ri yoxlay\u0131n, <b>M\u0259n AWS CloudFormation-un IAM resurslar\u0131n\u0131 yarada bil\u0259c\u0259yini q\u0259bul edir\u0259m<\/b> v\u0259 bas\u0131n <b>Qura\u015fd\u0131rma yarad\u0131n<\/b>.<\/li>\n<\/ol>\n<p>Qura\u015fd\u0131rmadan sonra Veeam Backup for AWS-un qura\u015fd\u0131r\u0131ld\u0131\u011f\u0131 EC2 instansiyas\u0131n\u0131n DNS v\u0259 ya IP \u00fcnvan\u0131n\u0131 brauzerd\u0259 t\u0259min ed\u0259r\u0259k veb-konsolu a\u00e7aca\u011f\u0131q, m\u0259s\u0259l\u0259n:<br \/>\n<code>https:\/\/ec2-135-169-170-192.eu-central-1.compute.amazonaws.com<\/code><\/p>\n<p>Konsolda Veeam Backup for AWS vasit\u0259sil\u0259 m\u0259lumatlar\u0131n qorunmas\u0131 \u00fc\u00e7\u00fcn qura\u015fd\u0131r\u0131lm\u0131\u015f resurslar g\u00f6st\u0259rilir:<\/p>\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" src=\"\/wp-content\/uploads\/2019\/12\/eb7ed2550eb15398c8c0732e1c2b7f52.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nT\u0259l\u0259bl\u0259r, rollar v\u0259 s. il\u0259 ba\u011fl\u0131 laz\u0131mi parametrl\u0259r geni\u015f \u015f\u0259kild\u0259 t\u0259svir edilir <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/configuration.html?ver=10\">s\u0259n\u0259d<\/a><\/noindex>.<\/p>\n<h3>Ehtiyat n\u00fcsx\u0259 siyas\u0259tl\u0259ri<\/h3>\n<p>\nInstansiyalar\u0131 qorumaq \u00fc\u00e7\u00fcn siyas\u0259tl\u0259r yarad\u0131l\u0131r. <\/p>\n<p>F\u0259rqli obyekt n\u00f6vl\u0259ri \u00fc\u00e7\u00fcn f\u0259rqli siyas\u0259tl\u0259r qura\u015fd\u0131ra bil\u0259rsiniz: m\u0259s\u0259l\u0259n, \u0259n az kritik olan tier 3 t\u0259tbiql\u0259ri \u00fc\u00e7\u00fcn siyas\u0259t, yaxud tier 2 v\u0259 tier 1 t\u0259tbiql\u0259ri \u00fc\u00e7\u00fcn siyas\u0259tl\u0259r. Siyas\u0259t ayarlar\u0131nda g\u00f6st\u0259rin:<\/p>\n<ul>\n<li>IAM rollar\u0131 olan hesab<\/li>\n<li>Regionlar - bir ne\u00e7\u0259 se\u00e7\u0259 bil\u0259rsiniz <\/li>\n<li>N\u0259yi qorumaq planla\u015fd\u0131r\u0131l\u0131r - bu, b\u00fct\u00fcn resurslar (all resources) ola bil\u0259r v\u0259 ya se\u00e7ilmi\u015f instansiyalar v\u0259 ya (etiketl\u0259r)<\/li>\n<li>Istisna olunmas\u0131 laz\u0131m olan resurslar<\/li>\n<li>Snapshot ayarlar\u0131, o c\u00fcml\u0259d\u0259n snapshot-lar\u0131n istifad\u0259 edilib-edilm\u0259m\u0259si v\u0259 saxlama m\u00fcdd\u0259tinin n\u0259 olmas\u0131<\/li>\n<li>Backup ayarlar\u0131: repo yolu, c\u0259dv\u0259l v\u0259 saxlama m\u00fcdd\u0259ti<\/li>\n<li>Xidm\u0259tl\u0259rin qiym\u0259tl\u0259ndirilm\u0259si (a\u015fa\u011f\u0131da)<\/li>\n<li>C\u0259dv\u0259l v\u0259 bildiri\u015f ayarlar\u0131<\/li>\n<\/ul>\n<p><\/p>\n<h4>Daxili xidm\u0259t qiym\u0259tl\u0259ndirm\u0259si<\/h4>\n<p>\nVeeam Backup for AWS h\u0259llin\u0259 daxildir avtomatik xidm\u0259t qiym\u0259tl\u0259ndirm\u0259si \u2014 bu, konkret siyas\u0259t\u0259 uy\u011fun olaraq backup xidm\u0259tl\u0259rinin qiym\u0259tini d\u0259rhal hesablay\u0131r. Hesablamaya a\u015fa\u011f\u0131dak\u0131 metrikalar daxildir:<\/p>\n<ul>\n<li>Backup qiym\u0259ti<\/li>\n<li>Snapshot qiym\u0259ti<\/li>\n<li>\u015e\u0259b\u0259k\u0259 qiym\u0259ti - bu, x\u00fcsusil\u0259 vacibdir, \u0259g\u0259r repo regiondan k\u0259nardad\u0131r, burada infrastruktur obyektl\u0259ri f\u0259aliyy\u0259t g\u00f6st\u0259rir (Amazon AWS dig\u0259r regionlara \u00f6t\u00fcrm\u0259 \u00fc\u00e7\u00fcn trafik hesablay\u0131r)<\/li>\n<li>Transaksiya qiym\u0259ti<\/li>\n<li>\u00dcmumi qiym\u0259t<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" src=\"\/wp-content\/uploads\/2019\/12\/d81df948587d769241c58887ed8769cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nVeril\u0259r CSV v\u0259 ya XML fayl\u0131nda ixrac edil\u0259 bil\u0259r.<\/p>\n<h3>Yard\u0131m\u00e7\u0131 komponentl\u0259r \u2014 Workers<\/h3>\n<p>\nTrafik x\u0259rcl\u0259rini azaltmaq \u00fc\u00e7\u00fcn avtomatik yard\u0131m\u00e7\u0131 komponentl\u0259r yaratma\u011f\u0131 konfiqurasiya ed\u0259 bil\u0259rsiniz \u2014 <b>workers<\/b> \u2014 m\u00fchafiz\u0259 olunan obyektl\u0259rin oldu\u011fu eyni AWS regionunda. Workers yaln\u0131z Amazon S3 buluduna \/ buluddan m\u0259lumat \u00f6t\u00fcr\u00fclm\u0259si zaman\u0131 v\u0259 ya b\u0259rpa d\u00f6vr\u00fcnd\u0259 avtomatik olaraq i\u015f\u0259 sal\u0131n\u0131r v\u0259 \u0259m\u0259liyyatlar ba\u015fa \u00e7atd\u0131qdan sonra ba\u011flan\u0131r v\u0259 silinir.<\/p>\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" src=\"\/wp-content\/uploads\/2019\/12\/0926f91f39f09f77e4f4511d1a6d02f9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Yedekleme<\/h3>\n<p>\nVeeam Backup for AWS backup \u0259m\u0259liyyatlar\u0131 \u00fc\u00e7\u00fcn daxili snapshot-lardan istifad\u0259 edir (bax. <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/EBSSnapshots.html\">Amazon EBS snapshots<\/a><\/noindex>). Backup zaman\u0131 Veeam Backup for AWS EBS volumlar\u0131na aid snapshot-lar\u0131n yarad\u0131lmas\u0131 \u00fc\u00e7\u00fcn AWS CLI komandalar\u0131ndan istifad\u0259 edir, bu volumlar EC2 instansiyas\u0131na ba\u011flanm\u0131\u015fd\u0131r. Sonra, se\u00e7diyiniz backup senarisi \u0259sas\u0131nda, Veeam Backup for AWS EC2 instansiyas\u0131 \u00fc\u00e7\u00fcn ya daxili snapshotlar z\u0259ncirini, ya da g\u00f6r\u00fcnt\u00fc s\u0259viyy\u0259sind\u0259 backup yaradacaq.<\/p>\n<h4>Daxili snapshot-lar<\/h4>\n<p>\nVeeam Backup for AWS EC2 instansiyas\u0131n\u0131n daxili snapshot-lar\u0131n\u0131 a\u015fa\u011f\u0131dak\u0131 kimi yarad\u0131r:<\/p>\n<ol>\n<li>\u018fvv\u0259lc\u0259 bu instansiyaya ba\u011fl\u0131 EBS volumlar\u0131n\u0131n snapshot-lar\u0131 \u00e7\u0259kilir.<\/li>\n<li>EBS snapshotlar\u0131na yarad\u0131lark\u0259n AWS etiketl\u0259ri t\u0259yin olunur. Bu etiketl\u0259rin a\u00e7arlar\u0131 v\u0259 d\u0259y\u0259rl\u0259ri \u015fifr\u0259l\u0259nmi\u015f meta-m\u0259lumatlar\u0131 ehtiva edir. Veeam Backup for AWS, meta-m\u0259lumatlar\u0131 olan EBS snapshotlar\u0131n\u0131 EC2 instansiyas\u0131n\u0131n daxili snapshotlar\u0131 kimi qiym\u0259tl\u0259ndirir.<\/li>\n<li>\u018fg\u0259r EC2 instansiyas\u0131 art\u0131q backup siyas\u0259ti il\u0259 i\u015fl\u0259nibs\u0259, Veeam Backup for AWS snapshot z\u0259ncirind\u0259 b\u0259rpa n\u00f6qt\u0259l\u0259rinin say\u0131n\u0131 yoxlay\u0131r. \u018fg\u0259r bu say siyas\u0259td\u0259 g\u00f6st\u0259ril\u0259n maksimum d\u0259y\u0259ri a\u015f\u0131rsa, \u0259n k\u00f6hn\u0259 n\u00f6qt\u0259 silinir. <i>Qeyd:<\/i> Saxlama v\u0259 avtomatik silm\u0259 siyas\u0259ti (retention) \u0259ll\u0259 yarad\u0131lan snapshotlara (y\u0259ni ayr\u0131ca yarad\u0131lan snapshotlardan) t\u0259tbiq edilmir. Bel\u0259 snapshotlar\u0131 silm\u0259k \u00fc\u00e7\u00fcn a\u015fa\u011f\u0131dak\u0131 kimi etm\u0259k olar <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/backups_remove.html\">burada<\/a><\/noindex>. (\u018fg\u0259r \"\u0259ll\u0259\" il\u0259 c\u0259dv\u0259ld\u0259n k\u0259narda siyas\u0259t i\u015f\u0259 salma\u011f\u0131 n\u0259z\u0259rd\u0259 tutursan\u0131z, bel\u0259 yarad\u0131lan snapshot \u00fc\u00e7\u00fcn retention i\u015fl\u0259y\u0259c\u0259k.) <\/li>\n<\/ol>\n<p><\/p>\n<h4>\u015e\u0259kil s\u0259viyy\u0259sind\u0259 ehtiyat n\u00fcsx\u0259l\u0259ri<\/h4>\n<p>\nVeeam Backup for AWS \u015f\u0259kil s\u0259viyy\u0259sind\u0259 ehtiyat n\u00fcsx\u0259 \u0259m\u0259liyyat\u0131n\u0131 bel\u0259 icra edir:<\/p>\n<ol>\n<li>\u018fvv\u0259lc\u0259, bu instansiyaya \u0259lav\u0259 olunan EBS h\u0259cml\u0259rinin snapshots-u al\u0131n\u0131r.<\/li>\n<li>Veeam Backup for AWS ehtiyat n\u00fcsx\u0259l\u0259r \u00fc\u00e7\u00fcn ba\u015flan\u011f\u0131c kimi EBS snapshot-lar\u0131n\u0131 istifad\u0259 edir. Ehtiyat n\u00fcsx\u0259 prosesi ba\u015fa \u00e7atd\u0131qdan sonra, bu snapshot-lar silinir.<\/li>\n<li>Sonra, bu instansiyan\u0131n yerl\u0259\u015fdiyi AWS b\u00f6lg\u0259sind\u0259, EC2 instansiya m\u0259lumatlar\u0131n\u0131 emal etm\u0259k \u00fc\u00e7\u00fcn k\u00f6m\u0259k\u00e7i worker i\u015f\u0259 sal\u0131n\u0131r.<\/li>\n<li>M\u00fcv\u0259qq\u0259ti snapshot-lardan EBS h\u0259cml\u0259ri yarad\u0131l\u0131r v\u0259 worker instansiyas\u0131na \u0259lav\u0259 edilir.<\/li>\n<li>Worker instansiyas\u0131nda EBS h\u0259cml\u0259rind\u0259n m\u0259lumat oxunur, daha sonra bu m\u0259lumat S3 anbar\u0131na \u00f6t\u00fcr\u00fcl\u00fcr, burada Veeam format\u0131nda saxlan\u0131lacaq.<\/li>\n<li>Incremental sessiyas\u0131 zaman\u0131 Veeam Backup for AWS S3 anbar\u0131ndak\u0131 ehtiyat n\u00fcsx\u0259l\u0259rinin meta m\u0259lumatlar\u0131n\u0131 oxuyur v\u0259 bunlar\u0131 \u0259vv\u0259lki sessiyadan d\u0259yi\u015f\u0259n bloklar\u0131 m\u00fc\u0259yy\u0259nl\u0259\u015fdirm\u0259k \u00fc\u00e7\u00fcn istifad\u0259 edir. <\/li>\n<li>Ehtiyat n\u00fcsx\u0259 prosesi ba\u015fa \u00e7atd\u0131qda, Veeam Backup for AWS m\u00fcv\u0259qq\u0259ti EBS snapshot-lar\u0131n\u0131 v\u0259 Amazon EC2-d\u0259ki worker instansiyas\u0131n\u0131 silir.<\/li>\n<\/ol>\n<p><\/p>\n<h3>M\u0259lumatlar\u0131n b\u0259rpas\u0131<\/h3>\n<p>\nVeeam Backup for AWS say\u0259sind\u0259 m\u0259lumatlar\u0131 a\u015fa\u011f\u0131dak\u0131 yollarla b\u0259rpa etm\u0259k m\u00fcmk\u00fcnd\u00fcr:<\/p>\n<ul>\n<li>Orijinal yer\u0259, orijinal instansiyan\u0131 \u00fcst-\u00fcst\u0259 yazmaqla. Bu instansiyadak\u0131 b\u00fct\u00fcn m\u0259lumatlar ehtiyat n\u00fcsx\u0259sind\u0259 saxlan\u0131lanlarla \u00fcst-\u00fcst\u0259 yaz\u0131lacaq, instansiyan\u0131n konfiqurasiyas\u0131 is\u0259 saxlan\u0131lacaq.<\/li>\n<li>Yeni yer\u0259, yeni bir instansiya yaradaraq. Bu senaryoda - \u0259g\u0259r yeni bir yer\u0259 v\u0259 ya yeni parametrl\u0259rl\u0259 b\u0259rpa etm\u0259yi se\u00e7s\u0259niz - b\u0259rpa ba\u015fa \u00e7atd\u0131qdan sonra instansiyaya t\u0259tbiq olunacaq konfiqurasiya parametrl\u0259rini g\u00f6st\u0259rm\u0259lisiniz:\n<ul>\n<li>Region<\/li>\n<li>\u015eifrl\u0259m\u0259 parametrl\u0259ri<\/li>\n<li>Instansiyan\u0131n ad\u0131 v\u0259 tipi<\/li>\n<li>\u015e\u0259b\u0259k\u0259 parametrl\u0259ri: Virtual Private Cloud (VPC), alt \u015f\u0259b\u0259k\u0259, t\u0259hl\u00fck\u0259sizlik qrupu<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><\/p>\n<h4>H\u0259cml\u0259rin b\u0259rpas\u0131<\/h4>\n<p>EC2 instansiyas\u0131n\u0131n h\u0259cml\u0259rini snapshot-dan v\u0259 ya ehtiyat n\u00fcsx\u0259d\u0259n, orijinal v\u0259 ya yeni yer\u0259 b\u0259rpa etm\u0259k d\u0259 d\u0259st\u0259kl\u0259nir. \u0130kinci halda, yeni yer \u00fc\u00e7\u00fcn AWS regionunu, Availability Zone-u v\u0259 dig\u0259r parametrl\u0259ri g\u00f6st\u0259rm\u0259lisiniz. <\/p>\n<p>B\u0259rpa prosesi zaman\u0131 h\u0259m\u00e7inin worker istifad\u0259 olunur. <\/p>\n<p>B\u0259rpa prosesi q\u0131saca bel\u0259 g\u00f6r\u00fcn\u00fcr (ehtiyat n\u00fcsx\u0259d\u0259n b\u0259rpa etm\u0259 n\u00fcmun\u0259si il\u0259):<\/p>\n<ol>\n<li>Veeam Backup for AWS uy\u011fun AWS regionunda worker i\u015f\u0259 sal\u0131r, t\u0259l\u0259b olunan sayda bo\u015f EBS h\u0259cml\u0259ri yarad\u0131r v\u0259 bunlar\u0131 worker instansiyas\u0131na \u0259lav\u0259 edir. <\/li>\n<li>Ehtiyat n\u00fcsx\u0259d\u0259n bu h\u0259cml\u0259r\u0259 m\u0259lumat b\u0259rpa edir.<\/li>\n<li>EBS h\u0259cml\u0259rinin detach edilm\u0259sini v\u0259 t\u0259l\u0259b olunan yer\u0259 (orijinal v\u0259 ya dig\u0259r AWS regionu) k\u00f6\u00e7\u00fcr\u00fclm\u0259sini h\u0259yata ke\u00e7irir, burada bu h\u0259cml\u0259r ayr\u0131-ayr\u0131 olaraq saxlan\u0131l\u0131r. <\/li>\n<li>\u018fm\u0259liyyatlar ba\u015fa \u00e7atd\u0131qdan sonra worker instansiyas\u0131n\u0131 silir.<br \/>\n <i>Qeyd:<\/i> Unutmay\u0131n ki, b\u0259rpa sonras\u0131 h\u0259cm avtomatik olaraq EC2 instansiyas\u0131na \u0259lav\u0259 edilm\u0259y\u0259c\u0259k (sad\u0259c\u0259 g\u00f6st\u0259ril\u0259n yerd\u0259 ayr\u0131 EBS h\u0259cmind\u0259 saxlan\u0131lacaq).<\/li>\n<\/ol>\n<p><\/p>\n<h4>Fayllar\u0131n b\u0259rpas\u0131<\/h4>\n<p>\nB\u00fct\u00fcn instansiyan\u0131 b\u0259rpa etm\u0259y\u0259 ehtiyac olmadan ayr\u0131-ayr\u0131 fayllar\u0131 b\u0259rpa etm\u0259y\u0259 imkan tan\u0131y\u0131r. <\/p>\n<p>Fayl s\u0259viyy\u0259sind\u0259 b\u0259rpa ba\u015flad\u0131qda, siz\u0259 b\u00fct\u00fcn fayl strukturlar\u0131n\u0131 g\u00f6rm\u0259k \u00fc\u00e7\u00fcn URL (worker-in ictimai DNS ad\u0131 \u0259sas\u0131nda) verilir, laz\u0131mi fayllar\u0131 tap\u0131b yerli komp\u00fcteriniz\u0259 y\u00fckl\u0259y\u0259 bil\u0259rsiniz. <br \/>\nEyni zamanda, t\u0259hl\u00fck\u0259sizliyin t\u0259min edilm\u0259si \u00fc\u00e7\u00fcn sertifikat\u0131 v\u0259 onun barmaq izini yoxlayaraq MiTM-nin (adam ortada) olmad\u0131\u011f\u0131na \u0259min ola bil\u0259rsiniz.<\/p>\n<p><img decoding=\"async\" alt=\"Tan\u0131\u015f\u0131n: Veeam Backup for AWS&#039;in yeni \u00e7\u00f6z\u00fcm\u00fc\" src=\"\/wp-content\/uploads\/2019\/12\/7205b4f5385ae0505ea287d689a9d6d9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Veeam Backup &amp; Replication il\u0259 inteqrasiya<\/h3>\n<p>\n\u018fg\u0259r infrastrukturunuzda Veeam Backup &amp; Replication qura\u015fd\u0131r\u0131l\u0131bsa, Amazon EC2 buluduna daxil olan ma\u015f\u0131nlar\u0131 Direct Restore to AWS funksionall\u0131\u011f\u0131 il\u0259 b\u0259rpa etm\u0259yi v\u0259 sonra bu bulud m\u0259lumatlar\u0131n\u0131 Veeam Backup for AWS il\u0259 qoruma\u011f\u0131 konfiqurasiya ed\u0259 bil\u0259rsiniz. <br \/>\nVeeam Backup for AWS t\u0259r\u0259find\u0259n yarad\u0131lan Amazon S3 anbarlar\u0131 il\u0259 Veeam Backup &amp; Replication-in i\u015fl\u0259m\u0259si d\u0259 d\u0259st\u0259kl\u0259nir \u2014 Amazon EC2 instansiyalar\u0131n\u0131n ehtiyat n\u00fcsx\u0259l\u0259rini on-premises infrastrukturuna b\u0259rpa ed\u0259 bil\u0259rsiniz.<\/p>\n<h3>Pulsuz versiyan\u0131n x\u00fcsusiyy\u0259tl\u0259ri<\/h3>\n<p>\nVeeam Backup for AWS-in pulsuz versiyas\u0131 10 EC2 instansiyas\u0131n\u0131 yarad\u0131b ehtiyat n\u00fcsx\u0259sini saxlama\u011fa imkan tan\u0131y\u0131r; ehtiyat n\u00fcsx\u0259l\u0259rd\u0259n b\u0259rpa etm\u0259 m\u0259hdudiyy\u0259tsiz h\u0259yata ke\u00e7irilir. <br \/>\n<i>Qeyd: <\/i>T\u00f6vsiy\u0259 olunur ki, istifad\u0259 edilsin <i>t2.medium<\/i>.<\/p>\n<p>Resurslar\u0131n t\u0259xmin\u0259n qiym\u0259ti \u2014 9.8 USD\/ayd\u0131r, a\u015fa\u011f\u0131dak\u0131 standart ayarlarla 24 saatl\u0131q istifad\u0259 \u00fc\u00e7\u00fcn:<\/p>\n<ul>\n<li>EC2 \u2014 1 t3.micro instans\u0131<\/li>\n<li>EBS \u2014 1 8 GB GP2 h\u0259cmi<\/li>\n<li>S3 anbar\u0131 \u00fc\u00e7\u00fcn konfiqurasiya \u2014 50 GB Standard S3 saxlama, 13 000 S3 PUT sor\u011fusu, 10 000 S3 GET sor\u011fusu, 50 GB S3 Select istifad\u0259si<\/li>\n<\/ul>\n<p><\/p>\n<h3>Faydal\u0131 ba\u011flant\u0131lar<\/h3>\n<p>\nVeeam Backup for AWS h\u0259lli <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\">\u0130stifad\u0259\u00e7i b\u0259l\u0259d\u00e7isi<\/a><\/noindex> (ingilis dilind\u0259).<br \/>\n<br \/>M\u0259nb\u0259: <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.0.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\/az\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"az_AZ\" \/>\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\/az\/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\udd47Tan\u0131\u015f olun: yeni Veeam Backup for AWS h\u0259lli | ProHoster","description":"Dekabr\u0131n \u0259vv\u0259lind\u0259 Amazon Elastic Compute Cloud (Amazon EC2) bulud infrastrukturunun ehtiyat n\u00fcsx\u0259sini saxlamaq v\u0259 b\u0259rpa etm\u0259k \u00fc\u00e7\u00fcn yeni Veeam Backup for AWS h\u0259lli t\u0259qdim edildi.","canonical_url":"https:\/\/prohoster.info\/az\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"az_AZ","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\/az\/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\/az\/wp-json\/wp\/v2\/posts\/54466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/az\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/az\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/az\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/az\/wp-json\/wp\/v2\/comments?post=54466"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/az\/wp-json\/wp\/v2\/posts\/54466\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/az\/wp-json\/wp\/v2\/media?parent=54466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/az\/wp-json\/wp\/v2\/categories?post=54466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/az\/wp-json\/wp\/v2\/tags?post=54466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}