This section describes how to migrate CIFS from an OES 2 SP3 or OES 11 environment to OES 11 SP3.
Before you proceed with the migration, review Section 20.2.2, Prerequisites. In this section, the source server refers to an OES 2 SP3 or OES 11 server, and the target server refers to an OES 11 SP3 server.
Server configuration information
Shares
Contexts
OES 11 server is already installed and CIFS is configured. For more information, see the OES 11 SP3: Novell CIFS for Linux Administration Guide.
NSS Pools and volumes are already migrated to the new OES 11 SP3 server from the OES 2 server. Use the cluster migrate resource_name node_name command to migrate the cluster pools and volumes. For details, see Using the Cluster Migrate Command
in the OES 11 SP3: Novell Cluster Services for Linux Administration Guide.
Non-cluster NSS volumes are already migrated to the new OES 11 SP3 server from the OES 2 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 the case of ID Swap, on the target server using iManager, replicate the following server properties:
Name
Comment
Domain/Workgroup
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 more information, see Managing CIFS Shares
in the OES 11 SP3: Novell 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 the CIFS iManager plug-in, replicate the CIFS user's context. For details, see Configuring a CIFS User Context
in the OES 11 SP3: Novell CIFS for Linux Administration Guide.
NOTE:After completing the migration, ensure that you reconfigure the CIFS service using yast2 novell-cifs or the iManager Add Context task to add the contexts to the cifsctxs.conf file, before you enable the subtree search feature.
Copying the CIFS configuration file:
Copy the /etc/opt/novell/cifs/cifs.conf file 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.
Restart the CIFS server using the rcnovell-cifs restart command.
Proceed with the proxy migration. For services using the common proxy, see Services that Are Using Common Proxy. For services using the service specific proxy, see Services that Are Using Service-Specific Proxy.
After performing the migration steps in Transfer ID Migration Procedure, perform the following tasks:
Run the following command to restart the service:
rcnovell-cifs restart
If you have enabled pass-through information levels capability on the target server, copying the cifs.conf file might overwrite the settings. To re-enable it on the target server after the migration is complete, run the novcifs -info-level-passthru=yes command.
After migration of the CIFS service to OES 11 SP3, 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 the "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 Novell CIFS services to the OES 11 SP3 target, verify that the migration process is complete by doing the following:
Verify that the NMAS methods for CIFS are installed and synchronized to the tree. For details, see Verifying LSM Installation
in the OES 11 SP3: Novell CIFS for Linux Administration Guide.
Log in to the CIFS server and attempt to access the data.