19.2 Migrating AFP to OES 2015 SP1

This section describes how to migrate AFP from an OES source server to OES 2015 SP1 target server.

Before you proceed with the migration, review Prerequisites.

19.2.1 What is Migrated

  • Server configuration information

  • Volume Aliases information

  • Contexts

19.2.2 Prerequisites

19.2.3 Modifying Thread Range

Beginning with OES 2015, 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 afptcpd.conf file and set the number of threads within the valid range and proceed with the migration procedure. If it is not changed and the minimum or maximum threads is out of the range, then AFP server will use default number of threads.

19.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.

    iManager: Using the iManager plug-in, enable support for DHX2 authentication and subtree search. For details, see Administering the AFP Serverin the OES 2015 SP1: 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. On successful migration, proceed to perform service specific proxy migration. For more information, see Section 32.0, Migrating Proxy users to OES 2015 SP1.

19.2.5 Verifying Migration

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