The procedures for migrating file system data from the NSS volumes or Traditional volumes on NetWare or from the NSS volumes on OES 2 Linux vary depending on whether the source server and target server are in the same eDirectory tree or in different eDirectory trees. This section covers the following scenarios:
NOTE:For more information about migration scenarios, see Section 1.0, Overview of the Migration Tools.
The source file system volumes are migrated to the target file system volumes within the same eDirectory tree.
The following are migrated from the source server to target server:
Volumes, folders and files
Users and their trustee rights
The source file system volumes are migrated to the target file system volumes in a different eDirectory tree.
The following are migrated from the source server to target server:
Volumes, folders and files
Users and their trustee rights
Create users in the target’s file system volumes.
An option to set a default global password for the new users created on the target server.
You can perform data migration by upgrading only the cluster nodes or both the cluster nodes and storage:
One or more NetWare nodes are replaced with OES 2 SP3 Linux nodes. Novell Cluster Services supports rolling server upgrade, using which one or more NetWare nodes can be replaced with OES 2 SP3 Linux nodes. For performing upgrade, refer to the Novell Cluster Services 1.8.7 for Linux Administration Guide.
All nodes and shared storage is replaced with new cluster with OES 2 SP3 Linux configured on a new shared storage. Migrating cluster volumes from NetWare cluster to a new Linux cluster can be achieved using OES 2 SP3 Migration Tool.
The OES 2 SP3 Migration Tool provides two options
and to perform cluster migration.If you select
option, migration continues uninterruptedly during cluster resource migrations to different cluster nodes. This option is valid only on the source server clusters. On migrating data to cluster volume on the target server, migration stops when the resource migrates to a different node. To continue migration you must make the resource active on the target server.If this option is not selected, migration stops when the resource migrates to a different node on source server. Once the resource comes up on the different node, re-start migration to continue the migration from where it failed.
On performing migration for DST volumes, the data is migrated for only the primary volume and does not include the secondary volume. To perform migration for all the volumes, remove the shadow volume relationship of the DST server.
When performing migration, consider the following:
The target server can be a DST or non-DST server.
Stop the DST policies before performing the migration.
For more information on stopping the policies, see Stopping a Running Policy
in the OES 2 SP3: Dynamic Storage Technology Administration Guide.
Only the data that is stored on the primary volume of the source server is migrated to the target server.
To migrate the data from all the volumes of the source server, remove the shadow volume relationship on the source server.
For more information on removing the shadow volume relationship, see Removing the Shadow Relationship for a Non-Clustered DST Shadow Volume
in the OES 2 SP3: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information, go to Section 16.4, Migrating File System Using GUI.
The source server can be a DST or non-DST server
Stop the DST policies before performing migration.
For more information on stopping the policies, see Stopping a Running Policy
in the OES 2 SP3: Dynamic Storage Technology Administration Guide.
The data is migrated from the source server to only the primary volume of the target server.
To migrate the data from the source server to all the volumes on the target server, remove the shadow volume relationship on the target server.
For more information on removing the shadow volume relationship, see Removing the Shadow Relationship for a Non-Clustered DST Shadow Volume
in the OES 2 SP3: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information go to Section 16.4, Migrating File System Using GUI.
Example 16-1 For Example:
Consider a scenario, where you are migrating data from a source non-DST server to a target DST server. The source server has volumes Vol1, Vol2, Vol3 of 3 GB each. The target server contains the primary volume Vol4 with 1 GB space and secondary volume Vol5 with 10 GB space. In this scenario you can migrate the data by using any of the following:
Migrating without the Shadow Volume Relationship: When the shadow volume relationship is removed from the target server, it acts as a non-DST server and the migration can be performed normally.
Perform the following to migrate the data:
Remove the shadow volume relationship. For more information see, Removing the Shadow Relationship for a Non-Clustered DST Shadow Volume
in the OES 2 SP3: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information go to Section 16.4, Migrating File System Using GUI.
Migrating with the Shadow Volume Relationship: Only 1 GB of data from the source server can be migrated to the primary volume Vol4 of the target server. If you need the data on all the volumes of source server to be migrated to the target server, perform the following:
NOTE:You require to stop the DST policies temporarily before performing migration.
Stop the existing DST policies.
Create a project to migrate the data less than or equal to 1 GB from the source server to the target server.
Perform the migration.
(Conditional) If some files or folders were open on the source server and did not get migrated to the target server, perform synchronization.
Synchronization must be performed before performing the next step.
Configure a DST policy on the target server to move the migrated data from the primary volume to the secondary volume.
As a result, there is space available on the primary volume of the target server to migrate additional data from the source server.
Stop the DST policy after the required data is moved from the primary volume Vol4 to the secondary volume Vol5.
In the Transfer ID scenario a series of tasks are executed for transferring the server identity of the source server to the target server. In the Migration Tool GUI, the file system is configured, then migrated. On successful migration of all of the services, the Start button changes to Transfer ID. For more information, see Section IV, Transfer ID Migration.
No additional steps are required for migrating a file system by using the Transfer ID scenario.
Use either of the following methods to perform a file system migration: