{"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\/en\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","title":{"rendered":"Meet: the new solution Veeam Backup for AWS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>At the beginning of December, a new solution was released <b>Veeam Backup for AWS<\/b> for backing up and recovering cloud infrastructures on Amazon Elastic Compute Cloud (Amazon EC2). <\/p>\n<p>With it, you can create backups of EC2 instances and store them in the Amazon Simple Storage Service (Amazon S3), as well as create EC2 snapshot chains in native format. <\/p>\n<p>To recover data, Veeam Backup for AWS offers the following options: <\/p>\n<ul>\n<li>Full EC2 instance recovery<\/li>\n<li>Instance volume recovery<\/li>\n<li>Recovery of files and folders from the guest OS of the instance<\/li>\n<\/ul>\n<p>\nAdditionally, since the solution creates backups in Veeam format, you can use Veeam Backup &amp; Replication to save copies of EC2 backups in on-premises repositories, and then perform data migration between cloud, virtual, and on-premises infrastructures. <\/p>\n<p>And undoubtedly, users will be pleased with the availability of a free version of the new solution. For a more detailed introduction to Veeam Backup for AWS, welcome below.<\/p>\n<p><img decoding=\"async\" alt=\"Meet: the new solution 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>Key Features<\/h3>\n<p>\nIn addition to the previously mentioned automatic creation of Amazon EBS snapshots and storing backups in Amazon S3 cloud, the solution includes:<\/p>\n<ul>\n<li>Multi-factor authentication for backup administrators<\/li>\n<li>Policy-based data protection<\/li>\n<li>Support for IAM role separation<\/li>\n<li>Support for cross-region configurations<\/li>\n<li>Built-in cost estimation algorithm for service operation, helping to control payments.<\/li>\n<\/ul>\n<p>\nAnd as already mentioned, there is both a free license and BYOL (build your own license), as well as a license based on resource consumption \u2014 everyone can choose what suits them.<\/p>\n<h3>Working steps<\/h3>\n<p>\nIn brief, the main steps are as follows:<\/p>\n<ol>\n<li>We check our infrastructure for compliance with the system requirements described <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/system_requirements.html?ver=10\">here<\/a><\/noindex>. <\/li>\n<li>We install Veeam Backup for AWS, as described below.<\/li>\n<li>We specify IAM roles. They are needed to access the AWS resources involved in backup and recovery:\n<ul>\n<li>If you plan to back up EC2 instances within a single AWS account, you can use the role <i>Default Backup Restore<\/i> \u2014 it is created during the installation of Veeam Backup for AWS. This role has the necessary permissions to access all EC2 instances and S3 buckets within the AWS account where Veeam Backup for AWS is deployed (the original AWS account).<\/li>\n<li>If you plan to back up or restore EC2 instance data between two different AWS accounts or want to use a dedicated IAM role with the minimum set of permissions for each operation, you will need to create the necessary IAM roles within the original AWS account and then add them to Veeam Backup for AWS. This is explained in detail in <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/iam_roles_add.html?ver=10\">the documentation<\/a><\/noindex>. <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Setting up the backup infrastructure, namely:\n<ul>\n<li>Configuring the S3 repository.\n<p><i>Note:<\/i> If you intend to protect data using natively created snapshots instead of backups, you can skip this step, as the S3 repository will not be needed in this scenario. \n <\/li>\n<li>Setting network configurations for auxiliary components <i>worker instances<\/i>.<br \/>\n<i>Workers<\/i> \u2014 are auxiliary EC2 instances running on Linux. They only run during backups (or restores) and act as backup proxies. In the worker settings, you will need to specify the Amazon VPC, subnet, and security group that these auxiliary instances will connect to. You can read more about all this <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/workers.html?ver=10\">here<\/a><\/noindex>.\n <\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Then we create a policy based on which backups or snapshots of EC2 instances will be created. I\u2019ll briefly explain this below.<\/li>\n<li>Restoration can be performed from the backup \u2014 I\u2019ll discuss this a bit later. <\/li>\n<\/ol>\n<p><\/p>\n<h3>Deployment and configuration<\/h3>\n<p>\nVeeam Backup for AWS is available on <noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/marketplace\/pp\/B081VXF1Q9\">AWS Marketplace<\/a><\/noindex>. <\/p>\n<p>The solution is deployed as follows:<\/p>\n<ol>\n<li>Log in to AWS Marketplace under the AWS account you intend to use for the solution installation.<\/li>\n<li>Open the Veeam Backup for AWS page and select the edition we need (paid or free). More details about the editions can be found <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/lic.html\">here<\/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>In the top right corner, click <b>Continue to Subscribe<\/b>.\n<p><img decoding=\"async\" alt=\"Meet: the new solution Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/bee5554b53ed411789b31d178d4f4875.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>On the subscription page, go to the section <b>Terms and Conditions<\/b> (usage conditions) and there click <b>Show Details<\/b>, then follow the link <b>End User License Agreement<\/b> and read the license agreement. <\/li>\n<li>Submit <b>Continue to Configuration<\/b> and proceed to configuration.\n<\/li>\n<li>On the page <b>Configure this software<\/b> we set the installation settings:\n<ul>\n<li>From the list of <b>Fulfillment Option<\/b> (deployment options), select the option for our product \u2014 <b>VB for AWS Deployment<\/b>.<\/li>\n<li>From the list of versions <b>Software Version<\/b> select the latest version of Veeam Backup for AWS.<\/li>\n<li>From the list of regions <b>Region<\/b> select the AWS region in which the EC2 instance with Veeam Backup for AWS will be deployed.<\/li>\n<\/ul>\n<p>\n<i>Note: <\/i>Learn more about AWS regions <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/using-regions-availability-zones.html\">here<\/a><\/noindex>.\n<\/li>\n<li>Submit <b>Continue to Launch<\/b> to proceed with the launch.\n<p><img decoding=\"async\" alt=\"Meet: the new solution Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/9264144271e73d7ad8dcb303340ae4d3.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>On the page <b>Launch this software<\/b> we perform the following steps:\n<ul>\n<li>In the section <b>Configuration Details<\/b> we check if all settings are correctly specified.<\/li>\n<li>From the action list <b>Choose Action<\/b> Clone <b>Launch CloudFormation<\/b>.<\/li>\n<li>The installation of Veeam Backup for AWS is performed using the AWS CloudFormation stack.\n<p><i>Note: <\/i>Here, a stack is a collection of cloud resources that can be managed as a single unit: create, delete, and use to run applications. You can read more in the AWS documentation.<\/p>\n<p>Click <b>2.1.7. Creating access keys<\/b> and start the stack creation wizard <b>Create stack wizard<\/b>.<\/li>\n<\/ul>\n<p>\n<\/li>\n<\/ol>\n<p>\n<b class=\"spoiler_title\">Creating an AWS CloudFormation stack<\/b>Creating an AWS CloudFormation stack:<\/p>\n<p><img decoding=\"async\" alt=\"Meet: the new solution 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>At this step <b>Specify template<\/b> you can leave the default settings for the stack template. \n<\/li>\n<li>At this step <b>Specify stack details<\/b> enter settings for our stack.\n<ul>\n<li>In the field <b>Stack name<\/b> enter a name; you can use upper and lower case letters, numbers, and hyphens.<\/li>\n<li>In the settings section <b>Instance Configuration<\/b>:<br \/>\n From the list of <b>Instance type for Veeam Backup for AWS server<\/b> you need to select the EC2 instance type on which Veeam Backup for AWS will be installed (hereinafter we will refer to it as <i>Veeam Backup for AWS server<\/i>). It is recommended to choose the type <i>t2.medium<\/i>.<br \/>\n From the list of <b>Key Pair for Veeam Backup for AWS Server<\/b> you need to select a key pair that will be used for authentication on this new server. If the desired key pair is not in the list, you need to create it as described <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/ec2-key-pairs.html\">here<\/a><\/noindex>. <br \/>\n Specify whether to enable automatic EBS volume backups for the Veeam Backup for AWS server (by default, yes, i.e. <i>true<\/i>).<br \/>\n Specify whether to restart the Veeam Backup for AWS server in case of software failure.<br \/>\n Specify whether to restart the Veeam Backup for AWS server in case of infrastructure failure.\n<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>In the network settings section <b>Network Configuration<\/b>:\n<ul>\n<li>Specify whether to create an Elastic IP address for the Veeam Backup for AWS server. See more here.<\/li>\n<li>In the field <b>Allowed Source IP Addresses for connection to SSH<\/b> specify the range of IPv4 addresses from which access to the Veeam Backup for AWS server via SSH will be allowed.<\/li>\n<li>In the field <b>Allowed Source IP Addresses for connection to HTTPS<\/b> specify the range of IPv4 addresses from which access to the Veeam Backup for AWS web interface will be allowed.<br \/>\n The IPv4 address range is specified in CIDR notation (e.g., 12.23.34.0\/24). To allow access from all IPv4 addresses, you can enter 0.0.0.0\/0. (However, this option is not recommended as it reduces the security of the infrastructure.)<\/li>\n<\/ul>\n<p>\n<\/li>\n<li>Based on the specified IPv4 addresses, AWS CloudFormation creates a security group for Veeam Backup for AWS with the corresponding rules for incoming traffic over SSH and HTTPS. (By default, port 22 is used for incoming SSH traffic, and port 443 for HTTPS.) If you plan to specify a different security group for Veeam Backup for AWS during the setup, be sure to manually add the appropriate rules to that group and check that access to AWS services is permitted (as outlined in the Requirements section of the user guide).<\/li>\n<li>In the section <b>VPC and Subnet<\/b> you need to choose an Amazon Virtual Private Cloud (Amazon VPC) and a subnet to which the Veeam Backup for AWS server will connect.\n<\/li>\n<li>At this step <b>Configure stack options<\/b> specify AWS tags, permissions for the IAM role, and other stack settings.\n<p><img decoding=\"async\" alt=\"Meet: the new solution Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/31062236b5ddf46ab22cd69a18c2cf06.jpg\" style=\"display:block;margin: 0 auto;\" \/>\n<\/li>\n<li>At this step <b>Review<\/b> check all settings, select the option <b>I acknowledge that AWS CloudFormation might create IAM resources<\/b> and click <b>Create stack<\/b>.<\/li>\n<\/ol>\n<p>After the installation, we will open the web console by entering the DNS or IP address of the EC2 instance where Veeam Backup for AWS is installed, for example:<br \/>\n<code>https:\/\/ec2-135-169-170-192.eu-central-1.compute.amazonaws.com<\/code><\/p>\n<p>The console displays the resources for which data protection is configured using Veeam Backup for AWS:<\/p>\n<p><img decoding=\"async\" alt=\"Meet: the new solution Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/eb7ed2550eb15398c8c0732e1c2b7f52.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nThe necessary infrastructure, role, and other settings are detailed in <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/configuration.html?ver=10\">the documentation<\/a><\/noindex>.<\/p>\n<h3>Backup Policies<\/h3>\n<p>\nTo protect instances, we create policies. <\/p>\n<p>Different policies can be configured for different types of objects, for example, a policy intended to protect tier 3 applications (the least critical), or policies for tier 2 and tier 1 applications. In the policy settings, we specify:<\/p>\n<ul>\n<li>An account with IAM roles<\/li>\n<li>Regions \u2014 multiple can be selected <\/li>\n<li>What is planned for protection \u2014 this can be all resources (all resources) or selected instances or (tags)<\/li>\n<li>Resources to exclude<\/li>\n<li>Snapshot settings, including whether to use snapshots and what the retention duration should be<\/li>\n<li>Backup settings: repository path, schedule, and retention duration<\/li>\n<li>Cost assessment of services (details below)<\/li>\n<li>Scheduling and notification settings<\/li>\n<\/ul>\n<p><\/p>\n<h4>Built-in cost assessment of services<\/h4>\n<p>\nVeeam Backup for AWS includes a built-in automatic cost assessment of services \u2014 it immediately calculates what the cost of backup services will be according to a specific policy. The calculation includes the following metrics:<\/p>\n<ul>\n<li>Backup cost<\/li>\n<li>Snapshot cost<\/li>\n<li>Traffic costs are particularly important if the repository is located outside the region where infrastructure objects operate (Amazon AWS charges traffic to other regions)<\/li>\n<li>Transaction costs<\/li>\n<li>Total cost<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Meet: the new solution Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/d81df948587d769241c58887ed8769cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nData can be exported to CSV or XML files.<\/p>\n<h3>Auxiliary components - Workers<\/h3>\n<p>\nTo reduce traffic expenses, you can configure the automatic creation of auxiliary components - <b>workers<\/b> in the same AWS region as the protected objects. Workers are automatically launched only during data transfer to\/from Amazon S3 cloud or during recovery, and after completing their tasks, they are turned off and deleted.<\/p>\n<p><img decoding=\"async\" alt=\"Meet: the new solution Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/0926f91f39f09f77e4f4511d1a6d02f9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Backup<\/h3>\n<p>\nFor backup operations, Veeam Backup for AWS uses native snapshots (see <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/EBSSnapshots.html\">Amazon EBS snapshots<\/a><\/noindex>). During backup, Veeam Backup for AWS utilizes AWS CLI commands to create snapshots of EBS volumes attached to the EC2 instance. Depending on the backup scenario you choose, Veeam Backup for AWS will create either a chain of native snapshots or a backup at the image level for the EC2 instance.<\/p>\n<h4>Native snapshots<\/h4>\n<p>\nVeeam Backup for AWS creates native snapshots of the EC2 instance as follows:<\/p>\n<ol>\n<li>First, snapshots of the EBS volumes attached to this instance are taken.<\/li>\n<li>EBS snapshots are assigned AWS tags upon creation. The keys and values of these tags contain encrypted metadata. Veeam Backup for AWS treats EBS snapshots with metadata as native snapshots for the EC2 instance.<\/li>\n<li>If the EC2 instance has already been processed by the backup policy, Veeam Backup for AWS checks the number of restore points in the snapshot chain. If it exceeds the limit specified in the policy, the oldest point is deleted. <i>Note:<\/i> The retention policy and automatic deletion do not apply to snapshots created manually (specifically, those created separately). Such snapshots can be deleted as described <noindex><a rel=\"nofollow\" href=\"https:\/\/helpcenter.veeam.com\/docs\/vbaws\/guide\/backups_remove.html\">here<\/a><\/noindex>. (If by 'manually' we mean the manual triggering of policies outside of the schedule, then a retention policy will apply to snapshots created this way.) <\/li>\n<\/ol>\n<p><\/p>\n<h4>Image-level backups<\/h4>\n<p>\nHere\u2019s how Veeam Backup for AWS performs image-level backups:<\/p>\n<ol>\n<li>First, snapshots of the EBS volumes attached to this instance are taken.<\/li>\n<li>Veeam Backup for AWS uses EBS snapshots as sources for backup. After the backup process is completed, these snapshots are deleted.<\/li>\n<li>Then, in the AWS region where this instance is located, a helper worker is launched to assist with processing the EC2 instance data.<\/li>\n<li>Temporary snapshots are used to create EBS volumes and are attached to the worker instance.<\/li>\n<li>Data is read from the EBS volumes on the worker instance, which is then transferred to the S3 repository, where it will be stored in Veeam format.<\/li>\n<li>During an incremental session, Veeam Backup for AWS reads backup metadata from the S3 repository and uses it to identify blocks that have changed since the previous session. <\/li>\n<li>When the backup is complete, Veeam Backup for AWS removes temporary EBS snapshots and the worker instance from Amazon EC2.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Data Recovery<\/h3>\n<p>\nWith Veeam Backup for AWS, you can restore data in the following ways:<\/p>\n<ul>\n<li>To the original location, overwriting the original instance. All data on this instance will be overwritten with what is stored in the backup, while the instance configuration is preserved.<\/li>\n<li>To a new location, creating a new instance. In this scenario\u2014if you choose to restore to a new location or with new settings\u2014you will need to specify the configuration parameters that will be applied to the instance upon completion of the restoration:\n<ul>\n<li>Region<\/li>\n<li>Encryption settings<\/li>\n<li>Instance name and type<\/li>\n<li>Network settings: Virtual Private Cloud (VPC), subnet, security group<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><\/p>\n<h4>Volume restoration<\/h4>\n<p>Restoration of EC2 instance volumes from a snapshot or from a backup is also supported, to the original or to a new location. In the latter case, you need to specify the AWS region, Availability Zone, and other parameters for the new location. <\/p>\n<p>A worker is also involved in the restoration process. <\/p>\n<p>The process looks like this in brief (using the example of restoring from a backup):<\/p>\n<ol>\n<li>Veeam Backup for AWS launches a worker in the required AWS region, creates the required number of empty EBS volumes, and attaches them to the worker instance. <\/li>\n<li>Restores data from the backup to these volumes.<\/li>\n<li>Detaches the EBS volumes and moves them to the required location (either the original or another AWS region), where these volumes are kept as separate. <\/li>\n<li>Removes the worker instance upon completion of operations.<br \/>\n <i>Note:<\/i> Don't forget that after recovery, the volume will not be automatically attached to the EC2 instance (it will simply be saved in the specified location as a separate EBS volume).<\/li>\n<\/ol>\n<p><\/p>\n<h4>File Recovery<\/h4>\n<p>\nAllows you to recover individual files without the need to restore the entire instance. <\/p>\n<p>When you initiate a file-level recovery, you receive a URL (based on the public DNS name of the worker) where you can see the entire file structure on the guest OS, find the necessary files, and download them to your local machine. <br \/>\nAdditionally, to ensure security, you can verify the certificate and its fingerprint to be sure there is no MiTM.<\/p>\n<p><img decoding=\"async\" alt=\"Meet: the new solution Veeam Backup for AWS\" src=\"\/wp-content\/uploads\/2019\/12\/7205b4f5385ae0505ea287d689a9d6d9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Integration with Veeam Backup &amp; Replication<\/h3>\n<p>\nIf Veeam Backup &amp; Replication is deployed in your infrastructure, you can configure the recovery of the machines it includes to the Amazon EC2 cloud using the Direct Restore to AWS functionality, and then protect this cloud data with Veeam Backup for AWS. <br \/>\nVeeam Backup &amp; Replication also supports working with Amazon S3 repositories created by Veeam Backup for AWS \u2014 backups of Amazon EC2 instances can be restored to on-premises infrastructure.<\/p>\n<h3>Features of the free version<\/h3>\n<p>\nThe free version of Veeam Backup for AWS allows backing up to 10 EC2 instances; recovery from backups is performed without restrictions. <br \/>\n<i>Note: <\/i>Recommended usage <i>t2.medium<\/i>.<\/p>\n<p>Estimated resource cost is 9.8 USD\/month, based on 24\/7 usage with the following default settings:<\/p>\n<ul>\n<li>EC2 \u2014 1 t3.micro instance<\/li>\n<li>EBS \u2014 1 GP2 volume of 8 GB<\/li>\n<li>Configuration for S3 repository \u2014 50 GB Standard S3 storage, 13,000 S3 PUT requests, 10,000 S3 GET requests, 50 GB S3 Select usage.<\/li>\n<\/ul>\n<p><\/p>\n<h3>Useful links<\/h3>\n<p>\nVeeam Backup for AWS solution on <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\">User Guide<\/a><\/noindex> (in English).<br \/>\n<br \/>Source: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/veeam\/blog\/481926\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u043d\u0430\u0447\u0430\u043b\u0435 \u0434\u0435\u043a\u0430\u0431\u0440\u044f \u0432\u044b\u0448\u043b\u043e \u0432 \u0441\u0432\u0435\u0442 \u043d\u043e\u0432\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 Veeam Backup for AWS \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440 Amazon Elastic Compute Cloud (Amazon EC2). \u0421 \u0435\u0433\u043e \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u043c\u043e\u0436\u043d\u043e \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u0442\u044c \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u0435 \u043a\u043e\u043f\u0438\u0438 \u0438\u043d\u0441\u0442\u0430\u043d\u0441\u043e\u0432 \u0415\u04212 \u0438 \u0441\u043e\u0445\u0440\u0430\u043d\u044f\u0442\u044c \u0438\u0445 \u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u043e\u043c \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 Amazon Simple Storage Service (Amazon S3), \u0442\u0430\u043a\u0436\u0435 \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u0442\u044c \u0446\u0435\u043f\u043e\u0447\u043a\u0438 \u0441\u043d\u0430\u043f\u0448\u043e\u0442\u043e\u0432 \u0415\u04212 \u0432 \u043d\u0430\u0442\u0438\u0432\u043d\u043e\u043c \u0444\u043e\u0440\u043c\u0430\u0442\u0435. \u0414\u043b\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-54466","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - 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\/en\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\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\/en\/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\udd47Meet the new solution Veeam Backup for AWS | ProHoster","description":"At the beginning of December, a new solution Veeam Backup for AWS was released for backing up and restoring cloud infrastructures of Amazon Elastic Compute Cloud (Amazon EC2).","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/znakomtes-novoe-reshenie-veeam-backup-for-aws","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","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\/en\/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\/en\/wp-json\/wp\/v2\/posts\/54466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=54466"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/54466\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=54466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=54466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=54466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}