Lately, I often face people who prefer using snapshots, wrongly thinking that they can serve as an alternative to a proper backup infrastructure. This comes from a misunderstanding of snapshots’ real functions. So, I’ve decided to sort things out in this post and describe some basic operations you can do with snapshots in VMware and Hyper-V environments.
The term “snapshot” refers to the absolute copy of the particular VM’s state that allows you to roll back to it whenever you want. You can always take a snapshot of the VM, be it running or switched off. Though, if you capture a running VM, its disk activity gets suspended (for a matter of seconds but still…).
So, what’s the main point of taking snapshots?
Server virtualization helped businesses increase productivity and efficiency of their IT infrastructures by abstracting physical servers’ workloads from the underlying hardware with little to no loss of functionality, VDI applied quite the same logic. Desktops and applications run inside virtual machines that are hosted centrally, either on a server or in the cloud. The purpose of VDI is to deliver fully-featured user desktops to a variety of devices including conventional PCs, thin clients, and even zero-client endpoints. But how something that was seen as a bright alternative to the traditional server-based computing model used by Citrix and Microsoft Terminal Services a decade ago ended up being a niched deployment?
We’ve all heard the expression “time is money” and you can’t put it better when talking about IT. Most businesses’ success and efficiency depends on their IT infrastructure. For real. We all want our applications to run as fast as possible and roll them out in a matter of minutes. Moreover, the more data you have, the worse the consequences are in the event of its loss. So, companies want to get back all their data and get it back as soon as possible in case something happens. That’s called Recovery Point Objective (RPO) and Recovery Time Objective (RTO) and the shorter they are, the better it is for your company. Finally, as your business grows, you want to provision it with the right amount of storage and capacity and in case you need to open another branch office, you want to deploy an IT infrastructure shortly without spending months for building it.
VMware ESXi is the industry-leading hypervisor that is installed directly on a physical server. It is a reliable and secure solution with a tiny hardware footprint. At the same time, ESXi architecture is easy in management, patching, and updating.
Recently, Mellanox has released iSER 220.127.116.11, the stable iSER driver build for ESXi. iSER is an iSCSI extension for RDMA that enables the direct data transfer out and into SCSI memory without any intermediate data copies. Here, we study the driver stability and performance to understand how the protocol streamlines ESXi environments.
Nowadays, virtualization has become one of the main worldwide trends in the IT sphere. The virtual environment helps saving money, making infrastructure easier to administrate, and giving more possibilities for scaling. A large variety of hypervisors from different vendors with different functionality and a number of virtual machines available for deployment are already present on the market. In most cases, hypervisor vendors have their proprietary VM types incompatible with those of competitors’. That is why sometimes it might be a challenge to deploy one hypervisor’s virtual machines on other hypervisors. This may come up with a very painful migration process between hypervisors in case of changing one, moving to different hardware or having several different hypervisors running. A V2V (virtual machine to virtual machine) converter could help solving this task. It can convert a VM and move one between VM formats and physical environments where the hypervisor is running. The review of the most popular and well-known solutions of VM converters will be provided in this article.