1. Presented by Jacob Wilson Microsoft Practice Lead/Principal Bross Group http://sharepoint.jacobtwilson.com 1

2. 2

3.  MCTS Certified in SharePoint 2010 Configuration  MCTS Certified in MOSS 2007 Configuration  MCTS Certified in PerformancePoint Server 2007 Application Development  Microsoft Practice Lead/Principal at Bross Group  Worked with SharePoint 2003 and 2007 over the past several years  Architecture, Branding, Installation, Upgrade, Configuration, Custom Development, and Administration  Worked with SharePoint 2010 and FAST Search for SharePoint 2010 over the past year  Architecture, Installation, Upgrade, Configuration, Custom Development, and Administration  Twitter: http://twitter.com/MOSSLeadhttp://twitter.com/MOSSLead  LinkedIn: http://www.linkedin.com/in/titan80http://www.linkedin.com/in/titan80  Blog: http://sharepoint.jacobtwilson.comhttp://sharepoint.jacobtwilson.com 3

4.  Founded 2004  Based in Lakewood, CO  Certified Woman-Owned Business  Denver Business Journal Best Places to Work  Tier one vendor to over 40 clients in CO 4

5.  Consulting  Staff Augmentation  Project Delivery  Application Development  Direct Placement

6. 6

7.  Upgrade Best Practices  Upgrade Paths  Upgrade Approaches  In-Place  Database Attach  Hybrid 1: Read-Only Databases  Hybrid 2: Detach Databases  Metalogix StoragePoint  Metalogix Site Migrator 7

8. 8

9.  Install MOSS 2007 SP2 and the October 2009 CU which has updates to the pre-upgrade tool.  Do some house cleaning. Remove old content databases, web applications, and IIS sites.  Resolve any errors in the Server logs or SharePoint logs.  Upgrade SharePoint Servers and SQL Server to 64 bit architecture. 9

10.  Run the pre-upgrade tool to discover any potential issues.  Resolve any issues discovered by the pre- upgrade tool.  Restore production servers and database backups to Test servers for a test upgrade.  Document any issues in the Test environment for resolution in the production environment. 10

11.  Ensure that the current production environment or new production environment has enough resources available for the upgrade (RAM, processor, disk space, bandwidth, etc.)  Perform one last backup of the production servers and databases before running the upgrade in production.  Ensure that the current 2007 environment complies with the 2010 software boundaries. 11

12.  If using the database attach upgrade approach ensure that all databases are set to read only.  Do not add any servers to the farm during the upgrade process (servers will not be added to the database).  During and after the upgrade check the upgrade logs to resolve any issues. 12

13. 13

14. 14

15.  In order to upgrade from a SharePoint 2007 single server configuration to a SharePoint 2010 farm configuration you must do the following:  Create a new SharePoint 2007 server farm  Move the databases from the SharePoint 2007 stand alone server to the newly created SharePoint 2007 server farm  Upgrade the SharePoint 2007 server farm to a SharePoint 2010 server farm 15

16. 16

17. 17

18.  You CANNOT upgrade from SharePoint Server 2007 to 2010 if you are on 32 bit hardware.  You must first upgrade to 64 bit servers before performing the SharePoint upgrade process. 18

19. 19

20. *Best for upgrading complete installation which includes servers. Does not provide continuous access to content while upgrading. Databases upgraded one at a time.  Run all pre-upgrade tasks.  Run SharePoint 2010 setup on the server that hosts the Central Administration site.  Run SharePoint 2010 on remaining front-end web servers and application servers.  Run the SharePoint 2010 configuration wizard on the server that host the Central Administration site. This server, the configuration database, the services, and the content databases are upgraded sequentially 20

21.  Run the SharePoint 2010 configuration wizard on all remaining servers in the farm.  Confirm that SharePoint 2010 upgrade process ran successfully.  If Visual Upgrade is being used preview the sites in the 2010 look and then complete the changes if the 2010 look is acceptable. 21

22. * Best for moving to new hardware or new farm where users don’t need access to existing content during the upgrade process. Does not upgrade existing servers. Databases upgraded simultaneously.  Run all pre-upgrade tasks.  Create and configure a new SharePoint 2010 server farm.  Transfer all customizations to the new SharePoint 2010 server farm.  Detach the content databases from the SharePoint 2007 server farm and take the old farm offline (stop all services). 22

23.  Attach the content databases to the SharePoint 2010 farm and upgrade the content.  Confirm that the SharePoint 2010 upgrade process ran successfully.  Perform any final configurations (this includes load balancer settings and AAM’s). 23

24. * Best if users need continuous read-only access to existing data during the upgrade process.  Run all pre-upgrade tasks.  Create and configure a new SharePoint 2010 server farm.  Transfer all customizations to the new SharePoint 2010 server farm.  Set all content databases to read-only.  Perform a backup of the content databases. 24

25.  Restore database backups to new SharePoint 2010 server farm.  Attach content databases to the new SharePoint 2010 server farm and upgrade content.  Ensure the upgrade process ran successfully.  Ensure that all databases are online and not set to read-only.  Perform any final configurations (this includes load balancer settings and AAM’s). 25

26. * Best if you need to upgrade complete installation including servers while speeding up the in-place upgrade process. Existing content is unavailable during the upgrade process.  Run all pre-upgrade tasks.  Take the original 2007 farm offline (stop all services).  Detach the content databases from the original 2007 farm.  Run an in-place upgrade on the original farm servers, services, and configuration database. 26

27.  Attach the content databases to the original farm and upgrade the content.  Confirm the upgrade process ran successfully.  If Visual Upgrade is being used preview the sites in the 2010 look and then complete the changes if the 2010 look is acceptable. 27

28.  Run all pre-upgrade tasks.  Create a small temporary SharePoint 2010 farm.  Take the original 2007 farm offline (stop all services).  Detach the content databases from the original 2007 farm.  Run an in-place upgrade on the original farm to upgrade servers, services, and configuration database. 28

29.  Attach the content databases to the temporary small SharePoint 2010 farm.  Reattach the content databases to the original farm.  Confirm the upgrade process has ran successfully.  If Visual Upgrade is being used preview the sites in the 2010 look and then complete the changes if the 2010 look is acceptable. 29

30. 30

31. On average, 90-95% of a SharePoint content database’s storage overhead is comprised of content BLOBs. Network- Addressable Content- Addressable Cloud

32.  SharePoint 2007 or 2010 support, leveraging published and supported BLOB remoting methods (EBS and RBS)  Admin experience surfaced in SharePoint Central Admin  More than just a BLOB Offloading solution  Archiving  Tiered Storage / HSM  Extensive on-premise and cloud storage platform support  Intelligent Endpoint Management  A long list of enterprise-class features 32

33.  Generally faster content upload and retrieval.  Substantially for large (> 100MB) content and bulk operations.  Content can be compressed or de-duplicated, adding to storage cost savings.  Content can be encrypted for greater transmission and storage security.  Implement multi-tiered content storage chargeback models leveraging on-premise and/or Cloud-based platforms.  Substantially increase the speed of upgrade/migration processes from SharePoint 2007 to 2010.

34. BeforeAfterDifference Large File Uploads (10- 100MB)Regularly timed out Several seconds to a few minutes Ranged from seconds to minutes faster Index Crawl (Full) > 24 Hours < 5 Hours Over 400% Faster BeforeAfterDifference Content Database(s) Size442GB Less than 14GB 97% Smaller BeforeAfterDifference Dozens of use case scenarios Passed 100% None "StoragePoint reduced our largest database by over 98% as well as alleviated several challenges in our growing environment. With Storagepoint, we can now leverage our SharePoint investment on a much larger scale.“ Mark Wiley - Chesapeake Energy IT Manager

35. SharePoint EBS SQL RBS Introduced with WSS 3.0 SP1, supported (but deprecated) in SharePoint 2010. COM interface. Implemented as a Farm-wide scoped feature…all BLOBs are remoted. No orphaned BLOB garbage collection Capability of SQL 2008 R2, only supported in SharePoint 2010. Well documented.NET interface. Implemented as a content database scoped feature. Orphaned BLOB garbage collection present OOB. Stubs or HTML Redirects These are supported BLOB remoting methods. They break OOB features and are not compatible with SharePoint OM use.

36.  The SharePoint upgrade process moves BLOB’s behind the scenes and does re-associations which takes significant time.  Because the BLOB’s are externalized you significantly reduce the database operations that need to occur with BLOB’s which equals a faster upgrade.  Need a demo of the product?  Email jwilson@brossgroup.comjwilson@brossgroup.com 36

37. 37

38.  Whether you are migrating between SharePoint servers, upgrading from SharePoint Portal Server 2003 to Microsoft Office SharePoint Server 2007, upgrading to SharePoint 2010, or simply reorganizing your SharePoint content, SharePoint Site Migration Manager 2010 is an easy to use, convenient way of getting your SharePoint data across. With its familiar copy-and-paste style user interface, you can quickly migrate your SharePoint content between servers, while preserving your valuable metadata. 38

39.  Migrate SharePoint Lists, Libraries, and even entire Sites between servers.  Upgrade from SharePoint Portal Server 2003 to Microsoft Office SharePoint Server 2007, or SharePoint 2010.  Reorganize your SharePoint content.  Consolidate your SharePoint environments. 39

40.  Easy to use  Similar to the windows file explorer, SharePoint Site Migration Manager has a familiar, tree- based, copy-and-paste style user interface.  Migrate list types  Document Libraries, Issues, Tasks, Contacts, Announcements, Discussions and Custom Lists can all be migrated while preserving views, metadata, and user-edit information.  Retain your valuable data  All version chains, metadata, user-edit information, and most views can be preserved using SharePoint Site Migration Manager.  Connect to multiple sites  Connect to multiple SharePoint sites, across any number of servers, for easy consolidation, or distribution of your SharePoint data.  Work remotely  Do all the heavy lifting for your SharePoint migration from the convenience of your own machine. SharePoint Site Migration Manager connects to any SharePoint site that you can access with your browser, even those outside your organization's intranet.  Batch your work  Multiple list migration operations can be batched up for convenience, and re-run at any time. Run your migrations at night and view the results/logs in the morning.  Compliant  All migration activity is done through the supported SharePoint API's. There are no unsupported, direct writes to the SharePoint database. 40

41.  Supported source systems:  SharePoint Portal Server (SPS) 2003  Windows SharePoint Services (WSS 2.0 and 3.0)  Microsoft Office SharePoint Server (MOSS) 2007  Microsoft Online Services (MOS) [a.k.a. BPOS, Exchange Online, or SharePoint Online] -- Standard and Dedicated versions  SharePoint 2010 41

42.  Supported target systems:  Windows SharePoint Services (WSS) 3.0  Microsoft Office SharePoint Server (MOSS) 2007  Microsoft Online Services (MOS) [a.k.a. BPOS, Exchange Online, or SharePoint Online] -- Standard and Dedicated versions  Sharepoint 2010 42

43.  More granular control of the upgrade process – item level  More flexible upgrade process to minimize downtime  Can automate the upgrade process with PowerShell snap-ins  Can consolidate multiple environments as part of the upgrade process  Can perform cross product upgrades such as upgrading from WSS 2.0 to SharePoint Server 2010 Enterprise 43

44.  The Metalogix site migrator is only useful when you are migrating to a new SharePoint farm as you must have a source farm and a target farm.  Cannot use for an in-place upgrade.  Doesn’t move server customizations or custom solution packages. This would need to be performed manually just like any other upgrade approach that involves moving to a new farm. 44

45. 45

46.  View the supported features here:  http://www.metalogix.net/Products/SSMM2010/Features/ http://www.metalogix.net/Products/SSMM2010/Features/  Need a demo of the product:  Email jwilson@brossgroup.comjwilson@brossgroup.com 46

47. 47

48.  Upgrade Best Practices  http://technet.microsoft.com/en-us/library/cc261992.aspx http://technet.microsoft.com/en-us/library/cc261992.aspx  Upgrade Paths  http://technet.microsoft.com/en-us/sharepoint/ee517214 http://technet.microsoft.com/en-us/sharepoint/ee517214  Upgrade Approaches  http://technet.microsoft.com/en-us/library/cc262483.aspx http://technet.microsoft.com/en-us/library/cc262483.aspx  Metalogix StoragePoint  http://blog.storagepoint.com/ http://blog.storagepoint.com/  Metalogix SharePoint Site Migration Manager  http://www.metalogix.net/helpSSMM/ http://www.metalogix.net/helpSSMM/ 48