SharePoint au Quotidien avec EROL

 

Retour page Accueil
Remonter

 

 

 

 

 

 

 

 

Migrating Databases and Sites

As your organization uses Microsoft's SharePoint Team Services to create sites and add content, you may find you require more bandwidth or processing power from your database, or just more space on your server. To solve database bandwidth and power issues, migrate your database content from Microsoft Data Engine (MSDE) to Microsoft SQL Server. To solve space issues, migrate sites to a new server.

Migrating from MSDE to SQL Server

By default, if SQL Server is not installed on your computer when you install SharePoint Team Services, the Microsoft Data Engine (MSDE) is automatically installed and used to store collaboration database content. If you find that you need to upgrade from the local MSDE installation to either a local or remote SQL Server installation, you can do so by performing the following steps:

  1. Install SQL Server 7.0 or SQL Server 2000.
  2. Back up the MSDE database.
  3. Restore the database information to the new SQL Server installation.
  4. Change the database connection to reflect the new database settings.

To back up and restore the database, you use the Enterprise Manager console for SQL Server.

To back up the MSDE database

  1. On the originating server, start SQL Enterprise Manager.

    SQL Enterprise Manager is part of the SQL Server installation.

  2. Establish a connection to the MSDE server, and locate the database you want to back up.

    For example, the collaboration database might be named servername_LM_W3SVC_1_COLLAB.

  3. Right-click the database, click All Tasks, and then click Backup Database.
  4. In the SQL Server Backup dialog box, under Overwrite, select Overwrite existing media, and then click OK.

The backup creates a file, such as servername_LM_W3SVC_1_COLLAB_backup, in the MSSQL\Backup directory on the origination server.

Now you can restore the database to your destination server - either the same server (with SQL Server now installed) or a remote, dedicated server for your SQL Server databases.

To restore the database to the destination server

  1. On the destination server, create a shared folder (if necessary) to the originating server’s MSSQL\Backup directory and copy the backed-up database (servername_LM_W3SVC_1_COLLAB_backup) to the destination server’s MSSQL\Backup directory.
  2. On the destination server, start SQL Enterprise Manager.
  3. Right-click Databases, click All Tasks, and then click Restore Database.
  4. For the database name in the Restore as Database field, enter the name you want the database to be called.
  5. Select From Device and point to the backed-up database.

After you have restored the database, you need to update the connection settings so that SharePoint Team Services can store data in the new database.

To change the database connection to reflect the new database settings

  1. On the server running SharePoint Team Services, click Start, point to Programs, point to Administrative Tools, and then click SharePoint Administrator.
  2. Under Virtual Servers, click Administration next to the virtual server for which you want to modify connection settings.

    Note that if the link says Upgrade or Extend, you need to upgrade or extend the virtual server before going to the Administration page.

  3. Under Administration, click Change database connection.
  4. On the Change Database Connection page, type the database server name, the database name, and the user name and password.

    Be sure to clear the Use local MSDE database server check box.

  5. Click Submit.

The virtual server will now use the specified database.

You can also use the command-line tools (owsadm.exe or owsrmadm.exe) to update the connection. To do so, you use the DatabaseConnection operation. The syntax is as follows: 

owsadm -o databaseconnection [-p <port> -ds <servername> -dn <database 
   name> -du <username> -dp <password> -c changepassword <new password>]

For more information about using the command-line tools, see Command-line Administration.

Migrating sites with Office XP Service Pack 1

Microsoft® Office XP Service Pack 1 (SP 1) includes updates to Microsoft FrontPage® 2002 and SharePoint Team Services that allow you to use FrontPage 2002 to migrate a SharePoint Team Services-based Web site from one Web server running SharePoint Team Services to another.

You must be an administrator on both the source and destination team Web sites to be able to migrate a site. This is because FrontPage 2002 and SharePoint Team Services require a user to have rights to view all content on the source team Web site and rights to create a site on the destination Web server.

The site migration process does not migrate all site settings or customizations automatically; you must recreate or re-establish the following settings after you migrate a site:

  • Security settings, such as user accounts and role memberships
  • Web discussions and subscriptions
  • Custom file orders for lists
  • Document library template settings
  • FrontPage document library rules

To make the transition easier, preserve the old site until you have reapplied any settings or customizations not included in the migration.

Installing Office XP Service Pack 1

Before you can migrate a site, you must do the following:

You do not need to update SharePoint Team Services on the Web server that is currently hosting the source Web site. For more information about installing Office XP SP 1, see the Microsoft Office Tools on the Web site or the Microsoft Office Resource Kit Web site.

Preparing the destination Web server

Before you can migrate your sites, you must prepare the destination virtual server appropriately, depending on the type of site you are migrating.

  • If you are migrating a subweb, you must determine which Web site or subweb on the destination Web server will host the migrated subweb. Also, you must be sure there is not another subweb with the same name at the destination.
  • If you are migrating a Web site to a new Web server, you need to create a new virtual server to host the site.

To create a new virtual server to host a Web site

  • In Internet Services Manager, create a new virtual server on the destination Web server.

    For more information about creating virtual servers, see Creating a New Virtual Server.

  • In SharePoint Team Services, extend the new virtual server with the SharePoint-enabled blank Web site type.

    For more information about extending virtual servers, see Installing SharePoint Team Services.

Publishing the site to the destination Web server

When the destination is ready, you use the updated FrontPage 2002 client to publish the site from the source to the destination Web server. For best results, when you migrate a subweb you should publish to a new subweb. If you publish to an existing SharePoint Team Services subweb that already contains lists, the resulting site may be corrupted or have broken views. For a Web site, you must publish to a new virtual server that has been extended with SharePoint Team Services using the SharePoint-enabled blank Web site type. Whether you are publishing a Web site or a subweb, you can optionally publish any nested subwebs at the same time.

To publish a Web site or subweb

  1. Open FrontPage 2002.
  2. On the File menu, click Open Web and navigate to the source team Web site.
  3. On the File menu, click Publish Web.
  4. In the Publish Destination dialog box, type the location of the destination team Web site (for a subweb) or virtual server you previously extended (for a Web site), and then click OK.

    If you are migrating a subweb and you chose to publish to a subweb that does not already exist, then FrontPage displays a dialog box asking if you want to create a subweb at that location. Click OK to create the new web.

  5. You can optionally choose to publish any nested subwebs by selecting the Include Subwebs check box.
  6. Click Publish.
Note   If the computer running FrontPage 2002 is also running Microsoft Windows 2000 Service Pack 2, you may receive a "time out" error message or a repeated request for a user name and password when migrating a site. To resolve this problem, in Windows, click Start and then click Windows Update. From the Windows Update site, download the latest service pack for Microsoft Internet Explorer.

Search and site migration

SharePoint Team Services uses Microsoft Windows Index Server as the search engine for document libraries. Index Server creates a unique catalog for SharePoint Team Services. When you move sites from one server to another, this catalog may not be created or updated correctly. Without an up-to-date catalog, searches will return no results, even if there are documents that match the search text.

If the search catalog for SharePoint Team Services was not created or was somehow deleted, you will receive the error message "There is no catalog" when you attempt to search. To fix this issue, you must create an Index Server search catalog for SharePoint Team Services. Before you can create the catalog, you must create a folder on your Web server to store the catalog.

To create a folder for the search catalog

  1. On the Web server, right-click the Start button, and then click Explore.
  2. In Windows Explorer, browse to C:\Inetpub, and then create a folder to hold the catalog.

    For example: c:\inetpub\mycatalog

  3. Exit Windows Explorer.

After the folder is ready, you can create the new catalog.

To create a new search catalog

  1. On the Windows desktop, right-click the My Computer icon, and then click Manage.
  2. On the Computer Management console, expand the Services and Applications item.
  3. Right-click Indexing Service, point to New, and then click Catalog.
  4. In the Name box, type OWS_Search_Proxy.

    Be sure to spell the name exactly as it appears above.

  5. Click Browse, select the folder you created in C:\Inetpub, and then click OK.
  6. Click OK to create the catalog.
  7. If you receive a notification indicating that the catalog will remain off-line until the service is restarted, click OK.

Finally, you can associate the new catalog with SharePoint Team Services and turn on the Indexing Service.

To associate the new catalog with SharePoint Team Services

  1. On the Computer Management console, expand the Indexing Service item.
  2. Right-click the OWS_Search_Proxy item you created, and then click Properties.
  3. Click the Tracking tab.
  4. In the WWW Server list, select Microsoft SharePoint Search Proxy, and then click OK.
  5. Right-click the Indexing Service item, and then click Stop.
  6. When the service has stopped, right-click the Indexing Service item, and then click Start.

After the Indexing Service restarts, the service will build the new catalog. After a short time, searches from the home page of the Web site based on SharePoint Team Services will return results.

If you search for content that you know exists in your document library and get no search results or if you receive the message "The template file can not be found in the location specified by 'CiTemplate=' in file Search.idq," then you may need to update the Microsoft Internet Information Services (IIS) instance number for the Web site based on SharePoint Team Services in the Search.idq file.

To determine the correct IIS instance number for your Web site based on SharePoint Team Services

  1. On the Web server running SharePoint Team Services, click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
  2. In the Tree pane, locate the Web site based on SharePoint Team Services where search is not functioning correctly.
  3. Right-click the name of the Web site based on SharePoint Team Services, and then click Properties.
  4. On the Web Site tab, under Active Log Format, click Properties.
  5. On the General Properties tab, at the bottom, note the value for Log file name.

The log file has a name such as W3SVC1\exyymmdd.log. The log file instance number is the number that appears after W3SCVC. For example, the log file name W3SVC1 indicates that the IIS instance number for that Web site is 1.

After you have identified the instance number, you can update the Search.idq file with the correct instance, and then restart your Web server.

To edit the Search.idq file to reference the correct IIS instance number

  1. On the Web server running SharePoint Team Services, click Start, point to Programs, point to Accessories, and then click Windows Explorer.
  2. Make sure that Explorer is set to view hidden directories by doing the following:
    • On the Windows Explorer Tools menu, click Folder Options.
    • Click the View tab.
    • Under Advanced settings, under Hidden files and folders, click Show hidden files and folders, and then click OK.
  3. In Windows Explorer, go to the folder that contains the files for your Web site based on SharePoint Team Services.

    By default the path is: c:\Inetpub\wwwroot

  4. Click the vti_script folder.
  5. Right-click the file search.idq, and then click Open With.
  6. On the list of available programs, click Notepad, and then click OK.
  7. Locate the "CIScope=" setting and change it to the IIS instance number you determined in the previous section.

    For example, if the lIS instance number is 1, change the line to: CIScope=1.

  8. On the File menu, click Save.
  9. Restart the Web server.

EROL  : jeudi avril 14, 2005 15:38:00 +0200

 

[ Retour page Accueil ] [ Remonter ]

Envoyez un courrier électronique à EROL GIRAUDY (attention nospam dans l'E-mail) pour toute question ou remarque concernant ce site Web et visitez la rubrique Condition Utilisation et CNIL. Copyright © 2005 EROL (les sigles et logos ci-après sont la propriété de : Microsoft, Supinfo, Adobe, Compaq, HP, Sybari, Veritas, Moreover, K-map, Vyapin, Plumtree, Ixos, TooStore, K-Map, eRoom, DocKIT,NQL, Only4gurus, Nsius, Sharepointexperts, Iora, Erol, KCura, FrontPages, Nsi, Frontlook, IBuySpyPortal, moreover, slipstick, networknowledge, clubsps.org ) MEGJIC, MEG-JIC
Dernière modification : jeudi, 14. avril 2005 15:02