HMwkr wrote:Equally, I am saying causation, not correlation. I am saying there is/was a scenario, a very unexpected (to me) scenario, wherein running a Veeam backup job caused a reboot of the source VM; repeatably, across multiple VMs on multiple hosts. If my hunch is right, that this was due to running Veeam backup jobs while MS updates were still thrashing post-install, then Veeam users could benefit from knowing this
HMwkr wrote:If you or anyone else is interested in following up on this I'd be happy to share event logs, whether that confirms my hunch or highlights a completely different cause.
HMwkr wrote:The pre-assessment reports sound useful. Although, if my hunch is right then they wouldn't have flagged up any problems in my scenario, unless I'd run them while the MS updates were still processing - and even then, would they pick up on that? I wouldn't expect them to, or hold it against them if they didn't.
Users browsing this forum: No registered users and 1 guest