Upgrade to Windows Sharepoint Service 3.0
My assignment for this project was to perform an upgrade from Windows SharePoint
Services (WSS) 2.0 to WSS 3.0. Our SharePoint site was hosted on a server we'll
call DesiredServer but the SharePoint databases were on a server we'll call OldSqlServer.
Also OldSqlServer was running SQL Server 2000. My tasks were as followed:
Upgrade WSS 2.0 to WSS 3.0.
Disconnect WSS 3.0 from databases on OldSqlServer and connect to databases DesiredServer
running SQL Server 2005.
This was simple until I did the upgrade. After downloading WSS 3.0, I successfully
performed the upgrade. Fortunately, there were no custom templates or web parts
to hamper the process. However, all the pretty site colors and schemes that users
set up were gone and set to the default. Unfortunately, I waited until we were running
WSS 3.0 to connect to the databases on DesiredServer. This was a task that was handled
within WSS 2.0's Central Administration site. I incorrectly assumed it would be
as simple using WSS 3.0's Central Administration. I quickly found out that you can
add and point to other content databases within WSS 3.0's Central Administration
site but you cannot switch configuration databases.
The Problem:
WSS 3.0 still was connected to the databases on OldSqlServer.
What I tried:
I backed up the databases on OldSqlServer and restored the .BAK files on DesiredServer.
Then, within WSS 3.0's Configuration Wizard, I disconnected from OldSqlServer. Next,
I connected to DesiredServer. Looked like a success, until I opened the Central
Administration site. The Central Administration site was still connected to OldSqlServer.
Why? Because the WSS 3.0 the Central Administration is a site all own its own. Therefore,
its configuration was never switched to the DesiredServer. This was a failed attempt
so I had to reconnect to OldSqlServer.
The Solution:
I had to perform a backup and restore within the Central Admin site. The directions
seem a bit confusing but I'm hoping to make sure no steps are skipped.
Create a folder to hold the .BAK files. Add read/write/modify sharing and security
permissions for 3 domain users (myself, the SharePoint databases dbo, and, most
importantly, the SQL Server Network account). Why? Because although you'll be doing
a backup and restore within Central Admin, Central Admin just tells the SQL Server
to do it. But it isn't the same as you doing it within SQL Server. Trust me. Also,
it doesn't matter who you're logged in as. The SQL Server Network Account will be
running the processes so it must have those permissions.
Open WSS 3.0 Central Administration.
Click the 'Application Management' tab. Then, under 'SharePoint Web Application
Management' sections, click 'Web application list.'
Document the existing web applications.
Perform a full backup for the entire farm:
Click the 'Operations' tab. Under the 'Backup and Restore' section, click 'Perform
a backup.'
Select the entire farm and click 'Continue to Backup Options.'
Select 'Full' as the backup type. Use the Universal Naming Convention (UNC) to enter
the location of the folder you created (i.e. \\server\sharedFolderYouCreated). Click
OK to continue.
Wait until the backup is performed successfully. I ran across a couple errors that
will be avoided by adding the sharing and security permissions and using the UNC.
Disconnect from the current farm:
Open the SharePoint Products and Technologies Configuration Wizard. Click Next to
continue.
In page Modify server farm settings, select Disconnect from this server farm and
click Next. In the dialog box that appears, click Yes to continue.
Click Finish in page Configuration Successful.
Connect to DesiredServer and create new farm:
Open the SharePoint Products and Technologies Configuration Wizard.
In page Connect to a server farm, CLICK 'No, I want to create a new server farm.'
Then click Next.
Type the server name (DesiredServer) and configuration database name. Specify the
required account for WSS. This is the dbo account that should have been given the
sharing and permissions. The account will should have securityadmin and dbcreator
rights on the DesiredServer.
Select the authentication method. Click Next.
Click Finish, in page Configuration Successful.
Create web applications for the documented web applications: (I'm not sure if these
steps are necessary but a Microsoft Tech told me to do it, so I did it.)
Open Central Administration and click 'Application Management' tab.
In 'SharePoint Web Application Management' section click 'Create or extend web application.'
Click 'Create a new web application.'
Specify the setting for the documented web applications but DO NOT CREATE TOP-LEVEL
SITES FOR THE WEB APPLICATIONS.
Add the same sharing and security permissions to the folder that the databases will
be restored to.
Restore the backup:
Open Central Admin. Click 'Operations' tab.
In section Backup and Restore, click restore from backup.
Enter the backup files' location using the UNC. Click OK to continue.
Select the backup and click 'Continue Restore Process.'
Select entire farm and click 'Continue Restore Process.'
Enter new configuration for the restore, the new database server (DesiredServer),
and new database names.
Wait until the backup performed successfully.
Cleanup:
Delete the web applications you created.
Delete the content databases that Central Admin created.
This upgrade process was an interesting project even though I made the mistake of
not switching database server locations within WSS 2.0 Central Administration. I
hope this helps all others who made the same mistake. A word of caution though...after
this upgrade, you will probably become the 'SharePoint Guy/Lady.'