AvePoint - Death of the FileShare, as you know it.


Published on

With files stored in myriad locations – file shares, cloud storage, and SQL Server to name a few – business users simply need one place to search and access the documents they need to complete their tasks.
Learn how to place all file share content at users’ fingertips via SharePoint 2010 – no migration, no additional storage costs, and no headaches

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

AvePoint - Death of the FileShare, as you know it.

  1. 1. Agenda AvePoint Company Overview SharePoint Overview Scale, Migrate, Protect, Manage AvePoint - DocAve Connector Real World Examples
  2. 2. Introductions Garth Luke (MCSE, MCP) Vice President, Sales - AvePoint California GM, AvePoint Australia Twitter : @GarthLuke LinkedIn
  3. 3. AvePoint Company Overview
  4. 4. AvePoint Corporate Overview Global Leader – SharePoint Governance & Management • Founded and Debuted in 2001 • Worlds Largest SharePoint-Exclusive Research & Development Team with 1,000Specialize Employees (600+ in R&D) d • Worlds Largest Provider of Enterprise-Class Governance and Infrastructure Management SolutionsExperience • 25 Offices, 13 Countries in 5 Continents & 8000+ Customers d • Depth-Managed, Microsoft Certified Partner • Comprehensive SharePoint Governance & Management Platform Invested • Offering True 24 x 7 Support - Microsoft Certified Technicians © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.
  5. 5. SharePoint Overview
  6. 6. Growing With SharePoint Enterprise Content Management Line of BusinessMore Valuable Applications Collaboration Tool Accelerated Content SharePoint Repository Growth More Complex AvePoint Confidential and Proprietary
  7. 7. SharePoint Needs No Performance Deployment Migration and SharePoint asInformation and Cost of IA Strategy Consolidation a ServiceArchitecture Optimization Brought to you by:
  8. 8. SharePoint Lessons• Information Architecture is ongoing – Changing Topology – Changing Taxonomy• Consolidation is actively happening – Global Farms – Central Farms• Service applications are the future – SharePoint as a Business O.S. Brought to you by:
  9. 9. Scale, Migrate, Protect, Manage
  10. 10. SharePoint Implementation Journey Scale Migrate Protect ManageInfrastructure Central Content SLAs UsersLoad Balancing Search enhanced Corrupt Data PermissionsConcurrently users Collaboration Disaster Recovery Data growth Brought to you by:
  11. 11. Content Migration to SharePoint 2010 & Cloud Websites Brought to you by:
  12. 12. Why migration doesn’t always make sense? • Problem begins with initialData in SQL Server migration • Need data for legal retention • SLAs still cover ALL SharePoint Year 0… Year 1… Year 2… Year3… content Active Content Stale Content Brought to you by:
  13. 13. Data Size & Composition SQL Storage Time• Understanding the composition of your data is VERY important• Data type usage is also equally important• Both will help you make calculated architectural decisions Brought to you by:
  14. 14. Storage costs can be challengingComfort level vs. Cost of Storage• What makes the most sense for SharePoint Data? Tier 1 Tier 2 Tier 3 SAN NAS Cloud Storage 1 TB 1 TB 1 TB Cost / GB / $12 $7 $1 Month Storage Cost / $12,000 $7,000 $1,000 Month Cost Savings / - $60,000 $132,000 Year Brought to you by: Brought to you by:
  15. 15. SQL Performance becomes a challenge SharePoints Ability to SharePoint Scalability with Extended BLOBs Scale 800 40 800 40 700 35 700 35 600 30 600 30 Requests Per Second (RPS)Requests Per Second 500 25 500 25 Seconds 400 20 400 20 Seconds (RPS) 300 15 300 15 200 10 200 10 100 5 100 5 0 0 0 0 300 Threads 400 Threads 500 Threads 300 Threads 400 Threads 500 Threads User Threads User Threads Native RPS RPS with Extended BLOBs AvePoint Confidential
  16. 16. What is stored in SharePoint? = BLOB (Binary Large OBject) Basically, a file Brought to you by:
  17. 17. What is stored in SharePoint? Metadata BLOB Brought to you by:
  18. 18. What is stored in SharePoint?Content DataBase Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Metadata BLOB Brought to you by:
  19. 19. AvePoint – DocAve Connector
  20. 20. The Basic Concept Brought to you by:
  21. 21. Anticipate Growth from the Start• Leverage RBS in SharePoint – 3rd party tools Stub• User and API driven Connector Upload Database User Web Front-end BLOB• Transparent user access• Transparent to development Disk Storage Brought to you by:
  22. 22. Architecture Scalability: Anticipate Growth Web Front-End Servers Application Server Application Server Storage Manager Connector Storage Cloud Storage File Server Clustered SQL Server Brought to you by:
  23. 23. Backing up BLOBsBecause we’ve changed the storage location of the content (BLOBs)… • Database-based backup solutions will NOT capture the content, only the metadata. • Need a plan to backup BLOBs synchronously – Out of sync timer jobs could cause data corruption! Brought to you by:
  24. 24. SharePoint Backup and Recovery • Hive • Solutions• Content DB Content • GAC • Cust.• Search Index • Gallery Features• Web Application Customisations • Site Definition• Site Collection• Site SharePoint Configurations • Central Admin DB• List/Library • Config DB• Folder Externalised Data (BLOB)• Item/Document • IIS Metabase• Version System Configurations • IIS Settings• Metadata Binary File (OS / • Web.Config SharePoint) • InetPub Brought to you by:
  25. 25. Real World Examples
  26. 26. • Reduced total migration time to Microsofts internal hosted SharePoint 2010 environment by two months Consolidation is actively happening• Migrated 12,000 site collections from SharePoint 2007 to SharePoint 2010• Transferred approximately 200 lists to SharePoint 2010 while maintaining customizations, metadata, and field values• Minimized business disruption by scheduling migration jobs to automatically occur off-hourshttp://www.avepoint.com/about/mtc-migration-to-2010/ Brought to you by:
  27. 27. Partnered with:A global oil and gas company headquartered in The Hague, Netherlands andwith its registered office in London, United Kingdom. The fifth-largest company inthe world (and the second-largest energy company)Customer name is confidential.Project Details:• Overall long term goal for SP : To use SharePoint as an ECM/Collaboration/Records Management platform;• 4 Year migration project : Total volume : 300 TB of legacy content migration (1 year & 80TB completed thus far)• Multiple different sources of content migration to SP2010 on Premise, O365 Dedicated (Livelink, FileSystem, SP2003, SP2007)• Using DocAve for Livelink, FileSystem, SP2003 & SP2007 Migration. Also using AvePoint Content Manager and Replication to restructure content on the fly (*Please note, that ALL AvePoint DocAve Modules fall within the same Web Based User Interface)Why was AvePoint Chosen over 8 other vendors?• A Genuine Global Presence;• The only vendor with real follow the sun 24x7 Support;• LAB resources that are accessible to the customer (Giving the ability to do like for like testing);• Ability & resources to do user acceptance testing;• Ability to architect a migration process as well as local resources to complete the work;• Single Vendor, Single UI, Single Automation UI : AvePoint’s DocAve Platform has 35+ Integrated Infrastructure Management Solutions within the same user interface;• The customer are able to use DocAve Migration Tools as well as their other DocAve modules to re- organise and manage their content. All through the same interface using other DocAve Modules;• During the first 3 month period, AvePoint delivered, tested and deployed 40 Design Feature requests. This is the power of AvePoint’s 600 man strong R&D Team (The Largest SP Dev team in the world).http://www.avepoint.com/resources/case-studies/
  28. 28. Real World Scalability Examples • Access 15TB of file-share data within SharePoint without migration • Reduce project time by 9-12 months • Enabled full SharePoint presentation & management of legacy file-share content without extra storage cost http://www.avepoint.com/resources/case-studies/ Brought to you by:
  29. 29. Real World Scalability Examples • SharePoint enabled 4,000 users (50% sales people), mobile access to legacy contents without changing user behavior • 7-8 TB of file-share data with customized fileshare rights management software • Heavy user access activity via File Explore view Saved 5-6 months project time without migration http://www.avepoint.com/resources/case-studies/ Brought to you by:
  30. 30. Real World Scalability Examples• Access 44 TB of file-share data within SharePoint without migration• Have files > 2GB in size• Challenge is very deep file structure and complex long file names, > 256 characters• Complex permission structure http://www.avepoint.com/resources/case-studies/ Brought to you by:
  31. 31. Real World Scalability Examples • 5 Petabytes of unmanaged file share • Use Connector SDK to provision libraries • Leverage records management and search to organize http://www.avepoint.com/resources/case-studies/ Brought to you by:
  32. 32. Thank-YouGarth LukeGarth.luke@avepoint.comTwitter @GarthLukeLinkedIn