Restore content database
I would like to install a content database into a new Farm, the problem the content database is from IU Update & the new Farm is patched to SP2. How can the content database be upgraded to be included in the new Farm? I believe it is only possible to restore the content database when Farm versions & all prior patches match, where in the content database can one find all patches applied? New Farm would need initial install (RTM) then each patch appied in order up to IU Update then content database can be installed, then upgraded to SP2 or above, it would be nice if an easier way is possible, but no of none.
July 9th, 2010 8:19pm

On the source farm, you will need to check what version your farm is running. This can be concluded from the Central Administration -> Operations -> Servers in farm page. Then do a search online on the version number, and you'll see what patch level the farm is running on. Download the patches that apply to the patch level, install them on your destination farm, move or copy your content database to the new SQL server / cluster, and attach your content database by either using the UI or STSADM (addcontentdb).
Free Windows Admin Tool Kit Click here and download it now
July 9th, 2010 8:47pm

I know the source content database is IU, but the destination Farm is already at SP2, that is the rub; how can the content database to updated without all the intermediate steps of loading an entirely new SharePoint Farm with all the same patch levels?
July 9th, 2010 10:18pm

Warning: The content database restore situation is worse than ever; since the content database is patched to IU it necessary to create a SharePoint Farm at this patch level to restore and then apply additional Service packs. The problem is 64-bit hardware uses Windows Server 2008 which does not support the SharePoint RTM or IU patch level, so there is no way to create the SharePoint Farm using this hardware. Windows Server 2008 requires SharePoint SP2 or later. Any one think of a possible workaround, besides creating a Farm on outdated hardware? Remember the content database needed to restore is at the Infrastructure Update patch level.
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2010 4:51pm

Hello Multisy, Attaching the database to a web application in the destination farm should upgrade it “on the fly”. This is actually a common method of upgrading to a later build or service pack and we find in many cases it can be faster to detach the content databases upgrade the farm and then attach the databases. Most likely you’ll have to do it via stsadm stsadm -o addcontentdb -url <http://servername:port> -databasename <ContentDBName> -databaseserver <NewPrincipalServer> Reference: http://technet.microsoft.com/en-us/library/cc262996(office.12).aspx Reagrds, Hiran Microsoft Online Community Support
July 12th, 2010 6:55pm

Before using the stsadm -o addcontentdb, I first created an empty web application using stsadm -o extendvs. Then executed the stsadm -o addcontentdb using the url of the web application created above. The OldDB content database is patched to IU and the current farm is patched to SP2, but the following error occurs: The specified SPContentDatebase Name=OldDB Parent-SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade the SharePoint application server before attemting to access this object. The SP2 Farm reports the OldDB is newer??? The problem here is the OldDB was patched from RTM to IU, but the Farm was created on Windows Server 2008 using SharePoint /w SP2 since this is the only way to install SharePoint using Windows Server 2008. The Farm has never been patched, while the OldDB has been patched, and I beleive is the source of the error. How to workaround installing older content database on a MOSS SP2 running on Windows Server 2008?
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2010 5:43am

Hi Multisy, You'll need to check the version column of the version table of the content database OldDB Parent-SPDatabaseServiceInstance The farm your attaching it to must be equal to or higher than that of the highest version shown in that table You'll probably find that the version of your database is higher than 12.0.0.6421 Reagrds, Hiran Microsoft Online Community Support
July 14th, 2010 1:26am

The version table was most helpful, versions were not what they were thought too be. Thanks
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2010 4:31am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics