You need to be aware of certain considerations when using Remote VSS-enabled backup solutions for Hyper-V over SMB configurations.
The shadow copy operation fails if there are more than 64 shares in a shadow copy set. This is a Microsoft requirement.
A shadow copy operation will fail if there is an ongoing shadow copy operation on the same CIFS server. This is a Microsoft requirement.
Certain limits apply only for shadow copies with automatic recovery.
This is the directory depth over which the shadow copy service creates a shadow copy backup set. Shadow copy creation fails if directories containing virtual machine file are nested deeper than five levels. This is intended to limit the directory traversal when cloning the share. The maximum directory depth can be changed by using a CIFS server option.
The available space must be at least as large as the combined space used by all files, directories, and subdirectories contained within the shares included in the shadow copy backup set.
The shadow copy creation fails if there are any links or non-regular files in the share to the shadow copy. The clone process does not support them.
Although shadow copy creation retains NFSv4 ACLs on files, the NFSv4 ACLs on directories are lost.
Microsoft specifications allow a maximum of 60 seconds to create the shadow copy set. If the VSS client cannot create the shadow copy set within this time, the shadow copy operation fails; therefore, this limits the number of files in a shadow copy set. The actual number of files or virtual machines that can be included in a backup set varies; that number is dependent on many factors, and must be determined for each customer environment.