vmotion-and-storage-vmotion-what-these-are-and-how-they-work

VMotion and Storage VMotion: What These Are and How They Work

VMware VMotion and Storage VMotion are products that allow the live migration of virtual machines among various physical servers, while the VMs are running, with no downtime, no interruption in service, and total transaction integrity. VMotion improves the availability of VMs by enabling maintenance without incurring disruption to the business operations. It moves VMs within pools of server resources so that resources are allocated according to the priorities of the business. VMotion is an important technology for delivering and empowering a dynamic, fully automated, and completely self-optimizing data center. 

How VMotion Works

VMotion and Storage vMotion

VMotion and Storage VMotion allow for the dynamic and cross-physical-system alignment of compute and storage resources, so that user performance isn’t impacted by ordinary maintenance.

There are three basic technologies that allow VMotion to dynamically align resources according to business priorities. First, it leverages the encapsulation of the entire state of a VM with a collection of files, which are stored on a shared storage component (such as Fibre Channel, NAS, or SAN). 

It either uses VMFS or NFS to allow a number of installations of ESXi to be able to access the same VMs at the same time.The second technology that empowers VMotion is the active memory and execution state of the VM, which is transferred via a high-speed network between Source and Destination. 

It enables the VM to instantly migrate from the source ESXi host to the destination ESXi host. Based on a proven preparation in precopying most of the data, the final switch happens so quickly that it is imperceptible to the user, because it keeps track of the transactions in memory by using a bitmap. When the whole of the system state and memory are migrated to the target ESXi host, VMotion then suspends the source VM, copies the bitmap over to the target ESXi host, and then resumes the VM operations on that target host. 

That process happens in less than two seconds when using a Gigabit Ethernet network.The third technology behind VMotion is the virtualization of the networks being accessed by the VMs. This is done via the ESXi host, so that even after migration occurs, the VM network identity and connections are saved. VMotion also manages the virtual MAC address during this process, informing the connected network switch of that change: After the destination machine is enabled, VMotion pings the router to make it aware of the new location of the MAC address. 

This occurs without any downtime or disruption to the users. 

How Storage VMotion Works

Storage vMotion

VMotion and Storage VMotion allow for the business’ priorities to be met without disrupting the workflow of the users.

Storage VMotion makes storage and capacity management more efficient. It is a feature of vSphere that delivers an easy, intuitive interface to allow the live migration of VM disk files across storage arrays, while causing no downtime and no interruption or heavy deterioration of the performance of the VMs. It works by relocating the VM disk files to various storage locations, enabling the business to be proactive about storage migration and to improve the performance of storage in terms of capacity management. 

Like vMotion, Storage VMotion is completely integrated with vCenter Server, which allows for the easiest possible migration and monitoring.Storage VMotion works with any OS and storage hardware that is supported by ESXi. It enables administrators to take advantage of a mixture of heterogeneous file formats and data stores, without incurring any downtime. 

With Storage VMotion, administrators can migrate VM disk files to alternate LUNs in order to optimize performance with no downtime. It allows administrators to increase or decrease storage allotment, without a lot of manual work. Additionally, Storage VMotion can act as a tool to tier the storage, based on the value of the data, performance requirements, and the cost of various storage solutions. 

If you’re in the market for a better VMware monitoring solution, Opvizor has your answer. Snapwatcher enables VMware snapshot monitoring and reporting so that you can track invalid snapshots that can happen when migrating virtual machines. Register for Snapwatcher here, to detect and solve all kinds of bad Snapshots.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.