Cool Solutions

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



By:

January 20, 2009 11:41 am

Reads: 5298

Comments:0

Score:0

Authors:

Prabudas Varadarajan

Pashupathinath Cheela

Table of Contents:

Overview:

This AppNote describes how the iFolder server and its corresponding data on NetWare 6.5 SP7 is migrated to OES2 SP1 Linux server. Novell iFolder is a collaboration suite that ensures your data is always current, secured, backed up, and available through the Network.

Novell has the vision of moving all NetWare servers running with services like DHCP, File and Print Services, iFolder etc., to OES2 SP1 Linux. This document explains about migrating iFolder Services from NetWare to OES2 SP1 using a utility called Novell Migration Tool. iFolder 3.7 is the most recent version of iFolder and available in OES 2 SP1 server. It has robust file sharing and synchronization features. Novell strongly recommends iFolder users to move from NetWare to OES 2 SP1.

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.

Introduction:

A brief introduction about the technologies used in this AppNote.

  1. iFolder: iFolder is a file synchronization software which ensures that user have the most recent version of user file where they go. Users can access their data from iFolder clients installed on their desktops or from Internet using their web browser.

    Using iFolder, we can designate any server (NetWare, OES Linux) as an iFolder server and publish information to a personal iFolder created on that server. Once your folder is created, you can install the iFolder client on the computers you regularly use and download information from your personal iFolder to any of those computers. The contents of your personal folder will be backed up in the iFolder server. To maintain data integrity, iFolder seamlessly synchronizes all your iFolder clients data. iFolder clients communicate regularly with the server-ensuring that the most current information is distributed to all of them.

  2. 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 exist – Consolidation and Transfer ID. In Consolidation data and services are migrated to target server. Where as in Transfer ID not only data and services but also entire server identity is transferred to target server.

Migration Process:

  1. Getting Started:

    Source server (NetWare 6.5 SP7) and Target server (OES2 SP1) should be installed at same context in the Tree. Also all iFolder users should be present in the same context of source and target servers.

    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 iFolder
    • Novell iManager
    • C/C++ Compiler and Tools

    Click to view.

    Fig 1: Package Selection

  2. Configuring iFolder service on target OES2 SP1 server
    1. During the server installation, iFolder service gets installed with the default configurations. If a user wants a different configuration, they can follow these steps. From the console type “yast2 novell-ifolder3″. And click continue. Then select all the options in Novell iFolder System Configuration options screen and click Next.

      Click to view.

      Fig 2.1: iFolder System Configuration

    2. In the iFolder System Configuration, screen keep the default values or give your choice values and click Next. It is recommended to keep default values.
      • Enter the name used to identify the iFolder server by the users in the Name text box.
      • System Description: Give a description for the server in the System Description text box.
      • Path to the servers data files: Enter the path for the folder where user’s data will be stored on the server
      • Path to the Recovery agent certificates path: Enter the path to folder where the security certificates will be stored by iFolder server

      Click to view.

      Fig 2.2: iFolder System Configuration (Contd..)

    3. In continuation to System Configuration keep the default values or enter your choice of values.
      • Name of iFolder Server: Enter a unique name for iFolder server for administrative purpose
      • iFolder Public and Private URL text boxes, give public and private IP or DNS resolvable Host names.
      • Select SSL options for iFolder: You can select SSL, Non SSL or both options based on your requirements.
      • If your server is a slave server, select Install in existing domain option and give Master server URL in the following text box

      Click to view.

      Fig 2.3: iFolder System Configuration (Contd..)

    4. In the LDAP configuration screen select your LDAP server and click Next.
      • From the listed set of eDirectory Servers, select the preferred server based on your requirements.

      Click to view.

      Fig 2.4: iFolder LDAP Configuration

    5. Enter the eDirectory Tree admin password and click OK.

      Click to view.

      Fig 2.5: iFolder LDAP Configuration (Contd..)

    6. User can keep default options or give your choice of values.
      • iFolder default administrator: Give the full context for the user who will be performing administrator operations on the iFolder server.
      • Give Administrator password in Admin Password and Verify password fields.
      • LDAP proxy user: Give full context for the iFolder proxy user.
      • Give LDAP proxy user password in proxy user password and Verify proxy user password fields.
      • LDAP search contexts: Add the ifolder user contexts where they in your LDAP.

      Click to view.

      Fig 2.6: iFolder System Configuration (Contd..)

    7. In the Web Access Configuration screen, keep the default values or give your choice of values.
      • In the alias text box, give an alias for the iFolder web access so that it will be accessible by the users using that alias.
      • Give the IP to be used for Web access application in the web access text box.
      • If you want to connect to the server using SSL, select the Connect to server using SSL option.

      Click to view.

      Fig 2.7: iFolder Web Access Configuration

    8. In the Web Admin Configuration screen, keep the default values or give your choice of values.
      • In the alias text box, give an alias for the iFolder web access so that it will be accessible by the users using that alias.
      • In the IP address filed give the IP address or DNS resolvable host name for the web admin application
      • If you want to connect to the iFolder server using SSL select the connect to server using SSL option

      Click to view.

      Fig 2.8: iFolder Web Admin Configuration

    9. Click “Yes” to restart Apache server. It completes iFolder server configurations on target server.

      Click to view.

      Fig 2.9: iFolder Configuration completes

  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.
    • There should be enough space in the Linux partition to hold the data moved from NetWare during the migration process.
    • 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 backup of 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 ‘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.
    Note: Encrypted iFolders files and folders will not be migrated from NetWare to OES Linux during the migration process.
  4. Backup of eDirectory data base and NICI keys on NetWare 6.5 SP7 and OESS 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.

    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:\_netware\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
  5. Authenticate to source and target servers.
    1. Launch migration utility using command ‘miggui’ from linux terminal on target server or Click Computer > More Applications > System > Novell Migration Tools.
    2. Authenticate to source server by clicking source server and then give tree admin credentials and click OK.

      Click to view.

      Fig 5.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 5.2: Authenticate to target server OES2 SP1 Linux

  6. Select migration type as Transfer ID.
    1. 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 6: Selection of Migration Type “Transfer ID”

  7. Start Migration.
    1. Click the Add button to select services – File system, Novell iFolder for migration.

      Click to view.

      Fig 7.1: Selection of services for migration.

    2. Configure the file system by selecting file system and click configure. Drag and drop iFolder directory from SYS:/iFolder from source to “/var/simias/data” folder on target server. And click OK.
      Note: If any other path than “/var/simias/data” is used during ifolder service configuration on target server. Then drag iFolder directory under SYS from source server and drop to path used during installation of ifolder service on target server in step 2.2.

      Click to view.

      Fig 7.2: Drag and drop iFolder data from source to target server

    3. Configure iFolder service for migration,
      • Source Information: Select 2.x Migration, since source server is NetWare.
      • ifolder 2.x data path: Browse the directory given during installation of ifolder service under step 2.2
      • Target Information: Enter target server admin credentials and Click OK.

      Click to view.

      Fig 7.3: iFolder service configuration

    4. After configuring both services click “Start” button for migration. And after successful migration start button changes to Transfer ID. Then click “Transfer ID”.

      Click to view.

      Fig 7.4: After successful migration, click Transfer ID

    5. Read the warning message given before starting Transfer ID operation and click OK.

      Click to view.

      Fig 7.5: Click “Yes” to Proceed.

  8. Transfer ID started
    1. eDirectory Precheck: Here it checks for time synchronization between source and target servers.

      Click to view.

      Fig 8.1: eDirectory prechek. Click “Next” to proceed

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

      Click to view.

      Fig 8.2: Preparation. Click “Next” to proceed

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

      Click to view.

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

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

      Click to view.

      Fig 8.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 8.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 8.6: DIB restore. Click “Next” to proceed

    7. IP Address Change: Click Next to change IP address of target server to 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 8.7: IP Address Change. Click “Next” to proceed

      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, Transfer ID screen is opened automatically where earlier it was stopped. Click Next to get IP change done.

      Click to view.

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

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

      Click to view.

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

    9. Reinitialize Server: Click Next to get target server reinitialized.

      Click to view.

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

    10. Repair: Click Next to repair eDirectory, iFolder service, LUM and other configuration files.

      Click to view.

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

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

      Click to view.

      Fig 8.12: Restart Server. Click Close

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

    Conclusion:

    This AppNote helps the customer to Migrate iFolder service and its related data from NetWare 6.5 SP7 to OES 2 SP1 Linux server. Now iFolder clients data which were earlier getting synchronized from NetWare server continue to synchronize iFolder server running on OES2 SP1 Linux.

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

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