2 |
Click Edit. |
• |
Click New. |
For detailed information on defining a migration job using the Job Designer, see “Migrator for Notes to SharePoint Designer” on page 91.
For detailed information on running a migration job, see “Migration Jobs” on page 62.
This tab contains the history of all of the migration jobs run for this database. It lists out each job with Date and Time the job was run, the status of the job and the description of the job. Double Clicking a job will open the log file for the job. This information is also viewable in the Task history node.
To migrate the failed items for a job, right click on the job entry, and select Migrated Failed Items. For more information, see Migrating failed items.
Once classes have been assigned to databases, this may be used as the basis for automatically assigning Triage decisions (such as the Complexity index of a database or whether the database should be migrated), effort estimates, target SharePoint destinations, and even the actual content migration jobs that need to be run. Note that while classes are assigned (or reassigned) every time you refresh your database views, the automatic Triage, Target Assignment and Migration Job Assignment only occur when the Apply class rules action is run by the user.
Under the Notes Database tree node are “by class” tree nodes. These nodes display the pre-defined classes and the databases that are members of each class. The By Technical Class tree node contains all of the defined technical classes. The By Business Class tree node contains all of the defined business classes. Select a class to see a list of the member databases in the results view.
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center