Designing a Microsoft SharePoint 2010 Infrastructure Vol 2 part 31 ppt

MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-3 Objectives After completing this module, you will be able to: • Describe the range of upgrade requirement options and the available upgrade methods. • Describe how to plan an upgrade to SharePoint 2010. • Explain the key upgrade considerations. MCT USE ONLY. STUDENT USE PROHIBITED 15-4 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 1 Identifying Upgrade Scenarios SharePoint 2010 offers a range of business benefits for users and IT staff, so it is likely that you will need to plan an upgrade. In addition to your technical understanding, you must also understand the business benefits of performing an upgrade. This will enable you to manage expectations and identify new opportunities. SharePoint 2010 has well-documented upgrade options, but you must understand which is most appropriate for your organization—particularly if you must upgrade from older product versions or migrate from platforms other than SharePoint Products and Technologies. Objectives After completing this lesson, you will be able to: • Describe the benefits of upgrading to SharePoint 2010. • Describe the supported methods for upgrading from Microsoft Office SharePoint Server 2007 to SharePoint 2010. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-5 • Explain the options available for upgrading from older versions of Office SharePoint to SharePoint 2010. • Describe some of the solution-specific upgrade options that should be reflected in an upgrade plan. • Describe options for migrating from platforms other than SharePoint Products and Technologies to SharePoint 2010. MCT USE ONLY. STUDENT USE PROHIBITED 15-6 Designing a Microsoft® SharePoint® 2010 Infrastructure Benefits of Upgrading to SharePoint 2010 Key Points Solution architects must recognize the benefits of upgrading a current Office SharePoint product implementation to SharePoint 2010. Stakeholders and the business community may not be aware of the potential benefits, so you should know what SharePoint 2010 can do for your organization. This does not mean that you should be selling the new solution; instead, you should understand how the new functionality that is available meets your business requirements. You should also identify current customizations that can be replaced by out-of-the-box functionality available in SharePoint 2010. This functionality falls into the following areas: • Sites and collaboration. SharePoint 2010 offers increased site deployment flexibility and usability through: • A single platform for intranet, extranet, and Internet sites that is often more cost-effective. • The familiar Fluent user interface (UI). MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-7 • Search. The integration of Microsoft FAST Search Server 2010 for SharePoint technologies and the extension of People Search provides: • Greater speed and flexibility to search for, and drill down into, business information. • The ability to create more effective groups by identifying key team members. • Enhanced options for customized search solutions. • Community development. SharePoint 2010 has greatly enhanced social computing features that can deliver: • Personalized environments with My Site Web sites, wikis, and blogs. • The ability to tag and comment on business content. • Business insights. SharePoint 2010 provides greatly enhanced business intelligence (BI) options that provide: • The information that information workers need directly to their Web pages. • The flexibility to develop user dashboards for personal and organizational BI. • Integration with existing BI assets, such as Microsoft Excel® 2010. • Content management. Using SharePoint 2010, businesses can manage: • Business documents and records and Web content. • Deployment of governance strategies and requirements through policies and workflows. • User self-service. SharePoint 2010 enables users to develop business solutions without the need to place additional workloads on IT staff through: • The availability of composite development tools, such as SharePoint Designer 2010 and Dashboard Designer 2010. • Self-service site and My Site deployment. These are primarily user benefits and opportunities, but SharePoint 2010 can also provide platform and IT services advantages with better administrative tools, information logging, and deployment security. As a solution architect, you must be able to review the business requirements from corporate strategy to usability and map potential solutions to requirements. MCT USE ONLY. STUDENT USE PROHIBITED 15-8 Designing a Microsoft® SharePoint® 2010 Infrastructure Methods for Upgrading from Office SharePoint Server 2007 Key Points There are two supported methods to upgrade from Office SharePoint Server 2007 Service Pack 2 (SP2) or later to SharePoint 2010. In-Place Upgrade An in-place upgrade installs SharePoint 2010 on an existing Office SharePoint Server 2007 implementation by installing the binaries and using the PSConfig command to configure the installation. There are some prerequisites, such as a 64- bit server environment and SP2, which must be available for you to be able to use this option. This may sound the most obvious route to take, and it is recommended for small topologies, but there are advantages and disadvantages to this approach, as follows: • Advantages. An in-place upgrade can maintain farm settings as long as these are compatible with the new SharePoint 2010 options. Farm-wide settings and customizations are preserved and upgraded, although all customizations should be tested after the upgrade completes. This also means that URLs remain the same without any need for IT interventions. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-9 • Disadvantages. An in-place upgrade means that there will be server downtime during the upgrade process. This is affected by the size of the implementation (such as the number of servers) and the volume of data on the farm. There is also little opportunity for rollback, because the upgrade will run until completion or failure. The rollback scenario is to restore the original Office SharePoint Server 2007 farm. The in-place upgrade is not granular, because it works on a server and farm basis. You should identify all customizations, which may require manual intervention to ensure successful upgrade. You must also review the automatic upgrade of Shared Services Provider (SSP) services. You must have a thorough understanding of farm content, customizations, and configuration before you attempt an in-place upgrade. This is necessary so that you can estimate the effort and resources that you require to perform the upgrade, such as additional database capacity to hold two versions of the business data. It is therefore essential that you pilot an in-place upgrade, with real data, to ensure that you know whether an in-place upgrade is practical. Of course, this entails more effort and available equipment. Database Attach Upgrade The second option is to perform a database attach upgrade. This takes place on separate hardware that is currently in use on the Office SharePoint Server 2007 farm. The process involves the installation and configuration of the SharePoint 2010 environment. The implementation team then attaches the Office SharePoint Server 2007 content databases to the new farm environment, which triggers a schema update on the SharePoint 2010 farm. This has a greater cost in server and database hardware, because you must deploy a new environment while the old one remains in place. However, if you are migrating from 32-bit servers to 64-bit servers, this may not be an issue. This is because you will have to install new server versions on the new equipment, and it would be of no benefit to install the previous release to perform an in-place upgrade. The advantages and disadvantages include: • Advantages. The major benefit of this approach is the ability to maintain business productivity, because the original implementation remains available except during the upgrade of individual databases. For speed, you can plan to attach multiple databases simultaneously, which may significantly reduce the overall upgrade time. You can also reorganize your content databases, consolidating several together to take advantage of revised software boundaries. MCT USE ONLY. STUDENT USE PROHIBITED 15-10 Designing a Microsoft® SharePoint® 2010 Infrastructure • Disadvantages. This approach provides upgrades for site or SSP content databases, but does not automatically update all customizations. This means that you must re-create all customizations manually. The database attach upgrade is generally preferred for business continuity and control, because you can upgrade databases in a granular manner. You can create a read-only version of the content database and provide user access to this to mitigate loss of productivity. This minimizes rollback issues, although it requires additional database resources. For implementations where you have large content databases, this is definitely the preferred option. Hybrid Upgrade You can plan to use a combination of the two upgrade options. This hybrid approach enables you to take advantage of the simplicity of an in-place upgrade and also gives you greater control over the upgrade process itself. An example plan may recommend the following approach: • Detach content databases from the Office SharePoint Server 2007 farm. • Perform an in-place upgrade on the farm, which now has no content. • Reattach the content databases to the new SharePoint 2010 farm, which triggers a database attach upgrade. This provides some of the advantage and disadvantages of each upgrade path: • You must have a 64-bit environment, but you will upgrade customizations. • You have limited rollback options, but you will have granularity of content upgrades. • You will have downtime during the in-place upgrade, but you will be able to limit downtime by providing read-only copies of content databases. Additional Reading For more information about hybrid upgrade options, see http://go.microsoft.com/fwlink/?LinkID=200923&clcid=0x409. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-11 Methods for Upgrading from Earlier Versions of SharePoint Key Points The supported scenarios are all based on Office SharePoint Server 2007 SP2 upgrades to SharePoint 2010. However, you will not always be in this situation. You will find that user departments may have a range of versions available to them, including: • Windows® SharePoint Services 2.0 • Microsoft Office SharePoint Portal Server 2003 • Windows SharePoint Services 3.0 • Office SharePoint Server 2007 You may also find situations where you are asked to plan for “upgrades” from platforms other than SharePoint technologies. This is a migration rather than an upgrade, but it is often the case that these requests arise when you are planning to upgrade a platform. MCT USE ONLY. STUDENT USE PROHIBITED 15-12 Designing a Microsoft® SharePoint® 2010 Infrastructure You should include a full backup of the farm as part of your upgrade plan, irrespective of which version of Office SharePoint you want to upgrade. You then require a plan that details the upgrade steps that are necessary to successfully upgrade your deployment. The next step for any plan is an in-place or database attach upgrade, so much of your plan involves getting the farm to a point at which you can perform one of these. As with any upgrade, it is essential that you perform a complete technical and user acceptance test review of the deployment. Whenever you complete a database update, you should create new content database backups. Windows SharePoint Services 2.0 For Windows SharePoint Services 2.0 updates, you must first upgrade the platform to Windows SharePoint Services 3.0. This is because there was a major redesign of the database schema between these versions. The three options available are: • In-place upgrade • Gradual upgrade • Data migration In-Place Upgrade The in-place upgrade is functionally the same and retains the same issues regarding rollback. When Office SharePoint Server 2007 was launched, this approach was recommended only for development, test, or staging environments. If you opt for an in-place upgrade, you must have a plan for a full restore in case of a catastrophic upgrade failure. You must also test for capacity and time resource requirements. Gradual Upgrade A gradual upgrade is a granular side-by-side upgrade process that enables you to upgrade a Windows SharePoint Services 2.0 deployment by one site collection at a time. This is the most common form of upgrade, because you maintain control over the entire upgrade process. A gradual upgrade also enables you to support users through the changes. This may be a particular advantage if you have a large number of customized, or unghosted, pages because users have modified pages that are now held in the content database. Uncustomized, or ghosted, pages are Web Part pages that are based on site definitions and are readily upgraded. This option was not included in the upgrade options from Office SharePoint Server 2007 to SharePoint 2010. . now has no content. • Reattach the content databases to the new SharePoint 20 10 farm, which triggers a database attach upgrade. This provides some of the advantage and disadvantages of each. and available equipment. Database Attach Upgrade The second option is to perform a database attach upgrade. This takes place on separate hardware that is currently in use on the Office SharePoint. Server 20 07 Service Pack 2 (SP2) or later to SharePoint 20 10. In-Place Upgrade An in-place upgrade installs SharePoint 20 10 on an existing Office SharePoint Server 20 07 implementation by installing