{"id":53098,"date":"2019-11-23T00:00:00","date_gmt":"2019-11-22T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline"},"modified":"2020-02-18T14:00:57","modified_gmt":"2020-02-18T11:00:57","slug":"operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","title":{"rendered":"Operation 'Migration': How the move to the DataLine cloud happens","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

About 7 years ago, the very first projects moved to our cloud simply and straightforwardly. Virtual machine images were uploaded to an FTP server, or they were brought on hard drives. Then, through a special import server, VMs were uploaded to the cloud.<\/p>\n

If it's not an issue for the client to turn off the virtual machine for a day or two (or there are no other options), then that can work. But if downtime should be a maximum of one hour, then this method won't be suitable. Today, I will discuss the tools that can help migrate to the cloud with minimal downtime and how our migration process is structured.<\/p>\n

\"Operation
\n<\/a><\/noindex><\/p>\n

Migration using Veeam Backup and Replication<\/h3>\n

\nVeeam Backup and Replication is widely known as a tool for creating backups and replicas. We use it for migration between our sites and for transferring clients from private virtualization to our cloud. The client\u2019s virtual machines are replicated to our vCenter, and then the engineer adds them to vCloud Director. <\/p>\n

The initial replication is performed on the powered-on virtual machine. At a scheduled time, the machine on the client's side is turned off. Replication is initiated once more to transfer the changes that occurred since the first replication. After that, the virtual machine is started in our cloud. <\/p>\n

\"Operation
\n
\nTypically, the time from when the machine is turned off on the client\u2019s infrastructure to when it is turned on in our cloud does not exceed half an hour, more often it takes 15-20 minutes. <\/p>\n

Meanwhile, the original virtual machine remains on the client's site. If something goes wrong, it's always possible to roll back and turn it back on. This method is also convenient for the client as it does not require them to have Veeam.<\/p>\n

Case 1
\nThe client had their virtual infrastructure based on VMware \u2013 40 VMs totaling 30 TB. The equipment on which the cluster was deployed was already outdated, and the client decided not to deal with purchasing new hardware and to move to a public cloud. The requirement for critical systems' downtime was no more than one hour. Veeam Replication was chosen as the tool. A plus was that the client's internet service provider was present in our data center, which allowed for a good channel to be organized. The migration took about a month, with downtime during the switch of up to 30 minutes for one group of virtual machines.<\/i><\/p>\n

Migration using Veeam Cloud Connect<\/h3>\n

\nVeeam Cloud Connect is a tool that helps set up the replication of virtual machines and run replicas in the cloud of a service provider. After the update in 2019<\/a><\/noindex> the year, it became possible to replicate virtual machines directly to vCloud Director. The only requirement is that the client must have their own Veeam Backup and Replication deployed, version 9 or higher. In short (the detailed version here<\/a><\/noindex>), the entire process looks like this.<\/p>\n

In vCloud Director, an organization is created with the necessary resources and networks. In Veeam Cloud Connect, we create an account, which the client connects to from their Veeam B&R, selects the DataLine provider and organization, and sets up replication tasks. Aside from the fact that this type of migration has minimal downtime of about 15\u201320 minutes, the client is not dependent on the provider's support and manages the entire process independently: creating replication tasks, performing the replication, shutting down machines, and starting them up at the new site. <\/p>\n

\"Operation
\n
\nCase 2
\nThe client's infrastructure, from where the migration was planned, was located in Belarus. It was necessary to transfer 90 VMs with a total volume of 27 TB, while the internet channel was 100 Mbps. If a backup was made and immediately uploaded to our cloud, it would take several days for some VMs. During that time, a large delta would accumulate on the VMs, which could negatively affect the performance of the machines or, even worse, cause the datastore to run out of space. The following actions were taken: first, the client made a local full backup and transferred its copy to our cloud via Veeam Cloud Connect. Then they created and transferred an increment to the cloud. The original virtual machine continued to operate. After shutting down the VM, the client made one more increment and also transferred it to the cloud. On our side, we deployed the virtual machine from the full backup, and then applied the two increments. This scheme ultimately minimized downtime to 2 hours when switching to our site. <\/i><\/p>\n

Migration using VMware vCloud Availability<\/h3>\n

\nIn March of this year, VMware released vCloud Availability 3.0, which allows for the migration of virtual machines between different clouds (vCloud Director \u2013 vCloud Director) and from the client's private virtualization environments to the cloud (vCenter \u2013 vCloud Director). The main convenience is the integration with the vCloud Director interface. This significantly simplifies the replication management process and minimizes downtime during switching.<\/p>\n

Using this tool, we migrated one of our clients from our Moscow cloud to our cloud in St. Petersburg. We needed to transfer 18 virtual machines with a total capacity of 14 TB. An organization was created for the client in the St. Petersburg cloud, and the necessary networks were set up. Next, from the vCloud Director interface, the client proceeded to the vCloud Availability settings, created replication tasks, and switched to the St. Petersburg site at a convenient time. The downtime during the switch was 12 minutes.<\/p>\n

\"Operation
\nThe migration scheme between DataLine clouds in St. Petersburg and Moscow.<\/i><\/p>\n

vCloud Availability has a VM migration mechanism from the client's site to our cloud. For this, a special vCloud Availability appliance is deployed in the client's vCenter. After a simple setup, a connection to the cloud is established and migration tasks are configured. The client also independently manages the entire process, minimizing the migration time.<\/p>\n

\"Operation
\nThe scheme for migrating virtual machines from a private installation to the cloud.<\/i><\/p>\n

VMware vCloud Availability has many other use cases, and we will discuss them in detail in a separate article soon. <\/p>\n

Preparation for migration <\/h3>\n

\nTo select a tool and actually start the migration, it is essential to determine the following points:<\/p>\n

Where we are migrating from. <\/b>If you are migrating from a private solution, you have complete freedom in choosing tools. If you are leaving a provider, it gets more complicated. Most likely, connecting the infrastructures of two providers and simply transferring the VMs will not be possible due to security concerns. Sometimes, the provider that the client intends to leave may even sabotage the process and delay things. Leaving a provider can still be done the old-fashioned way: by exporting VMs to disks and using FTP or migrating at the application level. The name of the latter is conditional, and it looks something like this.<\/p>\n

Case 3
\nIt was necessary to migrate the client's SAP system from a European provider: 34 VMs with a total size of 54 TB. Resources were allocated to the client in our cloud. A network connection was established between us and the European provider's infrastructure. Application servers were redeployed with the required configurations applied. Large databases were migrated by uploading backups to our cloud. Subsequently, replication was set up between the databases on our and the original sites. At the agreed time, we switched to the databases in our cloud.<\/i><\/p>\n

Data volume and internet channel.<\/b> We usually ask the client to provide a report on the systems with memory, CPU, and disk parameters. We assess whether the channel is sufficient to directly send replicas or backups of the virtual machines. <\/p>\n

Acceptable downtime.<\/b> For different systems and, accordingly, virtual machines, it can vary depending on their criticality for the business. Usually, the client comes with predefined requirements for downtime during migration, and based on that, we select the appropriate tool and migration plan. We try to schedule the final switch for the nighttime or weekends so that even minimal downtime goes unnoticed by the end users of the client. <\/p>\n

Based on this data, we can choose the tool and proceed with the migration itself. Here's what happens next.<\/p>\n

    \n
  1. Setting up network connectivity. <\/b>We establish network connectivity between our cloud and the client's infrastructure. Virtual machines will be copied over this network. If Veeam Backup and Replication is used, it is a dedicated channel, less often a VPN channel. If Veeam Cloud Connect is used, everything goes through the internet or the same dedicated channel.\n

    Then, the network for the VMs in the cloud is configured. Machines usually move in batches over several days. After the VMs have been moved to us and launched, they must interact with machines that remain at the original site. <\/li>\n

  2. Migration schedule.<\/b> When there are many machines, it makes sense to break them into groups and transport them in batches. Together with the client, we agree on a plan outlining when and which machines will move and when the final replication and switch to the new site will be carried out. <\/li>\n
  3. Test migration.<\/b> We migrate the test virtual machine and check if everything is configured correctly: network connectivity between sites, availability of the virtual machine for machines on the source site, account permissions, and more. This test helps avoid delays during the actual migration phase.<\/li>\n<\/ol>\n

    \nThat's all from my side. Feel free to ask questions in the comments and share your migration experiences.
    \n
    Source:     habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

    \u041b\u0435\u0442 7 \u043d\u0430\u0437\u0430\u0434 \u0441\u0430\u043c\u044b\u0435 \u043f\u0435\u0440\u0432\u044b\u0435 \u043f\u0440\u043e\u0435\u043a\u0442\u044b \u043f\u0435\u0440\u0435\u0435\u0437\u0436\u0430\u043b\u0438 \u0432 \u043d\u0430\u0448\u0435 \u043e\u0431\u043b\u0430\u043a\u043e \u043f\u0440\u043e\u0441\u0442\u043e \u0438 \u043d\u0435\u0437\u0430\u0442\u0435\u0439\u043b\u0438\u0432\u043e. \u041e\u0431\u0440\u0430\u0437\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d \u0437\u0430\u0433\u0440\u0443\u0436\u0430\u043b\u0438\u0441\u044c \u043d\u0430 FTP-\u0441\u0435\u0440\u0432\u0435\u0440, \u0438\u043b\u0438 \u0438\u0445 \u043f\u0440\u0438\u0432\u043e\u0437\u0438\u043b\u0438 \u043d\u0430 \u0436\u0435\u0441\u0442\u043a\u0438\u0445 \u0434\u0438\u0441\u043a\u0430\u0445. \u0417\u0430\u0442\u0435\u043c \u0447\u0435\u0440\u0435\u0437 \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0439 \u0438\u043c\u043f\u043e\u0440\u0442-\u0441\u0435\u0440\u0432\u0435\u0440 \u0412\u041c \u0437\u0430\u0433\u0440\u0443\u0436\u0430\u043b\u0438 \u0432 \u043e\u0431\u043b\u0430\u043a\u043e. \u0415\u0441\u043b\u0438 \u0434\u043b\u044f \u043a\u043b\u0438\u0435\u043d\u0442\u0430 \u043d\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0432\u044b\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u043a\u0443 \u043d\u0430 \u0441\u0443\u0442\u043a\u0438-\u0434\u0432\u043e\u0435 (\u0438\u043b\u0438 \u043d\u0435\u0442 \u0434\u0440\u0443\u0433\u0438\u0445 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u043e\u0432), \u0442\u043e \u043c\u043e\u0436\u043d\u043e \u0438 \u0442\u0430\u043a. \u041d\u043e \u0435\u0441\u043b\u0438 \u043f\u0440\u043e\u0441\u0442\u043e\u0439 \u0434\u043e\u043b\u0436\u0435\u043d \u0431\u044b\u0442\u044c […]<\/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-53098","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Operation 'Migration': How the move to the DataLine cloud happens | ProHoster","description":"About 7 years ago, the very first projects migrated to our cloud quite simply. Virtual machine images were uploaded to the FTP server, or they were brought on hard drives.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","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\u041e\u043f\u0435\u0440\u0430\u0446\u0438\u044f \u201c\u041c\u0438\u0433\u0440\u0430\u0446\u0438\u044f\u201d: \u043a\u0430\u043a \u043f\u0440\u043e\u0438\u0441\u0445\u043e\u0434\u0438\u0442 \u043f\u0435\u0440\u0435\u0435\u0437\u0434 \u0432 \u043e\u0431\u043b\u0430\u043a\u043e DataLine | ProHoster","og:description":"\u041b\u0435\u0442 7 \u043d\u0430\u0437\u0430\u0434 \u0441\u0430\u043c\u044b\u0435 \u043f\u0435\u0440\u0432\u044b\u0435 \u043f\u0440\u043e\u0435\u043a\u0442\u044b \u043f\u0435\u0440\u0435\u0435\u0437\u0436\u0430\u043b\u0438 \u0432 \u043d\u0430\u0448\u0435 \u043e\u0431\u043b\u0430\u043a\u043e \u043f\u0440\u043e\u0441\u0442\u043e \u0438 \u043d\u0435\u0437\u0430\u0442\u0435\u0439\u043b\u0438\u0432\u043e. \u041e\u0431\u0440\u0430\u0437\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d \u0437\u0430\u0433\u0440\u0443\u0436\u0430\u043b\u0438\u0441\u044c \u043d\u0430 FTP-\u0441\u0435\u0440\u0432\u0435\u0440, \u0438\u043b\u0438 \u0438\u0445 \u043f\u0440\u0438\u0432\u043e\u0437\u0438\u043b\u0438 \u043d\u0430 \u0436\u0435\u0441\u0442\u043a\u0438\u0445 \u0434\u0438\u0441\u043a\u0430\u0445.","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/operatsiya-migratsiya-kak-proishodit-pereezd-v-oblako-dataline","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-11-22T21:00:00+00:00","article:modified_time":"2020-02-18T11:00:57+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"53098","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 06:04:31","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 14:29:47","updated":"2026-01-24 06:04:31","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\/53098","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=53098"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/53098\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=53098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=53098"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=53098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}