15.3 Using the Migrate Windows Shares Utility

When you install an OES 2 Linux server or later, the Migrate Windows Share utility is automatically installed through YaST. This utility lets you perform basic data migrations from Windows to OES 2 Linux by using a graphical user interface (GUI) instead of command line tools.

To migrate Windows data shares:

  1. Prepare the source and target servers as instructed in Section 15.1, Prerequisites.

  2. On the target server, access the utility from the desktop by selecting Computer > YaST Administrator Settings > Open Enterprise Server > Migrate Windows Shares.

  3. (Optional) Create a new migration project:

    1. Select Create New Project.

    2. Specify the path to where you want the project file to be saved, or click Browse and select the path.

      The default path is /root/Desktop/ and the default project name is newProject.xml. You can change the path and project name as necessary.

      A subdirectory with the same name as the project is created in the specified path. The associated output and log files for the project are stored in this subdirectory.

      If a project with the same name already exists in the specified path, you are prompted whether you want to replace the old file. If you click OK, the new project overwrites the old one.

    3. Click Forward.

    4. Skip to Step 5.

  4. (Optional) Open an existing migration project. Select Open Existing Project, click Browse, select a project file (project_name.xml), then click Forward.

    If a selected file is not a valid migration project file, an error is displayed and you are prompted to select a valid project file.

  5. Authenticate to the source Windows domain:

    1. In the PDC (Primary Domain Controller) field, specify the IP address or DNS name of the PDC server.

    2. In the User Name field, specify the fully distinguished, typeful name of an Active Directory user with admin rights, or the Windows administrator of the source server.

      Use either the simple form (Administrator) or the LDAP comma-delimited format (cn=admin,cn=users,dc=novell).

    3. In the Password field, specify the password for the user.

      The Authenticate using Secure Socket Layer (SSL) option is unavailable for Windows source servers.

    4. Click Forward.

  6. Authenticate to the target tree.

    1. In the Server field, specify the IP address or DNS name of the target server.

    2. In the User Name field, specify the fully distinguished, typeful name of a user with admin rights in the target tree.

      Use the LDAP (comma-delimited) format. For example: cn=admin,o=novell

    3. In the Password field, specify the password for the user.

    4. Decide whether to use a secure connection.

      • To use a secure connection for LDAP authentication, make sure the Authenticate using Secure Socket Layer (SSL) option is selected (the default setting).

        When this option is selected, you must also ensure that TLS is enabled for LDAP on the source server. In iManager, click LDAP > LDAP Options > LDAP Group-server_name > Authentication Options and verify that Require TLS for Simple Binds with Password is selected (it is selected by default).

      • If you do not want to use a secure connection, deselect the Authenticate using Secure Socket Layer (SSL) option.

        You must also disable TLS for LDAP on the source server by using iManager > LDAP > LDAP Options > LDAP Group-server_name > Authentication Options and deselecting Require TLS for Simple Binds with Password.

      Failure to set these options as instructed can result in unpredictable system behavior.

    5. Click Forward.

  7. Select the source and target volumes.

    1. Click Add.

    2. In the Source Volumes column, select the source share you want to migrate.

      In the Target Volumes column, select the corresponding target volume.

      The target volume type is displayed after the volume path:

      • NSS indicates a Novell Storage Services volume.

      • NCP/POSIX indicates a NetWare Core Protocol volume on a Linux POSIX file system, such as EXT3 or XFS.

      If no entry is selected for the source or target volume, the first volume listed in the respective column is selected by default.

    3. If necessary, click Remove to clear the source and target volume entries and start over.

      The Remove All button is not functional in this release.

    4. When you have selected the desired source and target volumes, click Forward.

  8. Specify the settings for migrating the Windows users and groups.

    1. The Users and Groups to Migrate setting determines which users and groups to migrate from the Windows domain. Select one of the following options:

      • Select Migrate Only Users and Groups That Are Trustees (the default) to migrate only users and groups that have been assigned permissions to the data.

      • Select Migrate All Users and Groups to migrate all users and groups in the Windows domain regardless of whether they have been assigned permissions to the data.

    2. In the Target Context field, specify the container in the target eDirectory tree where you want User and Group objects to be created for the migrated Windows users and groups.

      Use LDAP (comma-delimited) format. For example: ou=blr,o=mycompany.

      If the specified context does not exist, it is created in the target tree.

    3. The Trustee Rights setting specifies whether or not you want to use inheritance to apply trustee rights.Select one of the following options:

      • Select Use Inheritance to Apply Trustee Rights (the default) if you want the migrated data to take advantage of the Novell rights model, which allows rights set at one level to flow down to lower levels in the file system hierarchy.

      • Select Statically Apply Trustee Rights if you want trustee rights to be explicitly assigned at each level in the file system hierarchy.

      In this release of the OES migration tool, selecting Statically Apply Trustee Rights has no effect. The migration always uses the default setting.

    4. Click Forward.

  9. Specify the file migration options you want to use for this migration project.

    1. The Duplicate File Resolution setting determines what action should occur when a file is being copied from the source server and a file with the same name and path exists on the target server. Select one of the following options:

      • Select Always Copy Source File (the default) if you want the source files to overwrite files with the same name on the target server.

      • Select Never Overwrite Existing File if you do not want the source files to overwrite files with the same name on the target server.

    2. Select the filter options you want.

      The File Date Filters let you set date ranges for Last Accessed and Last Modified to filter the files that are migrated from the source server.

      Only the Last Modified After filter is functional in this release of the OES migration tool.

      • If no filters are set, files are migrated regardless of their Last Accessed and Last Modified dates.

      • If you specify a date in the After column, only files accessed or modified after the specified date are migrated.

      • If you specify a date in the Before column, only files accessed or modified before the specified date are migrated.

      • If you set both an After and a Before date, only files accessed between the two specified dates are migrated.

      For each date filter setting, click Set to select a date from a calendar, or type a date in DD-MM-YYYY hh:mm:ss format. If necessary, click Clear to remove the date.

      The File Date Filters are inclusive in nature, meaning all files that fall within the specified date ranges are migrated.

    3. (Optional) Select File Type filter options.

      The File Type Filter lets you exclude all files of a specific type, as well as individual filenames.

      Enter filenames or extensions. Wildcard (*) specifications are permitted. For example, entering *.mp3 excludes all files with an extension of .mp3 from being migrated. Entering samplefile.txt excludes any files with this name from being migrated. Use a comma to separate multiple entries; for example: *.mp3, *.mov, *.tmp

      The File Type Filter is exclusive in nature, meaning all files that match the filter patterns are not migrated.

    4. When you have finished selecting your migration options, click Forward.

  10. Review the migration option summary:

    1. Expand the entries to verify that you have made the correct selections.

    2. Take the appropriate action:

      • If needed, click Back to go back through the previous pages and change the migration settings.

      • If you do not want to start the migration now, click Save to save the settings to the migration project file. You can open and continue the migration project later.

      • Click Cancel to exit the project without performing the migration.

      • Click Migrate to start the migration process. Continue with Step 11.

      The Verify button is enabled only after the migration has completed (see Step 14).

  11. Monitor the progress of the migration project.

    The Migration Status window displays the progress of the migration, and the field below shows the total number of errors and warnings, the time elapsed, and a status message.

  12. When the migration finishes or if it stops prematurely, click View Log to open the log file (project.log in the project folder) in a text editor.

    The log file records everything displayed in the Migration Status window. You should review the log to verify the success of the migration.

    If errors occurred, the messages recorded in the log file can help you determine what needs to be corrected before you attempt the migration again.

  13. Click Close to close the Migration Status window.

  14. (Conditional) To ensure that everything was migrated correctly, click Verify and review the log file again.

  15. Click Exit to exit the Migrate Windows Shares utility.