RVTools 4.7.1 is a Windows .NET 4.7.2 application which uses VMware vSphere...
VMware ESXi 8 has dropped the compatibility with a lot of old CPU models, a...
In VMware Workstation 17.6.1, when I create a Rocky Linux VM, there is no w...
The legacy C# vSphere Client for Windows is no more available for vSphere 6...
Debian like distributions have a nice option to manage distribution upgrade...
Usually, on one desktop machine you can only use ONE desktop hypervisor sol...
If you are using an embedded PostgreSQL database and a Windows user differe...
The Veeam Managed Hardened Repository is a bootable ISO based on Rocky Linu...
Veeam plug-in for Oracle RMAN can be used for transactionally-consistent RM...
One year ago, Broadcom killed the Free vSphere Hypervisor, but now, with th...
Reading Time: 2 minutesSome days ago I’ve got a strange error during the backup job of a vSphere 6.7 (not Update 1) environment with latest version of Veeam Backup & Replication. The job was starting correctly, VMs have been discoverted, but when the backup start to copy the VMDK the job failed with a “VDDK async operation error 14009” message.
Reading Time: 2 minutesSeams that the new VMware vSphere 6.7 Update 1 will break all the Veeam Backup & Replication backup jobs! As reported in the Veeam KB 2443, VMware 6.7 Update 1 is actually NOT supported by Veeam B&R and will be supported only with Veeam Backup & Replication 9.5 Update 4. More information are available on Veeam KB 2784 and this forum thread.
Reading Time: 3 minutesIn the last Veeam Community Forums Digest, there are some interesting notes about some possible issues with vSphere Storage vMotion, that usually is used to move backup your VMs in the original datastore during a Instant VM Recovery (IR). Seems that there is major bug in Storage VMotion functionality of vSphere 6.7 when you are using the optional IR feature that allows you to redirect virtual disk updates to the selected datastore.
Reading Time: 3 minutesIn the last Veeam Community Forums Digest newsletter there is an interesting note about possible performance issues in VMware vSphere backup based on hot-add transport mode. VMware has confirmed that the increased Hot Add times experienced by some Veeam customers who have installed Veeam Backup & Replication Update 3a and the reason is the latest Virtual Disk Development Kit (VDDK) 6.5 version used in U3a to support also vSphere 6.5 Update 2.
Reading Time: 3 minutesFinally, the v2.2 of Veeam Agent for Microsoft Windows is available also from the client update. Release on July 3, 2018 (see the release notes), the new agent versions (not only the v2.2 for Windows, but also the 2.0.1 for Linux) have been available from the Veeam Backup or other limited sources, but now are available to all. Not much news or improvements, mainly the official support for Windows 10 v1803 and some minor bug fixes.
Reading Time: 3 minutesIf you are using Veeam Backup & Replication with a VMware vSAN datastore you are probably following the Veeam KB 2273 (Configuration for VMware VSAN). But this guide is only limit to recommend the hot-add transport mode. So you are going to create several Veeam proxies because Veeam Backup & Replication chooses the most appropriate backup proxy to reduce the backup traffic on the VSAN cluster network. Maybe also one per host.
Reading Time: 3 minutesVeeam Software has finally announced the availability of the new Veeam Availability for Nutanix AHV, a “Backup & Replication” version for Nutanix Acropolis Hypervisor (AHV). In this way Veeam extend the supported (on-prem) hypervisors to the three majors: VMware vSphere, Microsoft Hyper-V and Nutanix AHV. Considering that also Nutanix it’s multi-hypervisors, the combination of Veeam and Nutanix can give the best. Still there isn’t a native solution for other KVM based hypervisors, but those workloads can be protected with the Veeam Agents.
| Disclaimer & Copyright
