Content Deployment is one of the final frontiers where SharePoint administrators fear to tread. Mark will explore Content Deployment from its origins to what to expect with SharePoint 2010 and covers his experiences when using content deployment in production environments, including tips and tricks to get your content deployment running smoothly, and how to keep it that way!
7. Content Deployment Perceptions The SharePoint team did a lot of work to optimize working with both Variations and Content Deployment. Both mechanisms are now more robust and reliable. Much better. I’ve found on a scale of 1 to 10 that Content Deployment 2010 is +3 to the scale of Content Deployment in SharePoint 2007. Microsoft has done some significant work with the content deployment feature within SharePoint 2010. MOSS 2007 automated content deployment had serious limitations and was often avoided because of unexpected results. It is a bit early to say whether 2010 will avoid all of those issues, but getting a chance to work with it over the last days has demonstrated some huge improvements. The SharePoint team did a lot of work to optimize working with both Variations and Content Deployment. Both mechanisms are now more robust and reliable. Its fantastic, its such an improvement on 2010! Content Deployment indeed has a bad rep. Well deserved back in 2007 when MOSS was released. Not so much anymore. If done properly CDS will work just great in 2007 and there are some *huge* companies with *huge* sites using it. 2010 includes all the fixes from the IUs and beyond, in addition it has much better reporting and support for SQL Snapshots on export. Along with other under the covers improvements with PRIME. I found the feature to be flaky in 2007, but if other improvements in 2010 are anything to go by I’m looking forward to seeing what it can do. Content Deployment has had a bad rap over the initial stages of SharePoint 2007, however since Service Pack 2 there have been no compelling reasons not to use it when replicating content from a staging site to a production site. Yes! In the right hands, an extremely powerful tool for SharePoint Web Content Management
10. Situations for CONTENT DEPLOYMENT? Security Concerns Site Performance Identical Content, Different Farm Topology
11. What doesn’t it do? Will not take anything stored outside of Site Collection Will not move configuration data or service application data Will not move solutions, features, assemblies Not designed for backup or restore purposes No Alerts, Audit Trail, Change Logs, Check In / Check Out State, Recycle Bin Items, Recycle Bin State, Security State, Workflow tasks, Workflow state. Bi-directional Replication
12. What’s new in 2010? Support for 2000+ pages on single site Web Analytics SQL Server Snapshot Support Publishing Sanity AJAX Content Deployment Aware Event Handling Support for Multi-Tenancy
13. Paths and Jobs Destination Server Source Server Web Application Web Application PATH Site Collection Site Collection Job
14. GUI Options Source Web Application Destination Farm Destination Web Application Transmission Security Users and Security API Options Compression Event Receiver Support Keep Temporary Files Content deployment anatomy : Path
18. Tips for successful implementation Security Hygiene Know your platform Documentation Common Sense
19. Tips for recovering failed Content deployments Was the Destination Site blank? Recreate the Path and Job Create a fresh blank Site Collection Content Deployment Manifest Reader MOSS2007 – Service Packs and Cumulative Updates Check Trace Logs Upgrade to SharePoint 2010
21. My Bloghttp://tinyurl.com/mrhodes Stefan Gossnerhttp://blogs.technet.com/b/stefan_gossner Spencer Harbarhttp://www.harbar.net Maxime Bombardierhttp://blogs.msdn.com/b/maximeb/ Resources
23. Thank you to our Sponsors PlatinumMedia Gold Silver Bronze
Hinweis der Redaktion
Much like astsadm –o exportInside the CAB file, only visible during operationManifest : Contains full listing of content and structure of the source site. Used to reconstruct source site and components during the import process.Export Settings : Catalog of all objects exported.Lookup List Map : simple lookup list that records sharepoint list item to list item references Root Object Map : Lists a hierarchy of dependant objects and ensures that any dependencies will be created prior to the dependants.System Data : Organises multiple manifest.xml when size of deployment exceeds a single manifest. Contains low level system data.User Group Map : List of users, security groups, security and permissions.View Forms List : List of web parts and denotes whether views or forms for lists.