Migrate content databases - moving from WSS2 to WSS3 on different WEB/SQL Servers

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

So I'm trying to Migrate from WSS2 to WSS3 on to a new Web and SQL Servers.

We currently have two independant WSS 2.0 Servers that are both storing Data
on a 3rd SQL 2005 Server. All machines are updated with the latest Software Updates.

I want to Move the Web Applications from the two WSS 2.0 servers to a single
new WSS 3.0 Server with Farm Potential.
I want to move the Content DBs from SQL 2005 Server A to SQL 2005 Server B
(WSS 2.0 Data to WSS 3.0 Data)

Topology of the new WSS environment is 1 Front End Webserver with potential for more, one Backend SQL Server.

So I'm trying to do this part of the Upgrade:
http://technet2.microsoft.com/windowsserver/WSS/en/library/700c3d60-f394-4ca9-a6d8-ab597fc3c31b1033.mspx?mfr=true

I'm following along in from this Word Document, which seems to be the same
content as the above link but more stuff.
"Upgrading to Windows SharePoint Services 3.0 technology"

So for the Migrate Content DBs. It has 3 steps:
Prepare the new Windows SharePoint Services 3.0 environment
Migrate content databases
Migrate content databases from WMSDE to Windows Internal Database

So in the prepare the new environment, there is no mention on how to get the
Web Applictions from the ols WSS2.0 server to the new WSS 3.0 Server.

Do I just create a Web App and give it a name for the DB, then in the
Migrate DB Process give it the same name, or have it as a Second DB to the
one that was created with the Web App?
Is there anyway to Copy more then one WebApp from the old server to the new
server. We have Several Sharepoint Sites it would be a pain to have to
create all 30+ of them over again. Anyway to Export the info to an XML
file, edit the Paths, etc then import it into IIS?

Is there a way to just create a Import File or create the Web apps via the
command line by hand, so I dont have to go through the Wizard each time?

The Step where it talks about adding Content DB to the Web Application seems to assume that the Root content DB is already there. All of my WSS sites are jsut single level Sites with only the Root Content.

Was thinking to just Detach from the WSS2 Server and Re-Attach to the new WSS3 server with the same name as the one that it created in the Web App Creation. then Running STSADM Upgrade on it.


Thanks
Scott<-

.

Relevant Pages

  • Re: Unable to do full text search
    ... I would suggest that rather than posting to the WSS newsgroup or the SQL ... Server newsgroup, you should have posted this to the SBS newsgroup as you ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Front End WSS3.0 Server
    ... WSS only listens to addresses for web applications that are in AAM. ... Another use for zones for a web application is when you extend a web app. ... When you add a second WFE to a server farm, WSS assumes that it will be ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS 3.0 TR and SQL 2005 - Could not load file or assembly Microsoft.SharePoint.ApplicationPa
    ... if you are only installing on one server. ... Also you should have already installed SQL Server 2005 on that server before ... WSS FAQ: www.wssv3faq.com / wss.collutions.com ... I tried to install WSS3.0 but it does not show any option to choose SQL ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Cannot restore to a new server (wss3 stsadm)
    ... The one you give seems to be for WSS 2.0. ... This process is not intended for moving a site to a new server. ... disaster recovery procedure for a new WSS 3.0/ SQL 2005 Express ... That text makes me believe that you need the configuration database to ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: WSS v3: Change DB server?
    ... Rather you need to re-configure WSS 3.0. ... You need to find the releveant content DB and attach to the server. ... Do I need to attach them all together into the new SQL server? ...
    (microsoft.public.sharepoint.windowsservices)