Link to home
Create AccountLog in
Avatar of Schuyler Dorsey
Schuyler DorseyFlag for United States of America

asked on

Migrating SharePoint 2010 to new server

I have a client with SBS2011 and they use the SP Foundation. I have already migrated the main content db to a backend (full blown) SQL box. Now I wish to move everything to a new dedicated SP box. (so the new box will house front end SP and all DB's on the sql box).

What is the best way to do this given the current scenario? Can I just perform a site collection backup and restore on the new SP box?
Avatar of Arnold Layne
Arnold Layne
Flag of United States of America image

Avatar of Schuyler Dorsey

ASKER

Thanks for the information! However, I moved the content db to the SQL box. When I attached it on the new SharePoint box, I can see all of the documents in the main library but when I try to view the properties of them or view the workflows I get "The item is no longer available. It may have been deleted by another user".
ASKER CERTIFIED SOLUTION
Avatar of Arnold Layne
Arnold Layne
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Thanks! They are using SharePoint Foundation 2010 since it is SBS2011. Is it just as easy to install SharePoint Foundation 2013 on the new box and upgrade/migrate them in the same step?
Migrate and update are two different things. The terms are a little misnamed and I often mistakenly use the wrong term. Migrate means moving to an entirely new software version of SP, for example 2010 to 2013, and upgrade means moving to a newer version of the same software (service packs...). So when I installed service pack one for SP 2010, I was performing an upgrade. But migrate doesn't mean migrate as in moving to another machine as it's name does suggest.

But yes, that might be the best idea if you intend to migrate to 2013 anyway. You might as well. But get your old stuff on to the new server first and THEN migrate it, so that the migrate can change the things it needs to change. If you add things from the old server to the new after the migration, the migration will not have had a chance to make the proper adjustments to the old stuff and this may cause you a few problems.
Thank you for the clarification, information and direction!
Heads up, I just found this

http://support.microsoft.com/kb/2724471

That effects things a lot. I really can't believe they do this crap. I don't know exactly what to do about this yet because I just ran into it and haven't researched a solution, but I wanted to catch you before you do anything and make you aware of this awful wrench in the works this causes. For someone who coordinates and uses multiple applications in their stuff all of the time, they are surprising horrible and the left hand often doesn't know what the right is doing. it's like different apps/os come from entirely different companies You may want to wait for service pack 2 for 2010 or research a solution or ask another question on the forum that is completely specific about the article above and what to do.