Designing a Microsoft SharePoint 2010 Infrastructure Vol 2 part 36 pdf

MCT USE ONLY. STUDENT USE PROHIBITED
Planning for Upgrading to SharePoint 2010 15-53
Logging and Status Reporting During Upgrades

Key Points
The use of logs and status reports may seem to be a post-planning activity. This
may be true, but you should plan for how your site administrators should use logs
and status reports during the upgrade process. You should also review logs and
reports on your test upgrades to mitigate problems later.
Logging During Upgrades
SharePoint 2010 provides a single upgrade log for each upgrade session, so there
will be a log for each session in a parallel database attach upgrade. This makes it
easier to review issues, because you can focus on specific upgrade tasks. This was
not the case with previous versions of Office SharePoint, where the single log just
grew larger with each upgrade. You should also plan for administrators to review
all entries in the upgrade error log, which only writes errors to disk. You can now
interrogate and report on all of the logs by using parsing tools, because the report
log schema is now structured.
MCT USE ONLY. STUDENT USE PROHIBITED
15-54 Designing a Microsoft® SharePoint® 2010 Infrastructure
Status Reporting During Upgrades
It is also useful for you to ensure that administrators track the status page, which is
now available throughout the upgrade process. The status report tracks the
upgrade history. Again, this enters multiple references for parallel upgrade sessions
If your administrators prefer to use the command-line upgrade options, these now
have a status indicator, so there should not be any doubt about whether the
upgrade is proceeding.

MCT USE ONLY. STUDENT USE PROHIBITED
Planning for Upgrading to SharePoint 2010 15-55
Mitigating Risks and Managing Failure

Key Points
For a smooth and successful upgrade, you must have a mitigation plan for all
possible upgrade risks.
Preventing Issues
If you prepare properly, you will have a much smoother transition, so remember
to:
• Perform farm analysis so that you understand the current SharePoint structure,
the business functionality, and the hardware platform. This will enable you to
develop both a cleanup schedule and a checklist for functional testing.
• Prepare the farm so that you can minimize issues such as service application
upgrade changes, solution deployments, problems, and platform support
issues.
• Identify and assess customizations so that you can redevelop or replace
customizations that do not work with SharePoint 2010.
MCT USE ONLY. STUDENT USE PROHIBITED
15-56 Designing a Microsoft® SharePoint® 2010 Infrastructure
• Test the upgrade in a test environment so that you can address functional and
user issues before you perform the production environment upgrade.
• Perform a database content check to ensure that data validity is not
compromised. Always check data with users.

Managing Failures
If you do encounter issues during your upgrade process, you must not panic.
There is a process for failure management, and you must build this into your
upgrade plan. The process is as follows:
• Determine the cause of failure. In the event of a failure, you should initially
consult the status page, the upgrade error log, and then the upgrade log. These
are designed to trap and report errors that you can then troubleshoot. Some of
these errors already have links to Knowledge Base and other documents that

refer to the errors that you may encounter.
• Fix the issue. This may seem obvious, but you must ensure that the people who
implement your plan have the knowledge and the authority to fix problems. If
you do not do so, you may find that the upgrade ended on Saturday morning
for an error that could have been fixed in a very short period of time.
• Resume the upgrade. You can restart SharePoint 2010 upgrades at the point of
failure. This means that you do not require a plan for backing out of a partial
upgrade because of a minor problem that you can fix, such as a minor
customization. In some cases, you might have to restart the upgrade to finish
upgrading your sites from Office SharePoint Server 2007 to SharePoint 2010.
For example:
• During an in-place upgrade, if the server restarts or the upgrade fails, you
must restart the upgrade process by using Psconfig.exe to upgrade the
remaining sites.
• During a database attach upgrade, any sites that cannot be upgraded will
be skipped. After you have corrected any issues in the sites (such as a
missing template or language pack, or the site being set to read-only or
having exceeded its quota), you can restart upgrade by using a Windows
PowerShell cmdlet to upgrade just the skipped sites.


MCT USE ONLY. STUDENT USE PROHIBITED
Planning for Upgrading to SharePoint 2010 15-57
Lab: Planning for Upgrading to SharePoint
2010

Exercise 1: Creating an Upgrade and Migration Plan
Scenario
Contoso, Ltd is about to acquire a smaller pharmaceutical company, Trey
Research. The SharePoint infrastructure at Trey Research includes Windows

SharePoint Services 2.0, Windows SharePoint Services 3.0, and Office SharePoint
2007 deployments. Trey Research includes SharePoint deployments over three
farms.
Your team must create an upgrade plan that will incorporate the intranet and
research sites at Trey Research into the central SharePoint 2010 farm. The Finance
department at Trey Research would like to keep its farm independent of the central
Contoso, Ltd farm. However, Contoso, Ltd IT will support this farm, and it will
require upgrading to SharePoint 2010. You should reuse Trey Research hardware
where appropriate.
MCT USE ONLY. STUDENT USE PROHIBITED
15-58 Designing a Microsoft® SharePoint® 2010 Infrastructure
Trey Research has a file share that it uses for document management. You must
ensure that the documents in this file share are transferred into the Contoso, Ltd
document site collection (Docs).
You have already gathered the requirements information about the three farms and
included it in an upgrade planning worksheet. You must now add your
recommendations on the Upgrade Approach, Steps, and Target Web Applications
to complete the upgrade planning worksheet.
The main tasks for this exercise are as follows:
1. Read the supporting information.
2. Complete the Upgrade Planning worksheet.

f Task 1: Read the supporting information
1. Read the lab scenario.
2. Log on to 10231A-NYC-DC1-15 as CONTOSO\Ed with the password
Pa$$w0rd.

f Task 2: Complete the Upgrade Planning worksheet
• In the E:\Labfiles\Lab15\Starter folder, complete the worksheet in the
Upgrade Planning Worksheet.xlsx file.

MCT USE ONLY. STUDENT USE PROHIBITED
Planning for Upgrading to SharePoint 2010 15-59
Module Review and Takeaways

Review Questions
1. What are the two options for upgrading to SharePoint 2010?
2. If you perform an in-place upgrade of a farm with SSP, what happens to the
services?
3. How can the use of read-only databases help you to minimize upgrade
downtime?

Best Practices Related to Upgrade Preparation
Supplement or modify the following best practices for your own work situations:
• Update your servers to SP2 of Office SharePoint Server 2007.
• Ensure that the environment is fully functioning before you perform an
upgrade.

MCT USE ONLY. STUDENT USE PROHIBITED
15-60 Designing a Microsoft® SharePoint® 2010 Infrastructure
• Run the Pre-Upgrade Checker tool to look for potential issues.
• Perform a trial upgrade on a test farm first.


MCT USE ONLY. STUDENT USE PROHIBITED
Planning for Upgrading to SharePoint 2010 15-61
Course Evaluation

Your evaluation of this course will help Microsoft understand the quality of your

learning experience.
Please work with your training provider to access the course evaluation form.
Microsoft will keep your answers to this survey private and confidential and will
use your responses to improve your future learning experience. Your open and
honest feedback is valuable and appreciated.
MCT USE ONLY. STUDENT USE PROHIBITED