none
Move a Web Application to another Farm

    Question

  • Greetz!

    I recently completed a 2007 to 2010 upgrade with migration to new hardware and a 2010 to 2010 new hardware migration so I'm not a total newbie to the migration process but I've had a request that's got me puzzled.

    I have a SharePoint farm that consists of 3 web applications. We are planning on completely redoing the installation (new VMs, new SharePoint installation, etc)  however one of the organizations that owns an application ( not a site collection or a site) does not want their app updated. I don't think this can be done but wanted to see if it was possible to somehow keep this app out of the loop by detaching and reattaching databases or something.

    Thanks,

    Rich


    Love them all...regardless. - Buddha

    Wednesday, March 21, 2012 2:30 PM

Answers

  • Hi Craig, Thanks for your reply.

    This is not a 2007 to 2010 migration.

    THanks


    Love them all...regardless. - Buddha

    • Marked as answer by KansasCoder Wednesday, March 21, 2012 9:06 PM
    Wednesday, March 21, 2012 9:03 PM

All replies

  • I have a SharePoint farm that consists of 3 web applications. We are planning on completely redoing the installation (new VMs, new SharePoint installation, etc)  however one of the organizations that owns an application ( not a site collection or a site) does not want their app updated. I don't think this can be done but wanted to see if it was possible to somehow keep this app out of the loop by detaching and reattaching databases or something.

    Well, you can certainly detach the database, though I'm not sure I understand what you are trying to accomplish. Is the request to keep the web application in a 2007 farm? Once detached, where do you intend to reattach the content database? Attaching it to a 2010 farm will upgrade the database, but does not automatically upgrade the look and feel ("user experience") unless you use the -UpdateUserExperience parameter with Mount-SPContentDatabase or the -preserveolduserexperience parameter with the Addcontentdatabase stsadm operation.


    Jason Warren
    Infrastructure Specialist
    Habañero Consulting Group
    www.habaneros.com/blog

    Wednesday, March 21, 2012 4:26 PM
  • The method you propose is used when moving content databases to a new server. I'm talking about an entire application which has a different url associated with it and is living on a different zone. Don't application settings live in the Admin Content and Config databases? If I stand up a new farm it will have a new config db and an admin content db. I guess my question is how to bring those db's to the new farm..if that's even supported!

    Both apps are currently on Sharepoint 2010. We have a single server that all this is done on. We are running virtual servers. We will rebuild the virtual environment then migrate the contentdbs via the attach-upgrade method. But this one org who has their own url on our farm doesn't want to move, ergo the conumdrum.

    I'm thiniking that we are just going to have to redo their application when we set up the new farm and move their content dbs over.


    Love them all...regardless. - Buddha

    Wednesday, March 21, 2012 7:12 PM
  • To echo Jason's point, I am still not sure what you mean by the "one org who has their own url on our farm doesn't want to move". Here are some thoughts:

    • Do you mean they wish to remain on SharePoint 2007? If this is the case, I'd urge them to plan an upgrade path as mainstream support is coming to an end this year - see my blog post for links to the official dates for MOSS 2007 and WSS 3.0 http://craiglussier.com/2012/02/22/microsoft-office-sharepoint-server-2007-moss-windows-sharepoint-services-3-0-mainstream-support-ends-soon/. If the reason they don't want to move is related to cost, I am sure the expiration of mainstream support may get them thinking about moving. Extended support would likely end up costing more than regular support should something go wrong and Microsoft needs to get involved.
    • What is the specific reason for them "not wanting to move". If it is a technical reason, do you have the source code to their custom app? 
    • As Jason mentioned, you can easily 'upgrade' the web application to SharePoint 2010 without upgrading the user experience (i.e. the User Interface). In addition, it would also be easy to re-point their url/domain to a new machine. If you have the source code, upgrade the Visual Studio Project to Visual Studio 2010, recompile, re-package and re-deploy (assuming customization was done within a Visual Studio feature/solution). I know this may not be trivial depending on what the custom code does, but this is the path you potentially will walk down.
    • If the 'other organization' has different service application needs, a SharePoint 2010 benefit is multi-tenant support that which will be easier for you to manage.
    • If you have three web applications in MOSS 2007 and only want to move two of them to SharePoint 2010, go ahead and use the content db attach method as previously mentioned. If you build a new SharePoint 2010 farm you can pick and choose what 2007 web applications (via the content db attach method) to migrate from SharePoint 2007 - this isn't a problem since you are building your new farm from scratch.

    If you have any other questions or feedback, please let us know.

    I hope this helps,

    Craig


    Senior Systems Engineer / SharePoint Architect | MSDN Profile | Blog | Twitter
    Microsoft Community Contributor Award 2011 Recipient

    Wednesday, March 21, 2012 8:57 PM
  • Hi Craig, Thanks for your reply.

    This is not a 2007 to 2010 migration.

    THanks


    Love them all...regardless. - Buddha

    • Marked as answer by KansasCoder Wednesday, March 21, 2012 9:06 PM
    Wednesday, March 21, 2012 9:03 PM