16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 42: Upgrading <strong>and</strong> Migrating to SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> 1107<br />

three hours to back up. The same site can take up to three hours to restore because<br />

so many files must be uploaded to the new server. The more files included on a site,<br />

the longer the restore process will take. It might therefore be advisable with large<br />

websites to back up each individual subsite. You would then back up the remaining<br />

sites. The SharePoint Migration Tool includes a parameter (-e) to exclude subsites;<br />

therefore, to back up the remaining sites you could specify the virtual server<br />

<strong>and</strong> exclude the large websites, which you backed up individually. As a general performance<br />

guideline, you will have the best backup/restore performance when using<br />

separate computers for each task. An example of such a configuration is:<br />

■ One computer running the SharePoint Migration Tool (Smigrate.exe)<br />

■ One or more computers running as front-end Web servers<br />

■ One or more computers running as SQL Server back-end servers<br />

There are two stages in upgrading from SharePoint Team Services or FrontPage<br />

2002 Server Extensions to <strong>Microsoft</strong> Windows SharePoint Services:<br />

■ First you back up your existing websites using the <strong>Microsoft</strong> SharePoint Migration<br />

Tool. Then if you want to upgrade the server from SharePoint Team Services<br />

to Windows SharePoint Services, remove SharePoint Team Services or FrontPage<br />

2002 Server Extensions from the virtual servers. During the backup process, you<br />

specify the URL for the website <strong>and</strong> the backup file to create. You can also specify<br />

the scope of the site migration (whether to migrate just the top-level website,<br />

or whether to migrate the top-level website <strong>and</strong> any subsites).<br />

■ Second you install Windows SharePoint Services on your server computer or to<br />

a new server <strong>and</strong> restore your websites to new locations on the existing server<br />

or to the same locations on a new server. During the restore process, you specify<br />

the new URL <strong>and</strong> the backup file from which to restore.<br />

Step 1: Backing Up the SharePoint Team Services Websites<br />

Use the SharePoint Migration Tool to back up the SharePoint Team Services websites<br />

into a single file or multiple files. See the discussion earlier in this chapter concerning<br />

backing up <strong>and</strong> restoring large websites. Complete the backup procedure, also<br />

known as the export procedure, as follows:<br />

1. Verify that your SharePoint Team Services installation is at <strong>Microsoft</strong> Office XP Service<br />

Pack 2 (SP2) or later. If the administrator runs the owsadm.exe -o upgrade comm<strong>and</strong><br />

after installing the service packs, the virtual server <strong>and</strong> the _vti_inf.html file<br />

version numbers will be updated. You can view these by using the <strong>Microsoft</strong><br />

SharePoint Administrator; the version number of the extended virtual servers will<br />

be 5.0.2.4330 if SP 2 is installed, or display http://virtualserver/_vti_inf.html in a<br />

browser. Right-click the page, <strong>and</strong> then click View <strong>and</strong> look for the keyword

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!