7 Appendix B: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

  • Windows 10 operating system 

  • Windows Server 2016 operating system

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 3:  Windows implementations use the Volume Shadow Copy service [MSDN-SHADOW] available on the application server and file server. The client implementation provides an extension to the VSS provider model by acting as File Share Shadow Copy Provider. The server implementation acts as the VSS requestor and makes use of the underlying VSS service to create shadow copies of the local volumes on which the file shares are hosted.

<2> Section 3.1.3:  Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 FSRVP servers set MinServerVersion to FSRVP_RPC_VERSION_1 (0x000000001).

<3> Section 3.1.3:  Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 FSRVP servers set MaxServerVersion to FSRVP_RPC_VERSION_1 (0x000000001).

<4> Section 3.1.4:  Windows servers additionally check whether the caller is a member of the local administrators or backup operators group.

<5> Section 3.1.4.2:  Windows Server 2012 R2 and Windows Server 2016 FSRVP servers set this retry attempt limit to 5. Windows Server 2012 operating system doesn't perform this verification.

<6> Section 3.1.4.3:  At any given time, Windows servers allow only one shadow copy set to be going through the creation process. If a client attempts to start a new shadow copy set while another set creation is in progress, Windows servers fail the client request with FSRVP_E_SHADOW_COPY_SET_IN_PROGRESS (0x80042316). If the following events occur in the order given, Windows servers fail a StartShadowCopySet request with FSRVP_E_SHADOW_COPY_SET_IN_PROGRESS (0x80042316):

  • The client aborts a shadow copy set that is in an "Added" or "Exposed" state.

  • The client attempts to start a new shadow copy set within 30 minutes of the last call to AbortShadowCopySet.

<7> Section 3.1.4.3:  Windows clients set this field to the GUID that is exposed by the shadow copy utility (VSS) to the backup applications. When this parameter is set to NULL, Windows servers fail the request with E_INVALIDARG (0x80070057).

<8> Section 3.1.4.4:  Windows clients set this field to the GUID exposed by the shadow copy utility (VSS) to the backup applications. Windows servers ignore this parameter.

<9> Section 3.1.4.6: Windows servers expose the shadow copy of the share by invoking the NetrShareAdd() method, as specified in [MS-SRVS] section 3.1.4.7.

If MappedShare.ShareName ends with "$\", then the FSRVP server creates the share as hidden by appending "$" to the exposed share name.

For example:

  • If MappedShare.ShareName is set to \\server\thisshare$\, the exposed name would be \\<any>\thisshare$@{ShadowCopy.ShadowCopyId}$.

  • If MappedShare.ShareName is set to \\server\thisshare\, the exposed name would be \\<any>\thisshare@{ShadowCopy.ShadowCopyId}.

<10> Section 3.1.4.11:  If ShadowCopySet.Status is "Started", "Added", "CreationInProgress", or "Committed", Windows Server 2012 FSRVP servers return an error value of 0x80042311.

<11> Section 3.2.3:  Windows clients set this timeout to 1,800,000 milliseconds.

<12> Section 3.2.3:  Windows clients set this timeout to 60,000 milliseconds.

<13> Section 3.2.3:  Windows clients set this timeout to 1,800,000 milliseconds.

<14> Section 3.2.3:  Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 FSRVP clients set ClientVersion to FSRVP_RPC_VERSION_1 (0x000000001).

<15> Section 3.2.4.2.1: Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 FSRVP clients set the PathFormat to "Hostname".

Show: