19.1 Migrating CIFS from Netware to OES 2018 SP2

The NetWare to Open Enterprises Server (OES) CIFS migration process can be either initiated from the Migration Tool or through a command line utility. For detailed information on migration through the Migration Tool, see Section 1.0, Overview of the Migration Tools and for information on the command line utility, see Man Page for Migration.

19.1.1 Migration Prerequisites

For the migration to happen successfully ensure the following requirements are met:

19.1.2 Migration Scenarios

The CIFS migration scenarios are explained in this section:

Migrate - Same Tree

Only CIFS shares and contexts of the source servers are consolidated. The remaining server configuration information is not consolidated. The target server configuration is overwritten with the source server configuration. For details on consolidation migration, see Migration Scenarios.

Migrate - Different Tree

CIFS consolidation for a Different Tree is not supported. However, it can be achieved by using the following procedure:

  1. Migrate the file system by using the Different Tree scenario. For details, see Migrating Data to a Server in a Different Tree.

  2. Re-configure CIFS on the target server. For details on configuring CIFS, see Setting the CIFS Server and Authentication Properties in the OES 2018 SP2: OES CIFS for Linux Administration Guide.

Transfer ID - Same Tree

In this scenario, the target is installed into the same tree with a temporary name and IP address. At the end of the procedure, the source server name and IP address are swapped for the target server name and IP address. For details on Transfer ID migration, see Section IV, Transfer ID Migration.

What is Migrated

The following table gives you a quick overview of what is migrated from NetWare CIFS to OES 2018 SP2 CIFS for the different scenarios:

Table 19-1 Migration Support for CIFS service

Service supported

Consolidation

Transfer ID

Same Tree

Different Tree

Same Tree

Different Tree

Migrating CIFS shares

Yes

No

Yes

No

Migrating CIFS contexts

Yes

No

Yes

No

Migrating server configuration information

No

No

Yes

No

19.1.3 Migration Procedure

Follow the instructions in either of these sections to perform the CIFS migration:

Using the Migration Tool

  1. Launch the Migration Tool on the target server in one of the following ways:

    Desktop: Click Applications > Other > Novell Migration Tools.

    Terminal: Log in as the root user and at a terminal prompt, enter miggui

    For details on configuring source and target Server information, selecting a migration type, opening a project, and all the tool buttons, see Section 2.0, Overview of the Migration GUI.

  2. Click Add, select Novell CIFS to migrate, and click OK.

    The Status is displayed as Not Configured.

  3. Select Novell CIFS and click Configure to configure the migration parameters.

  4. Under CIFS Shares, select the Source and Target shares for migration. Use Browse to browse for target shares. Use Add to add more source and target share mappings. Use Update to modify the configuration. Use Delete to remove the share mappings.

    When you have filled in the information, the dialog will be similar to the following:

    IMPORTANT:The Migration Tool does not support migration of CIFS shares on a cluster resource. After the file system migration, you will need to manually configure the CIFS shares on the target Linux system. For more information, see Managing CIFS Shares in the OES 2018 SP2: OES CIFS for Linux Administration Guide.

  5. Click OK to complete the configuration.

    The Status is displayed as Ready.

  6. Click Migrate to start the migration process. When you are prompted to save the project, click Yes.

  7. In the next dialog box, click Yes to proceed with the migration.

    Wait for the migration to be completed. The Status changes to Migrated. The message CIFS Migration Successfully Completed is displayed.

    NOTE:Use the Status > Service Information to verify for errors during migration. If there are errors, fix them and restart the migration procedure.

Using the Command Line

CIFS migration requires the complete source and target server details. Run the migCifs utility on the target server for migrating. An example migCifs command is shown below. For details on the command, see Table 19-2 and see migCifs in Man Page for Migration.

migCifs -s <sourceIPaddr> -p <sourceportnum> -a <sourceFDN> -w <passwd> -f <sec/nonsecConn> -d <targetIPaddr> -q <targetportnumber> -b <targetFDN> -x <passwd> -g <secure/nonsecureconn> -S <MigrationType> [-m <cifssharemappings>]
migCifs -s <sourceIPaddr> -p <sourceportnum> -a <sourceFDN> -w <passwd> -f <sec/nonsecConn> -d <targetIPaddr> -q <targetportnumber> -b <targetFDN> -x <passwd> -g <secure/nonsecureconn> -S <MigrationType> -c
migCifs -s <sourceIPaddr> -p <sourceportnum> -a <sourceFDN> -w <passwd> -f <sec/nonsecConn> -d <targetIPaddr> -q <targetportnumber> -b <targetFDN> -x <passwd> -g <secure/nonsecureconn> -S <MigrationType> [-m <sourcecifsshares>] -r

Table 19-2 migCifs Command Details

Command Option

Description

-s <sourceIPaddr>

Source server IP address. For example, -s 192.168.0.1.

-p <sourceportnum>

Port number of the source server. For example, -p 636.

-a <sourceFDN>

Source server FDN. For example, -a cn=admin,o=novell.

-w <passwd>

Password for the source server FDN. For example, -w mysrc.

-f <sec/nonsecConn>

Secure (SSL) or non-secure (Non-SSL) connection type of the source server. 1 for SSL and 0 for Non-SSL. SSL is preferred. For example, -f 1 or -f 0.

-d <targetIPaddr>

Target server IP address. For example, -d 192.168.0.2.

-q <targetportnum>

Port number of the target server. For example, -q 636.

-b <targetFDN>

Target server FDN. For example, -b cn=admin,o=novell.

-x <passwd>

Password for the target server FDN. For example, -x mytgt.

-g <sec/nonsecConn>

Secure (SSL) or non-secure (Non-SSL) connection type of the target server. 1 for SSL and 0 for Non-SSL. SSL is preferred. For example, -g 1 or -g 0.

-S <MigrationType>

Sets the Migration Type. 0 for Server to Server - Same Tree or Different Tree, 3 for Transfer ID, and 5 for Consolidation. For example, -S 0 or -S 3 or -S 5.

-m <mapfilename>

CIFS source to the target share mapping file. This is an optional command.

Create the file using any text editor. Separate individual sharemaps by a line.

  1. Open a new file in the text editor.

  2. Specify sourcesharename#targetsharepath. For example, share1#CIFSV1:linuxshare1

    share2#NSSvol:linuxshare2/cifsshare

  3. Specify the required number of share details and save the file.

-c

Does not migrate CIFS Shares and Server Configuration information from the source. Migrates only the CIFS Context information.

-r

Removes the shares related to NetWare server from the target server after a Transfer ID migration. If -r is passed, migCifs considers it as repair mode and retries the server configuration migration. If -r is not passed, then migCifs considers it as migration.

Pass the source only CIFS share file. The source shares are listed and each share terminated with a #. For example, /media/nss/CIFSV1:#. Do not pass the CIFS Password Policies files with this option.

19.1.4 Post-Migration Procedure

Restarting the CIFS Service

  1. Run the following command to restart the service:

    systemctl restart novell-cifs.service

Enabling “Share volumes by default” Option

After migration of CIFS service to OES 2018 SP2, default shares will not be mounted by CIFS.

  1. View the list of all available share points using the command novcifs -sl.

  2. Check the status of "Share volumes by default" attribute using the command novcifs --list-servers.

  3. Enable the “Share volumes by default” attribute using the command novcifs --share-vols-default=<netbios name of the physical or virtual server> --value=yes.

    For example, novcifs --share-vols-default=BLR8-192.168_W --value=yes.

19.1.5 Verifying the Migration

After migration is complete, the CIFS server on the target server must be available and running as it used to be on your NetWare server. This verifies that the migration has been successfully completed.

If the CIFS server is not running after migration, see Migration in the OES 2018 SP2: OES CIFS for Linux Administration Guide.

After a successful migration:

  • All the CIFS shares are migrated and listed on the target server.

  • All the CIFS contexts are migrated to the target server.

You can verify these steps for a successful migration by using either iManager or command line options.

Using iManager to Verify the Migration

  1. Open iManager on the target server.

  2. Go to File Protocols > CIFS.

  3. Browse or specify the OES server.

  4. Click OK.

  5. Click Start. This displays the CIFS status as Running.

  6. Click Shares. You must be able to list the sharepoints that were running on your NetWare and now migrated to OES 2018 SP2 server.

    For details on CIFS administration through iManager, see Using iManager to Manage CIFS.

Using CLI to Verify the Migration

  1. On the target server console, enter the command systemctl status novell-cifs.service.

  2. If the status is not running, enter the command systemctl start novell-cifs.service to start the server.

  3. If the status is running, enter the command systemctl restart novell-cifs.service to restart the server.

  4. Enter the command novcifs [-sl | --share --list] or novcifs [-sln sharename | --share --list --name=sharename]

    This displays the list of sharepoints that were available on NetWare and are now migrated to the OES 2018 SP2 server.

    For details on CIFS administration through command line utilities, see Using the Command Line to Manage CIFS in the OES 2018 SP2: OES CIFS for Linux Administration Guide.

19.1.6 Man Page for Migration

To access this man page with the command information, enter man migCifs at the command prompt.

migCifs(8)

A command line utility that communicates with the source and target servers for migrating CIFS configuration information from NetWare to OES 2018 SP2. The command must be run on a target server.

Syntax

Migrating the CIFS Service from NetWare to OES 2018 SP2

migCifs -s <sourceIP> -p <portnumber> -a <sourceFDN> -w <password> -f <sec/nonsecConnType> -d <targetIP> -q <portnumber> -b <targetFDN> -x <password> -g <sec/nonsecConnType> -S <MigType> [-m <mapfilename>]-t <source_treename>

Synchronizing after Consolidation

migCifs -s <sourceIP> -p <portnumber> -a <sourceFDN> -w <password> 
-f <sec/nonsecConnType> -d <targetIP> -q <portnumber> -b <targetFDN> 
-x <password> -g <sec/nonsecConnType> -S <MigType> -c

Repair after Transfer ID 

migCifs -s <sourceIP> -p <portnumber> -a <sourceFDN> -w <password> 
-f <sec/nonsecConnType> -d <targetIP> -q <portnumber> -b <targetFDN> 
-x <password> -g <sec/nonsecConnType> -S <MigType> [-m <sourcesharefilename>] -r

Options

Usage Options:

-s <sourceIP>

IP address of the source server.

-p <portnumber>

Port number of the source LDAP server.

-a <sourceFDN>

Fully Distinguished Name (FDN) of the source server tree administrator.

-w <password>

Password of the source server tree administrator.

-f <sec/nonsecConnType>

Enables or disables SSL connection for the source LDAP server. Set 1 for SSL and 0 for non-SSL connection.

-d <targetIP>

IP address of the target server.

-q <portnumber>

Port number of the target LDAP server.

-b <targetFDN>

Fully Distinguished Name (FDN) of the target server tree administrator.

-x <password>

Password of the target server tree administrator.

-g <sec/nonsecConnType>

Enables or disables SSL connection for the target LDAP server. Set 1 for SSL and 0 for non-SSL connection.

-S <MigType>

Sets the Migration Type. 0 for Server to Server - Same Tree or Different Tree, 3 for Transfer ID, and 5 for Consolidation. For example, -S 0 or -S 3 or -S 5.

-m <mapfilename>

Full path of the file that contains source and target server share mappings.

-t <source_treename>

Tree name of the source.

-c

Does not migrate CIFS Shares and Server Configuration information from the source. Migrates only the CIFS Context information.

-r

Removes the shares related to NetWare server from the target server after a Transfer ID migration. If -r is passed, migCifs considers it as repair mode and retries the server configuration migration. If -r is not passed, then migCifs considers it as migration.

Help Options

-h | --help

Displays the help information of the command and syntax.

-u | --usage

Displays the usage information of the command.

Files

/etc/opt/novell/cifs/cifs.conf

CIFS configuration file.

/etc/opt/novell/cifs/cifsctxs.conf

CIFS context file.

/etc/opt/novell/cifs/.cifspwdfile

Encrypted CIFS proxy user file.

/var/opt/novell/log/cifs.log

CIFS server log file.

/var/opt/novell/migration/Newproj[n]/log/cifs.log

CIFS migration log file.

Example

migCifs -s 192.168.0.1 -p 636 -a cn=admin,o=novell -w novell -f 1 -d 192.168.0.2 -q 636 -b cn=admin,o=novell -x novell -g 1 -S 0 -m /cifsShares.tmp -t novelltree

Authors

Copyright 2005-2020, Micro Focus Software, Inc. All Rights Reserved.

See Also

novcifs(8)

Report Bugs

To report problems with this software or its documentation, visit http://bugzilla.novell.com.