If some remote replica dir is deleted partially, per instance, if you delete some -flat.vmdk file but you don't delete the .map directory containing the data definitions, subsquent jobs running on the same remote dir will result in data loss, as the client will believe the files defined by the .blocklog files inside the .map dir do exist.
If some remote replica dir is deleted partially, per instance, if you delete some -flat.vmdk file but you don't delete the .map directory containing the data definitions, subsquent jobs running on the same remote dir will result in data loss, as the client will believe the files defined by the .blocklog files inside the .map dir do exist.
Some versions of ©ESXi do just that when you remove some VM from disk. The whole VM folder is not removed as it should happen and an indetermined number of files remain in the dir. Thus when you remove some VM do make sure that the whole VM dir is wiped from the disk.
This will be solved by enriching the replica check algorithm in future versions.
Last edit: 33HOPS 2023-07-30