nickl99 wrote:For reference all up it has 7 disks, all thick provisioned, spread over 2 different FC connected stores. 4 TB all up, the biggest disk is 1TB (only 10% used).
[28.07.2016 07:53:33] < 21584> dsk| WARN|VDDK logon has failed. Logon specification: [VC/ESX: [vsphere.domain.local];Port: 443;Login: [Domain\sac_VeeamBackup];VMX Spec: [moref=vm-165];Snapshot mor: [snapshot-45391];Transports: [san];Read Only: [true]]. VMDK path: [[PROD_TIER01_VOL_0] clstexchsvr01/clstexchsvr01_2.vmdk]. Read only mode: [true].
[28.07.2016 07:53:33] < 21584> dsk| >> |VDDK error: 13 (You do not have access rights to this file). Value: 0x000000000000000d
[28.07.2016 07:53:33] < 21584> dsk| >> |Failed to open virtual disk [PROD_TIER01_VOL_0] clstexchsvr01/clstexchsvr01_2.vmdk (flags: 4)
nickl99 wrote:It turns out there are many many more VM's that arent able to use SAN mode. So its looking like it could be Veeam proxy related. How can i systematically check that the Veeam proxy/repository has a valid non-LAN path to stores for all the VM's?
Users browsing this forum: No registered users and 11 guests