After you have completed the prerequisites procedures in Section 16.1, Preparing for File System Migration, you are ready to migrate the source server.
Launch the Migration Tool from the target server, using either of the following methods:
Desktop: Click
to launch the Migration GUI.Terminal Prompt: Log in as the root user and at a terminal prompt, enter miggui
Enter authentication credentials for the source server.
(Optional) Is Cluster Resource: This option supports only Consolidate scenario and does not support Transfer ID. If you want to migrate data in a cluster environment, you can perform either of the following:
Migrating Cluster Volumes: In the Volume Information tab displays all cluster volumes from the cluster resource as part of the source volume.
screen, specify the cluster resource IP and select the option. On configuring file system theMigrating Non Cluster Volumes from a Cluster Node: In the Volume Information tab displays all non cluster volumes present on the source server.
screen, specify the cluster node IP and do not select the option. On configuring file system theEnter your authentication credentials for the target server
Depending on the type of migration to perform, select the
as or .In the
panel, click and select .The
of the file system service is .IMPORTANT:File system is listed in the Service panel list only if it installed and configured on the target server.
To configure migration parameters for the file system, select
, then click .
Tabs |
Purpose |
---|---|
Identify the volumes or folders that you want to move from the selected source server to a selected target server. By default, all of the data in the volumes or folders that you select for migration in the source server tree is migrated to the target server. |
|
Customize the files and quotas that are migrating to the target server. You can also specify the home directory location and set options to synchronize the file system. |
|
You can migrate the trustee rights of the users from the source server to target server. You can also specify the global password for the new users created on the target server. This tab is enabled only in a Different Tree scenario. |
|
You can specify which users to migrate and how to handle the migration if the user already exists on the target server. This tab is enabled when you select the Custom User mapping option in the Trustee Options page. |
In the
tab, in the tree, select volumes or folders that you want to migrate, then drag and drop it in the tree.IMPORTANT:You cannot migrate a DFS junction. A DFS junction is displayed under the source tree as a folder because this junction appears in the file structure as a directory. Under
, the DFS junction can be dragged to the target server tree, but actually, the junction and the data are not migrated to the target server and migration fails.On migrating a directory to an existing file system (NSS, NCP volume, or Linux POSIX volume), there are access rights set on the target location that can be inherited by the folder and its contents after migration (either the trustees and trustee rights in the case of NSS and NCP, or the ACLs (access control lists) for Linux POSIX). You must modify the settings as needed to ensure that the files are available only to authorized users before you allow users to access the data in the new location.
NOTE:In the
tree, you cannot expand volumes or folders that are copied to the tree.For explanation on different tasks that can be performed in the Volume Information tab, refer to the table below, else proceed with default settings to Step 8.
Task |
Description |
---|---|
Target Location |
After you have selected volumes and folders for migration, you might want to identify the path of the folder or volume moved to the target server. In the tree, right-click the volume or folder that is selected for migration, then click from the drop-down menu. The tree in the view expands to display the volume or folder that was copied from the source server. |
Source Location |
After you have selected volumes and folders for migration, you might want to identify the path of the folder or volume moved from the source Server. In the tree, right-click the volume or folder that is highlighted for migration, then click from the drop-down menu. The tree in the view expands to display the volume or folder that was copied to the . |
|
|
Volumes or Folders selected for migration |
The volumes or folders that are selected for migration are highlighted in blue in the Source Server tree and the Target Server tree. |
Removing Volumes or Folders from the Target Server |
In the target server tree, right-click the volume or folder that you have decided not to migrate, then select . The folder no longer appears under the target server tree and is no longer a candidate for migration. |
Code Page |
This option is applicable only on source NetWare 5.1server. The Migration Tool detects the source server code page and mounts the source volumes. If the tool fails to detect the source server code page, it uses the default code page from the migration configuration file migconf.properties located in the /opt/novell/migration/plugin/conf/ folder on the target server. |
Follow Cluster Resource |
Select this option to perform uninterrupted migration when cluster resources migrate to different cluster nodes. This option is valid only on the source server clusters. For example, when a failure occurs on one node of the cluster, the resources are relocated to another node in the cluster. The migration tool connects to the cluster instead of individual server and performs uninterrupted migration during this failure. If this option is not selected, migration stops when the resource migrates to a different node. When the resource comes up on a different node, run the migration project again, the migration tool ensures that the migration process resumes from the state where it had stopped. On migrating data to cluster volume on the target server, migration stops when the resource migrates to a different node. To continue migration you must make the resource active on the target server. |
Click the
tab, then click to accept the defaults.or
Use the options to customize the files and quotas to migrate to the target server, then click
to save the settings.For explanation of the different tasks that can be performed in the File Options page, refer to the Table below.
Task |
Description |
---|---|
Duplicate File Resolution |
Determines what action to take when a file copied from the source server has the same filename as an existing file on the target server. Specify one of the following resolutions:
|
Quotas |
You might need to remove user quotas, If you are migrating the volume or folder to a larger NSS pool/ volume on the target server. NOTE:If you are migrating to a different file system (NSS to NCP volumes or from NSS to Linux POSIX volumes) on the target server, user quotas are not valid.
|
File Filters |
Determines which files to include for migration. If no filters are set, all files are migrated. You can specify the files that you want to migrate by specifying the date range or you can exclude the files from migrating by specifying the filenames or file extensions.
|
Home Directory Options |
Type the path where you want to create home directories for the users who are being migrated to the target server. For example, /media/nss/DATA/homes |
Sync Options |
The option performs synchronization of the target server with the source server. After completion of file system migration, if the source server is updated with new information, you can use the option for synchronizing the servers. The option is also available in the main Migration GUI window.Delete Files Not On Source: During synchronization of the servers, additional files or folders on the target servers are deleted that are not available on the source server. Delete Trustees Not On Source: This option is enabled only for same tree migration. Set this option to update trustee information on target server when trustees are deleted on the source volume on completion of migration or synchronization. Trustee information on the target server is deleted that is not available on the source server. To modify handling of trustees, or user options, change the options in the Trustee Options tab. |
Login Options |
This option indicates whether you want users to be logged in during the data migration. Disable Login On Source: This option is only applicable on source NetWare server. If you disable user login, the users cannot log in to the network and open files during the file copy. Users already logged in to the source server are not logged out, but no new logins are allowed until the migration completes. |
Click the
tab, then click to accept the defaults and migrate the trustee rights of users on the source server to target server.or
Use the options to customize the files trustee options to migrate to the target server, then click
to save the settings.For explanation on different tasks that can be performed in the
tab, refer to the table below.NOTE:In the Same Tree scenario, the
tab is disabled.
Task |
Description |
---|---|
Trustee Migration |
Specify an option to migrate trustee rights of users from the source server to the target server.
|
Existing User Options |
A username on the source server has a corresponding username on the target server. You can overwrite the trustee details of the user on the target server, or ignore the user.
|
New User Options |
Specify the global password for the new users created on the target server. eDirectory Password: Specify the password for the users to use, when they log in for the first time on the target server. |
(Conditional) If the Step 10.a to specify which users to migrate and how to handle the migration if the user already exists on the target server.
tab is enabled, click it, then continue withor
If the Step 12.
tab is not enabled, click to save your file system migration setup and return to the main Migration Tool window then continue withTo view the list of users on the source server and target server, click
, then select how to handle the users.Existing or Mapped Users: A username on the source server has a corresponding username on the target server. If the users are mapped, only the trustee details are migrated.
New Users: Users do not exist on the target server. Create new users on the target server, or ignore the users.
This is a global setting for all the users. Specify one of the following options to migrate users or ignore users.
Ignore All: Do not migrate the new users. Only existing users are migrated to the target server.
Create All: Create all users on the target server.
(Optional) To specify settings for individuals and groups that override the global handling of user migration, click the username, then assign one of the migration options from the drop-down menu:
Create: Create users on the target server and assign the trustee rights.
The users are created on the target server that is using the same FDN as the source server. The search context is used only to match the source server users to target server users in that context.
Ignore: Ignore the user and do not assign the trustee rights of the source user.
Browse: Assign an equivalent user by browsing the same context or a different context on the target server and assigning trustee rights.
After you have finished configuring the parameters in each tab, click
to save your file system migration setup and return to the main Migration window.Click
on the main migration window to begin the migration.The log files for the file system are located at /var/opt/novell/migration/<project name>/log. Following log files are created during file system migration:
filesystem.log: This stores the information about the command sequence and errors encountered during migration.
filesystem.success.log: This stores the list of all successfully migrated files.