The Art of SharePoint Evolution

Stories from a SharePoint Engineer that isn’t afraid of Visual Studio.

MOSS 2007 Backup/Restore Quirks and Site Migration

with 6 comments

Dude, I just spent the entire morning trying to restore a MOSS database and man did it suck. I was originally asked to delete a link to a document workspace from a site’s quick launch navigation. It looked like MOSS was playing tricks on me again, ever notice how sometimes subsites don’t get included on the parent’s quick launch? And sometimes they’re duplicated? In my case, I thought the user had just created duplicate workspaces so I just clicked on one and deleted the site. Should’ve been that simple right? Wrong…

 I went back to the parent site and both links were gone! I was like aww crap… I knew what had happened and I knew the recycle bin doesn’t support deleted sites. But I checked the recycle bins anyways. No dice. Next step - restore last night’s backup to a different server.

 This part just blew my mind, I had restored hundreds of content databases and attached them to web applications before no sweat. But for the life of me I couldn’t get any web applications I had created to recognize any of the sites in the content database. It would just say there was 0 sites in the site collection. After unsuccessfully trying to restore this database, I finally threw my hands up and booted up an old virtual machine that had a fresh MOSS 2007 install on it. Restored the database to that machine, created a new web application, attached the database and voila! Everything’s there.

Then I proceeded to use the content migration feature of SharePoint Designer to backup and restore the content. I have no idea why neither my production or test MOSS server wouldn’t recognize the sites from attached databases. Anybody else come across a similar problem?

Time to install the SharePoint Governance and Manageability tools from Microsoft IT…

Written by Henry

May 31, 2007 at 2:24 pm

Posted in SharePoint

6 Responses to 'MOSS 2007 Backup/Restore Quirks and Site Migration'

Subscribe to comments with RSS or TrackBack to 'MOSS 2007 Backup/Restore Quirks and Site Migration'.

  1. I ran into the same issue today. I was just testing backup and restore, so no lost data or sites.

    I did a full backup.
    Created a new application
    Restored the content database to a new name
    attached the restored content database to the new application
    IISRESET
    tried to browse to a known URL but received ’site not found’

    I have 2 WFE’s. site uses SSL. Moss 2007

    Any ideas as to what could be the fix?

    Bob

    10 Jan 08 at 12:47 pm

  2. As far as I know you cannot have the same site collection added to a server farm twice (which happens when you attach a restored database to the farm). SharePoint stores site collection GUIDs in its config database, hence the limitation.

    It also explains why attaching the restored database to a clean installation worked fine.

    Alex

    23 Jan 08 at 3:14 am

  3. Thanks Alex!

    Henry

    23 Jan 08 at 10:28 am

  4. Henry, do you know anything about setting up Project Server 2007 porfolio analysis views over an internet or extranet connection. Scenario is I have an internal Ip and and External IP with only certain ports opened at the firewall and no internet dns entry for a FQDN yet. Any insight you can provide would be greatly appreciated

    BeerCityGal

    11 Feb 08 at 4:14 pm

  5. i am gonna show this to my friend, bro

    Frazierez

    21 Mar 08 at 4:30 pm

  6. Excellent blog! Interesting article and very informative! I will necessarily subscribe for this blog. http://movie-cool.com/map.html

    BiilYBonnYU

    11 Nov 08 at 11:57 pm

Leave a Reply