Discover based on a case study how SharePoint and some additional solutions can be used to deploy a Worlwide Intranet.

1. SharePoint 2010Case StudyWorldwide Deployment Nicolas Georgeault Collaborative Infrastructures Consultant – Exakis SharePoint Specialist MAD about Horse-Ball (www.fihb-horseball.org) and Mojitos ;)

2. Whoam I? Nicolas Georgeault SharePoint Consultant @ Exakis Actually working on Hosted SharePoint at Orange Business Services Consultant & Speaker nicolasgt@exakis.com http://nicolasgt.exakis.com (CKS:EBE Blog on WSS3.0) http://www.facebook.com/nicolas.georgeault http://twitter.com/ngeorgeault Horse-Ball and Network enthusiast

3. Needsdefinition Worldwide company Divisions Geographically distant Publication Content deployment Procedure Content synchronization DRP needed Users can use SharePoint content offline Out of enterprise collaboration Extreme network situation Offline work 6 months on boats

4. Uni-Centric Deployment A single datacenter, with a geographically dispersed user base (Metro, State, Continent, Global).

5. Multi-Centric Deployment Geographically dispersed datacenters, with the user base clustered around them.

6. Hybrid Deployment Geographically dispersed datacenters, with a geographically dispersed user base.

7. Infrastructure base

8. Infrastructure base 3 Principal DataCenters Local and individual Farms 2 Web Front-End 1 Index + Central Administration 1 SQL Cluster for 2Tb 3 NetApp Filers All Databases hosted on Filers Index partitions hosted on Filers ForeFront TMG and UGA ForeFront protection for SharePoint

9. Disaster Recovery Plan

10. Disaster Recovery Plan 3 Secondary DataCenters (different than Principal ones) 1 Web Front-End 1 Index + Central Administration 1 SQL Server 2Tb - Log shipped ForeFront TMG and UGA ForeFront protection for SharePoint

11. Terminology…Who are the remote users? High bandwidth: 1 Mb/sec and up (aka broadband). Continental latency would be up to 125 millisecond round-trip. Global latency would be from 125 up to 300 millisecond round-trip. A low bandwidth would be a dialup modem, cellular phone, satellite link, etc. and usually associated with high latency.

12. WAN performanceThe relation between latency and experience Assuming response time of a LAN user at X (e.g. 2 seconds) for a first time access to a page (e.g. PLT1) A broadband user, with continental latency, would experience up to 2x-4x response time (e.g. 4-8 seconds) A broadband user, with global latency, would experience up to 4x-8x response time (e.g. 8-16 seconds) Low bandwidth, and extremely high latency response times’ experience is hard to predict

13. SharePoint 2010New capabilities

14. FSSHTTP and ODCA new, faster way to open and save files… Local client cache (Office Document Cache) and Incremental File Protocol (File Synchronization via Soap over HTTP) Requires both SharePoint Foundation 2010 and Office 2010 “cache” Office Rich Client Content Database Files (DOCx, PPTx…) ODC File Provider (WFE) FSSHTTP Client Web Front End Back End

15. FSSHTTP and ODCBenefit for remote users Modal-less save experience. Benefit of having an offline local copy that can be used when there is no network. Multi-Master conflicts are being resolved by the merge engine. Once the file is cached, FSSHTTP sends and receives only file diffs, requiring less network traffic than previous protocols (e.g. send the whole file back and forth).

16. Document centralisation Content deployment Synchronization Content deployment Synchronization

17. WhyDocAveReplicator?

18. Flexibility

19. Centralized publication Log Shipping Synchronization Log Shipping Log Shipping Synchronization Synchronization

20. Offline and External

21. SharePoint WorkspaceFormerly Groove Have an offline copy of a site/list End user is less affected by network latency Sync with the SharePoint Server in the background

22. 2 products in one…Collaboration client Users can create and maintain their own collaboration spaces. All documents can be saved and shared easily Optimized Synchronization protocol in extreme network situation

23. 2 products in one…SharePoint collaboration client Online/Offline SharePoint content SharePoint sharing content with enterprise external users Controlled by Groove Servers

24. Mobile Pages Light-weight versions of SharePoint pages Reduced network traffic, loads faster on narrow and latent connections Loads on both Mobile and Regular Browsers = 14 KB 432KB

25. Mobile Pages Benefit for remote users Recommended for high-latency users (above 300 ms RT) and/or narrow bandwidth Will allow navigating in a site hierarchy, fill simple forms, and consume textual data with acceptable performance

26. Office Web ApplicationWord, PowerPoint, Excel, OneNote

27. Office Web ApplicationsBenefit for remote users Remote users no longer need to download a large document just to review it or for a quick edit In most cases, Office in the browser has a faster time-to-first-page than rich client Does not require new versions of Office pushed to remote locations to utilize Metro XML Format (DOCX, PPTX…) and co-authoring features (=quicker adoption and faster ROI)

28. Shared Services ArchitectureFormerly Shared Services Providers In a cross-farm topology, some services can be federated (i.e. consumed from a remote farm

29. Shared Services ArchitectureBenefits… Simpler Admin experience, governing the organization from a single location Shared Services Architecture now allows a global company to consume from a “master” farm(s) It is now possible to enforce a company wide taxonomy from a single location Farm:Web Application :: Services associations allows for better isolation, load balancing

30. Uninterrupted Log-ShippingDeploying Read-Only Farms One R/W farm, with N R/O content R/O farms Locate content closer to remote users Govern traffic with URL’s Bonus: hot D/R farm

31. Windows 7 BranchCache Thin, expensive WAN links between main office and branch offices/remote areas High link utilization Poor application responsiveness Trend towards data centralization Branch Office / Remote Geo area Main Office

32. Distributed Cache Main Office Data Get Get ID ID Data Data Branch Office Get Get

33. Hosted Cache Main Office Get Get ID ID ID ID ID Data ID Data Data Data Search Search Get Put Offer Get Request Branch Office

34. Workloads R/W ratio, from the database perspective Write Most often provisioned for self service creation in an organization for enabling unstructured collaboration among small/medium teams. Site collection Administrator has the ultimate authority on the content and users, subject to IT governance. Hosting heterogeneous components, they typically serve a division/subsidiary of a large organization and tend to host MOST SharePoint workloads. Social feature set surfaces up in many workloads. This dedicated workload refers to the individual personalized sites. Records Management Internal or External corporate portal for sharing news, updates, workplace services etc. This is also usually the entry point to the centralized enterprise search. Typically hosted and authored centrally, but preferably replicated locally for viewers in large global organizations Team Collaboration Divisional Collaboration Document Management Central repository for storing, retaining and managing documents for legal and compliance reasons. Social Key scenarios include Large Scale Document Publishing and Collaborative Document Repository. Publishing Read

35. Read-Bound Workloads Includes the two Publishing Workloads: Intranet and Internet web sites, consuming search, as well as some flavors of the social workload.

36. Read-Write Workloads Includes team collab and divisional collaboration well as Document Management and some flavors of the Social Workload.

37. Write-Bound Workloads Includes flavors of Records and Document Management.

38. Questions?

39. Annex AvePoint Documentation

40. Understanding ReplicatorPROD107

41. DocAve Replicator Elevator Pitch 41 PROD107 “The Replicator allows you to set up a relationship between SharePoint locations, to keep the content in sync for global collaboration.” Definition in one sentence

42. Graphically Effectively replicate in low bandwidth situation using byte-level differencing and throttle control DocAve provides two-way replication Higher user-adoption rate Global collaboration made possible easily Local Server provides fast access speeds Replicate only the required contents 42 PROD107

43. DocAve Replicator to the Rescue 43 PROD107 Flexibility One-way, Two-way, one-to-many replication, within or across farms. Plus granular choice on what (and what else) to replicate. Event and schedule based replication Allows the latest changes to be replicated across locations for intense collaboration. Choose scheduled replication for everything else. Control network usage Efficient compressions and network throttling lets you minimize the impact of replication on your network infrastructure. Rule-Based Conflict Resolution Allow you to handle conflicts automatically (or notify the right people about it).

44. Flexibility 44 PROD107 Pick and choose what to replicate, down to the folder level, with or without security and configuration Replicate to one or many other locations Two-way replication to keep 2 locations in sync with each other, for intense collaboration Replicate within a farm, or across globally distributed farms Ability to map users/domains across farms Granularity and replication modes

45. Event Based (Real-time) Replication 45 PROD107 What is “it?”; there are 8 event triggers: New, Update, Delete, Move Check in, checkout, discard checkout List schema (definition) changes With event based replication, you can be sure that your data is globally up-to-date shortly after any changes – for near real-time collaboration Replicate as soon as “it” happens

46. Control Network Usage 46 PROD107 Need to control replicator network usage to prevent it from taking over WAN bandwidth (e.g. satellite) Turn on compression (zip up all the files) Incremental replication (only files that have change) Byte-Level Differencing (send over only parts of the document that have changed) Throttle network (limit bandwidth consumption) Connection retries (for unreliable connections) To help you make the most of your limited bandwidth

47. Byte-Level Differencing 47 PROD107 All files are ultimately a sequence of bytes. DocAve compares the document with previous replicated version, then sends only what changed. Only transmit the part of the file that changed

48. Rule-based Conflict Resolution 48 PROD107 Can skip, overwrite the loser, merge document versions, or save both copy and notify Decide who wins either by: One side (e.g. Source) always wins Last modified wins Highest version number wins Conflicts will arise when replicating

49. Other Features 49 PROD107 Ability to replicate when there is no direct network connectivity using offline mode (e.g. FedEx the replication file to other farm) Ability to replicate over Internet using standard protocols so firewall breach is not required Ability to “Backup Before Replication” so can undo Offline replication and extranet replication

50. References 50 PROD107 AvePoint Replication White Paper:Optimizing Data Access with Intelligent SharePoint Replication Case Studies Police Academy of the Netherlands uses DocAve to Replicate and Protect Mission-Critical SharePoint Data Global Banking For you and your customers