About serialization of VSS operations


  • In MSDN documentation, I found that few VSS operations can'r be preformed simultaneously e.g. Create snapshot, delete snapshot and import snapshot. It mentioned that it's irresponsibility of the requester provider to serialize this operation.

    I would like to know why this serialization is required?

    In my requester provider, I tried that at a time only one VSS api get invoked e.g DoSnapshotSet, ImportSnapshotSet, AddToSnapshotSet etc. I put the API level locking but it failed when multiple snapshots job executed.

    If I have to implement serialization in my requester provider, which APIs should be run in critical section to  ensure that different operations don't get failed. Is there any specific object that should not shared between different processes e.g. Writer, interface.

    Is there any serialization mechanism available in VSS framework to ensure that job doesn't get failed ?

    Thanks in advance

    Rahul Naik

    Saturday, July 07, 2012 3:02 PM