Our customer moved the VMs from Windows 2012 Hyper-V host server to 2019 Hyper-V host server, I tried to backup the Exchange 2010 servers via Veeam application-aware function (because we would like to use it for truncate logs) and it failed, the error message show failed to create production checkpoint.
was doing daily checking for servers as usual. There are two SSD drives happen lost communication at Storage Space Direct Server, this is not good, because those two SSD drives are the cache of Storage Space Direct.
I was trying to upgrade VBO 365 from V3 to V4, everything looks fine except upgrading Default Backup Repository, the status shows Upgrade failed “Access is denied”, it has never happed with other customers for upgrading VBO 365 from V3 to V4.
If you tried to run Hyper-V PowerShell script at Windows Server 2019 to get Hyper-V report from Windows Server 2012 R2 Hyper-V host, you will get the error message “The Hyper-V module used in this Windows PowerShell session cannot be used for remote management of the server ‘XXX”. Load a compatible version of the Hyper-V module……..”
Today, I try to publish blog via Microsoft word as usual, but it failed and show a warning message “Word cannot publish the pictures in this post. The most likely cause of this problem is that you do not have enough storage space. Contact your provider and try again, or choose a different picture provider”, this so weird and I am sure I didn’t change any settings at my blog site except enable SSL. I figure out the issues after do some research and test.