{"id":503,"date":"2009-05-11T20:52:00","date_gmt":"2009-05-11T20:52:00","guid":{"rendered":"https:\/\/brainlitter.itgroove.net\/2009\/05\/11\/how-to-backup-and-restore-migrate-a-single-sub-site-of-a-sharepoint-site-collection-using-stsadm-o-export-and-import\/"},"modified":"2009-05-11T20:52:00","modified_gmt":"2009-05-11T20:52:00","slug":"how-to-backup-and-restore-migrate-a-single-sub-site-of-a-sharepoint-site-collection-using-stsadm-o-export-and-import","status":"publish","type":"post","link":"https:\/\/regroove.ca\/brainlitter\/2009\/05\/11\/how-to-backup-and-restore-migrate-a-single-sub-site-of-a-sharepoint-site-collection-using-stsadm-o-export-and-import\/","title":{"rendered":"How to backup and restore (migrate) a single sub site (of a SharePoint Site Collection) using STSADM \u2013o export (and import)"},"content":{"rendered":"
\n

Ok, long title but I wanted to be as descriptive as possible\u2026 <\/p>\n

\u00a0<\/p>\n

Reference: http:\/\/msdn.microsoft.com\/en-us\/library\/bb507233.aspx<\/a> <\/p>\n

\u00a0<\/p>\n

I had need today, as I often do, to help a client ‘clean up’ their SharePoint environment. They wanted a new SharePoint site (built on a sound infrastructure, etc. \u2013 my favourite) but wanted to bring across ‘some’ of their old content. In this case, there was a sub site that they wanted to bring across in its entirety, with as much version history as possible. The Solution? STSADM \u2013o export<\/strong> <\/p>\n

\u00a0<\/p>\n

I’m going to outline the process here, of the steps I had to perform (and the pratfall I discovered, re: STSADM and it not liking cut and paste from other sources\/references resulting in ‘Command Line Error’ being returned \u2013 which in turn, turned out to be because the example syntax I was cutting and pasting from was using the wrong character format for the “-” (dash) character. Once I addressed that (thanks, in hints from: http:\/\/weblogs.asp.net\/soever\/archive\/2007\/12\/22\/sharepoint-stsadm-exe-and-the-infamous-quot-command-line-error-quot.aspx<\/a>, I was back on my way to finishing the task). So here goes\u2026 <\/p>\n

\u00a0<\/p>\n

The Requirement <\/h1>\n

Backup a sub site of an existing site collection, with security information and version history retained from one SharePoint Server Farm (not the entire site collection, as you would use \u2013o backup for that, see my ‘sandbox’ refresh post here<\/a>), to another. In my case, I’m able to bring the Security information across as they exist in the same domain. Note: You will want to avoid the “-includeusersecurity” command, if you going beyond the domain. <\/p>\n

\u00a0<\/p>\n

The Solution <\/h1>\n

STSADM \u2013o export<\/strong><\/span> <\/span>followed by STSADM \u2013o import<\/strong><\/span> (and the appropriate syntax, see example below). Here is a nice, syntax overview<\/a> for quick reference. <\/p>\n

\u00a0<\/p>\n

The Example <\/h1>\n

Note, all commands assume you can use the STSADM command (have it in your path, or have put yourself in the appropriate directory to run it \u2013 c:program filescommon filesmicrosoft sharedweb server extensions12bin<\/em><\/span>. <\/p>\n

\u00a0<\/p>\n

Export Syntax Example <\/em><\/h2>\n

stsadm -o export -url http:\/\/nfn-spsrv:23651\/sites\/nfnentportal\/treaty -filename “c:swexporttreatysubsitebackup” -includeusersecurity -versions 4 <\/strong><\/span><\/p>\n

\u00a0<\/p>\n

The above is indicating that I am: <\/p>\n