Link to home
Start Free TrialLog in
Avatar of Super222
Super222

asked on

SharePoint Backup Restore

Hi there,

I have a problem with Sharepoint backup restore!
Our customer's server worked properly before they took an image from windows! Their administrator said that he changed the windows partition size virtually and then an error occurred.
"Can not connect to configuration database"

I have tried to fix this problem but i couldn't. I tried so many ways but they didn't work.

 Then i decided to restore their backup but i faced with following error:

BEGIN RESTORE DATABASE [WSS_Content] FROM DISK=@db_location WITH STATS=5, FILE=1, MOVE @db_OldName TO @db_NewFile, MOVE @db_OldLogName TO @db_NewLogFile, NOREWIND, NOUNLOAD, RECOVERY
END

@db_location=E:\SPS backup - soheil\spbr0000\0000000F.bak, @db_OldName=WSS_Content, @db_NewFile=C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content.mdf, @db_OldLogName=WSS_Content_log, @db_NewLogFile=C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content_log.ldf, @db_name=WSS_Content
[9/10/2009 12:00:16 AM]: Error: Object WSS_Content failed in event OnRestore. For more information, see the error log located in the backup directory.
      SqlException: Unable to open the physical file "C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
File activation failure. The physical file name "C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content_log.ldf" may be incorrect.
5 percent processed.
10 percent processed.
15 percent processed.
20 percent processed.
25 percent processed.
30 percent processed.
35 percent processed.
40 percent processed.
45 percent processed.
50 percent processed.
55 percent processed.
60 percent processed.
65 percent processed.
70 percent processed.
75 percent processed.
80 percent processed.
85 percent processed.
90 percent processed.
95 percent processed.
100 percent processed.
Processed 296360 pages for database 'WSS_Content', file 'WSS_Content' on file 1.
Processed 5 pages for database 'WSS_Content', file 'WSS_Content_log' on file 1.
RESTORE DATABASE successfully processed 296365 pages in 111.051 seconds (21.862 MB/sec).
[9/10/2009 12:00:16 AM]: Debug:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreHelper.RunCommand(SPBackupRestoreInformation args, Boolean& restart, SPSqlBackupRestoreConnection connection)
   at Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreHelper.Run(SPBackupRestoreInformation args)
   at Microsoft.SharePoint.Administration.Backup.SPSqlRestoreHelper.Run(SPBackupRestoreInformation args)
   at Microsoft.SharePoint.Administration.SPDatabase.OnRestore(Object sender, SPRestoreInformation info)
   at Microsoft.SharePoint.Administration.SPContentDatabase.OnRestore(Object sender, SPRestoreInformation info)
[9/10/2009 12:00:16 AM]: Verbose: Starting OnPostRestore event.
[9/10/2009 12:00:16 AM]: Verbose: Starting object: Windows SharePoint Services Web Application.
[9/10/2009 12:00:16 AM]: Progress: [Windows SharePoint Services Web Application] 100 percent complete.
[9/10/2009 12:00:17 AM]: Verbose: Starting object: SharePoint - 80.
[9/10/2009 12:00:17 AM]: Progress: [SharePoint - 80] 100 percent complete.
[9/10/2009 12:00:17 AM]: Verbose: Notifying third parties that the restore completed.
[9/10/2009 12:00:17 AM]: Verbose: The IIS Web Site has been extended.  You may need to use iisreset.exe to restart IIS before your site becomes accessible.
[9/10/2009 12:00:17 AM]: Finish Time: 9/10/2009 12:00:17 AM.
[9/10/2009 12:00:17 AM]: Progress: Completed with errors, please refer to the log file for details.
[9/10/2009 12:00:17 AM]: Verbose: Deleting the file E:\SPS backup - soheil\spbr0000\sprestore.xml and replacing it.
[9/10/2009 12:00:17 AM]: Verbose: The backup/restore process included the following objects:
[9/10/2009 12:00:17 AM]:     *Farm\
        *[SharePoint_Config_86369bf6-97ba-4e81-9e69-9fceef82b9f2]\
        *Windows SharePoint Services Search\
            *[Search instance]\
                *[WSS_Search_APPSVR]\
        Windows SharePoint Services Web Application\
            SharePoint - 80\
                *WSS_Content\
        *[WSS_Administration]\
            *[Web Application]\
                *[SharePoint_AdminContent_a80e5dd1-ac31-484e-a46d-445b5a47083d]\

[9/10/2009 12:00:17 AM]: Completed with 0 warnings.
[9/10/2009 12:00:17 AM]: Completed with 1 errors.
[9/10/2009 12:00:22 AM]: Restore failed for Object WSS_Content failed in event OnRestore. For more information, see the error log located in the backup directory.
[9/10/2009 12:00:22 AM]: -------------------------------------------------

Sharepoint specification:
Installation Mode: Basic
Database: SQL Embedded Edition (SSEE)
Backup Mode: Full

Is there any idea?

Thanks in advance
Avatar of zephyr_hex (Megan)
zephyr_hex (Megan)
Flag of United States of America image

this looks like the error:
      SqlException: Unable to open the physical file "C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
File activation failure. The physical file name "C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content_log.ldf" may be incorrect.


do the MDF and LDF files specified above exist in the locations specified?
Hi,

If the database or the files do not exist in the location specifed try creating a blank WSS_Content DB with the files in that location and then restore over the blank copy.
Avatar of Super222
Super222

ASKER

Hi everybody

Yes they are exist!!!! at the first step of restoring, LDF and MDF files is created in this location "C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\".
 I'm wondering what does this error mean????!!!  May be the restore process can't read MDF and LDF files?? or backup files are corrupted??  what's your idea about it?

To mass:
Can you explain how can i restore db in a blank database via sharepoint restore process because when i start the restore process if i entered a database name that is exist in that location, restore process is stopped and said that a database name is exist!!!  Could you explain more about the solution please???

Thanks alot guys
Have you checked that the account you're using to perform the restore has write permissions on
C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\ ?
Yes.
The account is domain admin user.
ASKER CERTIFIED SOLUTION
Avatar of Super222
Super222

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial