12.2 Moving Non-Clustered Devices From NetWare 6.5 SP8 Servers to OES 24.4

This section describes how to move devices cross-platform from a NetWare 6.5 SP8 server to OES 24.4 server. NSS supports moves of devices containing NSS volumes between any servers that support a compatible media format. For information, see Section 12.1, Guidelines for Moving Devices from NetWare 6.5 SP8 to OES 24.4.

IMPORTANT:Similar handling is necessary when moving devices with NSS pools between any two OES servers (NetWare to Linux, NetWare to NetWare, or Linux to Linux).

To preserve the NSS pool and volumes on the device when you move it, you must modify the volumes’ Storage objects in eDirectory. You decommission the volume by removing its related Storage object from eDirectory for the original server. You recommission the volume by creating a new Storage object in eDirectory for the destination server. When moving clustered devices cross-platform for a cluster conversion from NetWare to OES, OES Cluster Services automatically manages the Storage object updates to eDirectory.

NOTE:The decommission and recommission terminology is used only to illustrate the process; it does not represent a particular technology or tool.

12.2.1 Prerequisites

The prerequisites in this section apply to moving multiple devices from a NetWare 6.5 SP8 server to an OES 24.4 server.

IMPORTANT:When moving a non-clustered device, you must also move any other devices that contribute segments to the NSS pools on the device you are moving.

Compatibility Issues for Using NSS Volumes Cross-Platform

Before you begin, make sure you understand the Section 8.2, Cross-Platform Issues for NSS Volumes.

Original NetWare Server

You can move NetWare 6.5 SP4 (or later) NSS media to an OES 24.4 server if the operating platform can support the NSS media format. NetWare 6.5 SP3, OES 1 SP2 Linux, and earlier servers do not support the new media format.

For information, see Section 5.1, Guidelines for Upgrading the Media Format of NSS Volumes.

Destination OES 24.4 Server

NSS and other needed services must be installed on the OES 24.4 server where you want to move the NSS volume. For information, see Section 4.2, Installing and Configuring NSS.

12.2.2 Setting Up File Access For Users on the OES Server

Before or after you move an NSS volume from NetWare to Linux, you need to set up file access for users on the OES server.

Set Up Users in eDirectory

The original server and the destination server can be in the same or different eDirectory trees.

If the destination server is in the same tree as the original server, the file system trustees and trustee rights continue to work after the move.

If the destination server is in a different tree, use eDirectory to enable or reassign affected users for access in the destination tree. For information, see the eDirectory website.

Set Up Protocols and Services

To provide access for users on the OES server, do one or more of the following depending on your network environment:

NCP Server and Services: Install and configure NCP Server to allow the users to access the volume with the Client for Open Enterprise Server or other NCP services. For information, see the OES 23.4: NCP Server for Linux Administration Guide.
OES CIFS: Install and configure OES CIFS to allow the users to access the volume with CIFS. For information, see the OES CIFS for Linux Administration Guide.
Linux Protocols and Services: Install and configure other protocols, such as Linux NFS to allow the users to access the volume with the non-NCP protocols. Using these Linux services requires that the users be Linux enabled to execute Linux commands and services on the volume.

For information about configuring Linux NFSv3, see Section 19.7, Exporting and Importing NSS Volumes for NFS Access.

For information about enabling users and the Linux service with Linux User Management (LUM), see the OES 23.4: Linux User Management Administration Guide.

For guidelines about users and access, see Section 6.5, Access Control for NSS.

12.2.3 Decommissioning Each NSS Pool and Its Volumes on the Original Server

For each NSS pool, decommission the pool and its volumes from the original server.

If you use native Linux protocols or Linux services (such as SSH and FTP) for user access on the destination OES 24.4 server, you must Linux-enable the current users of the volumes before you move the devices.

IMPORTANT:If you do not use native Linux protocols or services for user access, this step is not necessary.

Use one of the following methods to Linux-enable users of the volumes on the device:
- To enable multiple users at once, use the nambulkadd command.
  
  User IDs are automatically refreshed after the enabling process ends.
- To enable a single user at a time, use iManager.
For information, see the OES 23.4: Linux User Management Administration Guide.
Deactivate the pool on the device.
1. In iManager, click Roles and Tasks .
2. Click Storage > Pools.
3. Browse to select the original server where the NSS pool resides.
4. Select the pool you want to decommission, then click Deactivate.
Remove the eDirectory Storage objects for the NSS pool and each of its volumes.
1. In iManager, click Roles and Tasks .
2. Click eDirectory Administration > Delete Object.
3. Specify the name and context of the object or objects you want to delete.
4. Click OK.
Repeat Step 2 and Step 3 for each pool on the devices you plan to move.
If you are using DFS in the tree where the original server is located, run the vldb repair command.

On the primary VLDB server, at the command prompt, enter
```
vldb repair
```
This removes a GUID entry from the VLDB for each of the decommissioned volumes.
Remove or reallocate the devices from the original server. Depending on your storage configuration, this might require a server shutdown.

12.2.4 Recommissioning Each NSS Pool and Its Volumes on the Destination Server

For each NSS pool, recommission the pool and its volumes on the destination server.

Relocate or reassign the devices to the destination server.
Reboot the destination server to mount the devices.
If a pool on the devices you moved is not automatically activated, activate the pool.
1. In iManager, click Roles and Tasks .
2. Click Storage > Pools.
3. Browse to select the destination server.
4. Select the pool, then click Activate.
Create the eDirectory Storage objects for the NSS pool and each of its volumes.
1. In iManager, click Roles and Tasks .
2. Click Storage > Pools.
3. Browse to select the destination server.
4. Select the pool, then click Update eDirectory.
5. In the lower right, select View Volume Details to view all volumes on the selected pool.
  
  iManager opens to the Volumes page with the server and pool preselected.
6. For each volume in the selected pool, select the volume, then click Update eDirectory.
7. Repeat Step 4.d through Step 4.f for each NSS pool and its volumes.
Allow the eDirectory tree to stabilize.

This can take several minutes.
Run the vldb repair command.

At the server command prompt on the primary VLDB server, enter
```
vldb repair
```
This adds a GUID entry to the VLDB for each of the recommissioned volumes.

12.2.5 Using Scripts to Decommission and Recommission NSS Volumes

Scripts are available to automate the process of decommissioning and recommissioning NSS volumes that are not cluster-enabled, see Decommissioning Script and Recommissioning Script for moving NSS devices cross-platform. This decom_recom.zip file contains two Perl scripts:

decom.pl: The decommissioning script deactivates the specified pool, removes eDirectory Storage objects for a specified NSS pool and each of its volumes on the original server, then it repairs the VLDB, if it exists, to remove the volumes’ information from the VLDB. You provide the pool name, and the script automatically gets the list of volumes on the pool.
recom.pl: The recommissioning script activates the specified pool, creates eDirectory Storage objects for a specified NSS pool and each of its volumes on the destination server, then it repairs the VLDB, if it exists, to add the volumes’ information to the VLDB. You provide the pool name, and the script automatically gets the list of volumes on the pool.

The scripts support moving NSS volumes on NetWare 6.5 SP8 to OES 24.4. You can modify the scripts to move volumes between any two non-clustered OES servers:

NetWare to Linux
Linux to NetWare
NetWare to NetWare
Linux to Linux

Decommissioning NSS Pools on the Original Server with decom.pl

For each NSS pool, decommission the pool and its volumes from the original server.

If you use non-NCP protocols or Linux services for user access on the destination OES 24.4 server, you must Linux-enable the current users of the volumes before you move the devices.

IMPORTANT:If you use only NCP Server and NCP services for user access, this step is not necessary.

Use one of the following methods to Linux-enable users of the volumes on the device:
- To enable multiple users at once, use the nambulkadd command.
  
  User IDs are automatically refreshed after the enabling process ends.
- To enable a single user at a time, use iManager.
For information, see the OES 23.4: Linux User Management Administration Guide.
For each NSS pool on the device you are moving, run the decom.pl script and specify the name of the pool to decommission.
Remove or reallocate the devices from the original server. Depending on your storage configuration, this might require a server shutdown.

Recommissioning NSS Pools on the Destination Server with recom.pl

For each NSS pool, recommission the pool and its volumes on the destination server.

Relocate or reassign the devices to the destination server.
Reboot the destination server to mount the devices.
For each NSS pool on the device you moved, run the recom.pl script and specify the name of the pool to recommission.