SPVssDiscoveryHelper Class

Enables custom types of non-database content components to be protected by Volume Shadow Service.

Inheritance Hierarchy


Namespace:  Microsoft.SharePoint.Administration.Backup
Assembly:  Microsoft.SharePoint (in Microsoft.SharePoint.dll)


<GuidAttribute("90D39685-EA0E-47a9-8924-F95CA6B84A61")> _
<ObfuscationAttribute(Exclude := True, Feature := "renaming", StripAfterObfuscation := True)> _
<SharePointPermissionAttribute(SecurityAction.LinkDemand, ObjectModel := True)> _
<SharePointPermissionAttribute(SecurityAction.InheritanceDemand, ObjectModel := True)> _
Public Class SPVssDiscoveryHelper _
    Inherits SPPersistedObject
Dim instance As SPVssDiscoveryHelper
[ObfuscationAttribute(Exclude = true, Feature = "renaming", StripAfterObfuscation = true)]
[SharePointPermissionAttribute(SecurityAction.LinkDemand, ObjectModel = true)]
[SharePointPermissionAttribute(SecurityAction.InheritanceDemand, ObjectModel = true)]
public class SPVssDiscoveryHelper : SPPersistedObject


Use this class as a base class to create persisting child objects of the SharePoint Foundation farm that will pass information about custom non-database content components to the SharePoint Foundation VSS Writer service (sometimes called the SPF Writer service).

You will also need to create a VSS writer for your custom non-database component.

Custom database components only need to be registered in the configuration database for the farm. There is a built-in VSS writer in the SharePoint VSS Writer service that will include them along with the native SharePoint Foundation databases in the shadow copies. Accordingly, you do not need to create a VSS writer for them, nor do you need to derive classes from SPVssDiscoveryHelper or SPVssComponentDefinition for database components.

Notes to Inheritors

When you inherit from SPVssDiscoveryHelper, you must override the following members: Run.

An object of your derived class is persisted in the configuration database for the farm the first time you call the object's Update method.

Thread Safety

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

See Also


SPVssDiscoveryHelper Members

Microsoft.SharePoint.Administration.Backup Namespace

Other Resources

SharePoint Foundation and the Volume Shadow Copy Service

How Volume Shadow Copy Service Works

Starting and Configuring the WSS Writer Service

Volume Shadow Copy Service Technical Reference