Freigeben über

Migration - Move SharePoint 2007 from 1 server farm to another (Beta 2)

  • Artikel
Ref: https://technet2.microsoft.com/Office/en-us/library...
The scenario is to backup the Office SharePoint Server 2007 related databases from one farm and restore the contents and Shared Service Providers (SSPs) to the other farms. Migration scenario from Farm_A to Farm_B . This example assumes that the two farms have the same topology, service accounts, database names and application pool accounts. You can, however, migrate to a farm with different topology, service accounts, and database names.
Source Farm Steps:

1. Backup the whole farm

Note:

If you are backing up a stand-alone installation, start the Windows SharePoint Services Administration service before performing the backup.

1. (Optional) Backup the Single Sign On (SSO) master key on a removable media, such as a USB drive.

Target Farm Steps:

1. Make sure the Windows SharePoint Services 3.0 Web Service is started on the computers where you are hosting the portal sites, SSP and Central Admin sites.

2. Start the Office Search Service by following the farm setup instruction

3. (Recommended) Restore the whole farm using the Restore to the original farm (overwrite) procedure above, except that you would use the Create new option for step 7 rather than the Overwrite option.

Note:

The above migration steps will not migrate the configuration database and the central administrator web application. If you want to migrate the whole farm including the configuration database and the central administrator web application, use the restoreconfigurationdatabase switch of the stsadm.exe command line utility.

Note:

If you are restoring the backup to a stand-alone installation that uses SQL Server Express, you must start the spsadmin service and save the backup file to local folder.

1. After this type of migration, apply the following steps (these steps apply to the Beta 2 release only):

Step
Description

In the Default Content Access Account page, provide the password for the account you are using to crawl content.

This is required to run content crawls after the migration.

For any crawl rules that require credentials, provide the password for the account you are using to crawl content.

This is required to run content crawls after the migration.

Run the following from the command line: stsadm -o provisionservice -action start -servicetype spweb

This creates the Web application and application pools.

Run the following from the command line: stsadm -o setadminport -port <new admin port>

This changes the port number for the Central Administrator Web Application.

Run the following from the command line: iisreset /noforce

This saves that changes made by the two previous commands.

In the Internet Information Services Manager snap-in, navigate to the SharePoint Central Administration v3 application pool. On the Identity tab of the Properties dialog, provide the credentials for the application pool account.

This is required for the application pool to access the required resources.

On each of the target farm computers, run the following command from the command line: netlocalgroup WSS_RESTRICTED_WPG<the farm acct of the target farm> /a

This adds the farm account to the WSS_RESTRICTED_WPG group.

On each of the target farm computers, run the following command from the command line: netlocalgroup WSS_ADMIN_WPG<the farm acct of the target farm> /a

This adds the farm account to the WSS_ADMIN_WPG group.

Manually add any site hit rules to the target farm.

These rules might not have been migrated over.

On the Manage Personal Sites page, enter the correct URL in Preferred Search Center. At the command line enter: iisreset /noforce.

The "Preferred Search Center" URL still points to the source farm URL after migration.

1. (Optional) You can choose to restore each Web application, Default Web Site, and SSP separately using the Create new option. This way you can identify any problems you might experience with each restore item as you restore it.

2. Set the restored SSP to be the default SSP if is not already the default SSP.

3. Apply the workaround in the migration section of “Backup/restore workaround”.

4. If you cannot navigate to Search Setting page, check to see if the Windows Firewall is turned on. Windows Firewall will block all the search web service calls.

Backup and Restore for Single Sign-On Settings
Backup The SSO (Optional)

1. Backup the master secret

   1. Go to Central Administration page.

   2.Click Operations under Central Administration.

   3. Under Security Configurations, click Manage settings for single sign-on.

   4. Click Manage encryption key.

   5. You must have a removable drive to backup the key to.

2.Backup SSO database

      1. Go to Central Administration page.

      2. Click Operations under Central Administration.

      3. Under Backup and Restore, click on Perform a backup.

      4. On the Perform a Backup page, choose SSO.

      5. Start the backup by clicking Start Backup Process.

Restore or Migrate the SSO (Optional)

1. Configure SSO on that computer or farm. The database must have the same name as the source database.

2. Restore the backed up SSO database to the database created in above step.

            1. Go to Central Administration page.

            2. Click Operations under Central Administration.

            3. Under Backup and Restore, click on Restore from backup.

            4. Provide the path the backup file on the removable drive.

            5. Click OK.

3. Restore the master secret

            1. Go to Central Administration page.

            2. Click Operations under Central Administration.

            3. Under Security Configurations, click Manage settings for single sign-on.

            4. Click Manage encryption key.

            5. Put the drive on which secret was backed-up and click Restore after choosing the drive.

Migrating using SQL Server Tools

This scenario is a migration from the source farm to the target farm using SQL Server tools and Office SharePoint Server 2007 features and assumes that all features are the same, or compatible, between the source farm and the target farm.

Source Farm Steps

1. In SQL Server Enterprise Manager, backup all Office SharePoint Server 2007 related databases.

Target Farm Steps

1. Install Office SharePoint Server 2007 on the target farm computer. Do not create a SSP or portal.

2. In SQL Server Enterprise Manager, restore to the target farm computer, all Office SharePoint Server 2007 related databases except the configuration database and the central administrator content database. Use the Restore Databases menu option.

3. In the Office SharePoint Server 2007 central administrator console, create three web applications, one for the SSP, one for the People web application, and one for the portal site. If you have more web applications in the source farm, create the corresponding web applications in the target farm.

4. In the Office SharePoint Server 2007 central administrator console, detach the content database from the newly created web application by doing the following:

            1. From the Application Management page click the Content Databases link under the SharePoint Web Application Management section.

            2. Change the web application from the drop down list.

            3. Select the content database.

            4. Select Offline for Database Status and check the remove content database

            5. Click OK.

5. Attach the restored site Content database for the newly created web application, people web application and the SSP administrator web application.

            1. On the Application Management page click Content Databases under SharePoint Web Application Management.

            2. Change the web application from the drop down list

            3. Click Add a content database.

            4. Enter the SQL Server name and the name of the restored database.

            5. Click OK.

6. Restore the SSP

            1. On the Application Management page click Create or configure this farm's shared services.

            2. Click Restore SSP.

            3. Add relative info, SSP web application, people web application, SSP database name, search database name (optional) and click OK.

            7. Set the restored SSP as the default SSP for the target farm.

            8. Start the search crawl from the Search Setting page in the SSP administrator console.

            9. Click OK on the pop up dialog to resume the crawl.

 

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

Comments

  • Anonymous
    January 21, 2009
    PingBack from http://www.keyongtech.com/1999945-moss-2007-database-migration-from

  • Anonymous
    February 06, 2011
    I am trying to migrate a MOSS 2007 installation to a fresh build of Moss 2007 but the current MOSS 2007 does'nt have an SSP, any ideas. The site is there it has not SSP. am cleaning up an old contractor botch.

  • Anonymous
    February 06, 2011
    Neil - it doesnt matter if you have SSP or not. In your case, creating a new farm on the destination hardware and DB Detach - Attach mode would be best. Create 1 (or more) web app on the destination farm, take a SQL backup of the Cotnent DB in the Source Farm, attach it to the web app on the New Farm. Make sure the new farm is at least SP2 patch level. HTH

  • Anonymous
    March 22, 2015
    I absolutely love your blog and find nearly all of your post’s to be precisely what I’m looking for. <a href="http://staygreenacademy.com">SharePoint Online Training</a>