Description:FIELD OF THE INVENTION
[0001] The present invention relates to migration of virtual machines which are running (functioning) at on-premises computing environment to cloud environments. More specifically, the present invention relates to a method, a system and a cloud platform for migration of virtual machine(s) from on-premises or cloud to cloud environments.
BACKGROUND FOR THE INVENTION:
[0002] A virtual machine (VM) is a software emulation of a physical computer, running its own operating system and applications independently. VMs uses the host system's hardware resources while remaining isolated from other VMs. This allows multiple VMs to run on a single physical machine, enhancing resource utilization and security. VMs are essential in cloud computing and development environments.
[0003] A source host is the original computing environment where a virtual machine resides. This can be an on-premises server or a cloud-based server. The target environment is the destination computing environment to which the virtual machine is being migrated, typically a cloud-based server. The migration process involves transferring the virtual machine's data from the source host to the target environment to ensure seamless operations in a new environment.
[0004] Migration of virtual machines (VMs) involves transferring VMs from one host (source) to another (target), typically to optimize performance or resources. Prior art Methods include live migration, where VMs are moved without downtime; Cold migration, involving VM shutdown before transfer (migration); and Storage migration, which moves VM data to different storage devices. These methods ensure minimal disruption and efficient resource utilization during the migration process.
[0005] Agentless migration refers to the process of migrating virtual machines (VMs) without installing additional software agents on the source servers. Instead, it uses existing features like VM snapshots and Changed Block Tracking (CBT) to replicate data from the source VM to the target environment.
[0006] Current methods for migrating virtual machines (VMs) often rely on hypervisor-based migration, which involves creating a hypervisor layer to facilitate the transfer. However, these methods face limitations as they are not universally compatible with all cloud platforms, leading to issues with adaptability and agility. Additionally, hypervisor-based migrations require the source host to grant full access to its IT infrastructure to the migrator, posing security and operational challenges. For example, if a user wants to migrate VMs from an on-premises server to a cloud environment, the hypervisor-based approach may not work seamlessly across different cloud providers like AWS or Azure. Moreover, the need for complete access to the source host's infrastructure can expose sensitive data and complicate the migration process.
[0007] US10216531B2 describes a method for shifting virtual machines between different hosts within a cloud environment. The method involves extracting the virtual machine data, transferring VM to the target environment, and provisioning the virtual machine on the target environment. The method uses hypervisor layers of VMs for migration.
[0008] CN114356450A describes a cross-cloud migration deployment method and system. The method uses constructing project engineering, loading scene components, and configuring service protocols to facilitate the migration of virtual machines across different cloud environments. The method uses hypervisor layers of VMs for migration.
[0009] WO2020/019017A1 describes a method for migrating virtual machines within a cloud environment. It includes steps for extracting virtual machine data, transferring it to the target environment, and provisioning the virtual machine on the target environment. The method ensures synchronization of the virtual machine with the stored data to enable its functioning in the new environment. This method also uses hypervisor of VM for migration.
[0010] One major challenge in Hypervisor based methods of the patents described above is ensuring that the destination host has sufficient resources to accommodate the VM being migrated. This includes adequate CPU, RAM, and storage. If the destination host lacks these resources, the migration process can fail, leading to downtime and potential data loss. Proper planning and resource assessment are crucial to avoid such issues.
[0011] Another significant problem is network connectivity between the source and destination hosts. Slow or unstable network connections can disrupt the migration process, causing delays or failures. Ensuring a stable and high-speed network connection is essential for a smooth migration. Network configuration and bandwidth must be carefully managed to prevent interruptions during the transfer of VM data. If there are variations in these factors, there is loss of data while migration.
[0012] Therefore, there is a need for a more flexible and secure migration methods that can overcome these limitations and ensure smooth transitions between diverse environments.
OBJECTS OF THE INVENTION:
[0013] An object of the present invention is to provide a system, a method, a cloud platform for migrating virtual machines.
[0014] One more object of the present invention is to improve security of data by improving granularity of access, while migrating the virtual machines from a source host to a target environment.
[0015] One more object of the present invention is to provide a method, a system and a cloud platform for migrating VMs with improved agility to adapt to various types of computing platforms (environments).
[0016] One more object of the invention is to provide a method for migration which reduces loss of data while migration.
SUMMARY OF THE INVENTION:
[0017] The present invention addresses the challenges associated with migrating virtual machines (VMs) from on-premises environments or cloud to cloud platforms (environments). Traditional hypervisor-based migration methods face compatibility issues across different cloud providers and require full access to the source host's infrastructure, posing security risks. Additionally, these methods struggle with resource allocation and network connectivity, leading to potential downtime and data loss. The invention aims to provide a more flexible, secure, and efficient migration process that overcomes these limitations.
[0018] The invention comprises a method, a system, and a cloud platform for migrating VMs. The method, the system and the cloud platform use an extractor for retrieving the operating system data from the source VM, a migration tool for transferring said data to the target environment, a configurator for provisioning a new VM in the target environment, and a synchronizer for ensuring the new VM operates seamlessly with the transferred data. The system and the cloud platform can also include a buffer memory for temporary storage during the migration process and can be implemented as SaaS applications for enhanced scalability and flexibility.
[0019] The method for migrating virtual machines involves several steps of selecting the VM to be migrated, extracting the operating system data, transferring the extracted data to the target environment, provisioning a new VM in the target environment, and synchronizing the provisioned VM with the stored data. The method starts with selecting the VM through a user interface or a machine learning (ML) module. The extractor then retrieves the operating system data, which is to be transferred to the target environment using the migration tool. The configurator sets up the new VM with the necessary virtual hardware components, and the synchronizer ensures that the new VM operates correctly by synchronizing it with the stored data. This method ensures a smooth and secure migration process, minimizing downtime and data loss.
[0020] The system for migrating virtual machines includes several key elements such as an extractor, a migration tool, a configurator, and a synchronizer. The extractor is responsible for retrieving the operating system data from the source VM, ensuring that all necessary information is captured for the migration. The migration tool facilitates the transfer of this extracted data to the target environment, using techniques like vSphere, vMotion (Trade names of tools) or cold migration to ensure minimal disruption. The configurator provisions a new VM in the target environment based on the extracted data, setting up virtual hardware components such as CPUs, memory, network adapters, and storage. Finally, the synchronizer ensures that the provisioned VM operates seamlessly by synchronizing it with the stored data, maintaining consistency and performance.
[0021] The present invention enhances security by transferring only necessary data, reducing the need for full access to the source host's infrastructure. The present invention ensures compatibility across various cloud platforms.
BRIEF DESCRIPTION OF DRAWINGS:
[0022] Figure 1a shows a flowchart of a method for migrating VMs in accordance with the present invention;
[0023] Figure 1b shows a flowchart of one more embodiment of a method for migrating VMs in accordance with the present invention;
[0024] Figure 2a shows a schematic diagram of a source host and a target environment where the method shown in figure 1a is executed and also a system for migration in accordance with the present invention;
[0025] Figure 2b shows a schematic diagram of a source host and a target environment where the method shown in 1b is executed;
[0026] Figure 3a shows a schematic diagram of alternative embodiments of the system shown in figure 2a; and
[0027] Figure 4a shows a schematic diagram of a cloud platform for migrating VMs in accordance with the present invention.
DETAILED DESCRIPTION OF DRAWINGS:
[0028] The present invention provides a method (200), a system (300) and a cloud platform (400) for migrating virtual machines (VMs) from a source host (520) to a target environment (530). Using the method (200), the system (300) and the cloud platform (400), a user can migrate the Virtual machines (VMs) from the source host (520) to the target environment (530).
[0029] In a preferred embodiment of the invention, the method (200) (figure 1a) for migrating the VMs is provided. The method (200) migrates a virtual machine(s) (501a/501b/501c) (figure 2a) from the source host (520) to the target environment (530). The source host (520) can be an on-premises computing environment (520a) or a cloud environment (523b). The on-premises computing environment (520a) includes physical servers hosting applications and databases, networking equipment like routers and switches, and storage systems such as hard drives and SSDs, the features backup solutions for data recovery and various software applications. The cloud environment (523b) can include virtual servers that provide scalable computing resources. The cloud environment (523b) includes various storage solutions such as object storage, block storage, and file storage, networking services like virtual networks, load balancers, and firewalls manage traffic and security managed database services, data warehouses, and analytics tools. Additionally, the cloud environment (523b) includes security services like identity and access management, encryption, and threat detection, all managed by cloud service providers. The cloud environment (523b) can be a cloud platform. Trade names of some existing cloud platforms are Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), IBM Cloud, Oracle Cloud.
[0030] The target environment (530) is a cloud environment. The target environment (530) can be a cloud platform. The virtual machines (501a, 501b, 501c) can be running in the source host (520).
[0031] The method (200) starts at step (201).
[0032] The virtual machine (501a/501b) needs to be migrated from the source host (520) to the target environment (530) is selected. More specifically, the required Virtual machine (VM) (501a) can be selected through a user interface (U1) of a computing device (525) by a user or by a machine learning module (525a) which is preprogrammed for selecting. The machine learning (ML) module (525a) can be an artificial intelligence (AI) module.
[0033] At step 210, the data (550) of the selected virtual machine (501a) is extracted. More specifically, the data (550) is the data of an operating system (O1/O2) of the virtual machine (501a).The data can be one or more operating systems (O1, O2) which are responsible for the operations of the virtual machines(501a). The computing device (525), the source host (520) is configured with an extractor (310). The extractor (310) has a set of prestored modules (instructions) to extract operating system (O1) data from the virtual machine (VM) (501a) by accessing the VM's virtual disk files, such as VMDK (Virtual Machine Disk) files in VMware environments. The disk files store all the data of the VM, including the operating system, applications, and user files. The extractor (310) mounts the VMDK file to another working VM or use specialized tools like Disk Genius (Trade names) or qemu-nbd (Trade names) to open and extract the data. For example, in VMware (trade name), the VMDK file can be attached to another VM, change its status to online in Disk Management, and assign a drive letter to browse and extract the files. This process ensures that the operating system data is accurately retrieved without booting the original VM. Similarly, the extractor (310) may use such techniques to extract data from the operating system (O1) of the virtual machine (501a). Similarly, if the VM (501b) is selected to migrate, the extractor (310) extracts the operating system (O2) of the VM (501b). The data (550) with the Operating system (O1/O2) details forms an extracted data (550a).
[0034] At step 220, the extracted data (550a) from the source host (520) is transferred to the target environment (530) by a migration tool (320). The migration tool (320) may be vSphere vMotion (Trade name), which transfers the VM's memory and state to the target environment (530). Alternatively, a user can opt for cold migration techniques, where the VM is powered off before the transfer, ensuring no active processes are disrupted. The activity of the migration tool (320) can be triggered by a user through the user interface (U1). The extracted data (550a) after transferred to the target environment (530) forms a transferred data (552a). Further, the transferred data (552a) is stored in a memory (532) of the target environment (530). The transferred data (552a) stored in the memory (532) is a stored data (203).
[0035] At step 230, a respective virtual machine (502a) as per the extracted data (550a) is provisioned in the target environment (500). A respective virtual machine (502a) is the VM of the same functions and configurations of the Virtual machine (501a) which was intended to migrate from the source host (520) to the target environment (530). The Virtual machine (502a) is the VM at the target environment (530). Similarly, a virtual machine (502b) is configured at the target environment (530) for migrating the virtual machine (501b) from the source host (520) to the target environment (530).
[0036] More specifically, provisioning is done by a configurator (330). The configurator (330) is a sub module, or a module configured in the target environment (530). The configurator (330) may clone the VM (501a), deploying from a template, or creating from a blank virtual hard disk for provisioning the VM (502a). The provisioning process includes setting up a virtual hardware (H1, H2) according to the extracted data (550a). Setting up of the virtual hardware (H1) during the provisioning of a virtual machine (VM) (502a) involves configuring various components to ensure the VM (502a) operates effectively. Further, allocating virtual CPUs (vCPUs), which determines the processing power available to the VM (502a), and assigning virtual memory (RAM) to provide the necessary resources for applications and the operating system. Additionally, virtual network adapters (vNICs) are configured to enable network connectivity, allowing the VM (502a) to communicate with other devices and the networks (N1). Furthermore, storage is set up by attaching virtual hard disks (VHDs) or virtual machine disk files (VMDKs), which stores the VM's data and operating system (O1).
[0037] Other settings, such as virtual graphics adapters and peripheral devices, can also be configured based on the VM's (502a) requirements. This setup ensures the VM (502a) has all the necessary virtual hardware components to function as a physical machine.
[0038] The provision process involves installing necessary software, and configuring networks (N1, N2) settings according to the virtual hardware.
[0039] The user interface (U1) may have a set of modules to enable the user to perform the provisioning of the VM (502a) in the target environment (530).
[0040] At step 240, the provisioned virtual machine (502a) in the target environment (530) is synchronised with the stored data (203) to enable the functioning of the provisioned virtual machine (502a) in the target environment (530). A synchronizer (340) is associated with the target environment (530). The synchronizer (340) is a sub module with configured instructions. The synchronizer (340) synchronizes the provisioned virtual machine (502a) in the target environment (530) with the stored data (203).
[0041] The synchronizer (340) synchronises the entire contents of the source VM's (501a) virtual disk are compared with the target VM's disk using checksums. This comparison identifies any differences between the two disks, ensuring that the target VM (502a) has an exact replica of the source VM's (501a) data (550).
[0042] The synchronizer (340) track changes to the VM's (502a) data and replicate these changes to the target environment (530). The synchronizer (340) performs the delta synchronization operation, where only the changes made to the VM's (502a) data since the last synchronization are replicated. This ensures that the target VM (502a) remains up to date with minimal data transfer.
[0043] Hardware elements involved in synchronization include the target environment's (530) storage systems (532), such as SSDs or HDDs, which store the VM's (502a) data. Network adapters and controllers manage the data transfer between the source and target environments, ensuring efficient and secure communication. Additionally, the target environment's (530) CPU and memory resources are allocated to the VM (502a) to handle the synchronization tasks and maintain performance.
[0044] The synchronizer (340) may use VMware environment, vSphere Replication (Trade name) to schedule replication based on factors like data change rates and network bandwidth. The replication agent tracks changes to the VM's virtual disks and periodically sends these changes to the target environment. This process ensures that the target VM's data is continuously updated, maintaining consistency with the source VM.
[0045] The synchronization (240) of provisioned VMs (502a) involves a combination of software and hardware elements working together to ensure the VM operates correctly and efficiently in the target environment. This process minimizes downtime and ensures data integrity, providing a seamless transition for the VM (502a) from the source host (520) to the target environment (530).
[0046] The user interface (U1) may have a set of modules to enable the user to perform the synchronisation (240).
[0047] After the step of synchronisation (240), the VM (501a) is migrated from the source host (520) to the target environment (530) as the VM (522a). All the data related to the VM (501a) is transferred to the target environment (530) and the VM (522a) runs in the target environment (530) with all the data carried form the source host (520). The user may use the VM (522a) in the target environment (530) for computing operations. The method (200) ends at step 242.
[0048] Similarly, by following the steps of the method (200), the VM (501b) can be migrated from the source host (520) to the target environment (530) as the (522b) (by provisioning the hardware (H2) and network (N2)). Similarly, any number of VMs (501a, 501b, 501c) can be migrated from the source host (520) to the target environment (530) as VMs (522a, 522b, 522c) using the method (200). The VMs can be migrated one after the other or subsequently (parallelly). It is obvious to skilled person to configure the extractor (310), the migration tool (320), the configurator (330), the synchronizer (340) in the source host (520) or the target environment (530) accordingly for migrating the plurality of VMs (501a, 501b, 501c).
[0049] In one more embodiment (200a) (Figure 1b) of the method (200), there are two additional steps 221, and 222 for transferring the extracted data (550a).
[0050] At step 221, the extracted data (550a) is transferred from the source host (520) to a buffer memory (534) (Figure 2b) (generally refers as “staging area”). The extracted data (550a) is stored in the buffer memory (534). The buffer memory (534) can be a memory of a computing environment (580) which is functionally connected to the source host (520) and the target environment (530).
[0051] At step 222, the stored extracted data (551) in the buffer memory (534) is transferred from the buffer memory (534) to the memory (532) of the target environment (530).
[0052] In one more embodiment of the present invention (figure 2a), the system (300) for migrating VMs (501a, 501b, 501c) is provided. The system (300) has modules such as the extractor (310), the migration tool (320), the configurator (330) and the synchronizer (340). The details of the system (300) can be understood in relation to the method (200) described. The system (300) can be configured in a computing environment (not numbered) with the source host (520) and the target environment (530).
[0053] The extractor (310) of the system (300) is associated with the source host (520) for extracting the data (550) which is the data of the operating system (O1/ O2) of the virtual machine (501a or 501b) needs to be migrated from the source host (520) to the target environment (530). The migration tool (320) of the system (300) is associated with the source host (520) for transferring the extracted data (550a) from the source host (520) to the target environment (530).
[0054] The configurator (330) of the system (300) is associated with the target environment (530) for provisioning the respective virtual machine (502a) according to the extracted data (550a) in the target environment (530). The synchronizer (340) of the system (300) is associated with the target environment (530) for synchronizing the provisioned virtual machine (502a) in the target environment (530) with the stored data (203) to enable the functioning of the provisioned virtual machine (502a) in the target environment (500).
[0055] The modules (310, 320, 330, 340) can be configured separately in respective memories (not shown) of the source host (520) and the target environment (530).
[0056] A user can configure these modules in the existing source host (520) and the target environment (530) to migrate the virtual machines (501a, 501b).
[0057] In one more embodiment (300a) (figure 3a) of the system (300), the system (300a) has the buffer memory (534). The extracted data (550a) from the source host (520) is stored in the buffer memory (534) (figure 2b) of the system (330a) before transferring to the memory (532) of the target environment (530).
[0058] In one more embodiment (300b) (figure 3a) of the system (300), the system (300b) has an extractor (310b), a migration tool (320b), a configurator (330b), a synchronizer (340b). The extractor (310b), the migration tool (320b), the configurator (330b) and the synchronizer (340b) are SaaS applications. The source host (520b) and the target environment (530b) are connected into a Saas infrastructure (500b). The SaaS infrastructure (500b) has a set of hardware and software for enabling the SaaS applications to perform respective functions as SaaS services. The functions, configurations of the extractor (310b), the migration tool (320b), the configurator (330b), the synchronizer (340b) are same as of the functions, configurations of the extractor (310), the migration tool (320), the configurator (330) and the synchronizer (340). The extractor (310b), the migration tool (320b), the configurator (330b), the synchronizer (340b) has SaaS supportive applications which enable the SaaS based functioning of the extractor (310b), the migration tool (320b), the configurator (330b) and the synchronizer (340b).
[0059] In one more embodiment of the present invention a cloud platform (400) (figure 4a) for migrating the virtual machine(s) (501a, 502a, 502c) from the source host (520) to the target environment (530). The cloud platform (400) is connected functionally to the source host (520) and the target environment (530) trough networks (not numbered). The cloud platform (400) can be accessed by a URL or can be activating an application configured in a computing device (460). The computing device (460) is functionally connected to the source host (520) and the target environment (530).
[0060] The cloud platform (400) has the modules which are configured in a memory (not shown) of the cloud platform (400). The modules are an extractor (410), a migration tool (420), a configurator (430) and a synchronizer (440). The extractor (410) is associated with the source host (520) connected with the cloud platform (400). The extractor (410) extracts the data (550) of the virtual machine (501a/501b) needs to be migrated from the source host (520) of the cloud platform (400) to the target environment (530) of the cloud platform (400). The data (550) is the data of an operating system (O1, O2) of the virtual machine (501a or 501b) in the cloud environment.
[0061] The migration tool (420) of the cloud platform (400) is associated with the source host (520) for transferring the extracted data (550a) from the source host (520) to the target environment (530). The extracted data (550a) is stored in the memory (532) of the target environment (530).
[0062] The configurator (430) is associated with the target environment (530) for provisioning the respective virtual machine (502a) according to the extracted data (550a) in the target environment (500).
[0063] The synchronizer (440) is associated with the target environment (530) for synchronizing the provisioned virtual machine (502a) in the target environment (530) with the stored data (203) to enable the functioning of the provisioned virtual machine (502a) in the target environment (530).
[0064] The functions, configurations of the extractor (410), the migration tool (420), the configurator (430), and the synchronizer (440) of the cloud platform (400) are same as of the functions, configurations of the extractor (310), the migration tool (320), the configurator (330) and the synchronizer (340) of the system (300).
APPLICATIONS
[0065] By using the method (200), the virtual machine (501a) can be transferred (migrated) from the source host (520) to the target environment (530) as the VM (522a).
[0066] If a user needs to transfer VMs by storing in the staging area, the user can opt for the method (200a).
[0067] By using the system (300), the virtual machine (501a/501b) can be transferred (migrated) from the source host (520) to the target environment (530) as the VM (522a, 522b).
[0068] If a user needs to store the extracted data (550a) in a staging area (buffer memory (534), the user may configure the system (300a) in the source host (520) and the target environment (530).
[0069] If a user needs to transfer the VMs as SaaS operations, the user can opt for the system (300b)
[0070] If a user needs a cloud platform for migration of the VMs (501a, 501b) from the source host (520) to the target environment (530), the user can opt for the cloud platform (400) which can functionally connected to the source host (520) and the target environment (530) for migrating the VMs.
ADVANTAGES
[0071] The present invention (200, 300, 400) extracts the operating system (O1, O2) data of the virtual machine (501a, 501b), ensuring compatibility across different cloud platforms, thereby improved agility to adapt to various type of computing platforms (environments). The present invention (200, 300, 400) enhances security by transferring only the necessary data to the target environment (530), reducing the need for full access to the source host's (520) infrastructure. Therefore, the present invention is improving granularity of access, while migrating the virtual machines from a source host (520) to a target environment (530). Finally, provisioning (230) and synchronizing (240) the virtual machine (522a) in the target environment (530) ensures seamless operation without exposing sensitive data and without any data loss.
[0072] The present invention (200a, 300a) has an advantage of enhancing data integrity and reliability by providing a temporary storage area (buffer memory (534)) that can handle data inconsistencies and network interruptions, ensuring a smoother and more secure migration process.
[0073] An additional advantage of the present invention (300b) is enhanced scalability and flexibility, allowing for easier updates and maintenance of migration tools by the SaaS infrastructure (500b). The migration process in the SaaS infrastructure can leverage cloud-based resources efficiently, reducing the dependency on on-premises infrastructure and improving overall operational efficiency. , Claims:We Claim:
1) A method (200) for migrating a virtual machine(s) (501a/501b/501c) from a source host (520) to a target environment (530), the method (200) comprises steps of:
extracting (210) a data (550) of the virtual machine (501a/501b) needs to be migrated from the source host (520) to the target environment (530), wherein the data (550) is the data of an operating system (O1/O2) of the virtual machine (501a or 501b);
transferring (220) an extracted data (550a) of the data (550) from the source host (520) to the target environment (530), a transferred data (552a) of the extracted data (550a) is stored in a memory (532) of the target environment (530) as a stored data (203);
provisioning (230) a respective virtual machine (502a) as per the extracted data (550a) in the target environment (530); and
synchronizing (240) the provisioned virtual machine (502a) in the target environment (530) with the stored data (203) to enable the functioning of the provisioned virtual machine (502a) in the target environment (530).
2) The method (200a) as claimed in claim 1, wherein the method (200a) comprises step of:
transferring (221) the extracted data (550a) from the source hose (520) to a buffer memory (534) (staging area) to store therein; and
transferring (222) the stored extracted data (551) in the buffer memory (534) from the buffer memory (534) to the memory (532) of the target environment (530).
3) A system (300) for migrating a virtual machine(s) (501a, 501b) from a source host (520) to a target environment (530), the system (300) comprises:
an extractor (310) associated with the source host (520) for extracting a data (550) of the virtual machine (501a/501b) needs to be migrated from the source host (520) to the target environment (530), wherein the data (550) is a data of an operating system (O1/ O2) of the virtual machine (501a or 501b);
a migration tool (320) associated with the source host (520) for transferring an extracted data (550a) of the data (550) from the source host (520) to the target environment (530), wherein a transferred data (552a) of the extracted data (550a) is stored in a memory (532) of the target environment (530) as a stored data (203);
a configurator (330) associated with the target environment (530) for provisioning a respective virtual machine (502a) according to the extracted data (550a) in the target environment (530); and
a synchronizer (340) associated with the target environment (530) for synchronizing the provisioned virtual machine (502a) in the target environment (530) with the stored data (203) to enable the functioning of the provisioned virtual machine (502a) in the target environment (530).
4) The system (300) as claimed in claim 3, wherein the source host (520) is an on-premises computing environment (520a) or cloud environment (523b) or a cloud platform; and the target environment (530) is a cloud environment or a cloud platform.
5) The system (300a) as claimed in claim 3, wherein the system (300a) comprises a buffer memory (534) to store the extracted data (550a) from the source host (520) therein before transferring to the memory (532) of the target environment (530).
6) The system (300b) as claimed in claim 3, wherein the extractor (310b), the migration tool (320b), the configurator (330b), the synchronizer (340b) are SaaS applications, the source host (520b) and the target environment (530b) connected into(to) a Saas infrastructure.
7) A cloud platform (400) for migrating a virtual machine(s) (501a, 501b) from a source host (520) to a target environment (530), the cloud platform (400) comprises:
an extractor (410) associated with the source host (520) for extracting a data (550) of the virtual machine (501a/501b) needs to be migrated from the source host (520) to the target environment (530), wherein the data (550) is a data of an operating system (O1, O2) of the virtual machine (501a or 501b);
a migration tool (420) associated with the source host (520) for transferring an extracted data (550a) of the data (550) from the source host (520) to the target environment (530), wherein a transferred data (552a) of the extracted data (550a) is stored in a memory (532) of the target environment (530) as a stored data (203);
a configurator (430) associated with the target environment (530) for provisioning a respective virtual machine (502a) according to the extracted data (550a) in the target environment (530); and
a synchronizer (440) associated with the target environment (530) for synchronizing the provisioned virtual machine (502a) in the target environment (500) and the stored data (203) to enable the functioning of the provisioned virtual machine (502a) in the target environment (530).