RSS for all categories
FS#13697 — Veeam As A Service
Attached to Project— Dedicated Cloud
| Incident | |
| Backend / Core | |
| In progress | |
 |
Hello,
During backups from our Veeam As A Service solution, we have detected "freezes" from VM's OS during the snapshot removal.
After having a talk with Veeam and VMware, these freezes can be explained with this following KB : https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002836
It's an OS "lock" system due to the disk hot-add on the VM backup Proxy. It's a security process made by VMware in order to protect shared disk moved by hot-add.
The lock time is estimated at 35 seconds.
We have two workaround possibles for the moment :
- The locks can be avoided if you have the backuped VM on the same host where the VM backupProxy is hosted.
- We can low this lock time at 8 seconds, you can ask this operation at our support.
We're searching very actively with VMware a solution to avoid this system and to erase the impact you're getting during backups.
We keep you update about this subject.
During backups from our Veeam As A Service solution, we have detected "freezes" from VM's OS during the snapshot removal.
After having a talk with Veeam and VMware, these freezes can be explained with this following KB : https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002836
It's an OS "lock" system due to the disk hot-add on the VM backup Proxy. It's a security process made by VMware in order to protect shared disk moved by hot-add.
The lock time is estimated at 35 seconds.
We have two workaround possibles for the moment :
- The locks can be avoided if you have the backuped VM on the same host where the VM backupProxy is hosted.
- We can low this lock time at 8 seconds, you can ask this operation at our support.
We're searching very actively with VMware a solution to avoid this system and to erase the impact you're getting during backups.
We keep you update about this subject.