The procedures for migrating file system data from the NSS volumes or Traditional volumes on NetWare, or from the NSS volumes on OES, 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 the target server:
Volumes, folders, and files
Trustee rights for files
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 the target server:
Volumes, folders, and files
Trustee rights for files
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
In any of the following scenarios, compressed files are seamlessly migrated from the source server to the target server:
Source server volumes and target server volumes are compression enabled.
Source server volumes are compression enabled and the target volumes are not enabled for compression. Migration GUI uncompresses the migrated files on the target server volume.
Source server volumes are not enabled for compression and the target volumes are compression enabled. The Migration GUI compresses the migrated files on the target server volume.
The compress and uncompress commands run as a backend process in the migration GUI.
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 11 SP3 nodes. Novell Cluster Services support a rolling server upgrade. In this scenario, one or more NetWare nodes can be replaced with OES 11 SP3 nodes. For more information, see Converting NetWare Cluster Nodes to OES (Rolling Cluster Conversion)
in the OES 11 SP3: Novell Cluster Services NetWare to Linux Conversion Guide.
All nodes and shared storage is replaced with a new cluster with OES 11 SP3 configured on a new shared storage. You can migrate cluster NSS volumes from a NetWare cluster to a new Linux cluster with the Migration Tool.
The Migration Tool provides two options to perform the cluster migration: Is Cluster Resource and Follow Cluster Resource.
If you select the Follow Cluster Resource option, migration continues uninterrupted during cluster resource migrations to different cluster nodes. This option is valid only on the source server clusters. When migrating data to cluster NSS volumes on the target server, migration stops when the resource migrates to a different node. To continue the 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 the source server. Once the resource comes up on the different node, restart the migration to continue the migration from where it failed. The Migration Tool supports only source NSS volumes for migration.
When performing migration for DST volumes, the data is migrated for only the primary volume; it does not include the secondary volume. To perform migration for all the volumes, remove the shadow volume relationship of the DST server.
When performing the migration, consider the following:
The target server can be a DST server or a non-DST server.
Stop the DST policies before performing the migration.
For more information about stopping the policies, see Stopping a Running Policy
in the OES 11 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 about removing the shadow volume relationship, seeRemoving the Shadow Relationship for a Clustered DST Volume Pair
or Removing the Shadow Relationship for a Non-Clustered DST Shadow Volume
in the OES 11 SP3: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information, see Section 16.4, Migrating the File System Using the Migration GUI.
The source server can be a DST or non-DST server.
Stop the DST policies before performing the migration.
For more information about stopping the policies, see Stopping a Running Policy
in the OES 11 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 about removing the shadow volume relationship, see Removing the Shadow Relationship for a Clustered DST Volume Pair
or Removing the Shadow Relationship for a Non-Clustered DST Shadow Volume
in the OES 11 SP3: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information, see Section 16.4, Migrating the File System Using the Migration 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 and a secondary volume Vol5 with 10 GB. 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.
To migrate the data, complete the following steps:
Remove the shadow volume relationship. For more information, see Removing the Shadow Relationship for a Clustered DST Volume Pair
or Removing the Shadow Relationship for a Non-Clustered DST Shadow Volume
in the OES 11 SP3: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information, see Section 16.4, Migrating the File System Using the Migration 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 the source server to be migrated to the target server, complete the following steps:
NOTE:You must to stop the DST policies temporarily before performing the 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, several tasks are executed to transfer the server identity of the source server to the target server. In the Migration Tool GUI, the file system is configured and then migrated. After successful migration of all of the services, click Transfer ID. For more information, see Section IV, Transfer ID Migration.
Use either of the following methods to perform a file system migration: