Move a subweb (regular site) to another content DB in WSS 3.0 RRS feed

  • Question

  • Hi guys.

    There is a site http://webapplication.company.com/site. It is a regular site in site collection (aka subweb, sub site etc.). I need to move this site and it's subsites into another content DB and to preserv all links, so all content and sites and all that stuff could be accessible using old links, so no one notice any changes.

    What I have figured out is this:

    1) Create a new Content DB

    2) Export the site using stsadm -o export

    3) delete this site from SharePoint

    4) Create a new site collection and place it the new DB created in step 1

    5) Import the site from file using stsadn -o import

    But I have several concerns:

    1) Is the order of steps described above is OK?

    2) I assume that after import the site would have an address http://webapplication.company.com/site/site. First <site> is from site collection created in step 4 and second <site> is imported site from step 5. Am I right? If yes then how this can be changed? I need all links to be preserved and nothing changed from users point of view.

    I am SharePoint newbie so any help will be appretiated.

    Thursday, September 27, 2012 6:17 AM

All replies

  • The order is correct.

    Depending on whether the links are absolute (http://webapplication.company.com/site) or relative (/site), or generated automatically by SharePoint you may need to go through your links and update them if the new URL is different (which it will be since you're moving it)

    You should take a look at Gary Lapointe's stsadm extensions for SharePoint 2007, specifically the gl-moveweb extension. It is designed to move a web (sub site) from one location to another within the same farm. It will move security, content and other dependencies and handle the bits that move a web to the root web of a new site collections which it sounds like you might be doing.

    Jason Warren
    Infrastructure Architect

    Monday, October 1, 2012 1:40 PM
  • It is a very good solution, but for MOSS 2007. I am using WSS 3.0 though. I doubt that it will work in my environment.
    Tuesday, October 16, 2012 11:18 AM