Migration of SharePoint from SBS2003 to SharePoint 3.0 on Full Windows Domain
-
Monday, May 23, 2011 12:51 PM
Hello All,
I am looking for some advice on how to migrate a Sharepoint web site from an SBS 2003 environment to a SharePoint 3.0 environment in a seperate Windows domain. This is due to a company merger and the SBS domain will be switched off soon. I should say that I'm not a SharePoint expert by any stretch of the imagination!
I have tried backing up the companyweb site using the Sharepoint Portal Backup & Restore application, which has output some SPD files. I can't find a way of restoring those files into Sharepoint 3.
I've also tried using stsadm.exe to backup the site, but this only creates a 600KB file, which I can't see being anywhere near enough, especially as the backups from the above method are approx 500MB in all.
Does anyone have a guide for how to do this? Is it even possible?
Many thanks
All Replies
-
Wednesday, May 25, 2011 2:26 AMModerator
Hi, you'll need to get SharePoint 3.0 runnning on the new server (for example, Windows Server 2008 R2), then you have a few migration options:
- stsadm -o export/import
- Database detach/attach
- Office migrationYou will have to convert the SharePoint 2.0 databases to SharePoint 3.0 before you can use ststadm -o export/import. (Small Business Server 2003: How to Install Windows SharePoint Services 3.0 on SBS 2003 http://msmvps.com/blogs/bradley/archive/2007/12/12/small-business-server-2003-how-to-install-windows-sharepoint-services-3-0-on-sbs-2003.aspx) The easiest way to achieve that is via the database detach/attach method which does an upgrade during the attachment phase. Once in SharePoint 3.0, you could then use the export/import option to merge SharePoint 3.0 sites (which is recommended when you are going for an SBS 2008 migration).
However if you are going onto a clean non SBS site, you can just do a database deatch/attach on the new server and be done with it.Also you can't simply backup and restore SharePoint 2.0 sites to SharePoint 3.0 sites they need to be converted, so again the database detach/attach is the best option.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked As Answer by Sean Zhu -Moderator Friday, May 27, 2011 2:18 AM
-
Thursday, June 23, 2011 8:29 PM
Hi there,
I have the same situation but I'm not sure what you mean by Database detach/attach. I am going from SBS 2003 Sharepoint V2.0 to Windows 2008 Server Std R2. What commands would i need to enter on the SBS server and which ones on the new 200 R2?
Thanks
Craig
-
Tuesday, June 28, 2011 1:11 PM
Craig,
Have a look at my series of posts on migration for help:
Thanks
Robert Crane
www.ciaops.com
-
Friday, July 15, 2011 12:39 PM
Hello Robert,
I've followed most of your steps, but I get the following error message when running
stsadm –o addcontentdb –url http://<new WSS v3 site> -databaseserver <SQL_SERVER_NAME> -databasename <Old Sharepoint v2 database>
"The specified SPContentDatabase Name=STS_<ServerName>_1 Parent=SPDatabaseServiceInsta
nce Name=SQLEXPRESS is too old to be upgraded by this version of SharePoint. Ple
ase perform the needed intermediate upgrades before attempting this one."There are slight differences in our environment compasred to yours;
1) I'm not migrating to SharePoint 2010, it's SharePoint Services 3.0
2) I am migrating this SBS Sharepoint environment to an existing SharePoint server that has other sites on it, so I haven't run the stsadm -o deletecontentdb, as I don't want to mess up the existing sites on the destination server.
The Prescan tool completed successfully in the early stages of this migration.
Have you any ideas what's going wrong?
I wonder if this isn't the correct process as I am trying to make the old Companyweb site a sud-site of the destination server.
Any help would be appreciated
Thanks
Richard

