This type of backup is known as an image-level backup because the VM's disk is backed up at the block level and not at the file level as traditional guest OS agents do. It is also much more efficient as the backup server can mount the VM's virtual disk directly from the host data store. By using this method, the guest OS is not aware of a backup process, nor is it wasting host resources.
Instead of using guest OS backup agents, backup servers should go directly to the virtualization layer and not involve the guest OS. This method also causes unnecessary resource usage on the host, and if multiple backups are running simultaneously, it can cause performance bottlenecks. The guest OS no longer has direct access to physical hardware where the data resides, so a backup agent inside the guest OS must go through the virtualization layer to get to the VM data. While this works, it is inefficient because the virtualization layer sits in between the guest OS layer and the physical hardware layer. You cannot use traditional backup methods that use agents installed on the guest OS to back up VMs. Don't back up through the guest OSīacking up through the guest OS is probably the most common mistake made when backing up VMs. There are common issues to note, and here, we provide you with five that could cause problems with your backups, as well as best practices for optimum data protection. The process of backing up VMs, though, comes with complications.
0 kommentar(er)
