Your SlideShare is downloading. ×
Download It.doc.doc
Download It.doc.doc
Download It.doc.doc
Download It.doc.doc
Download It.doc.doc
Download It.doc.doc
Download It.doc.doc
Download It.doc.doc
Download It.doc.doc
Download It.doc.doc
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Download It.doc.doc

207

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
207
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Migrating Web Sites Based on SharePoint™ Team Services White Paper Published: February 2001
  • 2. Table of Contents Introduction...........................................................................................................3 Procedural Overview...............................................................................................3 Migration Steps...................................................................................................3 Assumptions.......................................................................................................3 Migrating SharePoint Team Services..........................................................................4 Preparing the destination server............................................................................4 Installing SharePoint Team Services and SQL Server.....................................................................4 Removing unneeded Web site files...................................................................................................4 Migrating the site................................................................................................4 Migrating Web data...........................................................................................................................5 Migrating data stored in the Microsoft SQL Server databases.........................................................6 Upgrading the site...............................................................................................7 Using the new site...............................................................................................7 Moving to SQL Server from MSDE.............................................................................8 Conclusion.............................................................................................................8
  • 3. Migrating SharePoint Team Services White Paper Published: February 2001 Introduction Despite the best planning, there will come a time when one or multiple virtual servers running SharePoint™ Team Services will need to be moved from one server to another. This migration, if executed correctly, can be hassle free for the server administrator. The following paper gives step by step instruction on migrating a SharePoint Team Services site from one server to another. Procedural Overview Migration Steps Migrating SharePoint Team Services consists of three basic steps: • Preparing the destination server • Migrating data • Upgrading the site to rebuild virtual directories When the migration is complete, all permission settings will be removed. Server administrators will need to add back any custom permissions such as “no anonymous browsing” or unique subweb permissions. Additionally, users will need to be added back to migrated sites. Assumptions The basic scenario described here is the migration of a server running Microsoft SQL Server and SharePoint Team Services to another server running SQL Server and SharePoint Team Services. Thus, the instructions assume the following: 1. There are two Web servers – the originating server where the site to be migrated resides and the destination server. 2. SQL Server 7.0 or SQL Server 2000 is being used to back up the originating database and restore the database to the destination server. 3. The same versions of SharePoint are running on both the originating and destination servers. If not, you should upgrade the originating server before attempting to migrate it. Any other migration scenarios will require some or all of these steps. For migrations from SharePoint Team Services servers running the Microsoft® Data
  • 4. Engine, a complete migration is not necessary. The “Moving to SQL Server from MSDE” section below describes the steps to accomplish this. Migrating SharePoint Team Services Preparing the destination server As with most backup and restore operations, you need to prepare the destination server by installing SharePoint Team Services and SQL Server 7.0 or SQL Server 2000. You will also need to remove certain files so that the migrated files can take their place. Installing SharePoint Team Services and SQL Server 1. On the destination Windows® 2000 Web server running Internet Information Services 5.0, install SQL Server 7.0 or SQL Server 2000 and Microsoft SharePoint Team Services. For more information about installing SharePoint Team Services, see the Departmental Deployment of Microsoft SharePoint Team Services white paper. 2. Using the SharePoint Administration pages, extend the default Web site with SharePoint. On the Extend Virtual Server page, choose SharePoint-Based Web site as the Site Type. 3. After extending the destination site as a SharePoint-Based Web Site, stop the Web server services on the destination server. To do so, from a DOS command prompt, type NET STOP IISADMIN /Y. Removing unneeded Web site files Once the Web server is stopped, you need to delete all of the template files that SharePoint added to the destination Web site. Since you are moving the origination site to the destination server, you need a clean place to which to move the site. 1. Open Windows Explorer and navigate to the destination Web sites content directory, typically c:inetpubwwwroot for the Default Web Site. 2. To delete all files in this directory, you must reveal hidden files and folders. To do so: a. On the File menu select Tools, Folder Options. b. On the Folder Options popup box, choose the View tab and check the Show hidden files and folders radio button. If the error message ‘Cannot delete alllibs.htm’ appears, this indicates that that IISAdmin services have not been stopped. c. Click OK. 2. At this point, you can select all files in the directory and press DELETE. (To permanently delete all files without first sending them to the Recycle Bin, press SHIFT+DELETE.) Migrating the site With the destination server prepared, the actual migration of data can begin. Remember that there are two types of data that need to be migrated: Migration of Web Sites Based on SharePoint Team Services 4
  • 5. • Web/File services data • Database data Migrating Web data 1. On the destination Web server, establish a share connection to the origination server’s drive where the origination Web site exists. For example: serverc$inetpubwwwroot. 2. On the destination Web server, copy the entire contents of the origination server’s Web site files to the destination Web server’s content directory. For example, you will copy the contents of serverc$inetpubwwwroot to the destination server’s c:inetpubwwwroot if c:inetpubwwwroot is the content directory on the destination server. 3. This step is a bit tedious and is required if your origination SharePoint site has subweb sites. On the destination Web server establish a share connection to the origination server’s System drive and navigate to the following location: serverc$Documents and SettingsAll UsersApplication DataMicrosoftWeb Server Extensions50W3SVC1. Since the example migration is for the Default Web Site, we are in the w3svc1 folder. If your origination Web site is on a different virtual server than the default Web site then you will need to navigate to the 50 directory and pick the appropriate w3svc directory. In the w3svc1 folder, you will see roles files for the root Web and for all subwebs. Copy all roles files from this directory to the destination server’s w3svc1 directory at serverc$Documents and SettingsAll UsersApplication DataMicrosoftWeb Server Extensions50W3SVC1. You will have to replace the destination server’s roles.ini file. In the roles.ini file find the [ROLES] section and remove any users or groups for any of the roles. For example: [ROLES] browser=08008800| DomainUsername, ows_123456_browser | View pages and documents. becomes: browser=08008800| |View pages and documents. Next, in the roles.ini file find the [USERS] section and remove any users. For example: [Users] DomainUsername=admin|FFFFFF03 becomes: [Users] Note: You will later need to add back any custom permissions that existed on the origination server. This is done using the SharePoint Site Setting for the root Web and all subwebs that had unique permissions. Migration of Web Sites Based on SharePoint Team Services 5
  • 6. Migrating data stored in the Microsoft SQL Server databases Now, you need to migrate the SQL Server data. This task consists of three basic steps: • Backing up the originating server’s database • Restoring that database to the destination server • Assigning the database to the destination server’s Web Backing up the originating database 1. On the originating server, open SQL Enterprise Manager and establish a connection to the origination site’s SQL server. 2. Locate the origination site’s database. For example, servername_LM_W3SVC_1_COLLAB. 3. Back up this database and, on the SQL Server Backup dialog, choose Overwrite existing media. 4. The backup creates a file servername_LM_W3SVC_1_COLLAB_backup in the MSSQLBackup directory on the origination server. Restoring the database to the destination server 1. On the destination server, establish a share to the origination server’s MSSQLBackup directory and copy the backed-up database (servername_LM_W3SVC_1_COLLAB_backup) to the destination server’s MSSQLBackup directory. 2. On the destination server, start SQL Enterprise Manager and restore the database: a. Right click Databases, All Tasks, Restore Database. b. For the database name in the Restore as Database field, enter the name you want the database to be called. c. Select From Device and point to the backed-up database. Assigning the database After the database is restored you will need to assign this database to the destination Web site with Regedit. 1. Open Regedit by clicking Start, Run, typing REGEGIT, and clicking OK. 2. Navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared Tools Web Server ExtensionsSecure. 3. Under the Secure key is a listing of all IIS virtual servers to which SharePoint is installed. For the purpose of this example we will use /LM/ W3SVC/1, which maps to the Default Web Site. Click on this key. Once you have clicked on the key /LM/W3SVC/1, you will see string values in the right pane. Double click on the string value DSN. You will need to change the Database value to be the name of the database you restored in step 13. For example: Provider=sqloledb;Server=sharepointbeta;Database=sharepointb eta_LM_W3SVC_1_Collab Migration of Web Sites Based on SharePoint Team Services 6
  • 7. becomes Provider=sqloledb;Server=sharepointbeta;Database=newdatabas ename 2. Once you have changed the registry key you can now restart the Web server by typing NET START W3SVC from a DOS command prompt. Upgrading the site The final task to the migration is to run an upgrade on the site. The upgrade regenerates the _vti_bin virtual directories for each subweb. To run the upgrade, use the SharePoint command line administration tool owsadm.exe. 1. Open a DOS command prompt and change directory to program filescommon filesmicrosoft sharedWeb server extensions50bin. 2. At the bin directory run the following command: Owsadm.exe –o upgrade –p /lm/w3svc/1 If you used a different virtual server than the Default Web Site, then you will need to find the IIS instance for the Web site to upgrade it. The IIS instance for the Default Web Site is /lm/w3svc/l. a. To determine the IIS instance for a different virtual server, navigate to Start, Programs, Administrative Tools, Office Web Server Administrator. b. Under the heading Virtual Servers, hover your mouse over the Administration link for the Virtual Server that you migrated the origination site to. When you hover over the Administration link, the IE display bar at the bottom of the browser reveals IIS instance of the site. The display will show the following for the Default Web site: http://servername:7325/fpadmdll.dll? page=vadmin.htm&port=/LM/W3SVC/1:&frport=Default+Web+ Site. Assuming that you find that the IIS instance is /LM/W3SVC/ 3, then to upgrade the site you would run: Owsadm.exe –o upgrade –p /lm/w3svc/3 Now that the site has been migrated and the Web server services have been started, you can browse the site using the IP address or NetBIOS name of the server. Since all permissions settings were removed, you should use the Site Settings to add back users that need author or admin permission to the site. The best way to get a listing of the users who need to be added back is to make a copy of the User List for the Site being migrated, as well as for any subwebs within that site. Both the full user name, indicating a domain or virtual server account, and the role appear on this page. The files relating to the migrated site can now be removed from the originating server. Using the new site For users in a Windows 2000 domain environment, the migration will be completely seamless since their password information is kept when they are added back to the newly migrated site. Migration of Web Sites Based on SharePoint Team Services 7
  • 8. Users who have only local server accounts will lose their passwords because they cannot be migrated. There are two methods of getting users back up and running. First, administrator can create generic passwords for users, inform them of their new passwords and require them to change them. A better method is to re-invite users to the site. This will generate new passwords automatically, which the users can then change. Moving to SQL Server from MSDE Many administrators will have SharePoint Team Services environments that use the Microsoft Data Engine (MSDE). For a variety of reasons, an administrator may want to change from using the MSDE to utilizing a newly acquired SQL Server. Let us assume that an administrator wants to leave the virtual server on the same server, but move the database(s) to the SQL server. She can back up her sites, copy the files to the box running SQL server, and, using the Enterprise Manger console of SQL Server, restore the database. (See “Migrating SharePoint Team Services” above for information on how to back up and restore databases.) For each SharePoint site, she can change the database connection to reflect the new database settings. To do so: 1. Open the Administration Pages by clicking Start, Programs, Administrative Tools, Microsoft SharePoint Administrator. 2. Under Virtual Servers, for the virtual server for which you wish to modify connection settings click Administration (if the link says “Upgrade” or “Extend,” you need to upgrade or extend your virtual server before going to the Administration page. 3. Under Administration, click Change database connection. 4. On the Change database connection page, enter the database server name, the database name, and the username and password. Be sure to uncheck Use local MSDE database server. 5. Click Submit. This virtual server will now use the specified database. The server administrator can use one of the command-line tools (owsadm.exe or owsrmadm.exe) to effect the same change using 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 on command-line operations and usage, see the SharePoint Team Services Administrator’s Guide. This can also be accomplished in the same manner if SQL Server is running locally and the Server Administrator decides to run a dedicated Web server and a dedicated SQL server. Conclusion While site migration is a relatively rare procedure, the ability to migrate SharePoint Team Services sites without loss of data is an important one. It Migration of Web Sites Based on SharePoint Team Services 8
  • 9. provides flexibility in terms of initial implementation: administrators don’t need to overbuild their infrastructure to account for potential growth but rather can respond to that growth when needed. It also means that administrators can change their minds about where they want their databases without affecting users.     The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Migration of Web Sites Based on SharePoint Team Services 9
  • 10. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2001 Microsoft Corporation. All rights reserved. Microsoft, Windows, and SharePoint are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. Other company and product names mentioned herein may be the trademarks of their respective owners. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Migration of Web Sites Based on SharePoint Team Services 10

×