This morning I attempted to use Veeam v8 to restore a SQL database to its state a couple of days ago and ran into some problems (complete db restore, not anything more granular than that). In Veeam's SQL restore wizard, it showed the path to the MDF and the LDF to have additional backslash characters. Even though I changed the target file names in the SQL restore wizard to remove these additional characters, Veeam was looking for source file paths with the extra characters and completely bombed.
While I realize the issue is not with Veeam, it did tip me off to a very odd misconfiguration of our SQL Server. We run SQL 2012 Standard (licensed for 4 cores) on a VM running Server 2012 (not R2). It turns out the production Epicor database has additional characters in its physical_name field. This is the only database on our SQL server with...