Limitations of STSADM -o export/import related to publishing sites

Valuable Internet Information » Stefan Go??ner : Limitations of STSADM -o export/import related to …

Wed, 27 May 2009 16:29:06 GMT

PingBack from http://valuableinternetinformation.com/?p=36438

Bamboo Releases SharePoint Project Management Central, Windows 7 Touch Pack, Office 2010 Not So Special?

SharePoint Daily — Thu, 28 May 2009 16:19:50 GMT

Top News Stories 5 Tips for Maximizing SharePoint (Intranet Journal) Though tools such as Microsoft's

re: Limitations of STSADM -o export/import related to publishing sites

Sushant — Sun, 31 May 2009 17:08:53 GMT

I am a regular follower of your posts. This post is also bang on target as usual :) just want to double check:

Are you saying that to migrate a very large publishing site what i need to do is to 1st migrate the root site along with some subsites to a root site and then migrate the individual subsites? Please confirm.

re: Limitations of STSADM -o export/import related to publishing sites

Stefan_Gossner — Sun, 31 May 2009 18:08:43 GMT

Hi Sushant,

if you just need to migrate the whole site collection you can do this at once.

But if you need to split the site collection into multiple pieces you need to ensure that each piece that does not start at the root of the site collection in the source site has to be migrated as a subsite of an existing site collection.

Cheers,

Stefan

SubSite to Site Collection

Nishant's World — Thu, 04 Jun 2009 02:23:53 GMT

Lets consider a scenario where a subsite (web) becomes substantially larger and you wish you could have

re: Limitations of STSADM -o export/import related to publishing sites

Paul — Fri, 12 Jun 2009 11:54:02 GMT

Hi Stefan,

I'm a MOSS 2007 novice and extremely concerned regarding our initial setup/structure of our initial MOSS 2007 implementation. Our sub sites have been created with the Publishing template and I would like to like to convert them to their own site collections. We are reasonably early in our MOSS 2007 implementation but I can see in the future one site collection/database etc may/will cause some headaches in the future eg ability to set quotas, database restores in a timely fashion etc. Is there other tools available to convert sub sites to site collections or are we better off recreating the new site collection and migrating the doc etc manually?

Thanks

PaulN

re: Limitations of STSADM -o export/import related to publishing sites

Stefan_Gossner — Fri, 12 Jun 2009 14:30:29 GMT

Hi Paul,

if the amount of data is reasonable I would suggest to recreate the site collections.

If not you could use the workaround to create a new site collection for using the publishing template and then import as sub site.

Cheers,

Stefan

re: Limitations of STSADM -o export/import related to publishing sites

Mike Edwards — Tue, 16 Jun 2009 10:51:34 GMT

I've been using the Export command to export 70 subsites. These sites were below a Publishing site, but not using any features from this site.

Export of the sites creates all the relevant .cmp files (one set per site) I then import them into a new site collection and they import without errors but not all of the data is there. Lots of the lsits are only partially populated, and some of the Doc libraries are missing many docs. Why would this be?

I've used the -Versions 4 switch, as most of the Doc libs have versionig on.

re: Limitations of STSADM -o export/import related to publishing sites

Stefan_Gossner — Tue, 16 Jun 2009 11:10:50 GMT

Hi Mike,

if I understand correct you exported team sites from the site collection. Is this correct?

The description sounds like a potential database inconsistency. I would recommend to open a support case with Microsoft to get this analyzed.

Cheers,

Stefan