18.2 Migrating AFP to OES 11 SP3

This section describes how to migrate AFP from an OES 2 SP3 or OES 11 source server to an OES 11 SP3 target server.

Before you proceed with the migration, review Section 18.2.2, Prerequisites.

18.2.1 What Is Migrated

  • Server configuration information

  • Volume Aliases information

  • Contexts

18.2.2 Prerequisites

18.2.3 Modifying the Thread Range

With OES 11 SP2 and later, the valid thread range is changed to as follows:

  • Minimum threads: 3 to 32, default value: 3

  • Maximum threads: 4 to 512, default value: 32

Before migration, manually edit the afptcpd.conf file and set the number of threads within the valid range, then proceed with the migration procedure. If it is not changed and the minimum or maximum threads is out of the range, the AFP server will use the default number of threads.

18.2.4 Migration Procedure

  1. Migrating Server Configuration information:

    Manual: Edit the /etc/opt/novell/afptcpd/afptcpd.conf in the source server and add support for DHX2 authentication and subtree search in the AUTH_UAM tag. After modifying the afptcpd.conf file, copy it from the source server to the target server.

    iManager: Using the iManager plug-in, enable support for DHX2 authentication and subtree search. For details, see Administering the AFP Server in the OES 11 SP3: Novell AFP for Linux Administration Guide.

  2. Migrating Volume Alias information:

    Copy the volume file /etc/opt/novell/afptcpd/afpvols.conf from the source server to the target server.

  3. Migrating Context information:

    Copy the context file /etc/opt/novell/afptcpd/afpdircxt.conf from the source server to the target server.

  4. Restart the AFP service for the configuration changes to take effect.

  5. After this migration, proceed with performing the service-specific proxy migration. For more information, see Section 32.0, Migrating Proxy Users to OES 11 SP3.

18.2.5 Verifying the Migration

Verify that the migration process is complete by checking for the following: