It is possible to copy the results of migration jobs from log files to other applications. This can be beneficial if you want to keep track of copy or incremental information outside of Metalogix Content Matrix, or want to manipulate the information for reporting or retention purposes. The log information is copied as text, to the clipboard, and can then be pasted within any other application that allows text pasting. For example, if a copy action was made, the logging can be copied into a Word file, or into an Excel spreadsheet, then saved.
NOTE: Only the end results of the total action will be copied.
To copy the logging for a job list:
1.Select a job from the Job List.
2.Right-click, and choose Copy selected job to clipboard (alternately Ctrl+C can be used).
3.Open the desired target program (for example: Microsoft Word, Microsoft Excel, Notepad, etc), then paste the content into the application (Ctrl+V, or the paste command in the application itself).
NOTE: The logging for each action within the list must be copied separately.
To copy the logging for job items:
·Select the desired job list or job item(s) that the logging is to be copied from, and open the job list to access the Log Viewer.
·Select any job items that are to be copied. Single or multiple items can be selected in the Log Viewer. In order to copy the logging for the entire job, all job items in the Log Viewer must be selected.
·When all of the desired items are selected, right-click on one of them, and select Copy Log Items to Clipboard, and select to either copy them with, or without details. The Details are a set of extra columns that are added to the logging. These columns are typically: Details, SourceContent, and TargetContent. These columns do not always contain extra information. The default copy option (Ctrl+C) is to copy the logging without the Details.
You can generate a zip file of data associated with a single job item to help Quest Support facilitate troubleshooting.
The high-level data collected in the zip file includes:
·Application Settings files.
·Product information (product version, license, etc.).
·Information about the job item (what action settings were set, the job log, etc.).
IMPORTANT: Please review the contents of the zip file before sending it to Support. While this feature attempts to only collect non-sensitive data, no guarantees can be made - it is up to you to ensure that any files in the zip folder are stripped of any confidential data. Regardless, Quest assures that the contents of the zip file will only be used for troubleshooting the associated support ticket.
To create a support zip file::
1.In the Job List, select the job for which the zip file is to be generated.
2.Use one of the following options:
§In the main ribbon, click the Help tab, then Create Support Zip File.
§Right-click and choose Create Support Zip File.
3.Save the file to the desired location using the desired file name.
4.If you wish to review the zip file for sensitive information, click Yes to open the zip file. Once you are satisfied with the contents of the zip file, it can be sent to Quest Support to aid in troubleshooting.
For migrations to SharePoint Online that use the Import Pipeline, you can monitor the progress of the job, including Microsoft-side processing, via the SharePoint Online Migration Jobs window.
NOTE: This window is used to monitor Objects and Actions Supported Using the Import Pipeline only. Any components of a migration that use CSOM can be monitored via Log Item Details.
To launch the SharePoint Online Migration Jobs window:
1.In the Jobs List, select the migration job you want to monitor/manage.
2.Right-click and choose Manage SharePoint Online Jobs.
NOTE: This option is available only if the Use Import Pipeline option was selected on the Configure Copy Options - List Content tab, and the window can be open for only one job at a time.
The following are the status messages that display in the SharePoint Online Migration Jobs window.
·Processing - Content Matrix is preparing batches for upload to the Import Pipeline.
·Queued - The batch is awaiting upload to the Import Pipeline.
·Running - The batch has been uploaded to the Import Pipeline and is being processed by Microsoft.
·Success - The batch has been processed successfully.
·Warning - The batch has been processed with one or more issues.
·Failed - Microsoft-side batch processing has failed.
To view batch details:
1.Select the batch whose detail you want to view.
2.In the ribbon menu, click View Job.
NOTE: The identifying URIs (Manifest, Blob Storage, and Azure Queue) are generated by Microsoft and can be used by Support for troubleshooting purposes.
While the job is running, you can view the progress in the Logs section of the window.
EXCEPTION: The progress of a running job cannot be viewed if it was configured using PowerShell.
Once the job has finished processing (or if the job was configured using PowerShell), the [Download Job Log] button becomes enabled, and you can view complete job details.
Jobs List Upload Duration Column
The column Upload Duration in the Jobs List displays the time it took for the job to upload via the Import Pipeline. If the migration was done with CSOM only, or the target was SharePoint on premises, the field will be blank.
Retrying a Failed Batch
Content Matrix automatically retries a failed batch up to five times by default. (This can be changed via the EnvironmentSettings.xml MaxAzureBatchRetryCount key.) You can also manually retry a batch by highlighting the batch then clicking Retry Job in the ribbon menu.
NOTE You can retry job batches any time before the Azure SAS URL for the job expires (which is 30 days for private containers and a number of days determined by Microsoft for SharePoint Online provided Azure containers). If you want to resubmit a job after this time period, you will need to re-create the migration job. It may still be possible to submit an API Support zip file for troubleshooting between the time that the Azure SAS URL expires and Microsoft destroys a container.
To create an API Support Zip file to send to Quest Support for troubleshooting:
1.Select the batch(es) for which you want to create the zip file. (Note that you can multi-select to create a separate zip file for each batch.)
2.In the ribbon menu, click API Support Zip.
3.Save the zip file(s), and send to Quest Support for troubleshooting.
Note that, by default, a zip file's name is its SPO Job ID. You can, however, rename it.
Many migration actions can be performed as a separate action after the initial migration is performed.
The following objects and settings can only be copied as a separate, post-migration task:
The following objects and settings can be copied both as part of a full migration or as a separate action: