Monitoring the migration is a common way issues are identified. When migration priorities are set for a group of users, a certain expectation of their progress accompanies their enablement. As users or files begin to lag behind the remaining users or files, an Operator will look into why. Frequently this is where issues, the point of their failure, and steps for remediation are identified. Quickly reviewing the appropriate grid can tell you if a user is not logging on, if the upload has completed, if a specific process has failed for a file, or if the user has fully completed their migration. Without monitoring your system, some issues may just not be found.
Most issues log entries in a console under Manage > Events. For most migrations, it is suggested to use this window as a sort of running tally of outstanding areas to investigate in a migration. Most events imply an issue which requires some actionable correction. Acknowledging events whose investigation has completed or have been resolved permits an Operator to have an easy view into what is wrong and what still needs resolution or investigation. Many issues identified by monitoring and review of exceptions can more easily be identified through the Events sub-menu.
Exceptions are instances of failures of some functionality within the product. Mostly identified via monitoring or event review, some level of exceptions occurs in every migration. The details of the exception provide a reason why the exception occurred. If you are able to identify a specific exception, review of the events, Console, or logs will help to better understand the nature of the failure. Log excerpts and collection are typically required for support tickets involving exceptions.
Backlogs are mostly identified by review of the Operations or Files sub-menus. Backlogs can indicate an issue with the environment’s tuning, exceptions, or services which are not running. Backlogs take place after a file has been centralized and it is already located on the local machine. The modules responsible for processing these files may have more work than they are able to process in the time allocated. Additional sizing or tuning may be required to eliminate the bottleneck and get the system caught up again. Bottlenecks not investigated or resolved are likely to recur as the migration continues.