database attach method migration wss3.0 to foundation 2010

Question

I am confused in data base attach migration method for the follwoing scenario .Can you please give me clarity? it is urgent.

We have a production system in wss3.0. I took  backup of the content database using sql servr management studio tool.

Can I restore this content DB to a test environment ( on sun Virtual box with 'windows 7' 64-bit host OS) and from test env't to new production system? 

If my testing is done and ready to move to new production system then How can I add the data accumulated during testing period (one month) to new prod'n system from wss3.0 system.

Best regards,

Answer 1

Yes, you can restore the content DB to the test environment to test the upgrade.  When you have tested everything on the virtual box and you are ready to migrate to production, then you would need to get a fresh backup of the database (be sure no one is using the system at the time) and restore it to the new production database server, then attach the SharePoint 2010 server to it.

I'm including a link that is from another forum because I think it describes your situation well.  The answer links to a couple of good blog posts on the subject of databaes attach migration: http://serverfault.com/questions/113714/wss3-0-to-sharepoint-foundation-2010-upgrade/113794#113794

---

Rob Wilson - MCT. MCTS, MCITP SharePoint. http://sharepointblog.kellerschroeder.com http://www.therobman.com/blog

Answer 2

Thank you for the reply.  I have gone through the links earlier but I didn't get clear picture for my scenario.

You are saying that I have to take fresh DB and attach it to production server. So, If I have built and tested any customizations/features in test environment then I need to re-build the same again in production system. I can't use the test environment DB . Am I right?

 

 

 

 

 

Answer 3

Hi MKDITTA,

                  you can use you existing Test Environment DB(it should be restore DB from WSS farm) in your production environment but you need to do all manual work which you did in test like migrating all customizations/features

Answer 4

You can use your test env db. But any data that are uploaded from the time of db backup in production will be lost if you are using DB from test. (However , you can make the production as read only after your backup to avoid this, since you are telling as feature development, which i feel should little time keeping this option is not suggested). But, the customizations what you would have build in test env, if you can package it as wsp, you can simply deploy the package in production, and take the proudction backup again to build new farm.

---

Satheesh

Answer 5

@MKDITTA You are correct.  The first migration to dev would just be a "trial run".  So after you attach the database, you would keep track of the steps needed to complete the migration for your customizations.  Since your waiting period is a month, I doubt that you'll want to keep the database read only for that entire period.  However, on the day you go live you could make it read only, get a fresh backup, do the attach method on production and then make the customizations you went through on the dev trial run.

---

Rob Wilson - MCT. MCTS, MCITP SharePoint. http://sharepointblog.kellerschroeder.com http://www.therobman.com/blog

Answer 6

Thank you guys for the clarification. I will implement all customizations in a wsp file and do the rest of the things.

all the best to you all.