The procedures for migrating file system data 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 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 target server:
Volumes, folders and files
Trustee rights for files
Users are created in the eDirectory tree where the target server is present. An option is provided to set a default global password for the new users created on the target server's eDirectory tree.
In any of the following scenarios compressed files are seamlessly migrated from source server to target server:
Source server volumes and target server volumes both are compression enabled.
Source server volume is compression enabled and target volume is not enabled for compression. Migration gui uncompresses the migrated files on the target server volume.
Source server volume is not enabled for compression and target volume is compression enabled. 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.
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 2023: 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, 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 2023: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information, go to 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 2023: 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 Clustered DST Volume Pair
or Removing the Shadow Relationship for a Non-Clustered DST Shadow Volume
in the OES 2023: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information go to 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/TB each. The target server contains the primary volume Vol4 with 1 GB/TB space and secondary volume Vol5 with 10 GB/TB 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 Clustered DST Volume Pair
or Removing the Shadow Relationship for a Non-Clustered DST Shadow Volume
in the OES 2023: Dynamic Storage Technology Administration Guide.
Configure the file system GUI to perform migration. For more information go to Migrating File System Using GUI.
Migrating with the Shadow Volume Relationship: Considering the Example 16-1, only 1 GB/TB (depending on Vol4 size) 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:
Stop the existing DST policies temporarily before performing migration.
Create a project to migrate the data less than or equal to 1 GB/TB (depending on Vol4 size) 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.
(Conditional) If the data size on the source server is greater than the space available on the primary volume of the target server, repeat Step 2 to Step 6 until the entire data is migrated.
OR
Enable the DST settings to increase the size on the primary volume of the target server to match with the data size on the source server, then perform Step 2 to Step 6 to migrate the data.
When performing data or trustee migration in Active Directory environment, you must ensure that on the source server and target server the pool containing NSS volumes is media-upgraded, the NSS volumes are AD-enabled, and trustee rights are assigned on the specific folders or files.
Table 16-1 Support Matrix in Active Directory Environment
|
Source Volume |
Target Volume |
Data Migration |
Trustee Rights |
|
|---|---|---|---|---|
|
eDirectory |
Active Directory |
||
|
AD-enabled |
AD-enabled |
Success |
Success |
Success |
|
AD-enabled |
Non AD-enabled |
Success |
Success |
Not supported |
|
Non AD-enabled |
AD-enabled |
Success |
Success |
Not applicable |
|
Non AD-enabled |
Non AD-enabled |
Success |
Success |
Not applicable |
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, click Transfer ID. For more information, see Section IV, Transfer ID Migration.
Use either of the following methods to perform a file system migration: