Update: HPE info added 9 September 2021 re HW boosts to performance and 5660 max usable capacity downshift from 5650. To Make sure there were no problems in the foreseeable future, I set DRS for the Veeam VM to be partially automated and set a DRS rule to always keep these 3 VMs together.Ĭonclusion: If you are backing up a VM using Virtual Appliance Mode through a particular ESX(i) host and not vCenter, be sure that the VM you want to backup and the Veeam VM are living on the same host. HPE has added three new models to its StoreOnce purpose-built deduplicating backup appliance range, upping capacities and transfer speeds. I vMotioned my Veeam VM to the same host as the vCenter and vCenter Database VMs and backups ran without any errors. As a last moment of testing, I tried to see if the VM location on the host was the problem, sure enough it was. See for yourself how an all-in-one appliance can give you 100 recovery confidence. After removing the individual ESX(i) hosts and re-adding them, the problem still persisted. High performance backup appliance for on-appliance recovery.
The Veeam log shows as if it is a login error. Logon attempt with parameters Port: 902 Login: VMX Spec: Snapshot mor: Transports: ] failed because of the following errors: Every single VM continued to run fine, but these 2 VMs would fail with the error message:īackup mode: HOTADD with changed block trackingīacking up file " XXXvCenter/XXXvCenter-flat.vmdk"Ĭlient error: Failed to open VDDK disk XXXvCenter/XXXvCenter.vmdk] ( is read-only mode - ) After that day, backups stopped working for these 2 VMs. I have my vCenter and vCenter Database VMs set to partial DRS because it's best practice to always know where these VMs are located in case of a failure so i moved these VMs back to their original host. Then one day I patched the ESX servers in our environment which made me migrate our VMs all around. Veeam Backup & Replication starts the appliance automatically and mounts the VM disks to the FLR appliance as additional virtual hard drives.
#Veeam backup appliances update#
To alleviate this issue, these 2 VMs cannot be backed up through vCenter, but instead you have to add the ESX(i) server to the list of servers and then add the VM to the backup job through the particular host.īackups then ran without a problem for about 2 weeks. Veeam Backup & Replication v8 Update 2 (or later) has a Veeam agent for pure 64-bit Linux systems. I set up a few jobs and I would have 2 VMs continuously fail, the vCenter and vCenter Database VMs. At first, all I did was add my vCenter server into the list of servers. We run our Veeam server as a VM and use the Virtual Appliance mode to backup all of our VMs. After about 2 weeks of frustration and testing I finally figured out why 2 of my VMs were not being backed up and hopefully this helps someone else out.