SharePoint Review Center

Everything about SharePoint – Architecture, Design, Development, Configuration, Administration, Issues, and Fixes

Content Deployment – Overview

Posted by Anthony Odole on June 25, 2009

Content deployment involves three core steps – Export, transfer, and import. Contents are exported and imported as cab file. You can dedicate a front end web server to perform the role of content deployment on a farm. Designating a server is the recommended approach when you have large quantity of content to deploy. You can deploy content from one farm to another, or from one site collection within a farm to another site collection within the same farm. Content deployment is limited to 10Mb, and in addition, IIS places a 29MB restriction on the size of file you can transfer. The size restriction can be modified in your web application.

After the first initial full deployment, always perform incremental deployments. Otherwise, you end up with a destination site that is out of synch. A delete scenario is a good example of where multiple full deployments can result into inconsistent environment.

Destination must be a blank site, at least for the first full deployment; Incremental deployment does not need to go to a blank site. The idea of incremental backup presumes there is a full backup already at the destination sited. Note that content deployment does not address the deployment of Features, assemblies, or configuration. Where content depends on assemblies containing web parts, custom fields or field controls – or other file system, it is best practice to deploy these other components close to the time of deployment. Whenever you deploy to a blank site, the publishing infrastructure is activated. If you have a feature installed on a destination site but not activated. Same feature which was already activated at the time of packing the content at the source will be activated as part of content deployment after the content has been unpacked and deployed at the destination server.

Security: You can specify an alternate account, or you can use the application pool account for the central administration site. If you are using either account, ensure that the account has access to the destination site.

You can use quick deploy to get your content published immediately if you don’t want to wait for the time that a scheduled job will run. But this quick deploy is only available to site owners. However, if you have Sharepoint publishing infrastructure Feature enabled, then users who belong to the quick deploy group will have a button that allow them to deploy quickly on the site


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: