I can tell you now that this is a recently discovered bug, 585632.
Engineering are currently working on this. I can provide you here with the public report, which is not yet showing up on our site (it should soon).
%%% TITLE:
Restore and clone may fail with error Logical file db_data is not part of database db, Use RESTORE FILELISTONLY to list the logical file names.
%%% DESCRIPTION:
When doing a database restore or cloning, the operation may fail with the
following error messages in SMSQL report:
Failed to prepare VDI mount snapshot.
Error encountered when executing sql command:
Msg 3234, SevLevel 16, State 2, SQLState 42000
[Microsoft][ODBC SQL Server Driver][SQL Server]Logical file 'db_Data' is not
part of database 'db'. Use RESTORE FILELISTONLY to list the logical file names.
Msg 3013, SevLevel 16, State 1, SQLState 42000
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating
abnormally.
Error Code: 0xc00408a0
Unable to get VDI command to perform snapshot creation or LUN restore.
The SQL command executed.
Failed to restore SQL Server database [db] of [inst].
The problem will happen under the following conditions:
1. Multiple databases are sharing same LUN or two LUNs;
2. Among databases sharing LUN(s), there are more than one databases whose
name's first 4 characters are the same, and those databases are belonging
to the same SQL Server instance, or different instances but the first 4
characters of those instances' names are the same.
With such configuration, when those databases are backed up at the same
time, one or more of backup metadata file may be overwritten during
the backup, so the restore or clone will fail.
%%% WORKAROUND:
To prevent this problem from happening again with newly created backup,
use the following workaround:
1. Add the following registry key DWORD (32bit) value named
"SupportLongDbName" under:
HKEY_LOCAL_MACHINE\SOFTWARE\Network Appliance\SnapManager for SQL Server\Server
Set its value to 0.
2. Restart SnapMgrService.
In case a restore is needed for the existing backup, you can manually
mount snapshot which contains the database, copy the database files
from the snapshot LUN manually, then attach the database using the
copied files.
%%% NOTES:
The workaround provided for preventing the issue from happening with
newly created backup does not apply to database with a long name, such
as more than 86 characters. For database with very long name, relocate
such database to separate LUN, so it does not share the same LUN with
other databases.
