locked
How to Restore one site from a full farm backup RRS feed

  • Question

  • I have a full farm backup (that was done via Central Administration).   I need to restore one specific site from that backup.  However, that site is one of many subsites within a site collection.  And the site collection is one of many site collections under a web application.  Web application being one of many web applications.

     

    The environment was set up so that each web application has it's own content-db.

     

    What would be the best approach to restoring that one subsite?  If I restore the web application, I'm going to fudge all of the site collections and subsites within it.

     

    I had the idea that I could restore it to a new content database, and then delete all of the site collections/sites that didn't need restoring.  Then migrating the content for that one site back to the original content db - but that just feels like i'm going around my rear to get to my elbow.

     

    Any thoughts?  Thanks.

    Thursday, April 17, 2008 2:25 PM

Answers

  • Thanks guys for the input.   Finally got it done (althought it was a roundabout way).  Highly recommend anyone reading this to check out the link that Paul provided - great stuff.  Also, there is a feature out on codeplex that is worth looking at (http://www.codeplex.com/governance). Of course, both of those are to prevent you from getting into this scenario.  

     

    If you find yourself stuck like I did, here's what actions I took.

     

    1. Retrieved the farm backup from production.
    2. Stood up a vritual MOSS environment (has to be same version as backup, service packs etc)
    3. Hacked the backup log on my virtual MOSS environment to include the farm backup from the production environment
    4. Restored the content database only (the one which contained my missing site)
    5. Created a new web application on my MOSS environment (no site collection, just the web application).
    6. Attached the retored content db in SQL Server Manager
    7. In central administration, removed the content database associated with my new web application
    8. Associated my newly attached restored content db with the new web application
    9. From there, Hooray, we have our site collection up and running. 
    10. Saved my sub-site as a template including data, saved lists as templates including data, etc...
    11. Migrated all of these templates & data to my production environment, and created a new site with appropriate data from the templates.

     

    It's a long process, with quarks and errors you'll have to get around.  I'm going to post a blog on it at sometime and at that time I'll update this thread.  But in a nutshell, that's how you can retrieve the site.

     

    -------------------------------------
    Dan Lewis
    http://weblogs.asp.net/danlewis

    Thursday, May 8, 2008 3:21 PM

All replies

  • Hey Dan,

     

    Unfortunately, you have a pretty sticky situation.  I would NOT recommend restoring anything in your production environment.  If you do not have a Test environment where you can restore your backup to and then recover the single site, I would suggest that you download Microsoft's Virtual PC from www.microsoft.com/virtualpc

    It's a free download that allows you to create a virtualized server environment where you can then restore your backup in order to retrieve the site in question.

     

    Hope that helps.


    Thanks

    C

    www.cjvandyk.com/blog

     

     

    Friday, April 18, 2008 1:28 AM
    Answerer
  • It won't help you with your current solution, but I just saw a presentation this week on data protection manager 2007 that you might consider looking at for future: http://feeds.feedburner.com/~r/PaulGalvinsSharepointSpace/~3/272102390/cns!1CC1EDB3DAA9B8AA!975.entry

     

    --Paul Galvin, Conchango
      RSS @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace
      Web site @ http://paulgalvin.spaces.live.com
      Twitter @ http://twitter.com/pagalvin
    Friday, April 18, 2008 10:14 AM
  • Thanks guys for the input.   Finally got it done (althought it was a roundabout way).  Highly recommend anyone reading this to check out the link that Paul provided - great stuff.  Also, there is a feature out on codeplex that is worth looking at (http://www.codeplex.com/governance). Of course, both of those are to prevent you from getting into this scenario.  

     

    If you find yourself stuck like I did, here's what actions I took.

     

    1. Retrieved the farm backup from production.
    2. Stood up a vritual MOSS environment (has to be same version as backup, service packs etc)
    3. Hacked the backup log on my virtual MOSS environment to include the farm backup from the production environment
    4. Restored the content database only (the one which contained my missing site)
    5. Created a new web application on my MOSS environment (no site collection, just the web application).
    6. Attached the retored content db in SQL Server Manager
    7. In central administration, removed the content database associated with my new web application
    8. Associated my newly attached restored content db with the new web application
    9. From there, Hooray, we have our site collection up and running. 
    10. Saved my sub-site as a template including data, saved lists as templates including data, etc...
    11. Migrated all of these templates & data to my production environment, and created a new site with appropriate data from the templates.

     

    It's a long process, with quarks and errors you'll have to get around.  I'm going to post a blog on it at sometime and at that time I'll update this thread.  But in a nutshell, that's how you can retrieve the site.

     

    -------------------------------------
    Dan Lewis
    http://weblogs.asp.net/danlewis

    Thursday, May 8, 2008 3:21 PM