Monitoring Migration Jobs
Migration Manager for SharePoint provides reports allowing you to monitor Sharepoint 2003-2007/2003-2010 jobs, track the migration progress and ensure that migration is successful:
State Report
Migration Manager allows you to compare the source and target locations for a migration job with its State Report. The report displays the following live statistics for source and target locations side by side:
ˆ the number of subsites ˆ the number of lists
ˆ the number of document libraries ˆ the number of documents
ˆ the number of document versions ˆ the number of list items
ˆ the number of attachments ˆ the total size of documents ˆ the size of the largest document
ˆ the number of documents by type ( le extension)
When exclusions have been con gured for the migration job, these sites and lists are excluded from the report as well.
Migrating SharePoint 2003 to 2007/2003 to 2010 83
The Remaining time represents the current estimation of the time required to complete the migration job. It is based on the migration speed (Change Rate) for the current job.
To view the report, select State from the Monitor menu. The report is displayed.
Each time you open the State report or refresh the page, the counters are requested from the source and target SharePoint. The request process may take few minutes.
Warning: It is not recommended to refresh the report very often dur-ing the migration process as it uses the service resources that perform migration and can harm them. When you open the report, click Refresh to initiate the counting process, wait few minutes and then click Refresh again to display the counters.
Note: The number of objects may not match for source and target sites in certain cases even when Migration Manager reports that the migration job is completed. The discrepancy typically comes from default lists, libraries and documents that are provisioned automatically for a SharePoint site. For instance, a SharePoint 2007/2010 site comes with a master page library that has no equivalent in SharePoint 2003.
Issue Report
The Issue report displays the job errors for post-migration analysis and trou-bleshooting.
To view the report, perform either of the following:
ˆ Select Issues from the Monitor menu on the Job Details page.
ˆ Click the link next to Issues on the Job Details page.
ˆ Click the link in the Issues column on the page listing the jobs.
Migrating SharePoint 2003 to 2007/2003 to 2010 85
The Issue report displays the summary of migration job issues.
By default, the report displays only rst 20 errors. To adjust the scope, change the Show First lter. Use the Filter issues by URL lter if you want to view issues for a particular site or list.
You can open all errors in Excel or save them in the .csv le. To do that, use the View all in Excel link.
To view the detailed information pertaining to a speci c issue, click the Show more... link.
Agents Report
The Agents report displays the state of the Migration Manager servers run-ning the migration job.
The server state includes:
ˆ Migration Manager services
ˆ Microsoft services that Migration Manager relies on (Message Queuing and Task Scheduler)
ˆ Migration Manager scheduled tasks
ˆ SharePoint permissions for the service account ˆ Free disk space
ˆ Source and target SharePoint versions
To view the Agents report, select Agents from the Monitor menu.
Migrating SharePoint 2003 to 2007/2003 to 2010 87
Web Part Migration
For SharePoint 2003-2007/2003-2010 jobs web parts and web part pages are not migrated during base content migrations.
Migration Manager provides a post-migration tool that automatically pro-cesses the sites in the scope of a migration job as follows:
ˆ Replicates web parts for the home pages of migrated sites.
ˆ Rebuilds custom web part pages in SharePoint 2003 document libraries, including their layout and web parts in SharePoint 2007/2010.
ˆ Rebuilds global pages for multipage meeting workspaces.
Note: Custom web parts are only migrated if their backing assemblies are installed on the target SharePoint 2007/2010 server.
Starting from Migration Manager 3.0 site home pages and custom web part pages in SharePoint 2003 document libraries are migrated automatically.
Web parts migration is initiated after a job completes initial migration. When a web parts migration is started, the job appears in the Web Part Migration view.
ˆ Name - the name of the migration job.
ˆ Running on - the server where the web part page migration tool runs.
ˆ Status - the current status of the web parts migration job.
ˆ Progress - the percentage of the web parts migration progress.
ˆ Last Updated - the time when the status was last updated.
ˆ Issues - the number of issues occurred during web part migration.
The Web Part job details page contains pairs of object URLs (the default aspx, document libraries, meeting workspace pages) participating in migra-tion and their processing state.
By default, the rst 100 errors are displayed. To adjust the scope, change the Show First lter. In order to facilitate management of URLs, there are
ltering (Filter pairs by URL) and paging on the page.
If any issues occur during web part pages migration, the link next to the Issues appears. Click the link to go to the detailed error report for the migration job.
The Migartion Job eld contains the job name linked to the Job Details page.
When the job is completed, it can be restarted. To restart web part migration, select Restart from the Web parts pages menu on the Job Details page.
Migrating SharePoint 2003 to 2007/2003 to 2010 89
Con guring Stored Credentials
To perform web part migration in two-agent deployment, con gure the stored credentials on the target server:
Note: To con gure stored credentials, you have to be logged on under the Quest Custom Page Migrator service account.