Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Upgrading from v2.0 to v3.0

  Asked By: Johnpaul    Date: Jun 13    Category: Sharepoint    Views: 1298

We're in the initial phase of moving our sharepoint application from server A to
server B. I've read many different "How To" publications, all with various
approaches. Could someone shed a little knowledge on a simple and correct
approach based on lesson learned?

Our source sharepoint 2.0 system has a web from-end on server A with a SQL200
back-end on a separate server. The target system will basically be the same
structure, except that our back-end database server will be SQL2005. It's my
understanding that we must upgrade to SP2 and then the to v3.0 on the source
server A prior to migrating to server B. Documentation indicates both servers
must have the EXCAT same sharepoint software versions installed, prior to
migration/moving. Both environments are running Windows Server 2000 SE as their
operating system.

Proposed Path:
Server A (source v2.0)
Run fidelity Backups (stsadm)
Upgrade In-place from v2.0 to SP2
Run fidelity Backups (stsadm)
Test
Upgrade In-place from v2.0 SP2 to v3.0
Test
Run fidelity Backups (stsadm)

Server B (target v3.0)
Download and install v3.0
Create empty site
Restore sites from Backups
Test

Issues:
Should stsadm be used for fidelity backups (security, permissions, etc) and SQL
tools to backup/restore the databases?
Target server B must have a different service account that source server A.
Are the web parts included in the backups using stsadm?

Am I on the correct upgrade path or am I missing something that can cause the
upgrade to fail? Any assistance and/or direction would greatly be appreciated?

Share: 

 

2 Answers Found

 
Answer #1    Answered By: Jaya Deoghar     Answered On: Jun 13

It sounds to me like that would be a supported upgrade.

However, this is not the way I planned on doing ours, so now I'm
wondering if there is something wrong with my plan. We basically
have the same scenario, but we planned on doing the following:

1. Run prescan.exe on WSSv2 web  front-end
2. Move WSSv2 databases to new DB server
3. Create WSSv3 web applications
4. Attach WSSv2 databases to WSSv3 web applications

I've done this before with production databases in a dev environment
and it worked fine. However, I'm still wondering if there are
caveats to this method.

 
Answer #2    Answered By: Candi Branch     Answered On: Jun 13

We are moving  forward with our migration to MOSS 2007. I just ran the
prescan tool against a copy of our production data and it came back with
tons of stuff. One of the things that I am particularly concerned with
are the sites that were created using Project server. These sites have
been flagged by the prescan tool. Has anyone encountered this before?
How did you handle it?

 
Didn't find what you were looking for? Find more on Upgrading from v2.0 to v3.0 Or get search suggestion and latest updates.




Tagged: