![]() ![]() Please comment if you have some own experience related with this topic. Be Social and share it in social media, if you feel worth sharing it. This time that information was not helpful but maybe good to know this behavior. VMDK file xxxxTSS001_1-000002.vmdk which was attached to VDP and not unlocked after backup complete in this view has different date than other VMDK files in VM folder. Some tips which we can use for this is use this command on every ESXi host ( yes i know if we have many hosts in cluster this is not the best solution but is some way): Is not easy to find where some VMDK is attached (locked) in VSAN configuration. Manually removed attached before VMDK file resolved problem. In this case for some reason this VMDK file xxxxTSS001_1-000002.vmdk wasn’t unlocked after backup and that was source of problem. How we saw this time locked file xxxxTSS001_1-000002.vmdk related was with VDP appliance “xxxxVDP001” which during backup proccess always temporary attach VMDK files in VM which is during backup task. VMDK file xxxxTSS001_1-000002.vmdk which was attached to one of disk “Hard Disk 6” in VM “xxxxVDP001” ( vSphere Data Protection ) was causing locking error during consolidation process.Īfter manually removed “Hard Disk 6” from VM “xxxxVDP001” ( vSphere Data Protection ) consolidation process completed successful. Right-click the backup proxy virtual machine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |