Webinar: Synchronizing Geo-Distributed Sharepoint
•Download as PPTX, PDF•
2 likes•1,131 views
If you use SharePoint, you probably have several disconnected farms or a central farm environment. As your SharePoint content and user-base grows, it's time to consider the agility and cost-efficiencies of deploying distributed SharePoint. In this joint webinar with Metalogix we covered how your geo-dispersed workforce can access the SharePoint content they need—wherever they are and whenever they need it. We covered: - Issues with MSFT centralized farm deployment for global access - Latency and bandwidth issues in SQL solutions for SharePoint synchronization - How to achieve proper synchronization across larger, multi-farm deployments - How to ensure access to all SharePoint content to any user, anywhere
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (9)
Similar to Webinar: Synchronizing Geo-Distributed Sharepoint
Similar to Webinar: Synchronizing Geo-Distributed Sharepoint (20)
More from WithumSmith+Brown, formerly Portal Solutions
More from WithumSmith+Brown, formerly Portal Solutions (20)
Recently uploaded
Recently uploaded (20)
Webinar: Synchronizing Geo-Distributed Sharepoint
- 1. 1 Synchronizing Geo-Distributed SharePoint v Larry Wolter Director, Product Marketing, Metalogix Daniel Cohen-Dumani Founder and CEO, Portal Solutions Pamela James Brooks Solutions Engineer, Metalogix
- 2. 2 Agenda Centralized SharePoint SharePoint Global Architectures SharePoint Availability Distributed SharePoint and High Availability Issues with SQL and Out of the Box SharePoint Solution
- 3. 3 Centralized SharePoint Local users are happy. Collaboration increases. What about distant or remote users?
- 4. 4 Central Farm Deployment Source: Global Architectures for SharePont Server 2013, MicrosoftSource: Global Architectures for SharePont Server 2013, Microsoft “Remote users who access content hosted on a Centralized SharePoint server must access across a WAN or other network link. This can result in a slow end-user experience and excessive bandwidth consumption charges for the organization.”
- 5. 5 What version of SharePoint are you using? Insta-Poll ⃝ SharePoint Online ⃝ 2013 ⃝ 2010 ⃝ 2007 ⃝ 2003 ⃝ Not sure
- 6. 6 Microsoft Recommends Redesigning pages for faster downloads Using WAN accelerators Optimizing the entire network Costly solutions that mask the real problem
- 7. 7 Disconnected Farms Microsoft: “Deploying more than one farm greatly increases complexity.” Siloed content Governance and Compliance harder to implement Cost associated with managing each farm individually Duplication of resources No single source of truth
- 8. 8 SQL AlwaysOn Groups and Clusters 8 Asynchronous Synchronous (Real Time) One-way only Live, bi-directional mirroring within a farm Microsoft says “Forcing failover is a last resort...” Mission critical and non-essential content are treated equally Effects SharePoint performance without fast network Does not affect SharePoint performance Active-Passive support only – Reduced RTO and RPO
- 9. 9 SharePoint Availability Options In-farm Redundancy for Server Failures Does not include database servers No availability during power or network outages No availability during system upgrades Stretch farms introduced with SharePoint 2010 Costly network infrastructure requirements Not supported in 2013 – availability delegated to DB Limited Capability – Reduced RTO and RPO
- 10. 10 Do you have a distributed workforce (offices or workers 300+ miles from headquarters)? Insta-Poll ⃝ Yes ⃝ No
- 11. 11 Replication Value • Sync geographically-distributed SharePoint − Data availability during communication loss • 24x7x365 SharePoint availability • Active fault-tolerance and fail-over (COOP) • Limit content sync for security, privacy, and compliance reasons • Sync between SharePoint versions
- 12. 12 Benefits Keeping distant users engaged and active Making content available during disruptions Sharing information with agencies and partners Supporting global access Providing fast continuous access of content to all users
- 13. 13 Challenges Remote offices need latest content to be productive Difficult to integrate content over multiple SharePoint farms Inability to quickly recover from outages Low bandwidth and high latency slow worker performance
- 14. 14 Impact Downtime threatens key operations and wastes money Regulatory / compliance risks Mission critical SharePoint apps at risk Unhappy remote users don’t fully adopt SharePoint
- 15. 15 Common Replication Scenarios Multi-homing Sync across all SharePoint versions On-premises / cloud sync Intranet/extranet sync Intranet/Extranet Sync between geo- distributed farms Geo-Replication AdaptiveReplication CrossVersions On-Premises/Cloud
- 16. 16 Content You Can Synchronize Original Content Structure, Collections Security Permissions Workflows Web Parts Look and Feel Social Data Video & Data
- 17. 17 What system/solution have you deployed for synchronization? ⃝ Third-party replication solution ⃝ SQL Database Mirroring ⃝ SQL AlwaysOn ⃝ Virtual machine replication solution ⃝ Traditional backup and restore ⃝ Other ⃝ Not sure Insta-Poll
- 18. 18 Major Use Cases Geographic Synchronization- Fast reliable access to SharePoint for a global workforce • Sync critical operation centers and content • Deliver fast access to content to all users • Synchronize all geographically dispersed SharePoint farms • Extend SharePoint content to customers and partners • Sync content over poor or challenged networks Always On - Ensuring high availability for SharePoint content • Decrease Recovery Time Objective (RTO) and Recovery Point Objective (RPO) • Content available during planned and unplanned outages • Continuity of operations (COOP)
- 19. 19 Distributed SharePoint via Replication
- 20. 20 Distributed SharePoint via Replication
- 21. 21 Distributed SharePoint via Replication
- 23. 23 Norwegian Cruise Line is the innovator in cruise travel with a 45- year history of breaking the boundaries of traditional cruising Today, Norwegian invites consumers to “Cruise Like a Norwegian” on one of its 11 Freestyle Cruising ships, providing guests the opportunity to enjoy a relaxed cruise vacation on some of the newest and most contemporary ships at sea OVERVIEW SharePoint content from HQ to ships goes over satellite networks and requires high level of bandwidth Satellite bandwidth is unreliable and at a premium since it competes with on-board internet cafes and phones Stay in compliance with the International Safety Management (ISM) code CHALLENGES Better able to address deployment issues and concerns around metadeta and versioning Metalogix Replicator ensured reliable connectivity even during network latency Uses minimal bandwidth since only replicates changes, not entire documents RESULTS Norwegian Cruise Line
- 24. 24 U.S. Air Forces Central Command Located at Shaw Air Force Base, South Carolina, U.S. Air Forces Central (USAFCENT) serves as the air component for a 27-nation area within the U.S. Central Command (USCENTCOM) area of responsibility. Their Areas of Responsibility include the Middle East and Central Asia and support the efforts of our deployed forces in Iraq and Afghanistan. OVERVIEW CHALLENGE Ensure continuity of operations (COOP) Redundant farm failover capability during outages Content is available during communication isolation Increased productivity with faster access to content Point of authority content maintained RESULTS Majority of staff have short tours and high turnover Disjointed flow of information Needed both a failover system and a way to give everyone access to each other’s files Reconcile intranet, internet and extranet Connect main base with 9 other bases across multiple countries, including some with satellite feeds Photo Courtesy of U.S. Air Forces Central Command
- 25. 25 Demonstration
- 26. 26 Key Differentiators Immediate, live, bi-directional replication for all SharePoint types Replicate even over low bandwidth or challenged networks Synchronize across larger, dispersed, multi-farm SharePoint deployments Replication across any combination of SharePoint version or editions - 2007, 2010, 2013 Install and use within SharePoint - No additional software to run and manage Capabilities Synchronize Multiple Farms across Critical Operation Centers Enable fail-over between farms to provide High Availability to all content during disruptions Securely exchange content between Domains, Intranets and Extranets Synchronize. Replicate. Collaborate. The Most Powerful Way To Sync Multiple SharePoint Farms Metalogix Replicator
- 27. About Portal Solutions We deliver modern digital workplace products and solutions that help organizations share what they know and find what they need by connecting people, data, and content.
- 28. 28 Questions
- 29. 29 Next Step: Free Migration Assessment Additional Resources Free Migration Assessment Let Portal Solutions’ experts assess your current environment. We’ll help you: • Identify which platform is best for your organization (Office 365, SharePoint On-Premises, Hybrid scenario) • Map high-level business needs to high-level features/functions • Determine which migration approach and timeline is right for you Request a free migration assessment today! Yes, Sign Me Up! Download a copy of 7 Office 365 Migration Best Practices.
- 30. 30 Thank You!
Editor's Notes
- Bio: Larry Wolter is the Director of Product Marketing at Metalogix. Larry has over 20 years of experience in creating industry-first, high technology product and service solutions for the enterprise and federal government vertical markets. Bio: Daniel Cohen-Dumani is the founder and CEO of Portal Solutions. He has more than 20 years of experience in the field of computer science and software development. He is a frequent speaker at SharePoint conferences and user groups, and a recognized SharePoint and Office 365 subject matter expert. Bio: Pamela James Brooks is an Enterprise Solutions Engineer at Metalogix, supporting all products with a specialty in replication of Microsoft SharePoint platforms.
- SQL also provides us with some high availability options with clusters and AlwaysOn availability groups. A synchronous, or real time, cluster can offer live, bidirectional mirroring within a farm. [CLICK] But on a typical network, SharePoint performance is affected because changes need to be saved to both databases. [CLICK] An asynchronous cluster solves that problem by transporting changes to a remote database. [CLICK] Except it’s only one way and treats your mission critical documents and Christmas party photos as equally important. Microsoft also documents that forcing failover with these databases is a last resort and recommends considering other factors. References: “Forcing failover…” http://msdn.microsoft.com/en-ca/library/10e7bac7-4121-48c2-be01-10083a8c65af#AsyncCommitAvMode *** Intentionally left out Azure and Office365, since we don’t have a clear advantage over them. Azure high availability is currently a preview offering and high availability is not supported. Office365 offers high availability, but you sacrifice SharePoint capabilities (no customizations, limited Enterprise Edition features) by using them. CLOUD Cloud adoption is slow 9% deployed exclusively in the cloud (82% on-prem, 5% hybrid) 12% of IT decision makers plan to deploy exclusively in the cloud (62% plan on-prem only, 26% hybrid) Source: August 2012 Global SharePoint Usage Online Survey
- We’ve seen the benefits of a replicated SharePoint environment. Let’s look at the tools Microsoft provides out of the box to help. Stretch farms synchronize changes between separate SharePoint farms. Farms can be configured with multiple WFE and app servers for redundancy. [CLICK] Except stretch farms also require less than 1 millisecond latency and faster than 1 gigabit per second bandwith [CLICK] Multi-server farms still use a single database, which can be a failure point. And what happens to remote clients during power or network outages? Or system upgrades? SharePoint doesn’t provide a complete solution for our high availability requirements out of the box. References: Stretch farms require < 1ms latency and > 1 Gbps bandwidth (http://technet.microsoft.com/en-us/library/cc748824%28v=office.14%29.aspx#Section4) 2013 does not support stretch farms. (http://technet.microsoft.com/en-us/library/cc262485%28v=office.15%29.aspx#hwLocServers)
- Five (5) Values
- Difficult to Integrate Multiple SharePoint Farms – SharePoint is still growing and becoming the collaboration standard for the Military and Government Agencies. As such, the ability to integrate and synchronize content across these farms is a major issue every day. Remote offices not working on current copies of mission critical documents – When remote offices are not working on the same versions of the documents that are stored at HQ, the results can not only lead to errors, the consequences can be severe or even deadly. Suppose there is a critical change to a ship’s operations policy document at HQ that details the key instructions of securing armament. If that change doesn’t get distributed to all the ships in a timely manner, well, you can just imagine what could happen. No ability to quickly recover content in event of disaster – In a high tempo operational environment you need to ensure live or “hot” access to critical content during a planned or unplanned outage. Connections / performance to remote offices unreliable or slow – Let’s not forget that those who manage SharePoint still have Service Level Agreements to their end users who are distributed across Low Bandwidth High latency
- Main Point: However, there are major business impacts as a result of the challenges in distributed SharePoint Environments Downtime threatens key operations and costs real $ Unnecessary regulatory / compliance risks Key SharePoint applications at risk Remote users unhappy with SharePoint performance
- Main point: Here are the main replication scenarios that we see in customer environments today Geo-Replication - Local, national or global deployments of multiple SharePoint farms with a single server or multiple load-balanced servers in each farm. Intranet/Extranet: Firewalled replication is an ideal solution for an intranet to extranet scenario, where extranet changes would not be captured therefore limiting the abilities of end users outside of your organization. Only internal users on the intranet side are able to see private information and change content Adaptive Replication - Adaptive mode allows your farms to be set up in a dynamic topology which is always changing. For instance, in a ship to shore scenario, the ships talking to one port can later switch to another point of communication, pulling content from the closest server available. With Adaptive applied the destination dynamically and automatically decides where the best source for obtaining data is located. Cross Version Support - Cross version ensures that you can update your SharePoint systems while maintaining the continuity of operations, gradually converting your farms from older versions of SharePoint to the latest. Cloud/Continuity of Operations Secondary SharePoint farms deployed to support disaster recovery and COOP (Continuity of Operation) scenarios. In the event that your main SharePoint farm stalls or is disrupted due to a natural disaster, you can maintain the continuity of operations.
- Content – documents, list items, master pages, site content types, site columns, site templates, and document templates Structure – sites, site collections, libraries (document, picture, slide, …), lists (discussions, issues, contacts, …), and folders Permissions – users, groups, and permission levels (including permission settings for sites, lists, and items) Workflows – business processes using SharePoint out of the box, SharePoint Designer, Visual Studio, and Nintex workflows Web Parts – SharePoint out of the box, Bamboo, CorasWorks, OSI, and more Look and Feel – web parts, page layouts, site navigation, views, themes Social Data – notes, tags, and ratings And More – alerts, feature activation, recycle bin restores, … What we don’t replicate is the SharePoint configuration settings. Things you would find in Central admin. Why? We don’t expect the farm to be identical
- Let’s consider a scenario, you have two SharePoint farms. can run out of Azure, Amazon Web Services, or Rackspace doesn’t require same platform or capacity And synchronize changes between the two farms. Now we distribute those same users between our farms. Your end users access SharePoint on the farms closest to them for a smoother SharePoint experience. [CLICK] As everyone knows nothing is constant and outages do occur, whether planned or unplanned.
- [CLICK] And in the event of an outage…
- In order to ensure the continuity of operations, you can simply redirect your end users to your other farm. Since the content has been synchronized, they have continuous access to all the documents they need.
- When HQ server come back up, synchronization happens automatically and all farms are back in sync and you point the users back to their local server.
- Norwegian Cruise Line is the innovator in cruise travel with a 45-year history of breaking the boundaries of traditional cruising. Norwegian Cruise Line implemented SharePoint to consolidate its content and make it accessible from a central server. The main SharePoint installation delivers shore to ship content using satellite transmissions. With guests on board a ship using the same satellite connection, the bandwidth is at a premium. The Norwegian Cruise Line’s Intranet Manager was also tasked with satisfying compliance requirements by deploying the mission critical International Safety Management (ISM) system. Norwegian Cruise Line decided to implement Metalogix Replicator. With Replicator, they could use one-way shore to ship content synchronization. Another key Replicator feature is byte-level differencing to minimize demand on bandwidth. The feature enables synchronization of only the changes made to documents, as opposed to replicating an entire document. Likewise, incremental synchronization means that if the company’s satellite bandwidth is interrupted at any time, the content in progress will resume synchronization where it left off once the satellite feed is operational. From a user perspective, all the key features of Replicator are built right into SharePoint’s user interface. You are still working within the familiar SharePoint user interface. It just has a lot more features with Replicator included in the solution.
- U.S. Air Forces Central Command’s Airmen used many different systems, internet, intranet, and extranet sites to store, share and refer to information. It became a colossal problem in a command where more than 99 percent of the people assigned to USAFCENT only stay for an average of six months during a tour. New folks come in and have to learn a new system, a new filing method and a new job and then remember to pass that on to their replacements a few months later. Many locations and bases use “shared and network drives” to store large amounts of information. All bases did it differently and other bases or sites didn’t have access to each other’s files. The AFCENT team decided on SharePoint Servers to connect Shaw Air Force Base to other bases and sites worldwide. AFCENT also determined that they needed an event-driven replication process to pick up and operate from virtually anywhere in the world. Sites replicate to each other to provide active Continuity of Operations and backup sites capable of handling essential processes in the event of a systems failure, even when shared over a network connecting multiple countries and sites via satellite.
- SharePoint-based businesses face the growing challenge of managing SharePoint content with greater speed, efficiency and accuracy within and among farms. SharePoint administrators need a replication and synchronization tool that offers a comprehensive solution for increasing the performance levels of content collaboration across your SharePoint environment. Pamela is ready to show you a SharePoint farm synchronization tool, which we call Replicator.
- Clients come to us when they feel overwhelmed in their email inbox where it seems that it is the only tool their team is using to communicate information, they are buried in their inboxes trying to track what version of a file attachment is right or wrong. Their employees are frustrated with the inability to find a resource to help them to do their jobs or a past work product that would jump start their tasks. They end up being embarrassed when someone send the wrong version of a proposal or the wrong work product that erodes the customer or employees confidence. Often their employees feel dis-engaged and not connected. Of all the people we meet with, we find that we a great fit for only about half of those organizations. And it those cases, we can deliver dramatic results. We don’t know if we are a good fit for you but if addressing those issues is something that is important to you, we should try to find out more about the issues and impacts