On 26.06.2016 16:49, Mark Phippard wrote: > The issue is that a lot of VSS repositories have hidden corruptions > that do not surface until you try to migrate the history. It seems > like the corruptions are often in the history or something, so it is > only when you start trying to extract old data that it surfaces.
The reason for that is that the architecture of VSS requires that every user has write access to the actual repository databases; these are just files in a shared folder, and VSS assumes that CIFS locking is sufficient to implement distributed transactions. Since that's not the case, there's no way to avoid silent corruptions. Back in the day I administered a VSS repository used by a team of some 20 or so developers ... fixing corruptions was a regular daily task. -- Brane
