Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Upgrade to WSS3.0 Host Header Based Site from WSS2.0 - HELP!

10 views
Skip to first unread message

AJ

unread,
Jun 29, 2009, 3:48:26 PM6/29/09
to
Hi Folks

I want to be able to restore the content DB from a WSS2.0 site/server
to a WSS3.0 farm. We have a single web application in the WSS3.0
environment that hosts many host header based sites. The host header
based sites currently utilise only one content DB as the DB size is
relatively small.

After I have restored the WSS2.0 site to my WSS3.0 SQL 2005 server how
do I go about creating a new host header based site that will use the
restored content DB?

I can easily create a new WSS3.0 host header based site using STSADM
which uses its own contentdb by using the createinnewdb switch and I
can later remove this content database. I was hoping I could remove
the content DB from the site and then simply attach the restored
database to the new host header based site by using the addcontentdb
switch. It would appear however as soon as I remove the content
database the new host header based site created is also deleted.

Does anyone have any wise words for me?

I have googled this to death but nothing seems to address host header
based sites.

TIA AJ

AJ

unread,
Jul 1, 2009, 1:29:28 PM7/1/09
to

Where are the MS people on this forum, dont they participate?
looks like im going to have to spend money on this one :(

spconsultant

unread,
Jul 6, 2009, 9:22:36 AM7/6/09
to
For the most part, these forums are supported by interested community
members helping each other out, but people tend to be pretty
responsive.

You need to intall and run the pre-update scan tool (Prescan) on your
wss 2.0 server. this will add some stuff to the database making it
suitable
to move, and alert you to any barriers to migration. Once that is
done,
you can restore your database to your 3.0 system, and attach it to a
web
application, At that time, the system will recognize the need to
upgrade
and it will start an upgrade.

Google for Migration/upgrade strategies. This is approach is the
datbase
upgrade approach.

> looks like im going to have to spend money on this one :(- Hide quoted text -
>
> - Show quoted text -

AJ

unread,
Jul 6, 2009, 10:11:17 AM7/6/09
to
> > - Show quoted text -- Hide quoted text -

>
> - Show quoted text -

Hi

Thanks for your response.

I figured out these steps from googling previously. What I am having a
hard time grasping is how I get the WSS2.0 site into the web
application that is hosting our host header based sites. I can easily
create another website and attach the restored WSS2.0 to it but that
would result in having two web applications on my front end server one
hosting the current host header based sites and the other hosting the
migrated WSS2.0 site. I want the migrated WSS2.0 site to go into my
exisintg web application. Do you happen to have the stpes/commands
needed to do this?
We use the STSADM command to create the host header based sites and
they all currently exist in one content DB.

Thanks!

AJ

0 new messages