Venkat, all tools have advantages and disadvantages. VSS is no exception. One need only look at the release notes to see the bugs. That alone will not reveal all the disadvantages however! [img]/images/graemlins/smile.gif[/img]
[ QUOTE ]
There is no disadvantages of using VSS,if u find other tools u can find backup problems.
[/ QUOTE ]
Actually, I have found that VSS makes it more difficult to restore from a corruption. The file in question that get's corrupted, does not match up to an original file, but to a hash. Even if I respter this file, the other files might not be able to still interact correctly with it. So, I cannot access any of the files, and might lose the entire day's load in order to restore to an uncorrupted version on backup.
Compare this with PVCS, which stores the version control for each file into a separate equally named file. When a file get's corrupted there, then only one file loses the last update, rather than an entire project. Both of these cases were real incidents, but in one case, the restore process was intuitive and simple, while in the other we needed to recreate a days' loads to get back to after the last backup.
I cannot speak for the many other VCS systems out there, but this difference exists.
That said, the fact that VSS is free with visual studio, and that file corruptions are rare events, VSS is still a good option for a small team with a small set of projects.
Software Test Engineer
If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.