11.3 Moving Non-Clustered Devices From NetWare 6.0 to OES 2 Linux
NSS supports moving the devices containing NSS volumes from a NetWare 6.0 server to an OES 2 SP1 (or later) Linux server. For information, see Section 11.1, Guidelines for Moving Devices from NetWare 6.5 SP8 to OES 2 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, while converting the cluster from NetWare to Linux, Novell 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.
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).
This section describes how to move devices cross platform from a NetWare 6.0 server to an OES 2 SP1 (or later) Linux or later server:
11.3.1 Prerequisites
The prerequisites in this section apply to moving multiple devices from a NetWare 6.0 server to an OES 2 SP1 (or later) Linux 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 Section 7.2, Cross-Platform Issues for NSS Volumes.
Destination OES 2 Linux Server
NSS must be installed on an EVMS-managed device on the destination server. For information, see Installing with EVMS as the Volume Manager of the System Device
in the OES 2 SP3: Installation Guide.
11.3.2 Setting Up File Access For Users on the OES 2 Linux Server
Before or after you move an NSS volume from NetWare 6.0 to OES 2 SP1 (or later) Linux, you need to set up file access for users on the OES 2 SP1 (or later) Linux 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 Novell eDirectory 8.8 Administration Guide.
Set Up Protocols and Services
To provide access for users on the OES 2 SP1 (or later) Linux 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 Novell Client or other NCP services. For information, see the OES 2 SP3: NCP Server for Linux Administration Guide.
-
Novell AFP for Linux: Install and configure Novell AFP to allow the users to access the volume with the Apple Filing Protocol. For information, see the OES 2 SP3: Novell AFP For Linux Administration Guide.
-
Novell CIFS for Linux: Install and configure Novell CIFS to allow the users to access the volume with CIFS. For information, see the OES 2 SP3: Novell CIFS for Linux Administration Guide.
-
Linux Protocols and Services: Install and configure other protocols, such as Novell Samba or 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 installing Novell Samba, see OES2 SP3: Samba Administration Guide.
For information about configuring Linux NFSv3, see Section 18.16, 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 2 SP3: Novell Linux User Management Administration Guide.
For guidelines about users and access, see Section 5.5, Access Control for NSS on Linux.
11.3.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.
-
On the NetWare 6.0 server, if the device you want to move contains any mirrored partitions, you must first break the mirror (remove all but 1 segment) before upgrading.
-
If you use non-NCP protocols or Linux services for user access on the destination OES 2 Linux 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 2 SP3: Novell Linux User Management Administration Guide.
-
-
Deactivate the pool: At a server console, enter
nss /pooldeactivate=pool -
Remove the eDirectory Storage objects for the NSS pool and each of its volumes.
-
In iManager, click
.
-
Click .
-
Specify the name and context of the object or objects you want to delete.
-
Click .
-
-
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.
At the command prompt on the primary VLDB server, enter
vldb repair
The VLDB Repair 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.
11.3.4 Recommissioning Each NSS Pool and Its Volumes on the OES Linux 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. At a server console, enter
nsscon
nss /poolactivate=pool -
Create the eDirectory Storage objects for the NSS pool and each of its volumes.
-
In iManager, click
.
-
Click .
-
Browse to select the destination server.
-
Select the pool, then click .
-
In the lower right, select to view all volumes on the selected pool.
iManager opens to the Volumes page with the server and pool preselected.
-
For each volume in the selected pool, select the volume, then click .
-
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.
On the primary VLDB server, at the command prompt, enter
vldb repair
The VLDB Repair adds a GUID entry for each of the recommissioned volumes to the VLDB.
-
Make sure the devices are up and working as expected on the Linux System.
-
For each device, you can optionally upgrade the format for its partitions (or segments, as specified in EVMSGUI) on the device, or leave the partitions in the old format.
Upgrading the partitions on the device to the NetWare 6.5 and later partition format is strongly recommended, but it is not necessary unless you want to mirror a partition on the device. Before you can create the mirror, you must upgrade the partition format of the partitions on the device you moved.
-
At a server console, open the EVMSGUI by entering
evmsgui
-
Right-click the segment, then select .
-
Repeat Step 8.b for every partition on the device that was moved to the OES 2 Linux server.
-
Click to save the changes.
-
-
If you want to mirror the upgraded partition from Step 8, see Section 13.7, Mirroring an Existing Pool with NSSMU.