Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
- From: "Daniel Bugday" <itkonsult@xxxxxxxxx>
- Date: Sun, 4 May 2008 22:57:04 +0200
I wrote an how to on this issue.. works perfect!
http://www.sharepointforum.com/en-US/Wiki/Forms/DispForm.aspx?ID=7
/Daniel Bugday
http://www.sharepointforum.com/
http://www.sharepointforum.com/en-US/Blog/default.aspx
<EF@xxxxxxxxxxxxx> wrote in message news:O1itRgGrIHA.1872@xxxxxxxxxxxxxxxxxxxxxxx
Hi Steven,
I having trying this out on a test environment for the past 2 days and I don't seem to get it work as expected.
My current WSS 2.0 is using scalable hosting mode.
I have only 1 web site (or also known as virtual server) with 1 IP address.
I create all my site collection using createsiteinnewdb.
All site collections have their own url (e.g. sales.domain.com, marketing.domain.com, it.domain.com).
Each site collection has its own content database.
Now I am trying out the content database migration to WSS 3.0.
I setup a new WSS 3.0 farm in VM.
I backup the content databases from the WSS 2.0 SQL Server.
Restore the content databases to the WSS 3.0 SQL Server.
Create a new web application in WSS 3.0 using the servername.domain.com as the URL.
Delete the content database created during the creation of web application.
I run the following to add the content database.
stsadm -o addcontentdb -url http://servername.domain.com -databasename STS_DB1.
Now if I try to add another content database to the same web application, it failed.
Now the site collection in STS_DB1 is suppose to be having the url sales.domain.com. But I can't use that url, instead I have to use servername.domain.com.
I also tried resetting up a new WSS 3.0.
Create a new web application using the servername.domain.com as the URL.
Add new content database.
Create new site collection with host header.
stsadm -o createsite -owneremail myemail@xxxxxxxxxx -url http://sales.domain.com -ownerlogin domain\mylogin -hhurl http://servername.domain.com
Add another new content database.
Create new site collection with host header.
stsadm -o createsite -owneremail myemail@xxxxxxxxxx -url http://marketing.domain.com -ownerlogin domain\mylogin -hhurl http://servername.domain.com
Now this match what I have in my current WSS 2.0. However, this is creating new site collections. How can I migrate the content database and get the same result?
Please help.....
Thanks,
Alex
"Steven Cheng [MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message news:h%23uCYd1qIHA.4284@xxxxxxxxxxxxxxxxxxxxxxxxxThanks for your reply Alex,
Regarding on the further questions you mentioned, I'll do some further
research on it. I'll update you if I can some new information.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Thread-Topic: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
Subject: RE: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
Date: Tue, 29 Apr 2008 22:52:02 -0700
Hi Steven,
Okay, I am now trying out the content db migration. I am trying to follow
the "Upgrading to Windows SharePoint Services 3.0 technology" document.
The
chapter I am looking at is "Deploy a new farm, then migrate databases".
There are a few things that I am not sure of as it is not mention in the
document.
1) After installing a new WSS 3.0 farm do I need to first create a new web
application prior to adding the content db? I am asking because the
command
"stsadm -o addcontentdb" needs a web application URL.
2) If creating a web application is required before adding the content db,
what should be the database name for the web application?
3) In WSS 2.0, I have 1 content db to 1 site collection and thus 1 unique
URL each. When I use the addcontentdb, how does it knows what is the URL
since I am only providing the web application URL?
4) It says when adding the content db, make sure the root site for the web
application is included in the first content db you add? What does this
means?
Thanks,
Alex
"Steven Cheng [MSFT]" wrote:
Hi Alex,http://blogs.technet.com/wbaer/archive/2007/03/31/upgrading-windows-sharepoi
As for WSS 2.0 scalable hosting upgrade, based on my research, seems most
one will recommend content db based migration on a new WSS 3.0 web
application. Here are two blog entries from some SPS engineers:
#Upgrading Windows SharePoint Services 2.0 Scalable Hosting Mode Server
Farms
nt-services-2-0-scalable-hosting-mode-server-farms.aspxhttp://blogs.msdn.com/joelo/archive/2007/05/30/wss-2-0-to-wss-3-0-farm-host-
#WSS 2.0 to WSS 3.0 Farm Host Header Upgrade FYI
header-upgrade-fyi.aspxPlease
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you.feel free to let my manager know what you think of the level of servicehttp://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
ications.issues
Note: The MSDN Managed Newsgroup support offering is for non-urgentwhere an initial response from the community or a Microsoft Supportfollow
Engineer within 1 business day is acceptable. Please note that each
up response may take approximately 2 business days as the supportrights.
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no3.0?
--------------------
Thread-Topic: Upgrading Windows SharePoint Services 2.0 scalable hosting
mode
thread-index: AciqERuv5/OXhhPORjqNE372boi/GQ==
X-WBNR-Posting-Host: 207.46.19.168
From: =?Utf-8?B?QWxleA==?= <EF@xxxxxxxxxxxxx>
Subject: Upgrading Windows SharePoint Services 2.0 scalable hosting mode
Date: Tue, 29 Apr 2008 08:53:03 -0700
Hi,
What is the best option to upgrade WSS 2.0 scalable hosting mode to WSSto
In the upgrade document from MS, I can only either perform In-Place or
Content DB migration. For the content db migration, if I understand
correctly which is actually like a manual in-place upgrade since I have
complete the migrating of all content databases before I can startcreatingnew sites.
Is there a better way of doing this?
Thanks,
Alex
.
- Follow-Ups:
- References:
- RE: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
- From: Steven Cheng [MSFT]
- Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
- From: EF
- RE: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
- Prev by Date: Re: Where can I find the best industry practices for deploying in a virtual environment?
- Next by Date: Editing a view
- Previous by thread: Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
- Next by thread: Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
- Index(es):
Relevant Pages
|
