Failed to add NFS datastore for NFS host '1bcdr01.xxx.com'. Failed to mount NFS volume (172.30.4.4:/VeeamBackup_1bcdr01.xxx.com). 172.30.4.4: Fault "PlatformConfigFaultFault", detail "NFS mount 172.30.4.4:/VeeamBackup_1bcdr01.xxx.com failed: Unable to connect to NFS serve...
3. Unable to connect V&R and Agent. Case: Unable to install backup agent: cannot connect to 10.39.140.56 Error: Failed to get path for 'veeaminstaller' utility for OS platform 'Unknown' Tried: So I tried direct inst...
Seems to be a similar issues and yes I do use Veeam but in this lab environment I didn't have Veeam installed.I was able to rule it down to Hyper-V replication. If its enabled I can easily reproduce this problem, disabling it...
After click "remove server "from hyper-v console, every time when I open Hyper console ,I need to connect to server. After Deleted some files in Disk driver , the free space increased in drive inside of the VM . but its not replicating or increase the free space while inspect the VHD...
After click "remove server "from hyper-v console, every time when I open Hyper console ,I need to connect to server. After Deleted some files in Disk driver , the free space increased in drive inside of the VM . but its not replicating or increase the free space while inspect the VHD...
Seems to be a similar issues and yes I do use Veeam but in this lab environment I didn't have Veeam installed.I was able to rule it down to Hyper-V replication. If its enabled I can easily reproduce this problem, disabling it then the problem stops....
If I restore the server from a Veeam backup (from the previous day when checkpoints didn't work) then I can create and apply a checkpoint successfully. It doesn't appear to be a permissions issue. Would there be a 'lock' file or anything similar that could stop a checkpoint applying?
If I restore the server from a Veeam backup (from the previous day when checkpoints didn't work) then I can create and apply a checkpoint successfully. It doesn't appear to be a permissions issue. Would there be a 'lock' file or anything similar that could stop a checkpoint applying?
If I restore the server from a Veeam backup (from the previous day when checkpoints didn't work) then I can create and apply a checkpoint successfully. It doesn't appear to be a permissions issue. Would there be a 'lock' file or anything similar that could stop a checkpoint applying?
After click "remove server "from hyper-v console, every time when I open Hyper console ,I need to connect to server. After Deleted some files in Disk driver , the free space increased in drive inside of the VM . but its not replicating or increase the free space while inspect the VHD...