SharePoint Content deployment on same or different server farm
Content deployment allows you to copy content from a source farm or site collection to a destination farm or site collection. Most content deployment topologies include two or more server farms, to separate the authoring environment from the production environment.
Content deployment settings for both incoming and outgoing deployment jobs are configured on the Content Deployment Settings page, which is accessed from the Operations tab on the SharePoint Central Administration Web site. 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 allows 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.
Content deployment
paths and jobs are configured on the
Manage Content Deployment Paths and Jobs page, which is also accessed from the Operations
tab on the SharePoint Central Administration
Web site. You use the Manage Content Deployment Paths and Jobs page to create
and manage content deployment paths and jobs, and to enable and manage Quick Deploy jobs. You can also specify
the scope and schedule for jobs, and can manually test, run and cancel jobs.
Important: It is important to note that 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 stored within that site collection.
The following topics and objectives are part of content
deployment:
Configure
content deployment settings
Use the following procedure to configure content
deployment settings. Content deployment settings for both incoming and outgoing
deployment jobs are set on the Content Deployment Settings page. If your farm
is an authoring farm, you do not need to configure incoming (import) settings.
If your farm is a staging farm, you need to configure both incoming (import)
and outgoing (export) settings. If your farm is a production farm, you do not
need to configure outgoing (export) settings.
To
configure content deployment settings - (To allow Incoming Content
Deployment Jobs on the Production Site)
1.
On the
top navigation bar of the Central Administration Web site, click Operations.
2.
On the
Operations page, in the Content Deployment section, click Content
deployment settings.
3.
On the
Content Deployment Settings page, in the Accept Content Deployment Jobs
section, do one of the following:
-
If you
want to accept deployment jobs, select Accept incoming content deployment
jobs.
Note: You do not need to accept incoming jobs if the server is
part of the authoring farm. Only servers in staging or production farms need to
accept incoming deployment jobs.
4.
In the Connection
Security section, do one of the following:
-
To use
the HTTP protocol, select Do not require encryption.
5.
Click OK.
Create a new content
deployment path
Use this procedure to create a new content deployment path.
To create a new content deployment path
1.
On the top navigation bar of the Central Administration Web site,
click Operations.
2.
On the Operations page, in the Content Deployment section, click Content deployment paths and jobs.
3.
On the Manage Content Deployment Paths and Jobs page, click New Path.
4.
On the Create Content Deployment Path page, type a name for the
content deployment path in the Type
the name of this path box.
5.
Type a description of the content deployment path in the Type the description of the content deployment path
box.
6.
In the Source Web
Application and Site Collection section, in the Source Web application list, click
a source Web application.
7.
Click a source site collection on the Source site collection menu.
The Web application and site collection
determine from where the content is being deployed. After you make your
selections, the source location is displayed under URL.
8.
In the Destination
Central Administration Web Application section, type the URL of
the destination Central Administration server in the Type the URL of the Destination Central
Administration Server box. We test in this example on the same
server firm. You have to configure everything depending on destination server.
9.
In the Authentication
Information section, select one of the following:
10.
Connect by using the application pool account Select this option if
you want to use the application pool account to authenticate on the destination
Central Administration server.
- Connect
by using a different account Select
this option if you want to use an account other than the application pool
account for authentication on the destination Central Administration
server. If you select this option, select an authentication type and
provide credentials for the account to use for authentication.
- Click Connect.
11.
You are connected to the destination Central Administration
server, which supplies a list of eligible destination Web applications and site
collections.
12.
In the Destination Web
Application and site collection section, click a destination
Web application in the Destination
Web application list.
Note: Before define Destination Web application; you
have to create a "Blank Site" where you want to deploy. This step is IMPORTANT, because Blank Site is the
only template that you can import any other template into this.
13.
In the Destination Site
Collection list, click a destination site collection.
14.
In the User Names
section, select the Deploy user names
check box if you want user names to be included when this path is used for
content deployment.
15.
In the Security
Information section, in the Security information in the content deployment list,
click one of the following:
1.
All
2.
Roll Definitions Only
3.
None
16.
Click OK.
Create Content Deployment Job
-
Click
New Job:
-
Type
a name, and then select the path you created:
-
Keep
all other default values, and click OK.
Run Content Deployment Job
-
From
the context menu on the job, select Run Now:
-
Refresh
the page, and then click on the text Running:
-
Watch
the status of the job:
When the status changes to Succeeded, you
can click on the URL to the production site to verify that the content was
deployed.
Run Quick Deploy Job
-
Select
Quick Deploy Settings from the Quick Deploy context menu:
-
Select
Allow Quick Deploy jobs along this path, and set the schedule to check every 10
minutes, then click OK.
-
Visit
the staging site and edit a page
-
Make
some changes
-
Publish
the page
-
Show
the page editing toolbar
-
From
the Tools menu, select Quick Deploy
-
The
changes will be picked up and deployed to production within 10 minute
Reference:
http://technet.microsoft.com/en-us/library/cc262004.aspx
http://technet.microsoft.com/en-us/library/cc263157.aspx
http://technet.microsoft.com/en-us/library/cc262075.aspx
http://technet.microsoft.com/en-us/library/cc263090.aspx
http://blogs.msdn.com/jackiebo/archive/2007/02/26/content-deployment-step-by-step-tutorial.aspx