(I will only accept my own answer if one of these approaches actually works and it's before someone else's suggestion.) Is there a way to reduce the impact of the stun onto MySQL or the virtual network or Centos.Īnswering my own question from research. Is there a way to prevent or reduce the "stunning" of a VMWare guest during imaging. I believe the "stun" means the virtual machine simply freezes for a time (around 30s) then continues normally. Veeam haven't been much help either, saying "reboot the target" or "we just use VMWare APIs". My "IT guy" has made a few tweaks to the Veeam config including skipping empty blocks (the majority of the new disk is empty), but this didn't seem to help at all. HARD DISK CONTROLLER SMART ARRAY P420I/ZERO MEMORY CONTROLLER (RAID 0/1/1+0) The target of the Veeam process is a ReadyNAS over a 1Gb dedicated ethernet (i.e. The old disks would have been similar only smaller. The new disks are 2x300GB Gen8 15k SAS in RAID1. ![]() Ever since the disk was increased, we've been getting these problems during backups - presumably due to the increase time it takes to perform snapshot related functions. ![]() ![]() The change which seemed to initiate this problem was increasing the physical disk size to 300GB, from about 100, and resizing the guest filesystem to use most of the new capacity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |