+ All Categories
Home > Documents > SharePoint content deployment presentation

SharePoint content deployment presentation

Date post: 14-Jun-2015
Category:
Upload: jtbarrera
View: 877 times
Download: 4 times
Share this document with a friend
Popular Tags:
13
SharePoint 2010 Content Deployment The what is that, who should use it, and when it should be used Prepared for: SharePoint Saturday Los Angeles Date: September 18, 2010
Transcript
Page 1: SharePoint content deployment presentation

SharePoint 2010 Content Deployment

The what is that, who should use it, and when it should be usedPrepared for: SharePoint Saturday Los AngelesDate: September 18, 2010

Page 2: SharePoint content deployment presentation

2

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.

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

What is it?

Page 3: SharePoint content deployment presentation

3

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

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

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

Page 4: SharePoint content deployment presentation

4

Author on Production via an extended web application

Custom solution? Backup and restore

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

Page 5: SharePoint content deployment presentation

5

Authoring and Production Farm

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

So what do you need to pull this off?

Page 6: SharePoint content deployment presentation

6

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

Next step up…

Page 7: SharePoint content deployment presentation

7

Single Publishing Farm

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

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

Page 8: SharePoint content deployment presentation

8

Who gets it and who doesn’t…

I’m still interested….

Page 9: SharePoint content deployment presentation

9

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

The Details Please….

Page 10: SharePoint content deployment presentation

10

Spin up that VM!

Enough Talk! Let take a look at SharePoint…

Page 11: SharePoint content deployment presentation

11

Not enough Planning... Plan for which server are the export import server Plan content deployment paths Plan job scheduling Plan for large jobs 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

Common Pitfalls

Page 12: SharePoint content deployment presentation

12

Database Snapshots!

Import Settings◦ UnattachedContentDatabase◦ ExportFrontEndFileStreams

Removed Export part – ‘retry’ is gone

Custom deployment aware event handlers and feature activation code

So What new in SharePoint 2010?

Page 13: SharePoint content deployment presentation

13

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


Recommended