domingo, 5 de febrero de 2012

Notes Chapter 5 – Sharepoint 2010 Unleashed

Migrating from Legacy Sharepoint to Sharepoint 2010


Microsoft provides for two out-of-the-box upgrade options: the in-place upgrade and the database-attach options.

The first and most straightforward option for upgrading to SharePoint 2010 is the in-place upgrade option. With this option, an existing SharePoint 2007 server is upgraded in place to SharePoint 2010. The advantage to this approach is that it is easy to perform and utilizes existing hardware and preserves custom farm settings such as Audiences or Search customization. The main disadvantage to this approach is that the hardware must be SharePoint 2010-capable and there is no going back when the migration starts.

The database attach upgrade process works off of a completely different concept. With this approach, you build the new SharePoint 2010 environment on completely different hardware and configure it to best practices. You have the option of completely rebuilding all farm aspects and can even have the new SharePoint environment serve as a farm target for multiple source farms of various versions (WSS, MOSS Standard, MOSS Enterprise). When the migration is ready to take place, it is done one content database at a time and is performed by attaching the database (or a restore of the database) to the new farm and upgrading it on that farm.

The significant advantage to this approach is that it is much more forgiving if there are errors, and it allows for easy fallback to the old farm if the migration fails.

The main disadvantage to this approach is that it migrates only content and does not migrate any farm settings, such as audiences or custom search settings.

This pre-upgrade check runs as an extension to the STSADM command-line tool, included in the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN folder on a SharePoint 2007 Server (either WSS or MOSS). When an environment is completely upgraded to SP2, this tool can be run without risk because it is read-only and makes no modifications to any of the files on the server.Run the pre-upgrade check by typing stsadm –o preupgradecheck

This farm passphrase is used for all new server additions to the farm, so be sure to store it in a safe place. The purpose of the passphrase is to avoid servers being added to the farm without prior consent of an administrator.

The database attach process is a much more risk-averse migration process and is subsequently more likely to be used for most environments. It has the significant advantage of

enabling SharePoint administrators to create new best-practice SharePoint 2010 environments and simply move the databases to a new farm and upgrade them there.

The exact syntax to use when upgrading is Mount-SPContentDatabase –Name DBNAME–DatabaseServer DBSERVER –WebApplication (where DBNAME, DBSERVER, and http:// are all names of your databases, servers, and webapps, respectively).

After migration, the site collection looks and feels exactly like a SharePoint 2007 site, assuming the option was chosen to keep the existing visuals temporarily during the

upgrade process. Site administrators need simply to click on Site Settings to see the new visual upgrade option available to them

Visual upgrade is not available when upgrading My Site. When upgraded, My Site immediately assume the new SharePoint 2010 visuals.

Use the in-place upgrade process only for those environments that are smaller than 30GB and for those environments without a large amount of customized web parts or other complexities.



No hay comentarios:

Publicar un comentario