locked
Move the Whole SharePoint From Test to Deployment RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I developed a SharePoint SiteCollections Using

    -SharePoint 2010 Server.

    - Visual Studio 2010

    -InfoPath 2010

    it have alos Event recievers ,pages, Visual webParts.

    --------------------

    I want to do :

    Move or Copy whole SharePoint Application with it's contents and features .., etc

    to the Deployment Server Which it totally cleaned. ( have just SharePoint Server and SQL Server2008R2) as the Development environment.

    I want to just copy whole Application to the deployment Server.

    -----------------

     SharePoint 2010 Solutions (WSP) , was not a good solution ,

    I want to copy Everything inside my Application at once.

    -----------------

    thank u for help

    Wednesday, February 22, 2012 11:02 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    SharePoint really isn't designed to work that way.  Even if you do a full backup of your SharePoint environment and restore it to the deployment server it won't work.  SharePoint backups don't backup the files that have been added to the file server through the deployment of WSP solutions and other features.  The normal process would be as follows:

    1. Build your base SharePoint environment on the deployment server
    2. Install all your customizations on the Deployment server by installing your WSPs.
    3. Move any content and your hierarchy backing up your Sharepoint test environment and restoring it to the deployment server.

    Note: that will work the first time you do a deployment.  But step #3 can't be used to deploy changes to content once your deployement server is completed.  SharePoint is designed to have content created by users directly in the production system unless you are using Publishing.  But if you are using the Publishing features for deployment then the expectation is that the production system is read only content.  Even with Publishing you can't make changes in both Production and Staging and not run into errors when deploying content.

    The traditional model of Test -> QA -> Production deployment only works in SharePoint for things developed in Visual Studio and deployed as WSP solutions. 

    Paul Stork SharePoint Server
    MVP Chief SharePoint Architect: Sharesquared
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    Wednesday, February 22, 2012 12:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    User Powershell command to backup and restore it on Target server.This time you will not see your site fully functionally.
    List all your Custom Solution and backup through SPFarm back with item parameter.
    If you have application pages and layout related stuff such as images,themes and css must be copied mannually and paste it on your target server.

    Except these formalities there is no ready made activities which will do all in ONE.

    Murugesa Pandian.,MCTS|App.Devleopment|Configure

    Wednesday, February 22, 2012 1:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tareq,

    You really don't want to worry about Site Collection and its related Lists.It will be comes as it is in Development Server when your restore it on Production Server.

    You need to identify those custom solutions[Features,Visual WebParts] and take a backup using SPFarm backup with item parameter.Once the solution were installed on Production you can see the whole replecation on your production server.

    Murugesa Pandian.,MCTS|App.Devleopment|Configure

    Wednesday, February 22, 2012 3:49 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    SharePoint really isn't designed to work that way.  Even if you do a full backup of your SharePoint environment and restore it to the deployment server it won't work.  SharePoint backups don't backup the files that have been added to the file server through the deployment of WSP solutions and other features.  The normal process would be as follows:

    1. Build your base SharePoint environment on the deployment server
    2. Install all your customizations on the Deployment server by installing your WSPs.
    3. Move any content and your hierarchy backing up your Sharepoint test environment and restoring it to the deployment server.

    Note: that will work the first time you do a deployment.  But step #3 can't be used to deploy changes to content once your deployement server is completed.  SharePoint is designed to have content created by users directly in the production system unless you are using Publishing.  But if you are using the Publishing features for deployment then the expectation is that the production system is read only content.  Even with Publishing you can't make changes in both Production and Staging and not run into errors when deploying content.

    The traditional model of Test -> QA -> Production deployment only works in SharePoint for things developed in Visual Studio and deployed as WSP solutions. 

    Paul Stork SharePoint Server
    MVP Chief SharePoint Architect: Sharesquared
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    Wednesday, February 22, 2012 12:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    User Powershell command to backup and restore it on Target server.This time you will not see your site fully functionally.
    List all your Custom Solution and backup through SPFarm back with item parameter.
    If you have application pages and layout related stuff such as images,themes and css must be copied mannually and paste it on your target server.

    Except these formalities there is no ready made activities which will do all in ONE.

    Murugesa Pandian.,MCTS|App.Devleopment|Configure

    Wednesday, February 22, 2012 1:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    oops,

    This is very bad news,

    I have a lot of features , event recievers ..,

    if i could Recompile it over the Deployment Server .., so it will be fine..,

    The problem is how to copy the Site collection with it's Lists and Relations between lists ,

    because I tried that once .., then I lost every relation between lists also every page which have a filters webParts..,

    all was damaged.

    I used the other Solution using Visual studio .., I lost the lists fields names because of it was in Arabic language and it refuse to accept the language when create the list defenition from existing list. at deployment project .

    thank u for help

    Wednesday, February 22, 2012 1:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tareq,

    You really don't want to worry about Site Collection and its related Lists.It will be comes as it is in Development Server when your restore it on Production Server.

    You need to identify those custom solutions[Features,Visual WebParts] and take a backup using SPFarm backup with item parameter.Once the solution were installed on Production you can see the whole replecation on your production server.

    Murugesa Pandian.,MCTS|App.Devleopment|Configure

    Wednesday, February 22, 2012 3:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tareq,

    You really don't want to worry about Site Collection and its related Lists.It will be comes as it is in Development Server when your restore it on Production Server.

    You need to identify those custom solutions[Features,Visual WebParts] and take a backup using SPFarm backup with item parameter.Once the solution were installed on Production you can see the whole replecation on your production server.

    Murugesa Pandian.,MCTS|App.Devleopment|Configure

    I feel that this is the optimal Solution ..,

    So please tell me what do you mean by : Once the solution were installed on Production Server ?  you can see the whole replecation on your production server.

    - okay Consider that I have all features and custom web parts out so i can Reinstall it in the production server...

    you told me that the Site collection and all lists pages .. relations .., automaticlly replaced at production server.,

    Also do you mean the Backup which is in Centeral Admin ?

    if you could please tell me the solution step by step?

    thank u for help

    Sunday, March 4, 2012 12:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Another question What if I installed and made sites, features,modules, ...etc, And I made a full backup from admin website, Then the whole server crached or have to re-install everything Can I just restore my backup from administration website at my new frish sharepoint server.?

    thank u for help

    Thursday, March 8, 2012 2:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This is good data. Thanks.
    Thursday, June 14, 2012 3:06 PM