This section describes how to migrate CIFS from a supported OES server to OES 2018 SP2.
Before you proceed with the migration, review Prerequisites. In this section, the source server refers to supported OES versions and the target server refers to an OES 2018 SP2 server.
Server configuration information
OES server is already installed and CIFS is configured. For details, see OES 2018 SP2: OES CIFS for Linux Administration Guide.
NSS Pools and volumes are already migrated to the new OES 2018 SP2 server from a supported source OES server. Use the cluster migrate resource_name node_name command to migrate the cluster pools and volumes. For details, see OES 2018 SP2: OES Cluster Services for Linux Administration Guide.
Non-cluster NSS volumes are already migrated to the new OES 2018 SP2 server from a supported OES server. This can be done by unmounting the corresponding file system from the source machine and mounting it on the target machine.
Migrating Server Configuration information:
In case of ID Swap, on the target server using iManager replicate the following server properties:
Support for Oplocks
Support for DFS
Migrating Share information:
During the migration process, all shares except the shares that have been manually added are migrated. To replicate the shares that are manually added, use the CIFS iManager plug-in. For details, seeOES 2018 SP2: OES CIFS for Linux Administration Guide.
Migrating Context information:
Manual: Copy the context file /etc/opt/novell/cifs/cifsctxs.conf from the source server to the target server.
iManager: Using CIFS iManager plug-in, replicate the CIFS user's context. For details, see OES 2018 SP2: OES CIFS for Linux Administration Guide.
NOTE:After completing the migrate, ensure that you reconfigure CIFS service using yast2 novell-cifs or use the iManager Add Context task to add the contexts to the cifsctxs.conf file, before you enable subtree search feature.
Copying CIFS configuration file:
Copy the CIFS configuration file /etc/opt/novell/cifs/cifs.conf from the source to the target server.
CIFS configuration settings are stored in eDirectory and configuration files. During Transfer ID migration, the settings in eDirectory are migrated automatically, whereas the settings stored in the configuration files are not. To migrate them manually, copy the cifs.conf file to the target server.
If the source server is OES 2015 SP1 or older version, add the following parameters manually in the /etc/opt/novell/cifs/cifs.conf file on the target server.
-LOG_LEVEL with the required option. The available log level options are: debug, info, and error. For example, to configure debug as the log level, add the parameter -LOG_LEVEL debug
Restart the CIFS server using the systemctl restart novell-cifs.service command.
Proceed to perform proxy migration. For services using the common proxy, see Services that are Using Common Proxy.
After performing the migration steps in Transfer ID Migration Procedure, perform the following tasks:
Run the following command to restart the service:
systemctl restart novell-cifs.service
If you have enabled pass-through information levels capability on the target server, copying the cifs.conf file might overwrite the settings. Re-enable it on the target server after the migration is complete by running the novcifs -info-level-passthru=yes command.
After migration of CIFS service to OES 2018 SP2, default shares will not be mounted by CIFS.
View the list of all available share points using the command novcifs -sl.
Check the status of "Share volumes by default" attribute using the command novcifs --list-servers.
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.
After you have migrated the CIFS services to the OES 2018 SP2 target, verify that the migration process is complete by checking for the following details:
Verify that the NMAS methods for CIFS are installed and synchronized to the tree. For details, see OES 2018 SP2: OES CIFS for Linux Administration Guide.
Log in to the CIFS server and attempt to access the data.