thank you Petr, sure I will continue working with the support team, my concern is that I cannot simply "retry and reproduce the issue" because of the high impact it can have on a super critical production DB server.
The two VMs were on the same datastore and ESXi host; it's a two hosts cluster and it's sadly not possible to separate the test VM where the restore is running into from production VMs.
The backup repository is a Synology NAS. Everything is in the same datacenter.
I also guessed it could be an excessive load, but it sound so strange to me that the network traffic on the production server falls exactly to zero
https://ibb.co/b0cJSCg
during the restore, while the traffic on the test vm is high... why should all the resources go to the restore process?
https://ibb.co/tw0s1Tzj
The two VMs were on the same datastore and ESXi host; it's a two hosts cluster and it's sadly not possible to separate the test VM where the restore is running into from production VMs.
The backup repository is a Synology NAS. Everything is in the same datacenter.
I also guessed it could be an excessive load, but it sound so strange to me that the network traffic on the production server falls exactly to zero
https://ibb.co/b0cJSCg
during the restore, while the traffic on the test vm is high... why should all the resources go to the restore process?
https://ibb.co/tw0s1Tzj
Statistics: Posted by tinto1970 — Jul 23, 2025 2:00 pm
