OPERATIONAL DEFECT DATABASE
...
...
A File Backup/file to tape job skips VSS snapshot creation on SMB share and ends with the following message in the log: Failed to create a VSS snapshot, failing over to direct backup from the file share
Requirements Note: In the section below, reference is made to a General-Purpose Backup Proxy; this role is assigned to the Veeam Backup Server by default. Additional General Backup Proxies can be created as needed, which can be important if the Veeam Backup Server is off-domain or in a segmented domain, per best practices. Below are the requirements for VSS to function when backing up from an SMB3 share hosted by a Windows File Server: The General-Purpose Backup Proxy and the Windows File Server hosting the SMB3 Share must run Windows Server 2012 R2 or later. The General-Purpose Backup Proxy and the Windows File Server hosting the SMB3 Share must be joined to the same AD domain. The account used to add the SMB3 to Veeam Backup & Replication must be a domain-level account with sufficient permissions to access the share and trigger the VSS snapshot on the Windows File Server hosting the SMB3 Share. The File Server VSS Agent Service role must be enabled on the Windows File Server hosting the SMB3 Share. The General-Purpose Backup Proxy must be able to resolve both the hostname and IP address of the Windows File Server hosting the SMB3 Share. For more information on the VSS for SMB File Shares feature, see the following Microsoft page:https://docs.microsoft.com/en-us/archive/blogs/clausjor/vss-for-smb-file-shares
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
