how do I restore a content database?

Question

I did a complete uninstall and reinstall of SharePoint Server 2007 Enterprise, along with SQL Server 2005 Std, for reasons I won't go into.  I only had a small Image Library on the previous site (which was never "public").  I want to restore the portion of the old backup that contains this so I can avoid having to re-do all the work put into it.
I'm pretty sure it'll be contained in the previous top level site's content database (in this case, WSS_Content).  My thinking is to restore it to my new top level site and then go to Central Admin > Application Management > Content Databases so I can add it.  However, I am unsure what to do when I get to the Restore page where I choose whether to do a New Configuration or Same Configuration since I get a warning pop-up that says something about overwriting everything if I choose "Same".  Plus the database to be restored was associated with an SSP named SSP1, which doesn't exist anymore; should I edit the path to read, "Farm\<new SSP name>\<top level site name and port number>\WSS_Content?  Or do I need to restore the original top level site and SSP in order to restore the content database?

Many thanks in advance!

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 1

Hi Mike,

If it is just a content database then you should be able to just go to Central Admin>Applications>content databases and add it back.  If your newly installed SharePoint is at a more recent level of updates than when it was built before you will have to use the stsadm -o addcontentdb command to add the content db back.

After adding it back, then if you go to Central Admin>Applications>Site collections you should see the site collection listed and how to access it.  If you had it under a managed path that you created then you will need to add that managed path back first before you can access it.  If it was just under the default /sites then you should be all set.

Hopefully that helps.

Sincerely,
Karl

Answer 2

I'll give it a try first thing in the morning.  Thanks!

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 3

Well, it didn't work, and I'm not sure why.  Here's the command I used:

stsadm.exe -o addcontentdb -url http://<sitename> -databasename wss_content04132009

And I got this error:

The specified SPContentDatabase Name=WSS_Content04132009 Parent=SPDatabaseServiceInstance Name=wctintranet has been ugraded to a newer version of SharePoint.  Please upgrade this SharePoint application server before attempting to access this object.

SP2 has been applied to both WSS and SharePoint, plus the April Infrastructure Updates.  I also have run a forced update against WSUS and then Microsoft Update, so I know I'm up-to-date.  So .... why the error?  Do I need to place SQL Server 2005 in Single-User mode for this recovery operation?

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 4

Could you check the versions in CA by going to operations -> Servers in Farm and compare the differences. This is a very common upgrade error which comes from differences in patches.

Debasish

---

SharePoint Architect

Answer 5

I have a single server.  The version is 12.0.0.6504.

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 6

Mike
The service pack level and hot fix along with security patch level should match exactly in yoiur both server the old srver and the new server.
go to http://www.mindsharpblogs.com/penny/articles/481.aspx to find the patch level and then comparre on your new server .
THis will help

Answer 7

Try doing this:

1. STSADM.EXE -o upgrade -inplace -forceupgrade –url http://webapp  for each web application, then
2. psconfig -cmd upgrade -inplace b2b -wait –force

Regards,
Debasish

---

SharePoint Architect

Answer 8

The versions number says it's the April 2009 Cumulative Update for both WSS 3 and SP 2007.  Maybe I need to uninstall those so I match the level of the content database I'm trying to restore (backup dated 13 April 2009).

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 9

Well, it almost worked.  I have 3 web apps and the stsadm command for each seemed to work fine.  Ran the psconfig command and it failed on task 2 of 4.  Here's the Application Log Errors:

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Database
Event ID:    3759
Date:        7/2/2009
Time:        12:10:32 PM
User:        N/A
Computer:    WCT-SHAREPOINT
Description:
Database 'SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23' on SQL Server instance 'wct-sharepoint\wctintranet' is not empty and does not match current database schema.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
============================
Event Type:    Error
Event Source:    SharePoint Products and Technologies Configuration Wizard
Event Category:    None
Event ID:    104
Date:        7/2/2009
Time:        12:10:32 PM
User:        N/A
Computer:    WCT-SHAREPOINT
Description:
Failed to initiate the upgrade sequence.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
Microsoft.SharePoint.Upgrade.SPUpgradeException: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
   at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o)
   at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
=====================
Event Type:    Error
Event Source:    SharePoint Products and Technologies Configuration Wizard
Event Category:    None
Event ID:    100
Date:        7/2/2009
Time:        12:10:32 PM
User:        N/A
Computer:    WCT-SHAREPOINT
Description:
Configuration of SharePoint Products and Technologies failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at F:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_7_2_2009_12_10_23_573_839895483.log, fix the problem, and run this configuration wizard again.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
==================
Here's the ERR entries from the PSC log:

07/02/2009 12:10:32  7  ERR            Task upgradebootstrap has failed with an unknown exception
07/02/2009 12:10:32  7  ERR            Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
   at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o)
   at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

07/02/2009 12:10:32  7  ERR            An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
Microsoft.SharePoint.Upgrade.SPUpgradeException: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
   at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o)
   at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

07/02/2009 12:10:32  7  ERR              Task upgradebootstrap has failed
07/02/2009 12:10:32  7  INF              friendlyMessage for task upgradebootstrap is An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
07/02/2009 12:10:32  7  INF              debugMessage for task upgradebootstrap is An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
Microsoft.SharePoint.Upgrade.SPUpgradeException: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
   at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o)
   at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

07/02/2009 12:10:32  1  ERR          Failed to initiate the upgrade sequence.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
Microsoft.SharePoint.Upgrade.SPUpgradeException: The specified SPContentDatabase Name=SharePoint_AdminContent_39bdfd07-dbe9-46ec-bfa6-55e0699ecd23 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
   at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o)
   at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 10

I took a look at KB953338 and saw that SP2 can't be uninstalled.  Read KB873125 and it says to completely uninstall the Office suite in order to uninstall a Service Pack.

The reason I bring this up is that the content database I want to restore was backed up prior to SP2 and the April 2009 CU.  If I understand this right, then SP needs to be at the exact same level as the database being restored.  So ... If I do this I can restore it and then install SP2 and the April ( and now June) CU's.

Comments?

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 11

That is true. Even with SP1 you would not get the option to uninstall. So, the only way I can think now is to re-install the suite with SP1 and once you are done with attaching the databases, use the psconfig command to upgrade.

Debasish

---

SharePoint Architect

Answer 12

I'll get on it; tonight and tomorrow and report back.

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 13

Okay, I've done a few things with no success.  I got to SP1 with the April CU, did the restore and got the same error message - the content database version was newer than the one I was trying to restore it to. (Not sure why)  So I backed out and did the stsadm and psconfig commands outlined above - they were successful, but same result.  Tried to go into CA > Application Management > Content databases and ad it there - same error.

Ran Microsoft Update to see if there was something I mised from that month, but saw nothing.

It'd sure be helpful if the Backup and Restore History would have a column that listed the server version of the job - it'd end the guessing games.

Here's a thought ... what about if I did a restore of the Full Farm?  Would it matter what version of the SharePoint Server was?

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 14

Hi Mike,

 

The error message indicate the backup database version was newer than you current SharePoint farm, so upgrade your SharePoint farm is needed.

 

I am not understand “I got to SP1 with the April CU”, did you mean SP2 with April CU?

If not, could you please try to Create an installation source that includes software updates (Office SharePoint Server 2007) (http://technet.microsoft.com/en-us/library/cc261890.aspx) and try to restore again?

You could get the latest update in Updates Resource Center for SharePoint Products and Technologies (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx)

 

Based on the error log, you tried to restore Central Administration Site (SharePoint_AdminContent_GUID), but from the previous reply, you wanted to restore a normal content database.

I suspect this should be the cause of database schema issue.

Could you please confirm whether the action is what you want?

 

If not, please try to get the correct content database and try again.

 

Let me know the result if possible.

-lambert

---

Sincerely,

Lambert Qin | Microsoft TechNet Managed Forum Support

Posting is provided "AS IS" with no warranties, and confers no rights.

Answer 15

You are correct; it should have read as "SP1 and the August 2008 CU".  I tried just these updates since the application of SP2 and the April 2009 CU was - I think - the cause of the problem.

As for what I am restoring, I select Farm then on the next screen I select just the WSS-Content choice and then try a restore.

I will try to restore this again and report back.

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 16

Not done yet, but wanted to let you know what is in the sprestore.log file.

[7/6/2009 10:01:47 AM]: Verbose: Adding WSS_Content to Restore list.
[7/6/2009 10:02:08 AM]: Progress: Starting Restore.
[7/6/2009 10:02:08 AM]: Start Time: 7/6/2009 10:02:08 AM.
[7/6/2009 10:02:08 AM]: Verbose: Requested by WHOOPER\Moss_Admin.
[7/6/2009 10:02:08 AM]: Verbose: Backup/Restore Settings:
    Restore
    Backup Method: Full
    Top Component: Farm\SSP1\SharePoint - 80\WSS_Content
    Directory: \\wct-sharepoint\spbackup
    Progress updated: 5
[7/6/2009 10:02:08 AM]:     Restore Method: New
    Backup ID: b66d2408-6eb3-4c23-8c44-898f4c8ed803

[7/6/2009 10:02:09 AM]: Verbose: Starting OnRestore event.
[7/6/2009 10:02:09 AM]: Verbose: Current object: WSS_Content04132009-2 (previous name: WSS_Content).
[7/6/2009 10:02:09 AM]: Verbose: [WSS_Content] SQL Server Connection String: Data Source=wct-sharepoint\wctintranet;Initial Catalog=WSS_Content04132009-2;Integrated Security=True.
[7/6/2009 10:02:09 AM]: Verbose: [WSS_Content] SQL command started at: 7/6/2009 10:02:09 AM. This command may take a while to complete and without notification.
[7/6/2009 10:02:09 AM]: Verbose: [WSS_Content] SQL Server Command:
IF EXISTS ( SELECT * FROM master..sysdatabases WHERE has_dbaccess(name)=1 AND name=@db_name )
BEGIN
    SELECT 1 as ErrorCode
END
ELSE
BEGIN RESTORE DATABASE [WSS_Content04132009-2] 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=\\wct-sharepoint\spbackup\spbr0007\00000017.bak, @db_OldName=WSS_Content, @db_NewFile=E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\WSS_Content04132009-2.mdf, @db_OldLogName=WSS_Content_log, @db_NewLogFile=E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\WSS_Content04132009-2_log.ldf, @db_name=WSS_Content04132009-2
[7/6/2009 10:02:13 AM]: Progress: [WSS_Content] 5 percent complete.
[7/6/2009 10:02:17 AM]: Progress: [WSS_Content] 10 percent complete.
[7/6/2009 10:02:19 AM]: Progress: [WSS_Content] 15 percent complete.
[7/6/2009 10:02:23 AM]: Progress: [WSS_Content] 20 percent complete.
[7/6/2009 10:02:27 AM]: Progress: [WSS_Content] 25 percent complete.
[7/6/2009 10:02:30 AM]: Progress: [WSS_Content] 30 percent complete.
[7/6/2009 10:02:32 AM]: Progress: [WSS_Content] 35 percent complete.
[7/6/2009 10:02:34 AM]: Progress: [WSS_Content] 40 percent complete.
[7/6/2009 10:02:35 AM]: Progress: [WSS_Content] 45 percent complete.
[7/6/2009 10:02:35 AM]: Progress: [WSS_Content] 50 percent complete.
[7/6/2009 10:02:35 AM]: Progress: [WSS_Content] 55 percent complete.
[7/6/2009 10:02:36 AM]: Progress: [WSS_Content] 60 percent complete.
[7/6/2009 10:02:36 AM]: Progress: [WSS_Content] 65 percent complete.
[7/6/2009 10:02:36 AM]: Progress: [WSS_Content] 70 percent complete.
[7/6/2009 10:02:36 AM]: Progress: [WSS_Content] 75 percent complete.
[7/6/2009 10:02:37 AM]: Progress: [WSS_Content] 80 percent complete.
[7/6/2009 10:02:37 AM]: Progress: [WSS_Content] 85 percent complete.
[7/6/2009 10:02:37 AM]: Progress: [WSS_Content] 90 percent complete.
[7/6/2009 10:02:37 AM]: Progress: [WSS_Content] 95 percent complete.
[7/6/2009 10:02:38 AM]: Progress: [WSS_Content] 100 percent complete.
[7/6/2009 10:02:38 AM]: Verbose: [WSS_Content] SQL Server Message: Processed 4504 pages for database 'WSS_Content04132009-2', file 'WSS_Content' on file 1.
[7/6/2009 10:02:38 AM]: Verbose: [WSS_Content] SQL Server Message: Processed 2 pages for database 'WSS_Content04132009-2', file 'WSS_Content_log' on file 1.
[7/6/2009 10:02:43 AM]: Verbose: [WSS_Content] SQL Server Message: RESTORE DATABASE successfully processed 4506 pages in 27.368 seconds (1.348 MB/sec).
[7/6/2009 10:02:43 AM]: Verbose: [WSS_Content] SQL command completed at: 7/6/2009 10:02:43 AM.
[7/6/2009 10:02:43 AM]: Verbose: [WSS_Content04132009-2] Verifying that the database restoration is complete.
[7/6/2009 10:02:43 AM]: Verbose: [WSS_Content04132009-2] SQL Server Command: USE [master]
                        SELECT status FROM master..sysdatabases WHERE name=@db_name
    @db_name=WSS_Content04132009-2
[7/6/2009 10:02:43 AM]: Debug: [WSS_Content04132009-2] Database status is 65536.
[7/6/2009 10:02:43 AM]: Verbose: [WSS_Content04132009-2] SQL Server Command: SELECT TOP 1 1 FROM [WSS_Content04132009-2]..sysobjects
[7/6/2009 10:02:43 AM]: Verbose: [WSS_Content04132009-2] Database restoration has been verified.
[7/6/2009 10:02:43 AM]: Verbose: Starting OnPostRestore event.
[7/6/2009 10:02:43 AM]: Verbose: Current object: WSS_Content04132009-2 (previous name: WSS_Content).
[7/6/2009 10:02:43 AM]: Error: Object WSS_Content04132009-2 (previous name: WSS_Content) failed in event OnPostRestore. For more information, see the error log located in the backup directory.
    SPException: Cannot attach database to Web application. Use the command line tool or Central Administration pages to attach the database manually to the proper Web Application.
[7/6/2009 10:02:43 AM]: Debug:    at Microsoft.SharePoint.Administration.SPContentDatabase.OnPostRestore(Object sender, SPRestoreInformation args)
[7/6/2009 10:02:43 AM]: Verbose: Notifying third parties that the restore completed.
[7/6/2009 10:02:43 AM]: Verbose: The IIS Web Site has been extended.  You may need to use iisreset.exe to restart IIS before your site becomes accessible.
[7/6/2009 10:02:43 AM]: Finish Time: 7/6/2009 10:02:43 AM.
[7/6/2009 10:02:43 AM]: Progress: Completed with errors, please refer to the log file for details.
[7/6/2009 10:02:43 AM]: Verbose: Deleting the file \\wct-sharepoint\spbackup\spbr0007\sprestore.xml and replacing it.
[7/6/2009 10:02:43 AM]: Verbose: The backup/restore process included the following objects:
[7/6/2009 10:02:43 AM]:     *Farm\
        *[SharePoint_Config]\
        *Windows SharePoint Services Web Application\
            *SharePoint - MySites12345\
                *WSS_Content_f05586d54a884aca986a936cc7f3cf34\
        *[WSS_Administration]\
            *[Web Application]\
                *[SharePoint_AdminContent_4f53bd22-e6da-4424-af5f-fff6e1d09511]\
        *SSP1\
            *[SharePoint - 80]\
                *WSS_Content04132009-2\
            *[SharedServices1_DB]\
            *[UserProfileApplication]\
            *[SessionStateSharedApplication]\
            *[Shared Search Index]\
                *[SharedServices1_Search_DB]\
        *Global Search Settings\
        *Windows SharePoint Services Help Search\
            *[Search instance]\
                *[WSS_Search_wct-sharepoint]\

[7/6/2009 10:02:43 AM]: Completed with 0 warnings.
[7/6/2009 10:02:43 AM]: Completed with 1 errors.
[7/6/2009 10:03:04 AM]: Restore failed for Object WSS_Content04132009-2 (previous name: WSS_Content) failed in event OnPostRestore. For more information, see the error log located in the backup directory.
[7/6/2009 10:03:04 AM]: -------------------------------------------------


I will try the STSADM.exe command and report back.

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 17

STSADM.exe command failed (stsadm.exe -o addcontentdb -url http://wct-sharepoint -databasename wss_content04132009-2)

"The specified SPContentDatabase Name=wss_content04132009-2 Parent=SPDatabaseServiceInstance Name=wctintranet has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object."

I also see this in my Application (Event) log:

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Database
Event ID:    3759
Date:        7/6/2009
Time:        10:17:08 AM
User:        N/A
Computer:    WCT-SHAREPOINT
Description:
Database 'wss_content04132009-2' on SQL Server instance 'wct-sharepoint\wctintranet' is not empty and does not match current database schema.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 18

Hi Mike,

 

Thanks for your update.

 

Now I know your scenario as follows:

1.    Current farm had SP1 with August 2008 CU updated.

2.    You restored a content database from a Full farm backup.

3.    The content database (WSS_Content04132009-2) was restored to SQL Server database successfully.

4.    The backup failed with mismatched schema when attaching the content database to a web application.

If I misunderstand your scenario, please feel free to correct me.

 

Based on the error message, the backup file was built under a more recent updated SharePoint environment and it cannot be restored to a farm that has lower version.

 

You could verify the updates version of the content database with the SQL query: SELECT * FROM Versions Where VersionId = ‘00000000-0000-0000-0000-000000000000’.

For your information, the version of SP1 with August 2008 CU should be 6327.

 

Please try to update with current farm with the version shown in the content database and attach the content database again.

For your information, the versions of each update was recorded in Available updates section of Deploy software updates for Office SharePoint Server 2007 (http://technet.microsoft.com/en-us/library/cc263467.aspx)

 

 

Let me know the result if possible.

-lambert

---

Sincerely,

Lambert Qin | Microsoft TechNet Managed Forum Support

Posting is provided "AS IS" with no warranties, and confers no rights.

Answer 19

I couldn't figure out how to find the GUID so I could run the SQL query, so I rechecked my server version and saw it was at 6318, Infrastructure Update (KB951695 and KB951297).  Looks like what I need to do to get to 6327 is download and install the hotfixes for the Cumulative Update (KB957109, KB956056 and KB956057).

Am doing that now and will report back after they are installed and I've tried to attache the restored DB.

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 20

I was able to successfully attach the restored content database.  But ... my Image Library is empty.  The site is there, with the edits to the navigation I made, but there is no content.

Did I make a wrong assumption that all content that I, or any other user, would have added to any SharePoint site would be inside the WSS_Content database?

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 21

Mike,
When you say any SharePoint site you mean same web app ? or it is different web app? If it is different we app then the content database will also be differnt . Again even if it is same web app abd different site colelction depends how you create the site collection. You can create new site collection and ue diffwernt web app. You can have more than one database on the web app and or site collection.

Answer 22

Well, I was speaking in general, but to answer your question, it's a new web app, as far as the restored content database is concerned.

Not quite sure I follow your thoughts; are you saying that, in order to see the content (in this case, the image library), I also need to restore the web app?

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 23

Hi Mike,

 

Glad to hear the content database was successfully attached.

 

SharePoint content (including the content in the Image Library) was stored in the content database, you need not to restore the web application for the scenario.

 

You could see the modified navigation, I suppose the site was successful restored.

One possibility that cause the Image Library empty is that there was no content in the Image Library when performing the backup.

 

If the content database don't contain sensitive data, could you please back the content database in SQL Server and upload it to the workspace and let me do further research in my local?

Workspace URL: (https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=27d8325b-0c3d-403c-a6e1-ad0d3f0a72d7)

Workspace Password: X$*W04e-T#5Ww

 

If you cannot upload the content database, could you please take a new backup and try to restore the it to the farm and verify whether the Image Library was still empty?

 

Let me know the result if possible.

-lambert

---

Sincerely,

Lambert Qin | Microsoft TechNet Managed Forum Support

Posting is provided "AS IS" with no warranties, and confers no rights.

Answer 24

I am uploading a backup of that content database to you for analysis as I type.

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 25

If it is just a content database then you should be able to just go to Central Admin>Applications>content databases and add it back.  If your newly installed SharePoint is at a more recent level of updates than when it was built before you will have to use the stsadm -o addcontentdb command to add the content db back.

So I can better understand this, are you saying that "Add a content database" in the UI should only be used when the content database is from a Sharepoint that was at the same revision as the current one?  Else you use stsadm?

Answer 26

Hi Mike,

 

Thanks for your cooperation.

 

I restored the content database in my local, I could see the “Pictures, Slides and Video” library, but I didn't find any contents in the library.

I also checked the content database in SQL Server, I could not find the contents either.

 

I suppose the library was empty in the backup file.

 

Please try to make a new backup file with the content and verify whether the issue is still existed?

 

Let me know If you need further assistance.

-lambert

---

Sincerely,

Lambert Qin | Microsoft TechNet Managed Forum Support

Posting is provided "AS IS" with no warranties, and confers no rights.

Answer 27

I've restored a newer WSS_Content database, one I confirmed has the image library in it.  It is attached through Application Management > Content Databases > Add Content Databases to the top level site on port 80.

Now ... how do I "see" the Library and it's contents?

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)

Answer 28

Hi Mike,

 

If you still could not see the contents, I suggest you to contact Microsoft Customer Support Services (CSS) via telephone so that a dedicated Support Professional can assist you in a more directly way. Please be advised that contacting phone support will be a charged call.

 

To obtain the phone numbers for specific technology request please take a look at the web site listed below.

http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

 

If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

 

Thanks for your understanding.

-lambert

---

Sincerely,

Lambert Qin | Microsoft TechNet Managed Forum Support

Posting is provided "AS IS" with no warranties, and confers no rights.

Answer 29

We can't afford that, so I'll just reproduce the image library.  Thanks for all the help.

---

Mike Webb, IT Admin, Platte River Whooping Crane Maintenance Trust, Inc. (a 501(c)(3) conservation nonprofit org.)