Common Migrations 2007 t0 2013 issues and planning Important

Migrate from MOSS 2007 to SharePoint 2010 - Step by Step

In this article, I'm walking through Migrating from MOSS 2007 to SharePoint 2010 using database attachment method.

Overview

1. Run Preupgradecheck in MOSS 2007 server.
1. Analyze & Fix the issues.
2. Take the back up of content database from MOSS 2007.
3. Restore the content databases backup to SQL Server of SharePoint 2010.
4. Create web application in SharePoint 2010.
5. Attach the MOSS 2007 content databases to SharePoint 2010.
6. Post Migration fixes

1. Run preupgradecheck in MOSS 2007 Server

This will be our primary analysis and reporting tool providing us with invaluable information regarding your SharePoint 2007 farm and actions that may be required to be taken prior to upgrading to SharePoint 2010. It is better to have October CU: http://support.microsoft.com/kb/976730/ where the preupgradecheck is enhanced further.

Run the preupgradecheck as below in command prompt:

stsadm.exe -o preupgradecheck

Once you get "Operation completed successfully", it will launch the “SharePoint Products and Technologies Pre-Upgrade Check Report”. It can also be located under the following location;

%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\Logs\

1(a). Analyze the report and Fix the following settings:

• I would strongly recommend you to document your current environment first! see 25 Things to Document before You Start SharePoint Migration
• Identify any third party components used and deploy them to SP2010. E.g. Nintex, 3rd party features, including web parts, solutions and custom workflows
• Setup Incoming/Outgoing email settings in SP2010 environment
• Modified Web.Config entries
• Alternate Access Mappings (AAM)
• Replicate Quota templates & Managed Paths to SP2010
• Fix Event Receivers: Fix "Event Receivers Fix "Event Receivers Missing" issue in SharePoint Migration
• Fix missing web parts Fixing "Missing Web Parts" issue in Migration
• Fix missing features Fix "Features Missing" issue in SharePoint Migration
• Find and Delete Orphaned Users
• Empty Recycle Bins Empty SharePoint Recycle Bins Programmatically with PowerShell
• Check-in All the checked out files
• Fix orphaned sites: Find and Delete Orphaned site collections in SharePoint
• Limit and Cleanup Versioning
• Trim Audit log Trim audit log to Improve Performance
• Delete Closed Web Parts: Closed Web Parts in SharePoint - How to Find, Restore and Delete
• Fix “Content database with modified database schemas” issue when upgrading to SharePoint Server 2010 : http://sharepointnomad.wordpress.com/2010/12/12/fix-content-database-with-modified-database-schemas-issue-when-upgrading-to-sharepoint-server-2010/

2. Take the Content Database Backup from MOSS 2007

Set the database to read-only before taking backups.

Set the database as read only:

1. On the MOSS 2007’s database server, click Start, point to All Programs, Microsoft SQL Server, and then click SQL Server Management Studio.

2. Traverse to Databases node by expanding the tree.
3. Right-click the name of the database that you want to set to read-only, and then click Properties.

4. In the Properties dialog box, click the Options tab.

5. Under State, select the Database Read-only to True, and then click OK

Backup the database:

Follow these steps to take back-up:

1. Traverse to Databases node by expanding the tree.
2. Right-click the database you want to back up, point to Tasks, and then click Backup Database

3. In the SQL Server Backup dialog box, specify a name for the backup, select Back-up type - Full, select a destination, and then Click OK to start the backup process.

4. Repeat these steps to back up the databases that are used by MOSS 2007 in the environment.

3. Restore the back up on SharePoint 2010’s SQL Server:

1. Open the SQL Server Management studio, traverse to “Databases” node. Then right click the “Databases” node and choose “Restore Database…” from the context menu.

2. Specify the Database name, Restore Source, Destination, File names in the screens.

3. Click “OK” to start the restore operation and Wait for the restore to complete! The time of restoring database depends upon the database size and server’s capacity.

4. Create web application in SharePoint 2010

1. In the SharePoint Central Administration, click on “Application Management” and click on “Create or extend Web application” under “SharePoint Web Application Management”.
2. Again click on “Create Web application”. Set the settings according to the needs say http://SharePoint2010.company.com
3. Don’t create any site collection.
4. Install & Copy the solutions, file system changes (like images, themes) from MOSS 2007 to MOSS 2007 servers.

Remove content database of the newly created web application in SharePoint 2010

Now, we need to delete the content db of the newly created web application in order to avoid any URL conflicts. Run the below stsadm command:

stsadm -o deletecontentdb -url http://SharePoint.company.com -databasename < MOSS2007_Migration_Content>

5. Attach restored database with the newly created web application in SharePoint 2010

Test the content database

Before attaching the content databases to the Web applications, use the Test-SPContentDatabase PowerShell cmdlet to verify that all of the custom components that you need for that database. It checks for all artifacts such as feature, setup files, web parts,etc that are referred in the content database are installed in the farm and provide you with an report.

Test-SPContentDatabase -Name <DatabaseName> -WebApplication <URL>

Delete the corrupted objects

stsadm -o databaserepair -url <URL of SharePoint site> -databasename < name of database> -deletecorruption

Finally, we need to attach the restored MOSS 2007 database to MOSS 2007 by running the STSADM

1. The Content DB containing the root site collection is always applied first.
2. The other content DBs can be applied in any order.

Important:

Attach the Content DB of the Root Site collection First. And then Attach the Content DBs of other Site Collections.

stsadm.exe -o addcontentdb -url http://SharePoint.company.com -databasename < MOSS2007_Portal_Content>

Or you can use the PowerShell cmd-let: Mount-SPContentDatabase

Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL> 

Post Migration fixes

Once the content database attachment process is over, we have to manually fix the below things:

• Fix the List/Site templates: Migrating SharePoint 2007 Site/List Templates(.stp) into SharePoint 2010
• Remove any unused/classic web parts Remove a Webpart programmatically using PowerShell
• Fix the alerts: Fix Alerts after URL Change in SharePoint Migration
• Fix Incoming E-mail settings: Find All Incoming E-Mail Enabled Lists and Libraries in SharePoint
• Fix InfoPath form URLs: Migrate InfoPath Forms to SharePoint 2010
• Perform the Visual upgrade to get the SharePoint 2010 Look and Feel if needed. Visual Upgrade All Sites in a web application Using PowerShell

Unit Test:

Browse the migrated sites in SharePoint 2010 and check their look& feel and functionality.

Before and After:

References:

• Tech-net guide - Perform a database attach upgrade: http://technet.microsoft.com/en-us/library/cc303436.aspx
• Resolving Migration issues: http://technet.microsoft.com/en-us/library/cc262967.aspx

 

Preupgrade Issues and command

1.       No source code is available for MOSS 2007 customizations done earlier.
Resolution: Thankfully dlls were compiled for any CPU. We took the copies of dlls from GAC in MOSS 2007.
2. MOSS 2007 with SP1 and we can not install SP2 on production due to possible uncertain issues that can happen with existing live portal.
Resolution: SP2 is required to run the preupgrade checks before migration. Created a separate 64 bit MOSS 2007 environment with SP2. Restored database backup from production MOSS 2007 environment to test MOSS 2007 environment. Upgraded the database to SP2.
3. No solution packages are available to identify other files such as custom images and aspx pages.
Resolution: There were few custom images used on the portal. Copied all the images from production environment to test MOSS 2007 environment without replacing the duplicates. Filtered the new images folder by modification date to identify custom images used.

 

5.1 file not found, could not load assembly, etc.

Resolution: Added dlls in GAC of test MOSS 2007 environment. Since there were many dlls used (bad programming by old MOSS 2007 developers). Every control, web part had separate dll. Created PowerShell script to add dlls in GAC using gacutil.

Below script adds all the dlls in current directory to GAC and restarts the IIS to take effect.

1 2 3 4 5 6

foreach ($file in Get-ChildItem -Filter "*.dll" ) { Write-Host $file.Name .\gacutil.exe /nologo /i $file.Name } iisreset

5.2 The control is not marked as Safe Control.
Resolution: Copied all the custom safe control entries from web.config of production web application to test MOSS 2007 web.config.

5.3 Web part/control errors due to missing appsettings in web.config
Resolution: Copied all the custom appsettings from web.config of production web application to test MOSS 2007 web.config.

5.4 Error in webparts using SSP (user profile).
Resolution: Removed these web parts since they were no longer required. You can review the code using reflector and create a new webpart for the SharePoint 2010 environment.

When I restored the database of SP 2007 (64 bit) on SP 2010 web application, everything was working perfectly fine when I accessed site using application server url but when I used web server url, only top level site collection was working. For other site collections, I was getting page not found error. But alternate access mappings saved me and thanks to Paramesh for his help on Microsoft forum.

2. After migration to SharePoint 2010 site, some of the navigation links were missing from quick launch, top navigation bar and TOCPart web part. This was due to the default limit of 20 for global and local dynamic child limit under navigation settings. Increased the limit to 100 and it solved the purpose. Used below PowerShell script to increase the limit.

1 2 3 4 5 6 7 8 9 10 11

$webapp = Get-SPWebApplication http://sp2010server:1000 foreach ($s in $webapp.Sites) { foreach($web in $s.AllWebs) { $pubWeb = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web) $pubWeb.Navigation.GlobalDynamicChildLimit = 100 $pubWeb.Navigation.CurrentDynamicChildLimit = 100 $pubWeb.Update(); } }

3. Moving site to https binding.

We need to install SSL certificate on server in order to open site in secure i.e https protocol.
Modified website bindings in IIS and added https binding with above SSL certificate. Modified alernate acces mappings to add https url.

Read more: http://www.sharepointdiary.com/2011/09/migrate-from-moss-2007-to-sharepoint-2010.html#ixzz3CLyTU86h

Monitoring tools Sharepoint 2013

Overview of monitoring tools

There are many tools for you to monitor SharePoint 2013 and troubleshoot problems. Different tools cover different aspects of the environment, although there may be overlapped areas. Consider which tools can maximize your monitoring benefits. The following monitoring tools are available:

• SharePoint Health Analyzer
  On the Central Administration home page, click Monitoring, Health Analyzer. You can use this built-in feature to analyze and resolve problems in the following areas: security, performance, configuration, and availability. Health Analyzer rules are predefined and run at scheduled intervals, such as hourly, daily, weekly, and monthly. If an error is detected, the corresponding rule is triggered. Each rule has a brief explanation about why the error occurs and provides you with a link to a detailed article that contains step-by-step guidance to resolve the problem. When you take actions by following the guidance, you can re-run the rule to verify resolution. If the error does not appear in the list, the problem is resolved.
• Timer Jobs
  On the Central Administration home page, click Monitoring, Timer Jobs. SharePoint 2013 uses configurable timer jobs to collect health data and then writes the data to the logging folder and to the Logging database. The data is then used in reports to display the health status of the farm servers.
  You can reschedule a timer job, enable or disable it, and run it on demand. Daily, weekly, and monthly schedules also include a window of execution. The timer service will select a random time within this interval to start running the timer job on each applicable server. This feature is appropriate for high-load jobs that run on multiple servers on the farm.
  
  

  Note:
  Running timer jobs at the same time on all servers on the farm can affect system performance. You must schedule them carefully to avoid overlap with other timer jobs.

  
  
• Reporting
  On the Central Administration home page, click Monitoring, Reporting. This feature lets you configure diagnostic logging and data collection, and view administrative and health reports. Because some configurations will use up drive space and adversely affect system performance you must carefully plan what configurations to set.
• Windows PowerShell
  Windows PowerShell is a powerful tool for monitoring SharePoint 2013. You can run commands to obtain the exact logs that you want to view. For more information, see View diagnostic logs in SharePoint 2013.
• System Center 2012 - Operations Manager with System Center Management Pack for SharePoint Server 2013
  System Center 2012 - Operations Manager is a powerful monitoring platform that lets you monitor services, devices, and operations for many computers in a single console. By using Operations Manager, you can view status, health, performance information, and alerts generated for availability, performance, configuration and security situations. For more information, see Operations Manager (http://go.microsoft.com/fwlink/p/?LinkID=226376).
  To use Operations Manager to monitor SharePoint products, you must install System Center Management Pack for SharePoint Server 2013. You can use this tool to monitor events, collect SharePoint component-specific performance counters in one central location, and raise alerts for operator intervention as necessary. Download and install System Center Monitoring Pack for SharePoint Server or System Center Monitoring Pack for SharePoint Foundation.
• Event Viewer
  Event Viewer is a Microsoft Management Console (MMC) snap-in. It lets you browse and manage event logs. It is a very handy tool for troubleshooting problems. You can filter for specific events across multiple logs, and reuse useful event filters as custom views. For more information, see Event Viewer (http://go.microsoft.com/fwlink/p/?LinkId=253618).
• SharePoint Developer Dashboard
  This tool provides diagnostic information that can help a developer or system administrator analyze performance of SharePoint Web pages. This utility can help if a page is loading slowly, a Web Part is not performing, or if a database query on the page is not performing. The SharePoint Developer Dashboard is disabled by default. You can enable it by using Windows PowerShell. For more information, see SharePoint Developer Dashboard (http://go.microsoft.com/fwlink/p/?LinkID=199580).
• Windows Management Instrumentation (WMI)
  WMI provides many classes for you to monitor the SharePoint 2013 environment. For each manageable resource, there is a corresponding WMI class. For more information, see WMI Overview (http://go.microsoft.com/fwlink/p/?LinkId=188652).
• SQL Server Reporting Services (SSRS)
  SQL Server Reporting Services provides a full range of ready-to-use tools and services to help you create, deploy, and manage reports for your organization. It also has programming features that let you extend and customize reporting functionality. By using SQL Server Reporting Services, you can create interactive, tabular, graphical, or free-form reports from relational, multidimensional, or XML-based data sources. You can publish reports, schedule report processing, or access reports on-demand. You can use SQL Server Reporting Services to create reports based on predefined models, and to interactively explore data within the model. You can select from a variety of viewing formats, export reports to other applications, and subscribe to published reports. The reports that you create can be viewed over a Web-based connection or as part of a Windows application or SharePoint site. For more information, see SQL Server Reporting Services (http://go.microsoft.com/fwlink/p/?LinkId=253387).

Migrating from SharePoint 2007 to SharePoint 2013

SharePoint 2007 provides a great collaboration platform, but as the business matures, so should the platform. Now-a-days companies that invested heavily in SP 2007 are now developing a SharePoint strategy may be confused regarding migration to SharePoint 2010 and or 2013. Needless to say, an upgrade to a newer version is a great undertaking for IT. However, besides the IT involvement, there is also training and end-user adoption. Training and end-user adoption are budget intensive and during this period end users are not as productive as they used to be while working within the old, familiar version of the platform. Companies are looking for a way to migrate to SP 2013, the latest version, however, being 2 versions behind means going through 2 phases of migration as well as end user training and adoption. Even though, from a technical and Microsoft supported perspective, there is no option to jump from 2007 straight to SharePoint 2013 without using third party tools, there is an option to cut the cost and the effort of migrating to the latest 2013 version by almost half by first migrating to 2010 as an interim migration utilizing a trial license for 2010. You can accomplish this without purchasing full version of 2010 and skip the associated end user training and adoptions steps.

Even though there is an established method of upgrading from 2007 to 2010, this approach is often not a viable option due to the difference in the hardware support for each version. If 2007 version was supported on 32 bit servers, 2010 is only supported on 64 bit environments. In this case, an upgrade is just not an option and attaching the database is the only supported way of moving to 2010. In moving from 2010 to 2013, a database upgrade is the only officially supported option. From a high level point of view, this is a "database attach" migration approach that will entail the same steps as any other migration from one version of SharePoint Platform to the next. They are:

 Assessing and updating your 2007 Environment

 Planning for an interim 2010 environment with the emphasis on SQL Server

 Planning for and setting up the 2013 Environment

 Initial database migration from 2007 to 2010 and testing on 2010

 Final database migration from 2010 to 2013

Going straight to SharePoint 2013 from 2007 is not necessarily the right approach for companies with a lot of customizations and widely used, third party components or companies with user base that is not familiar with office 2010 products. However, this is still a viable option that greatly benefits other companies. Here are some other important steps not covered within this posting, but definitely worth mentioning.

 Planning for End User training for SharePoint 2013

 Developing both a Migration Cut-Out and Communication Plan

 Planning for End-User support on final SharePoint 2013 platform

All three above mentioned items should be initiated before you begin the migration process.

Assessing and Updating 2007 Environment (Preparing for migration)

This preliminary step of updating/patching the 2007 environment as well as cataloging and fixing any pre-upgrade issues, can also be one of the most resource intensive from the IT perspective. First and foremost, the 2007 environment needs to be updated to the latest Service Packs and CUs, the minimum is to have at least Service Pack 2 installed. Before applying the latest updates make sure that your environment is stable enough to go through this procedure. Also, make sure that during the application of Service Packs or the latest CUs, you are following the steps outlined in the procedures for applying

these updates. For the list of the latest updates please refer to this resource: http://technet.microsoft.com/en-us/sharepoint/bb735839.aspx

Even if you are not running the upgrade, it is strongly recommended to run the pre-upgrade check tool, which will help to gather a report on any issues the environment might have in the upgrade process as far as custom elements or unsupported customizations are concerned. Another benefit of running the pre-upgrade check tool is to aid in the process of cataloging all installed components, customizations, servers and important configurations of the environment.

In order to run the pre-upgrade check tool, open up the command prompt, navigate to the (12 Hive)\bin directory and run the following command:

STSADM –o preupgradecheck

The output of the pre-upgrade check will result in an Html report that will open up in the browser. You can alternatively access this report in the (12 Hive)\LOGS directory. After addressing the issues that preclude the content databases from upgrade, you should repeat the above step and re-run the tool to make sure that all issues are resolved. You might have to repeat this process several times until your databases are ready for upgrade.

Note: the pre-upgrade check will not modify your 2007 content database

To catalog all customizations, you can use the Upgrade worksheet from Microsoft http://www.microsoft.com/en-us/download/details.aspx?id=28772

As the last preparation step you should catalog all content databases with their respective web applications and the list of site collections residing in each content database, as you will have to identify the owners of those sites or people responsible for the site content and administration. This is an important step as this is a list of people that would be the first level of the migration testing.

From the 2007 Central Administration site, go to Application Management and click on the Web Application List. Under each web application you will find a list of their respective databases. Catalog all web applications and their databases as well as the list of all site collections for each database. To list all site collections for each database you can use the following command:

From the command Prompt window, navigate to (12 Hive)\bin folder

Run STSADM –o enumallwebs > sitelist.xml

From this report you can catalog all necessary information using this template as a sample [link to the Content Databases Catalog].

At this point your SharePoint 2007 environment is ready to have it’s databases migrated to SharePoint 2010

Plan and set up the interim 2010 environment

In the scenario of database migration from SharePoint 2007 to SharePoint 2013, the SharePoint 2010 environment is an interim environment, serving only to upgrade your 2007 content databases to the 2010 content database schema, thus preparing your content databases for 2013 upgrade. Due to this process, there is no need to plan for service applications, high availability, backup and recovery or user load and scalability. In fact, you can use a single Virtual server to install the SharePoint 2010 farm. The only planning that will have to be done is on the SQL server side. SQL server has to be sized appropriately to handle the databases that are restored from the 2007 SQL content database backup allowing some room for expansion in database size as well as database log size during the DB schema upgrade process and many transactions that will place while the upgrade process run., That requires you to make sure that the DB log files have room to expand to accommodate the changes that will be occurring. The above mentioned "Content Databases Catalog" sample catalog can help you approximate the size of DB expansion that you should allow on the new SQL 2010 Server. Once your 2010 Interim Farm is set up, make sure it is updated with the latest Service Packs and CUs. The list of latest updates tomay be found at: http://technet.microsoft.com/en-us/sharepoint/bb735839.aspx

Planning and setting up the end state 2013 Environment

Even though you have completed all steps described above, this is an important preparation step and probably one the most IT intensive. You need to plan and set up your end state 2013 Environment before you start the migration of databases from 2007 to 2010. Your SharePoint portal should be available for end users in read only mode in 2007 version, from the point that you set up your databases to read only mode, until you fully migrate to 2013.

Database migration from 2007 to 2010 and testing on 2010

Before migrating databases, set the databases that you are planning to migrate to read only mode which will ensure that users cannot add, modify or delete any content, so users do not update any information and they do not lose their changes while the databases are being moved to 2010 and subsequently 2013. The DBs can be set read only from the SQL Management studio by selecting the content database name, clicking the right mouse button, and then select "Properties" and under "Options" menu, set the "state" option to "read-only". At this point you are ready to back up the content database.

To restore databases to a new SQL Server you will need the following permissions: the user must have CREATE DATABASE permissions to be able to execute RESTORE. If the database exists, RESTORE permissions default to members of the sysadmin and dbcreator SQL server roles and the owner (dbo) of the database.

Important Note: Always create backup copies of all your content databases before upgrading them. This will ensure that you always have unmodified copies of your content DBs to fall back to.

Once the backup is created, restore backups to the new SQL server using the following steps:

1. Copy the BAK file to new server.

2. Create an empty DB in Management Studio with the same name as the previously backed up 2007 content DB

3. Restore from backup, you may need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db).

After the databases are restored, you are ready to attach them to the 2010 Farm. In the interim SharePoint 2010 Farm, create a Web application corresponding to the 2007 web application that the content database belongs to, remove the default 2010 content DB from the newly created web application and attach the restored 2007 content database through the PowerShell command

Note: Even though there are 2 ways to attach the 2007 content DB to 2010 environment, STSADM and PowerShell Command, you still should use the PowerShell command:

Mount-SPContentDatabase -Name [DatabaseName] -WebApplication [URL] -Database Server [ServerName]

As the database is being upgraded and attached you will see the progress percentage running in the PowerShell window.

Once the database upgrade and attach process is finished you can browse to the URL of the web application that you attached the database to.

All managed paths that have existing sites will be recreated for sites in this content database.

Make sure that you add AAM for this Web Application, otherwise you may have issues accessing Site Collections that exist on managed paths other than the default top level Web app site collection.

You can preview the site in 2010 interface, by selecting the "Visual Upgrade" option in the Site Actions menu.

After you preview the upgraded User Interface (UI), you can optionally finalize the upgrade to the UI from the Site Settings menu.

"Visual Upgrade" allows a Site Administrator to "Preview" sites in SharePoint 2010. This is a nice feature that allows you to fix what would appear broken in 2010, but the fact is that you need to upgrade to the 2010 UI before you migrate it to the final 2013 environment. The "Visual Upgrade" feature allows to have a chance to fix 2007 customization for 2010. When you preview your sites in 2010, involve the site owners to review and fix all issues while you can still switch to the 2007 version that supports 2007 components. Once site owners test and fix issues in 2007 you can finalize the UI upgrade. This is important before migrating databases to 2013 version of SharePoint because SharePoint 2013 does not have support for SharePoint 2007 components and when content databases are upgraded to 2013, all sites will be automatically upgraded to the 2010 look and feel without leaving an option of fixing issues

in the SharePoint 2007 UI.

It is important to finish the visual upgrade before you move the content databases to 2013. The fewer processes that take place during the upgrade to 2013, the less issues during the upgrade to resolve.

You can also update the UI of all sub-sites in a Site Collection, once you ensure that sites have migrated property.

Regarding the upgrading of "My Sites"; you need to upgrade the My Sites Host first, once this site is upgraded, you can upgrade the rest of My Sites.

Database migration from 2010 to 2013

After the migration of the databases from 2007 to the 2010 farm, the last step is to migrate it to the 2013 environment. This final migration will require the same steps as previous migration. In fact, "database attach" is the only supported way of upgrading from SharePoint 2010 to the 2013.

Before taking the first step to move the 2010 content databases to the 2013 environment, back up the databases that you previously upgraded. You can use the same "Content Databases Catalog" spreadsheet that you filled out prior to moving databases to SharePoint 2010. Once the databases are backed up, move them to the SQL server that will be used to house your content databases:

1. Copy the database back up file to the SQL server

2. Create databases with the same names that 2010 content databases used

3. Restore the content databases in the SQL Management Studio

4. Create the corresponding Web Applications in SharePoint 2013 Central Administration site, use the same port numbers that you used in 2010.

Before you actually attach the new databases and upgrade them, you should run the test command on those databases. Open up the SharePoint 2013 Management Shell and run the following command:

Test-spcontentdatabase –name [content database name] –webapplication [URL for 2013 Web Application]

This report will provide you information on any configuration changes that need to be done in SharePoint 2013 before you upgrade the databases. Once all issues are resolved, open SharePoint 2013 Management Shell, and run the following command to finally attach and upgrade the database to SharePoint 2013:

Mount-spcontentdatabase –name [content database name] –WebApplication [url corresponding to the 2013 Web Application]

Note: For My Sites content databases, attach the content database that contains the My Site host before attaching databases that contain the My Sites. To upgrade my sites, you should upgrade the My Sites Host Site Collection first.

Repeat this process for all databases, when the process is complete, you can view the databases in the Central Administration under the "Content Databases" link.

When your content databases are successfully attached, the upgrade is almost done, but as in case with the upgrade from 2007 to 2010 where there was the last step of the "Visual Upgrade", there is still a similar option that is called "Deferred site collection upgrade". "Visual Upgrade" in 2010 allowed Site Administrators to "Preview" the site in SharePoint 2010 and then finalize the UI upgrade to 2010. This option of running site was available because SharePoint 2010 was installed with SharePoint 2007 supporting component. When SharePoint 2013 is installed it installs the files for SharePoint 2010 as well.

This allows sites migrated from 2010 environment to continue to run in 2010 mode, all new sites that are created in 2013 will be running in 2013 mode. When SharePoint 2010 sites are running on SharePoint 2013 you will need to start upgrading, but this time it is only available on a site collection level. Site Collection Administrators have a choice of using a "Site Collection health check" to determine any potential issues and address it before upgrading and upgrade when the Site Collection is ready for the UI upgrade. Once the site collection is ready, administrator can request an upgrade evaluation site which is a separate copy of their Site Collection in 2013 mode. This 2013 version of the site collection is available for 30 days, by default, until timer job deletes it. The default value of 30 day can be changed though.

Now you can point your old 2007 portal URL to this new migrated 2013 farm.

At this point you have successfully migrated from SharePoint 2007 to SharePoint 2013. You can decommission your old 2007 and interim 2010 environments. By default, when you created the web

applications in the new SharePoint 2013 environment, a default content database was created for each web application. You can remove those databases and delete them from the SQL Server.

The success of the migration will be largely determined by the End-User adoption rate. A well-developed migration plan and end-user training and support will be the key factors to the migration success. Features that are introduced to end-users within SharePoint 2013 are drastically different than what is available in 2007 version of the product.
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&cad=rja&uact=8&ved=0CEMQFjAA&url=http%3A%2F%2Fwww.discovertechnologies.com%2FDocuments%2FMigrating%2520from%2520SharePoint%25202007%2520to%2520SharePoint%25202013.pdf&ei=3KWxU4HrDdaMqAbt64GYCA&usg=AFQjCNHCKVnwEsP4-hlqlXX6B62xWXGEqw&sig2=VL3EBGUSjn55IXnHwmISUg&bvm=bv.69837884,d.b2k

Sharepoint 2013 Differences and new feature

New Feature of SharePoint

1.       Distributed Cache :- in earlier version of SharePoint each server have dedicated cache, so when a request comes to a server, server take this information from the

        Content database and load into the memory and information is accessible. once

2 request with the same information comes server look into the memory if information is available

Into memory it loads from the memory no need to go each time into content database. rule applies to all there servers. Distributed cache has a new feature when each server no need

to have cache and cache can store into a single server so whenever a request comes from any server with same information it can loads from the memory not from content database

another way to increase the performance.

 

2. Minimal download strategy: - only loads the page portion which has changed, another way to increase the performance.

3. shredded storage :- store the data in smaller pieces into content database and when access it merge all the data for a request and give a quick response. it reduce the space

of SQL data storage, decrease the amount of network traffic, allow the faster backup of content database. by default enable but you can reenable it per web application level

 

What's new feature

Branding :- Design changes : dreamweaver, HTML5,CSS3,New themes, windows 8 design,New cellphones,div based layout not table based, more compatiable for mobile sections

device based rendering using channels like site core, different content can be shown to different devices

Infrastructure changes :- sharded storge,SQL Improvment,Cache Serivice,Request Managment,Themes,Sharing

 

Authentication changes :- easy migration from classic to windows claims based powsershell also available. can be authenticating from services like lynch and exchange server

App authentication, authorization request by apps.

 

Best practices

minimum hardware requirment:- 64-bit,4 cores, 16GB RAM for prod,10-24 for dev,80 GB free space--sql server all same with 8GB for dev and 16 GB for prod 2012, windows server 2008 R2

APP Store and office app available

Cloud OnPrimise hybrid:-

hardware

virtual or physical

server topology

network topology

secuirty

UAG,TMG

DB STRUCTURE

SECUIRITY AND AUTHENTICATION

DEVICE SUPPORT

DISTRIBUTED CACHE

BCS:RPO,RTO,CLUSTERING

INFORMATION ARCHITEC

GOVERNANCE

 

Sites:-skydrive pro-- store document on cloud and synch from your laptop.

dynamicsites:- allow dynamic site store content, organize contento

dynamic navigation:-Manage term set to manage navigation.

SiteSharing content :- easy to share

 

Search :- Only one search included everything Enterprise Search + Fast Search, personalize search with search history,rich contextual previews,new search artict,new content search webpar

 

sharepoint designer changes:- design is not available

Changes which has been removed :-

Visual upgrade :-

Document workspace site template

group site work template and group work solution

visio process repository team temaplate

 

 

Cross site publishing:-

Create site collections for cross-site publishing : content authore and content publishing
Activate the Cross-Site Collection Publishing feature:- Cross-Site Collection Publishing

Create content for authoring sites:- you can use manage metadata, term store, textonomy tool

To make a term set available for tagging content :- in TAXONOMY TERM STORE section, click the term set that you want to make available for tagging.Click the INTEDED USE tab, and then select Available for Tagging.

Create catalog content by using SharePoint lists:-

To share a library or list as a catalog:-

To make a term set available to all site collections:-

Configure search for cross-site publishing