I see the following pattern, which does lead to file corruption.
Server Win2008R2SP1 Clients Win7Sp1
SMBv2 enabled
Server running on VMware Vshpere 5.1 ESXi host, Disks are VMFS volumes on local hardware RAID.
I am backing up the whole shared (non system) volume of the W2008R2 server via a 3rd party software (SEP sesam), which creates a temporary VSS snapshot, which it backs up and after backing it up it deletes this temporary snapshot. In most cases this works without problem.
But if during the backup i.e. between the creation of the temporary snapshot and it's deletion there are files already open read only (but by users with full filesystem rights) and then closed before the temporary snapshot is removed these files can get
corrupt (like file table pointing to non existent or wrong data) - but the metadata you see in file properties are correct.
Of the same volume there are taken snapshots to allow the previous versions feature on regular intervalls but not during backup. If I try to repair the corrupted file by replacing it with it's previous version (which should be the identical file as the corrupted one as there should not have happened any change to it) this does not work. BUT if I copy the previous version to another location the correct uncorrupted file is placed into this location - and from there I can overwrite the corrupt file thus repairing effectively the corrupted file.
If I backup the volume without VSS snapshot I eventually get a could not backup open files list, but no file corruption.
Has anybody seen similar problems or any other idea. I know there have been file corruption problems before SP1 but those should be solved in SP1.
Wolfgang