Configure content deployment settings
Applies to: SharePoint Server 2010
Content deployment enables you to copy content from a source site collection to a destination site collection. Content deployment settings for both incoming and outgoing content deployment jobs are set on the Content Deployment Settings page on the Central Administration Web. To configure content deployment, there must be at least one server in each server farm of your topology that contains the Central Administration application server role. You use the Content Deployment Settings page to accept or reject incoming content deployment jobs for an entire server farm. You can also set specific servers within your farm to be used for receiving incoming content deployment jobs or for sending outgoing content deployment jobs. This enables you to spread the load for content deployment jobs across multiple servers in your farm, based on the available server resources and the needs of your farm. Each farm must be configured to accept or reject incoming or outgoing content deployment jobs, based on the role it has within your content deployment topology.
If your farm is an authoring farm, you must configure outgoing (export) settings.
If your farm is a staging farm, you must configure both incoming (import) and outgoing (export) settings.
If your farm is a production farm, you must configure incoming (import) settings.
For information about how to design a topology for your content deployment scenario, see Design content deployment topology (SharePoint Server 2010).
Content deployment is a one-way process: content is copied from a source site collection to a destination site collection. The content deployment feature does not support round-trip synchronization from source to destination and back again. Creating new content or changing existing content on the destination site collection can cause content deployment jobs to fail. Because of this, you should consider restricting permissions on the destination site collection so that users cannot make changes directly to content that is stored within that site collection.
Configure content deployment settings
Use the following procedure to configure content deployment settings.
To configure content deployment settings
Verify that you have the following administrative credentials:
- You must be a member of the Farm Administrators group on the Central Administration server.
On the Central Administration Web site, click General Application Settings.
On the General Application Settings page, in the Content Deployment section, click Configure content deployment.
On the Content Deployment Settings page, in the Accept Content Deployment Jobs section, do one of the following:
To accept deployment jobs, select Accept incoming content deployment jobs.
To reject deployment jobs, select Reject incoming content deployment jobs.
You do not have to accept incoming jobs if the server is part of the authoring farm. Only servers in staging or production farms have to accept incoming deployment jobs.
To specify the server as either an import or export server, do one of the following:
If you are using the server to receive incoming deployment jobs, in the Import Server section, on the Server you want to use to manage import of content deployment jobs menu, click the server that will receive jobs.
If you are using the server to send deployment jobs, in the Export Server section, on the Server you want to use to manage export of content deployment jobs menu, click the server that will send jobs.
Both the export server and the import server must host an instance of the Central Administration Web site.
In the Connection Security section, do one of the following:
To use the HTTPS protocol, select Require encryption (recommended).
If you select HTTPS protocol, make sure that the URL to the destination Central Administration Web site begins with https:// when you create a content deployment path, or you will be unable to connect to the destination Web site.
To use the HTTP protocol, select Do not require encryption.
In the Temporary Files section, type the temporary file path that both the import and export servers (as applicable) will use for storage of temporary files.
By default, a temporary file path on the local system drive is provided. Depending on the amount of storage space on the server and the amount of content to be deployed, you might want to consider using a storage location on another server. The account that is used to run the timer service must have read/write permissions to this location.
In the Reporting section, in the Number of reports to retain for each job box, type the number of reports that you want to keep for each content deployment job that originates from this farm, and then click OK.