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

I have authoring environment and production environment for my public facing site. Now the requirement that I have is there is one Private document library which should only be available in authoring environment and should never export to production.

Is it possible to exclude certain documents or library from a content deployment job?

share|improve this question
Welcome to SharePoint Stack Exchange! Please tag by feature and not by version or product. This helps to attract more attention to your question and keep it relevant. See How do I use tags for general guidelines. – Alex Angas Jul 28 '11 at 1:05

With the way content deployment works (i.e. it replicates the whole content database) this wouldn't be possible. However, with the correct permissioning on the library, you should be able to make it not visible to users who shouldn't see it.

In addition, I would recommend moving that content somewhere else (i.e. add a content database to the web application and add a new site collection in that content database, like /sites/privatecontent).

share|improve this answer

This tool may help you :

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.