Transcript
Page 1: Share point content deploymet presentation Chicago

SharePoint 2010 Content Deployment

What is that, who should use that, and when that should be used

Date: October 16, 2010

Prepared for: SharePoint Saturday Chicago

Page 2: Share point content deploymet presentation Chicago

2

What is it?Microsoft says:•Content deployment deploys content from a source SharePoint Server 2010 site collection to a destination site collection. The complete source site collection can be deployed, or a subset of sites can be deployed.

Page 3: Share point content deploymet presentation Chicago

3

What do I say it is?•Control•Security•Testing•Complexity

Page 4: Share point content deploymet presentation Chicago

4

That’s great! I’m going to go use it right now!

Consider your particular scenario. Is it a good fit?•Farm Topologies are Completely Different•Servers have specific performance tuning requirements•Security concerns for content on the destination

What do you gain?• Control• Security• Testing• Complexity

Page 5: Share point content deploymet presentation Chicago

5

Content Deployments are horrible! Isn’t there a better way?

•Author on Production via an extended web application

•Custom solution?•Backup and restore

Page 6: Share point content deploymet presentation Chicago

6

So what do you need to pull this off?

Authoring and Production Farm

Use this for:• Internet-facing sites• Extranet sites with read-only access

Page 7: Share point content deploymet presentation Chicago

7

Next step up…

Authoring, Staging, and Production Farms

Use this for:• Multi-stage approval process business requirement• Validating content that reflects production environment• Testing content with custom web parts and code

Page 8: Share point content deploymet presentation Chicago

8

Now that is to big. What about the little guy?

Single Publishing Farm

Use this for:• Intranet deployments• External testing/validation is not needed• When one farm is all you have

Page 9: Share point content deploymet presentation Chicago

9

I’m still interested….

Who gets it and who doesn’t…

Page 10: Share point content deploymet presentation Chicago

10

The Details Please….

So what does it take to set this up?

A Path…

…is the road to get from A to B

A Job…

…is the car that drives you from A to B

Page 11: Share point content deploymet presentation Chicago

11

Enough Talk! Let take a look at SharePoint…

Spin up that VM!

Page 12: Share point content deploymet presentation Chicago

12

Common Pitfalls

Not enough Planning...•Plan for which server are the export import server

•Plan content deployment paths•Plan job scheduling•Plan for large jobs

Page 13: Share point content deploymet presentation Chicago

13

And the Complexity Continues…

•Keep content in scope•I exported the child but not the parent•Use empty site collection as a destination (Not blank!)

•Install required features on destination but don’t active

•What's your patching level?•Don’t forget the language packs

Page 14: Share point content deploymet presentation Chicago

14

So What new in SharePoint 2010?

•Database Snapshots!

• Import Settings–UnattachedContentDatabase–ExportFrontEndFileStreams

•Removed Export part – ‘retry’ is gone

•Custom deployment aware event handlers and feature activation code

Page 15: Share point content deploymet presentation Chicago

15

Questions?

Page 16: Share point content deploymet presentation Chicago

16

Javier BarreraBlog: http://www.techgrowingpains.comTwitter: @BlueUser


Recommended