Built in tools for migrating MOSS 2007 SP1 content into new unconfigured farm with same name server
Hi All, As part of my DR plan I'd like to utilize the current MOSS 2007 SP1 and SQL Server 2008 built in tools for migrating MOSS 2007 SP1 content into new unconfigured farm with same name server, may I know if I miss something here ? Use Central Administration site's backup and restore tools --> Entire farm structure and it's settings. perform stsadm -preparetomove Use SQL Server 2008 right click database backup option on the MOSS_ContentDB and then I'm lost in restoring it in the new Farm process, shall I create new CA and SSP or attach/restore the SQL server MOSS_ContentDB first ? any kind of help would be greatly appreciated. Thanks/* Windows Infrastructure Support Engineer */
March 11th, 2010 3:37pm

Hi,>> migrating MOSS 2007 SP1 content into new unconfigured farm with same name serverplease clarify,are you moving from server to another server?if yes, the other server has the same OS and MOSS version or not?are you going to use the same SQL server?give more detials of the current and the wanted caseBest Regards, Ammar MCT http://ahmed-ammar.blogspot.com Posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
March 11th, 2010 3:48pm

If the backups for the configuration database and central administration database were taken when the SharePoint farm was running, restore them into the new farm is not supported since it might lead to inconsistency between configuration database and content database. In this case, you have to: 1. create a new SharePoint farm on the new server and create new CA and SSP; 2. after that, you can create new web applications on the new farm; 3. remove the content database for the newly created web application with SharePoint built in tool such as stsadm; 4. restore/attach the content database backup on the new SQL server with SQL server management tools; 5. add then restored content database into the web application created in step 3 with SharePoint built in tools; 6. run a full crawl for search. If the backups for the configuration database and central administration database were taken when the SharePoint farm was stopped, you can restore configuration onto the new server. Since the farm is stopped, SharePoint backup tools is not available to you, you should use SQL tools to back up the databases. You still need to run a full crawl after restore since search index is not in SQL server database. Actual SharePoint disaster recovery plan can be more complicated that what I had listed before, for example, you should all take customization into consideration. Please download and read Data protection and recovery for Office SharePoint Server (White paper): http://go.microsoft.com/fwlink/?LinkId=102839&clcid=0x409 Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com
March 12th, 2010 6:06am

Hi Ahmed, Yes I do move it into another server that I've just rebuild but haven't rename it back to the same with the current server (which is broken). no the OS version is 2008R2 and all of the component is newer Old: Windows Server 2008 Standard SP2 WSS 3.0 SP1 MOSS 2007 SP1 SQL Server 2008 Standard New: Windows Server 2008 Standard R2 SP2 WSS 3.0 SP2 (Slip stream install) MOSS 2007 SP2 (Slip stream install) SQL Server 2008 Standard SP1 what i want is to move all of the content into the newly built server without any 3rd party apps help and avoid broken link when migrating all of the content into the new server. Most importantly the user doesn't have to update all of their bookmark. Thanks/* Windows Infrastructure Support Engineer */
Free Windows Admin Tool Kit Click here and download it now
March 12th, 2010 2:45pm

Hi Gu, Thanks for the reply, correct me if I'm wrong: Using CA farm / site recovery tools: 1. the Web apps must be running but cannot backup the MOSS_ConfigDB (therefore all of the settings in the new farm must be the same eg. Service name, port, etc..) Using the SQL data backup from SSMS: 1. SharePoint must be OFF but all MOSSDB can be backed up and restored into the new server/farm (only SSMS backup and restore involved). I'd like to know if that is the correct way in doing the backup and restore ? last resort I shall then just use MS DPM 2007/* Windows Infrastructure Support Engineer */
March 12th, 2010 2:52pm

Hi All, I've performed the backup from the CA site, however one option is error see the attached code Shared Search Index Object Shared Search Index failed in event OnPrepareBackup. KeyNotFoundException: Object e2581ec6-0096-4756-bad4-0df75dc2d0c1 not found. is that ok since i don't bother with the search content (can be rescheduled for another crawling). Does anyone know if that error is ok / negligible ? Thanks. and when I go to the SSMS and look at the *_ContentDB all backup destination has been prefilled with the .BAK (same as the destination directory source) [MOSS_Farm_Config]\ Windows SharePoint Services Web Application\ MySite - 10001\ MySite_ContentDB\ Sandbox Web Application\ WSS_Content\ SharePoint - 80\ SharePoint80_ContentDB\ [WSS_Administration]\ [Web Application]\ SharePoint_AdminContent_f632e5bf-cbd9-4d9f-a819-1811feb4f2b6\ SharedServices1\ [SSP-10000]\ SSP_ContentDB\ [SharedServices1_DB]\ [UserProfileApplication]\ [SessionStateSharedApplication]\ *[Shared Search Index]\ [SharedServices1_Search_DB]\ Global Search Settings\ Windows SharePoint Services Search\ [Search instance]\ [MOSS_Search_DB]\/* Windows Infrastructure Support Engineer */
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2010 6:42am

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

Other recent topics Other recent topics