void SetBackupSucceeded( Guid instanceId, Guid writerId, VssComponentType componentType, string logicalPath, string componentName, bool succeeded )
Sub SetBackupSucceeded ( instanceId As Guid, writerId As Guid, componentType As VssComponentType, logicalPath As String, componentName As String, succeeded As Boolean )
void SetBackupSucceeded( Guid instanceId, Guid writerId, VssComponentType componentType, String^ logicalPath, String^ componentName, bool succeeded )
The logical path of the component to be added. For more information, see Logical Pathing of Components.
The value of the string containing the logical path used here should be the same as was used when the component was added to the backup set using AddComponent(Guid, Guid, VssComponentType, String, String).
The logical path can be .
There are no restrictions on the characters that can appear in a non-null logical path.
The name of the component.
The value of the string should not be , and should contain the same component as was used when the component was added to the backup set using AddComponent(Guid, Guid, VssComponentType, String, String).
|ArgumentNullException||One of the arguments that cannot be was|
|ArgumentException||One of the parameter values is not valid.|
|OutOfMemoryException||Out of memory or other system resources.|
|SystemException||Unexpected VSS system error. The error code is logged in the event log.|
|VssBadStateException||The backup components object is not initialized, this method has been called during a restore operation, or this method has not been called within the correct sequence.|
|VssObjectNotFoundException||The backup component does not exist.|
|VssInvalidXmlDocumentException||The XML document is not valid. Check the event log for details.|
When working in component mode (when SetBackupState(Boolean, Boolean, VssBackupType, Boolean) is called with its select components argument set to ), writers the state of each components backup using BackupSucceeded.
Therefore, a well-behaved backup application (requester) must call BackupComplete.after each component has been processed and prior to calling