Novell Cool Solutions

Migration of CIFS from NetWare 6.5 SP7 to OES 2 SP1 Linux



By:

February 12, 2009 2:19 pm

Reads:9,162

Comments:0

Score:Unrated

Print/PDF

Objective
Introduction
Migration Process
     1. Getting Started
     2. Configuring CIFS Service on Target OES 2 SP1 server
     3. Prerequisites
     4. Backup of eDirectory Database and NICI keys
     5. Select Migration Type as Transfer ID
     6. Start Migration
     7. Transfer ID Started
     8. Post Migration Tasks
Conclusion

Objective:

This AppNote helps users who are using CIFS protocol on a NetWare 6.5 SP7 server and intend to have the same service and File system access on OES 2 SP1 Linux. It also helps to successfully migrate the CIFS service and bring up the service on OES 2 SP1 Linux.

Novell has a vision of moving services like AFP, CIFS, DHCP and iPrint from NetWare to OES2 Linux. This AppNote explains migration of CIFS service from NetWare 6.5 SP7 to OES2 SP1 Linux.

Introduction:

A brief introduction about the technologies used in this AppNote.

CIFS: Novell CIFS enables Windows and Linux client workstations to create, copy, delete, move, save, and open files on OES 2 Linux / NetWare servers. CIFS allows read and write access from multiple client systems simultaneously. All these various file operations and sharing of resources on a network are managed from a CIFS server.

The CIFS protocol offers various services, service announcements, user authentication and authorization, and naming service running on a CIFS server. To provide file sharing and other services to clients accessing a CIFS Server, it uses NetBIOS over TCP/IP (NBT) and SMB services. CIFS file sharing is achieved by a mechanism called Browsing services or advertising.

Migration: Migration is the process of migrating the services, file system data, and eDirectory information from an existing NetWare server to an OES 2 SP1 Linux server. There are 2 types of migrations – Consolidation and Transfer ID. In Consolidation, data and services are migrated to the target server. Where as in Transfer ID, not only data and services, but also the entire server identity is transferred to the target server.

Note: In this AppNote NetWare 6.5 SP7 server is referred to as the source server and OES 2 SP1 Linux server is referred to as the target server.

Migration Process:

  1. Getting Started
    • The source server (NetWare 6.5 SP7) and Target server (OES2 SP1) should be installed at the same context in the Tree.
    • Select the following patterns from the software selection during installation of the Target server.
      • Pre-Migration Server (This selection makes server as non-replica server in the eDirectory tree, which is mandatory for Transfer ID)
      • Novell Storage Services (NSS)
      • Novell CIFS
      • Novell iManager
      • C/C++ Compiler and Tools

    Click to view.

    Fig 1: Package Selection

  2. Configuring CIFS Service on Target OES 2 SP1 Server
    1. From the target server console run ‘yast2 novell-cifs’ and click continue. In the CIFS configuration screen enter the eDirectory tree admin password and click OK.

      Click to view.

      Fig. 2.1 CIFS service configuration (contd.,)

    2. Add eDirectory users context where CIFS users exist and click Next.

      Click to view.

      Fig. 2.2 CIFS service configuration (contd.,)

    3. Select “CIFS Default password policy” to be applied to CIFS proxy user and for CIFS users and click Next to complete the CIFS service configuration on the target server.

      Click to view.

      Fig. 2.3 CIFS service configuration

  3. Prerequisites
    • Ensure that the source server and target server are running supported versions of NetWare, or Linux server software and updated with latest patches.
    • User must have sufficient rights to perform migration.
    • Verify all CIFS shares are visible from iManager before launching migration project. If any share missing intended for migration, add it from iManager.
    • Set simple password to all CIFS users.
    • Ensure that all the eDirectory operations are complete before performing Transfer ID migration.
    • Verify the health of source server eDirectory by loading dsrepair and run the following option:
    • Unattended Full Repair. If any errors are reported, resolve them before attempting the migration.
    • Verify the health of target server eDirectory by loading ndsrepair and run the following option: Unattended Full Repair. If any errors are reported, resolve them before attempting the migration.
    • It is recommend to take backups of the eDirectory database and NICI keys on both the source server and target server.
    • Ensure the host name and IP address of source server and target server are resolved using DNS server or /etc/hosts file.
    • Ensure all the eDirectory replicas are up and working in the current partition. Otherwise eDirectory migration cannot be completed successfully.
    • Time is synchronized across all the servers that host the eDirectory replicas in the partition where the source server and the target server resides. Time should be synchronized between source & target servers.
    • Verify time synchronization at source NetWare server using dsrepair –> Time synchronization. If the source server is not in time sync, then restart NTP/Timesync on the NetWare server.
    • Verify time synchronization at destination server using the ‘ndsrepair -T’ command. If it is not in time sync, then run ‘/etc/init.d/ntp restart’ on the terminal to get this server into time sync.
  4. Backup of eDirectory database and NICI keys on NetWare 6.5 SP7 and OES2 SP1 Linux servers

    In case of Transfer ID failure at any stage with the following procedure eDirectory data base and NICI keys are restored on NetWare 6.5 SP7 and OES2 SP1 Linux servers.

    Note: A tester version of backup and restore method (can say work around) is provided below. For more information about Novell eDirectory Backup and Restore is available in Novell eDirectory 8.8 Administration Guide.

    To backup and restore on a NetWare Server 6.5 SP7:

    Backup:

    1. load tbx
    2. unload ds
    3. mkdir sys:\_netware\dib.bak
    4. copy /q sys:\_netware\* sys:\_netware\dib.bak
    5. load ds
    6. mkdir sys:\system\nici.bak
    7. copy /q sys:\system\nici\* sys:\system\nici.bak\

    Restore:

    1. load tbx
    2. unload ds
    3. copy /q sys:\_netware\dib.bak sys:\_netware\
    4. load ds
    5. copy /q sys:\system\nici.bak\* sys:\system\nici\

    To backup and restore on a OES 2 SP1 Linux Server:

    Backup:

    1. /etc/init.d/ndsd stop
    2. mkdir /var/opt/novell/eDirectory/data/dib.bak
    3. cp -rp /var/opt/novell/eDirectory/data/dib/* /var/opt/novell/eDirectory/data/dib.bak
    4. mkdir /var/opt/novell/nici.bak
    5. cp -rp /var/opt/novell/nici/* /var/opt/novell/nici.bak
    6. /etc/init.d/ndsd start

    Restore:

    1. /etc/init.d/ndsd stop
    2. cp -rp /var/opt/novell/eDirectory/data/dib.bak/* /var/opt/novell/eDirectory/data/dib/
    3. cp -rp /var/opt/novell/nici.bak/* /var/opt/novell/nici/
    4. /etc/init.d/ndsd start

    Authenticate to source and target servers

    1. Launch migration utility using command ‘miggui ‘ from the Linux terminal on the target server or click Computer > More Applications > System > Novell Migration Tools.
    2. Authenticate to source server by clicking source server and then give the tree admin credentials and click OK.

      Click to view.

      Fig 4.1: Authenticate to source server NetWare 6.5 SP7

    3. Click on the target server and give Tree admin credentials to authenticate to the target server. And press OK.

      Click to view.

      Fig 4.2: Authenticate to target server OES2 SP1 Linux

  5. Select Migration Type as Transfer ID.

    The Transfer ID scenario runs a series of tasks for transferring the server identity of the source server to the target server. The identity of the server is made up of its IP address, host name, eDirectory identity, NICI keys, and the user certificates from the source server. On successful completion of the Transfer ID migration, the target server functions with the identity of the source server.

    Click to view.

    Fig 5: Selection of Migration Type “Transfer ID”

  6. Start Migration
    1. Click the Add button to select services File system, CIFS for migration.

      Click to view.

      Fig 6.1: Selection of services for migration.

    2. Select CIFS service and click configure for migration. Under CIFS shares tab
      • Source: Select source share name
      • Target: Browse location of target share. Click Add to add source and target shares pair.

      After selecting the source and target CIFS shares click OK.

      Click to view.

      Fig 6.2: Selection of source and target shares pair

    3. Under the Password policies tab, add CIFS policies used on source NetWare server. Click Add to add policies for migration.

      Click to view.

      Fig 6.3: Selection of CIFS policy for migration

    4. Click File System to configure for migration. Here drag the source NetWare volumes and drop them on the corresponding target server volumes.

      Click to view.

      Fig 6.4: Selection of source and target volumes

    5. Click the File Options tab to configure the file migration options and click OK.
      • Duplicate File Resolution: Select Always copy source files it is recommended.
      • Quotas: Selecting them makes quotas will be lost during migration of data.
      • File Filters: Select dates to filter out the data which users is not interested to be migrated to target server.
      • Home Directory: Enter full path as “media/nss/” to home directory for users on target server.
      • Sync Options: By selecting this option makes deletion of data on target volume which is not present on source volume.

      Click to view.

      Fig 6.5: File Options configuration

    6. Click Start to start the migration process. After successful migration, the Start button changes to Transfer ID. Click Transfer ID.

      Click to view.

      Fig 6.6: After successful migration, click Transfer ID

    7. Read the warning message given before starting Transfer ID operation and click YES.

      Click to view.

      Fig 6.7: Click “Yes” to proceed Transfer ID

  7. Transfer ID Started
    1. eDirectory Precheck: Here it checks for time synchronization between the source and target servers.

      Click to view.

      Fig 7.1: eDirectory Precheck. Click “Next” to proceed

    2. Preparation: Here the migration tool unconfigures eDirectory on the target server and removes the Unix work station object of target server.

      Click to view.

      Fig 7.2: Preparation. Click “Next” to proceed

    3. DIB Copy: Depending on the eDirectory DIB size of the source NetWare server, it takes some time to copy DIB from the source server to the target server.

      Click to view.

      Fig 7.3: DIB copy. Click “Next” to proceed

    4. Click Next, it gives a pop-up message that the source servers DIB is backed up at sys:backup.nds. The DIB copy operation automatically locks the eDirectory database on the source server.

      Click to view.

      Fig 7.4: Click “OK” to proceed

    5. Shutdown Source: Shutdown source NetWare server manually. Click ‘Next’, it gives a warning message to make sure that source server is switched off. Click OK to continue.

      Click to view.

      Fig 7.5: Shutdown source. Click “OK” to proceed

    6. DIB Restore: Source server DIB which was taken backup during DIB copy step will be restored on target server.

      Click to view.

      Fig 7.6: DIB restore. Click “Next” to proceed

    7. IP Address Change: Click Next to change the IP address of the target server to the source server IP address. Do not run these operation using remote SSH session. After executing this step the Linux servers IP address gets changed.

      Click to view.

      Fig 7.7: IP Address Change. Click “Next” to proceed

    8. NOTE: If you are executing this operation from a remote SSH session, then save and close the migration project. Login to the target server directly and open the previously saved project. After authenticating to the target server, the Transfer ID screen is opened automatically where earlier it was stopped. Click Next to get IP change done.

      Click to view.

      Fig 7.8: IP Address change warning message. Click “OK” to proceed

    9. Host Name change: Click Next for host name change. After this step, the host name of the Linux server is changed to the host name of the source NetWare server.

      Click to view.

      Fig 7.9: Host Name Change. Click “Next” to proceed

    10. Reinitialize Server: Click Next to get the target server reinitialized.

      Click to view.

      Fig 7.10: Reinitialize Server. Click “Next” to proceed

    11. Repair: Click Next to repair eDirectory, CIFS service, LUM and other configuration files.

      Click to view.

      Fig 7.11: Server Repair. Click “Next” to proceed

    12. After successful repair, close the migration project and restart the target server. This completes the Transfer ID process successfully.

      Click to view.

      Fig 7.12: Restart Server. Click Close

      After reboot, the target Linux server host name and IP will be seen with the IP and host name of the source NetWare server. Now the source NetWare server can be decommissioned.

  8. Post Migration Tasks
    1. Assign universal password policy to all CIFS users.
    2. Set universal password to all CIFS users.
    3. Restart CIFS service on target (OES2 SP1 Linux server).

Conclusion:

This AppNote helps the customer to Migrate CIFS service and its related data from NetWare 6.5 SP7 to OES 2 SP1 Linux server. Now CIFS clients which were accessing CIFS shares earlier from the NetWare server can continue to access CIFS shares on OES 2 SP1 Linux seamlessly.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS