Solved

HELP!!!  Still testing the migration process from WSS 3.0 to SharePoint Foundation 2010.

Posted on 2012-03-16
15
698 Views
Last Modified: 2012-08-14
Hi, I am not sure if this is a problem, but here is the scenario.

I am migrating from WSS 3.0 (default install, meaning it is using SQL 2005 EE locally) on Server 2003 R2 x32 to SharePoint Foundation 2010 x64 on Server 2008 R2 with remote database SQL Server 2005 x64.

Server1: Server 2003 R2 x32 Standard Edition / WSS 3.0 default install (database content name is "WSS_Content.mdf")

Server2: Server 2008 R2 Standard Edition / SPF 2010 x64 / database content name is "SharePointFoundation2010.mdf" & resides on a remote server running Server 2008 R2 & SQL Server 2005 x64 SP4.


My question/concern is when I perform a back up of the WSS_Content (WSS 3.0) database and move it over to the new server running SQL 2005 x64 SP4 and attach it, will it need to the same name as the current database that I named during the SPF2010 Farm installation setup (SharePointFoundation2010.mdf)?  Or will I be able to restore the WSS_Content to this already existing mdf file somehow?  If I can restore it then what is the process of doing so?

If not, would I just be better off, uninstalling SharePointFoundation2010 and reinstalling it and using the default configuration name (SharePoint_Config) like the old WSS 3.0 has for it's?

Or maybe a better way to describe my concern is under SPF 2010 Web Applications section, the following:

- SharePoint - 80
- SharePoint Central Administration v4

Well, the SharePoint - 80 usually points to the "SharePoint_Config", but the Server2 configuration I installed was customized, I guess, because the SharePoint - 80 is pointing to the "SharePointFoundation2010" instead of the default "SharePoint_Config".  Will this be a problem with my migration of the database content (WSS_Content.mdf)?


Hopefully I am making sense, because I am not sure if I understand it myself.  LOL


Thanks in advance.
0
Comment
Question by:rsnellman
  • 9
  • 6
15 Comments
 

Author Comment

by:rsnellman
Comment Utility
What I was referring to earlier in SharePoint Foundation 2010 is to find Central Administration / Web Application / Servers in Farm...

Configuration database name:  "SharePoint_Config"   is the default name, but I customized it during setup and called it "SharePointFoundation2010".
0
 
LVL 38

Assisted Solution

by:Justin Smith
Justin Smith earned 500 total points
Comment Utility
no the databases don't have to be the same name.
0
 

Author Comment

by:rsnellman
Comment Utility
OK, so how do I proceed in connecting the database (WSS_Content) from the WSS 3.0 server to the new server running SQL Server 2005 SP4 with SharePoint Foundation 2010?

Would I perform a restore from SQL Server 2005 SP4 on the new server overwriting the current database for SharePoint Foundation 2010?

Or another way?
0
 
LVL 38

Accepted Solution

by:
Justin Smith earned 500 total points
Comment Utility
When you deployed Foundation, did you do a simple stand alone install?  Or did you do an advanced - complete install?

I'm guessing the current WSS_Content in your Foundation was deployed as part of your install, and doesn't have any real content.  If so, I would delete the web application that was created by the wizard in Foundation and choose to delete the data.  This will remove the wss_content db from your Foundation server.  

Then you can do the restore.  Then you'll create your 2010 web application and specify a temporary database name (like wss_content_temp).  After your web app is created, go into Content Databases in Central Admin, and remove the _temp database.  Then attach the wss_content database, which will upgrade it.
0
 

Author Comment

by:rsnellman
Comment Utility
Yes, I created a general WSS_Content database with my Foundation installation.  So, it contains nothing of importants at this time.

Thanks, I will try this and let you know how it turns out.

Thanks again.
0
 
LVL 38

Expert Comment

by:Justin Smith
Comment Utility
Just an FYI, if you ever need remote assistance, I'm available.
0
 

Author Comment

by:rsnellman
Comment Utility
Thanks.  I appreciate that.  One last thing, how do I attach the wss_content database to the SharePoint Foundation web application?

Do I have to use the command prompt with "stsadm -o addcontentdb" command?

Also, why did I need to delete the current wss_content database on Foundation & from SQL Server 2005 when deleting the current web application then create a wss_content_temp database when creating a new web application just to delete the wss_content_temp database?

Sorry, I just don't understand why.


Thanks.
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Author Comment

by:rsnellman
Comment Utility
OK, I am missing something, because I cannot attach the content database to SharePoint Foundation.

Here is what I am trying:

Within SharePoint Foundation 2010 Management Shell:

stsadm -o addcontentdb WSS_Content.mdf

But it comes back with a command line error.  No other details, just an error.

What am I missing?

I have never attached a content database in SharePoint before.  So, I am sure it is something I am doing wrong.


Thanks.
0
 
LVL 38

Assisted Solution

by:Justin Smith
Justin Smith earned 500 total points
Comment Utility
You have to specify a web application in your stsadm command.  Also, don't add the .mdf to the end of the name.

http://technet.microsoft.com/en-us/library/cc263422(v=office.12).aspx

You delete the current wss_content database in Foundation because it's garbage.  Also, if that database already exists, you aren't gonna be able to restore the database from WSS if it's also named wss_content.  

When you create your new web app, you use a dummy name with _temp at the end, so you know you can delete it.  Then you attach the restored wss_content database to the Web app through the STS command.  This will upgrade the database.  You can then detach the dummy one and delete it.
0
 

Author Comment

by:rsnellman
Comment Utility
Oh, OK.  Opps.  I already deleted the dummy temp database and am now trying to attach/upgrade the real database.  It is already in SQL Server 2005 x64, just need to get Foundation to see it.

Gotcha, makes more sense now.

I really appreciate all your help with this.  I have been trying off and on for over a year to get this migration completed.  It has been a high priority but then again other fires make it sit on the back burner for sometime.  Now I have time to complete this project and feel that I am very very close to finalizing it.

Thank again.
0
 

Author Comment

by:rsnellman
Comment Utility
Awesome.  The test migration worked like a charm.  Now to proceed with the production migration.

Also, how should I proceed if I want to add a ssl cert to the sharepoint site?

Do I do that during the migration or after I have the migration completed successfully?


Thanks again.
0
 

Author Comment

by:rsnellman
Comment Utility
I am sorry, if I am getting on another topic and should start another question thread then I can do that too.  I just trying to ironing this out and be done with this project.
0
 
LVL 38

Expert Comment

by:Justin Smith
Comment Utility
Wait till afte the migration and after everything is up and running on the new platform.
0
 

Author Comment

by:rsnellman
Comment Utility
OK.  Thanks.  You have been a life saver.
0
 
LVL 38

Expert Comment

by:Justin Smith
Comment Utility
LOL.  Glad it worked out.
0

Featured Post

Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Join & Write a Comment

Scenario:  You do full backups to a internal hard drive in either product (SBS or Server 2008).  All goes well for a very long time.  One day, backups begin to fail with a message that the disk is full.  Your disk contains many, many more backups th…
In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now