I’m having an issue with the SMSP backup job I’ve configured for a customer. The SharePoint components are backing up okay, but it appears that indexing of the backed up data is failing. There is an SQL server error when the cloned database is presented to the SQL server as follows:
"[Microsoft][ODBC SQL Server Driver][SQL Server]Logical file 'WSS_Content_c553abc3-1f78-471e-a32e-d2082bdf8b49' is not part of database 'SMSP_B_WSS_Content_c553abc3-1f78-471e-a32e-d2082bdf8b49_sqlsnap__mssqlr2_05-24-2012_14.38.05'. Use RESTORE FILELISTONLY to list the logical file names.
Msg 3013, SevLevel 16, State 1, SQLState 42000"
I’ve attached the SMSQL clone backup log file which I think is most relevant, and the SMSP backup log file.
The customers SharePoint environment is as follows:
Microsoft Office SharePoint server 2010 Enterprise Edition SP1
2 x WFE servers – control / member agent
1 x SP Index server – member agent
1 x SP Application server - member agent
SQL server 2008 running on a Windows 2008 Failover cluster – member agents
SMSP 6.1 x64
Data ONTAP 8.0.2P3
SnapDrive 6.4 x64
SMSQL 5.2 x64
Host Utilities 6.0
Any advice on how to remediate this issue would be most appreciated.
Thanks for your reply. Yes that is the issue I'm facing and it is with SMSP. It is worrying because I read in the BURT that backup database metadata will be overwritten where databases have the same first four characters in their database name, as is the case with the customer's Sharepoint databases evidently. I will get the customer to execute the workaround as soon as possible.