Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 2012-03-16
15
Medium Priority
?
727 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
ID: 37730310
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 2000 total points
ID: 37732675
no the databases don't have to be the same name.
0
 

Author Comment

by:rsnellman
ID: 37738717
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
Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

 
LVL 38

Accepted Solution

by:
Justin Smith earned 2000 total points
ID: 37738738
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
ID: 37742850
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
ID: 37743297
Just an FYI, if you ever need remote assistance, I'm available.
0
 

Author Comment

by:rsnellman
ID: 37743820
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
 

Author Comment

by:rsnellman
ID: 37743920
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 2000 total points
ID: 37744010
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
ID: 37744104
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
ID: 37748619
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
ID: 37748788
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
ID: 37748837
Wait till afte the migration and after everything is up and running on the new platform.
0
 

Author Comment

by:rsnellman
ID: 37748929
OK.  Thanks.  You have been a life saver.
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 37749053
LOL.  Glad it worked out.
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A safe way to clean winsxs folder from your windows server 2008 R2 editions
In case you ever have to remove a faulty web part from a page , add the following to the end of the page url ?contents=1
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

824 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