1.From the Manage Queue dialog, select the job that you want to delete from the Distributed Migration Job list. The row selector icon and the highlighted row indicates the selected row.
NOTE: Only jobs with a status of Queued or Done can be deleted. Deleting a job from the queue will not remove or delete any of the logging information that has already been sent to the main Job list for the Agent Database.
2.Click Delete Job.
(If the button is disabled, check that the selected job has a status that is either Queued or Done.)
A dialog will display asking you to confirm the deletion.
You can view the progress of a migration tab in real-time via interactive log files. The logs are fully searchable, and are based on SQL Compact Edition (SQL CE) file types. The log files are tied into Job files (.LST), and these files are limited to 4GB in size.
To view an interactive log:
After starting an action, click Details>> in the progress dialog box.
NOTE: All logging in Metalogix Content Matrix is done through jobs. If a job list is deleted from the Job List, all logging for those actions will also be deleted. There is no backup for the job lists, unless the job is manually saved to another location. Once a job list is deleted, all logging for the actions within that job list are gone. Metalogix Content Matrix will automatically hold any job lists created through any copy or compare actions, in the Job Lists section, and these job lists can only be deleted through the appropriate Delete commands. The job lists can also be manually selected and saved through the Job list section.
There are two types of jobs in Metalogix Content Matrix:
A job list is a collection of job items. A Job list is created for each copy or compare action that is made. Any "Copy" action/job that is in the Job List section can be used as the base of an incremental copy job. Job items can be viewed in the Log Viewer, by opening a job list. There are three basic ways to open a job list to access the Log Viewer:
·Double-click on a job list.
·Select a job list, then in the Job List section of the toolbar click View Log.
·Select a job, right-click, and choose View log.
Job items are job files, or logging, for individual items within the scope of an action. For example, if a SharePoint site is copied, there would be a job item for adding each list and each item in that list, and one job item for adding or creating each site or sub-site. If a SharePoint list with five documents is copied, then there would be a job item for adding/creating the list, and then one job item for adding each of the documents.
Job items are job files, or logging, for individual items within the scope of an action. For example, if a SharePoint site is copied, there would be a job item for adding each list and each item in that list, and one job item for adding or creating each site or sub-site. If a SharePoint list with fie documents is copied, then there would be a job item for adding/creating the list, and then one job item for adding each of the documents.
From the Log Viewer you can select and view any job items that exists within that job list.
NOTE: Some actions in Metalogix Content Matrix have the ability to run with Verbose Logging. This option will increase the size of the log file.
To view Log Item Details:
1.From the Log Viewer, select the item whose details you want to view.
2.Use one of the following options:
§Double-click on the item.
§Right-click and choose View Job Item.
§If the job is currently running, click Details>>.
The Job Details dialog contains the following information:
·Operation - The last operation performed on the item.
·Status The status of the item. If a compare action is being performed then this could be: completed, different, or missing.
·Item Name - For items, the Item ID. For documents, the Filename.
·Time Started The time the action for the item was started.
·Time Finished The time the action for the item was finished.
·Bytes Copied The bytes (B) that were copied in the action. This will be displayed in KB in some cases.
·Source - The Source URL for the item.
·Target - Target URL for the item.
·Information - Provides an informational message about the item, such as. This section will provide a description for any different and/or missing attributes/metadata for an item.
·Details View - Any errors that were encountered with the item when an action was performed.
·Content Comparer tab - Any differences between Source and Target content (from a compare action). You can display this information in either a Grid View, which displays a metadata property grid for the item, or as a Text View, which displays a XML text format of the item. This option is most useful if Verbose Logging has been checked
You can also:
·Use [Copy] to copy all of the item information and details (including the Details tab) into the systems clipboard. You can then paste the information when it can then be pasted to another location. When pasted the information will look similar to that of the actual Log Item Details dialog. This can be used for easy copy/pasting of an items migration log details.
·Use [Prev] and [Next] buttons to move to the previous or next item on the list (if applicable).
You can export a selected job or multiple jobs from the Job List section into a Microsoft Excel file. The export will include all of the operations within each job (whether it is a migration action or some other action), and their details. This is to help users better understand their migration data and results, and provides another way to review the resulting logs.
In addition to the log details that are provided, there are also a number of tables and charts that can be accessed in different tabs within the Excel file. These tables and charts will help breakdown the information in a more visible manner.
To export one or more jobs to an Excel file:
1.In the Job List, select the job(s) you want to export.
2.Use one of the following options:
§From the Job List menu, select Export Excel
§Right-click and choose Export selected job to Excel.
3.Save the file to the desired location.
By default the Excel file will open after it has been created. This process may take a few minutes depending on the size of the selected job(s) and the number of actions in the log(s).