SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're about to move a site from a parallel site collection into a subsite of the other site collection. Both SC's are in the same Web Application. We have not been able to get the command line version of Export-SPWeb to work (see: Migrating a site from one SC to another - ContentType problems) but we have been able to get the Central Administration export site functionality to work. Unfortunately we can't enable UseSqlSnapshot because it's not an option on the web interface.

So my question is: does executing a Site Export from Central Administration lock the database for Writes AND Reads? or just Writes? And does sharepoint handle this gracefully?

share|improve this question
Sean McDonough says on his blog: "Prior to SharePoint 2010, site collection backup operations required some form of site collection lock to avoid data changes that would compromise the consistency of the backup being created. Locks of this type impacted the end-user experience adversely by preventing writes and updates to the target site collection until the backup operation could be completed."… Can anyone confirm? – Tom Halladay Jul 28 '11 at 13:41
up vote 1 down vote accepted

Running a test on this right now. Kicked off a Site export (not a Site Collection) (Central Administration > Backup & Restore > Export a Site or List > Selected Site, but no list) and am able to use & make changes to the site being exported, during export.

Answer: nothing is locked, site is usable. Perhaps the web triggered export is using /UseSqlSnapshot by silent default?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.