5 Tips to Optimize SharePoint While Preparing for Hybrid
•Als PPTX, PDF herunterladen•
0 gefällt mir•478 views
For organizations planning to migrate to a hybrid deployment of the their SharePoint and Office 365 infrastructure, optimizing their current SharePoint is a crucial step in reducing the amount of work required for a successful migration, increase end-user performance and decrease the risk of an unsuccessful migration. Join Metalogix SharePoint expert Adam Levithan on March 17, 2016 for 5 Tips to Optimize SharePoint While Preparing for a Hybrid Deployment, a comprehensive live webinar where he unveils the top five optimizations that organizations need to consider before they plan to move to a SharePoint 2013 or SharePoint 2016 hybrid deployment. Key takeaways Such optimizations will help SharePoint Admins and IT professionals: Provide the best end-user experience, Gain early warnings as performance issues are developing Obtain better insight into the interdependency between SharePoint infrastructure and applications With the upcoming release of SharePoint 2016, hybrid deployments are quickly becoming the new standard for SharePoint deployments. Adam's help increased the success of several companies migrating to hybrid deployments and will be happy to share his insights, experience and solutions with attendees.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie 5 Tips to Optimize SharePoint While Preparing for Hybrid
Ähnlich wie 5 Tips to Optimize SharePoint While Preparing for Hybrid (20)
Mehr von Adam Levithan
Mehr von Adam Levithan (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
5 Tips to Optimize SharePoint While Preparing for Hybrid
- 1. Adam Levithan Senior Product Manager, Metalogix alevithan@metalogix.com @Collabadam 5 Tips to Optimize SharePoint While Preparing for a Hybrid Deployment
- 2. Agenda › Hybrid Drivers › 5 Tips › Questions
- 3. Drivers • Access to documents and content - regardless of technical issues • Ownership of information • Ease of Use • We already purchased it Business Needs
- 4. Drivers • Keeping all users engaged and active (no matter where they are or how they connect) • Providing the best possible speed and access to content even through disruptions • Keep confidential information shared with partners/agencies in approved environments (and safe) • Keep information authoritative across all systems Business Concerns
- 5. Drivers 6
- 8. SharePoint 2016 Hybrid Scenarios
- 9. TIP 1 Know your Hybrid
- 12. Authentication, Authorization & Permissions You Microsoft Azure AD 3rd party clouds/hosting
- 13. Considerations Service Level Agreements (SLA) Controlling Roll-out of Features Regulations/ Compliance Security
- 14. TIP 2 Plan your Architecture
- 15. Changes In SharePoint Over Time
- 16. What’s In your SharePoint? • URLs • Site Collection Name • Site Collection Size • Sub site count • Large Lists • Document Versions • Customizations • Site Location/position • Content DB – Size, Number • Site Collections per DB • Duplicate or Orphaned Site Collections • My Sites – Content DB, Size
- 17. Case Study: Moving Workloads Identity/ Authentication RecordTemporary TypeofContent Instant Message E-Mail Social Team Sites/ ExtranetEFSS Intranet Document/ Records Management Individual Team Enterprise Audience Originally presented at Portal Solutions http://www.portalsolutions.net
- 18. Case Study: Distribution of Content On-Premises On-Premises Identity/ Authentication Hybrid Customized Business Process Document/ Records Management Team Sites Intranet Regulated E-mail & Archives Cloud EFSS Extranet Social E-mail
- 20. TIP 3 Network
- 22. Network 23 • Where are you starting? • Where are you going? • What is the current load? • How much content are you moving? • How much time have you given yourself? • Can you migrate simultaneously?
- 23. Network Optimization Capacity Load Traffic Isolation • Web • Database • Service Applications • Search • Authentication Indexing
- 24. TIP 4 Database
- 25. Database Distribution • Provisioning overhead • Data isolation • Content storage • Query locks and throttling • Utilization • Recoverability • Resource Consumption • Availability System Services Site Collections Lists
- 28. Proactive 29
- 29. For the people Business User • Want system to work • Experience Productivity Loss SharePoint Team • Receive the first call • Hands-on troubleshooting Information Technology • Responsible for entire system • Dependent on SharePoint Team
- 30. • Architecture • Authentication / SSO / ADFS / Azure AD • Look & Feel/ User experience differences • Network • Network topology, Latency & Throttling of Transactions • Database • Keeping information up to date - Authoritative information • Compliance / Risk • Backup Services C Summary
- 31. Resources • http://hybrid.office.com/img/SharePoint_Book_2016.pdf • http://www.metalogix.com/Resources/Promotions/Diagnostic- Manager/white-papers-and-e-books/five-pillars-to-optimize-o365- readiness • http://www.metalogix.com/Events/Webinars.aspx March 24th – SharePoint 2016 for IT Pros Cloud & Hybrid SharePoint: Backup & Recovery Lessons from the Field Hybrid Dilemma Webinar Series 32
Hinweis der Redaktion
- For organizations planning to migrate to a hybrid deployment of the their SharePoint and Office 365 infrastructure, optimizing their current SharePoint is a crucial step in reducing the amount of work required for a successful migration, increase end-user performance and decrease the risk of an unsuccessful migration. Join Metalogix SharePoint expert Adam Levithan on March 17, 2016 for 5 Tips to Optimize SharePoint While Preparing for a Hybrid Deployment, a comprehensive live webinar where he unveils the top five optimizations that organizations need to consider before they plan to move to a SharePoint 2013 or SharePoint 2016 hybrid deployment.
- Access to documents and content - regardless of technical issues "If I can't get to my documents, I'll just use a different method for my workflow..." Availability to documents "You promised me 99.999% uptime and availability for all of my information - this is a Mission Critical operation and I need them all the time..." Ownership of information "Thanks for letting me manage the permissions to my files, it helps to ensure that I control who has access... wait , what do you mean I can't change who has access?" Ease of Use "Why does my information not synchronize and show up between the different portals and apps?"
- As a business there are larger concerns than with each individual in the organization. Ofcourse we want to provide and easy-to-use system, ofcourse we want it to be responsive and mobile for employees to be efficient. But on a larger scale, what happens if confidential information is leaked, what is the overall security of technology assets for all of our company. IT doesn’t put up firewalls because they’re fun toys to play with (quite boring actually) but because they’re necessary to have the confidence protecting sensitive content.
- I hope you don’t mind sarcasm Hybrid is a combination of any two things If you learn anything it’s that you’ve gone through these challenges before However you came to your decisions (check through your e-mail archive) before, you can do that again when applying it to the cloud, on-prem and office 365 hybrid dilemma
- We’ve seen this happen all the time Organizations want to change, but they have 2 years left on their enterprise agreement and don’t want to double pay for Office 365 You’re probably not in purchasing, so if you don’t know what your licensing is right now we’d highly recommend you go find out
- Good Guy Azure AD Who are you and what does your company want you to have access to This diagram is complicated, but it demonstrates the power of Azure Active directory How are you controlling this?
- Just bring up the overall SLA, don’t talk about the effect of the SLA This list could go on forever What are the outside pressures your organization is feeling Do you have Sensitive content within SharePoint? Is your content hosted in they country that regulates your company?
- Adam
- Adam So here’s the simple question: How is your current SharePoint environment configured? We could spend a whole session on the details of migration but I’d like to cover just a few of those items Large Lists Orphaned items My favorite, documents that have never been checked in. We actually came across these issues so many times that they’re included within our Migration Expert tool (it’s free, I’m not selling anything here) NEXT SLIDE
- Here’s a quick way to look at the phrase workloads It doesn’t align exactly with Microsoft, but pretty close When you look at what to put where, you can look at the different types of content – Temporary to Record Or you can look at the audience, individual to enterprise Of course the mix of this Kaleidoscope of collaboration can change for each organization but we’ll use this to demonstrate a real-life hybrid scenario
- So this is a real-world scenario – a regulated pharma company that Adam worked with in his consulting days They built a sophisticated Business solution in SharePoint 2010 and decided it needed to stay there because it would be to hard to move They then determined that the Intranet, with sensitive information about upcoming trial dates, would best be secured on premises Hey did use Cloud for extranet, for individual – non drug project – content, and they’re marketing team was already using Dropbox. Phew, so that’s pretty complicated an I hope that you don’t have to do that yourelves, At each step they made of choice of the value and risks involved with each type of content
- So let’s start on-prem First, CLICK those archives of yours might be most appropriately stored on-prem in file shares CLICK Then, CLICK if we think of the case study before, and your organization has invested in building a business process into SharePoint 2010, well then you still have that Ofcourse, CLICK here’s where SHarePoint (2013 or 2016 in a few weeks) comes in to build the hybrid story with Office 365 CLICK HOWEVER, it isn’t even that easy, because within SharePoint itself you have a decision CLICK to hybridize (yes I believe that’s an actual word) Site Collections, and especially One Drive for business Now I can hear some scratching heads because there’s a cloud, pretty straight forward, but then Office 365 is under another Azure cloud. This is quite literal that Office 365 uses Azure as its infrastructure. I could certainly draw Amazon Web services in the mix here too, it’s a perfectly good alterntanative, but as with most Microsoft strategies the power of these individual systems is that they are interoperable. Also, CLICK in the azure cloud you have several alternatives for storing those archive files that you identified in your ROT analysis – Azure blob storage And finally,CLICK to complete out the parrellal description to the case study we reviewed – who says your organization is only using products within the Microsoft system. You can add SalesForce in here and keep going with different cloud services that Microsoft won’t attempt to recreate. SO What are some of the considerations in all of these locations
- I love this cartoon Do I really need to say anything But let’s remember that throttling makes a lot of sense, how can any cloud service provider know the difference between a denial of service attack and a mass migration of content into its system Not only when moving your content to the cloud, but active hybrid scenarios it’s a good thing to know how your network performs
- Migrations/Initial Data Transfer Internal and External Bandwidth ExpressRoute Azure Storage Cloud Content Delivery Network Geographic Distribution (WAN link balancing) Page contents
- ERIC
- 1 Some content will simply not function in the cloud. Office 365 offers a different set of features than on-premises SharePoint. Some page components are not available, certain types of sites don’t exist and many customizations are either deprecated or illadvised. A review of all the content pages with a focus on what will and won’t work online can result in a great deal of data storage savings as pages are refactored to be cloud-ready. There is little point in wasting time and bandwidth trying to move items to the cloud that simply won’t function in that environment. 2 Document versions can consume a huge amount of database space. Prior to SharePoint 2013, each version of a document resulted in a duplicate of the object being stored separately in the database. Over time this can result in gigabytes of storage that serves no useful purpose. Examining each document library and modifying version control settings to truncate old versions can greatly reduce the amount of data in the current on-premises database and minimize what gets sent over the wire to Office 365. 3. Sites and workspaces that are accessed infrequently on-premises are unlikely to be accessed any more frequently in the cloud. These can either be excluded from the migration process or the content archived and the site deleted. A thorough review of existing sites by content owners often results in the discovery of many unused sites, the elimination of which can provide a tremendous amount of storage savings.
- SQL) Gain early warning of developing performance issues through alarms and alerts Understand the relationship between SharePoint infrastructure and applications Make the correct decisions about adding or removing servers to the SharePoint farm based on performance Analyze historical information for trending, capacity planning, and to quantify the impact of future changes
- Critical SharePoint is being used to support complex customizations and workflows, as a result the business users have expectations for the system’s performance. Plan future SharePoint needs based on metrics supporting growth and performance. SharePoint has had an unexpected outage and it’s hard to understand the cause at a single point in time. (Network, Server, SQL
- ADAM The business user expects perfect and consistent service and when things go wrong it should be easy to fix Who They are Not experts Just want it to work so they can do their day job Impact Productivity loss Frustration with performance and outages Damage to brand IT is held/measured based on an SLA Who they are Expectation of service which is difficult to manage Lack visibility and insight Lacks factual data Mostly hearsay or word or mouth Impact Noise and pain as a result Financial penalty impacts and scores Loss of credibility The SharePoint team experienced staff, funding, tools and process to proactively manage capacity and performance identify problems, troubleshoot and find root cause Provide tangible proof of problem Especially when its not a SP problem Network of storage Nasty site customization or list Impact act proactively - instead reactive cant predict impact of changes waste time and resources finding root cause loose credibility