The actions performed during the migration process are recorded in an XML file. You can create a project file and execute the actions later at your convenience.
To create a new project, click
.You can either specify the path or browse to the location to create a new project. For example, /var/opt/novell/migration/NewProj1.xml.
The filename can be up to 64 characters long and can include any character except \ * ? < > | "/. The project name also serves as the project's folder name, so you might want to keep it short. The project folder stores the log files and other files associated with the project.
To open an existing migration project, click /var/opt/novell/migration/NewProj1.xml.
. For example,To save all the configuration settings of a migration project, click
.On successful authentication of the credentials of the source server and target server, you can select the services you want to migrate. For more information, refer to the Source help and the Target help files.
The services to be migrated are listed in the
pane.Click
, to select the services for migration.NOTE:In the
screen, if you have specified the cluster pool IP address and selected , then you can migrate file system only.If you do not want to migrate a service to the target server, Click
.Displays list of services to be migrated.
Order: When multiple services are configured for migration, numbers are listed adjacent to each service. The number indicates the order in which migration proceeds. The order is created by the migration tool and cannot be edited.
Service: Lists the name of services to be migrated.
Status: Displays the status of the service and last executed date and time of migration or synchronization of a service.
The following table describes the different states during migration:
State |
Description |
---|---|
Not Configured |
The service is not configured |
Ready |
The service is configured and ready to migrate. |
Migrating |
The migration of a service is in process. |
Stopped |
The migration of a service is stopped. |
Migrated |
The service is successfully migrated to the target server. |
Synced |
The services on the source server are synchronized with the target server. |
Dependencies: Lists the dependent services to be migrated. The migration process continues whether or not the dependency is completed.
Configure: Select the service for which you want to configure the migration options, then click
.Summary: The tree view displays migration options configured for a selected service.
Sync: The migrated service on the target server is compared with the source server and only the updated information is migrated to the target server.
You can run the migration project at any time. To run the migration project at a later date, you must schedule the project as follows:
You can schedule the migration project to run on multiple days.
Select the date.
Specify the time to run the project.
Specify the duration to run the project.
Click
to save the schedule.The migration project runs on the scheduled date and time.
You can view the date and time of the scheduled project. The tab displays the week view of the scheduled project.
You can set email notifications for receiving errors, warnings, and the status of migration.
In the
field, specify the email ID to receive notifications. You can include multiple email addresses separated by commas.In the
field, specify the email address that the notification email will be sent from.Under
, select the option to generate the email.In the
field, specify the mail server IP address of the recipient's mail server.Specify the port for the recipient's mail server. The default port is 25 in a non-secure mode.
To send e-mail with a secure SMTP connection, select
.Specify the interval (in minutes) to send e-mails for errors encountered. The default time is 15 minutes, but you can increase or decrease the interval as necessary. The e-mails are sent only if Error notification (in the Email tab) is set and if errors are encountered.
The progress of migration and sync along with error is recorded in the migration.log file and service-specific logs in the servicename.log file. A log directory is created in the same path as the migration project. The associated output and log files for the project are stored in this directory. For example, /var/opt/novell/migration/NewProj123/log/migration.log.
If a fatal error is encountered during the migration process, migration is stopped and details are logged in the log files.
The Migration Logs window displays logs for overall migration and service-specific migration. Using the search functionality, you can filter logs for specific type of error messages and keywords. The search results are displayed in a new search window. By default, only the last log file is filtered and results are displayed. You must select the
option to search all log files for the project.A tree view displays migration options configured for all the services selected for migration.
Displays the service status and logs.
Displays the status of the selected service. If a service is in a migrating state, the progress of the migration is displayed.
State |
Description |
---|---|
Ready |
The service is configured and ready to migrate. |
Precheck |
The prerequisites and migration options configured for each service are validated. |
Migrate |
The service is in the process of migration. |
Sync |
The migrated service is being synchronized with the service on the source server. |
Service Start Time: The date and the time when migration started for a specific service.
Service Elapsed Time: The execution time of service migration.
Remaining Time: The time remaining to complete migration of a service.
Project Start Time: The date and the time when migration started for a specific complete project.
Project Elapsed Time: The execution time of project migration.
Progress bar: The progress of migration for a service.
The tree view displays the progress of migration and sync for each service.
Service State: The current state of migration for a service whether it is Ready, Precheck, Migrate or Sync.
Progress Status: The progress of migration for a service. For example, Successfully Completed.
Migration Status: The status of migration for a service. For example, Complete.
Number of files/folders to migrate: The total number of files and folders on the source server that are to be migrated to the target server.
Number of files/folders migrated: The total number of files and folders successfully migrated to the target server.
Data to be migrated: The amount of data on the source server that is to be migrated to the target server.
Migrated data: The amount of data successfully migrated to the target server.
Trustee errors: The number of errors encountered when performing trustee migration. The error details are recorded in the filesystem.log file.
Total errors: The total number of errors encountered when performing migration. Click the link to display the service-specific log file.
Migration Start Time: The date and time when migration starts for a project.
Migration End Time: The date and time when migration is completed.
Service State: The state of sync for a service.
Progress State: The progress of sync for a service.
Sync Status: The status of sync for a service.
Number of files/folders to sync: The total number of files and folders on the source server that are modified and need to be synced to the target server.
Number of files/folders synced: The total number of files and folders successfully synced to the target server.
Data to be synced: The amount of data on the source server that is to be synced to the target server.
Synced data: The amount of data successfully synced to the target server.
Trustee errors: The number of errors encountered when syncing trustees. The error details are recorded in the filesystem.log file.
Total errors: The total number of errors encountered when performing sync. Click the link to display the service-specific log file.
Number of files/folders deleted on target: The total number of files and folders that are deleted from the target server because those files and folders were deleted from the source server.
Sync Start Time: The date and time when synchronization of service starts for a project.
Sync End Time: The date and time when synchronization of services is completed.
For trademark and copyright information, see Legal Notices.