Skip to main content
Version: 2.2

Configure source filesystems

Configure source filesystems for each product to migrate your data from depending on what your environment is:

  • Hadoop Distributed File System (HDFS) - Add one source filesystem only for each product.
  • S3 sources (IBM Cloud Object Storage, Amazon S3) - Add one or more source filesystems.

Data Migrator supports the following filesystems as a source:

Configure source filesystems with the UI

The Filesystems option under the Filesystems & Agents menu shows the source and target filesystems Data Migrator can use for data migrations.

Select Filesystems to:

  • View and configure source and target filesystems.
  • Add or remove targets.

Add a source filesystem

To add a source filesystem from your dashboard, select the following:

  1. From the Dashboard, select a product under Products.
  2. In the Filesystems & Agents menu, select Filesystems.
  3. Select Add source filesystem.

For information about configuring filesystem health check notifications and email alerts, see Configure email notifications with the UI.


If you have HDFS in your environment, Data Migrator automatically detects it as your source filesystem. However, if Kerberos is enabled, or if your Hadoop configuration doesn't contain the configuration file information required for Data Migrator to connect to Hadoop, configure a HDFS source with additional Kerberos configuration.

If you want to configure a new source manually, delete any existing source first, and then manually add a new source.


If you deleted the HDFS source that Data Migrator detected automatically, and you want to redetect it, go to the CLI and run the command filesystem auto-discover-source hdfs.

Configure HDFS as a source

See Configure a HDFS source filesystem.

Configure source filesystems with the CLI

Data Migrator migrates data from a single source filesystem. Data Migrator automatically detects the Hadoop Distributed File System (HDFS) it's installed on and configures it as the source filesystem. If it doesn't detect the HDFS source automatically, you can validate the source. You can override auto-discovery of any HDFS source by manually adding a source filesystem.


At this time, Azure Data Lake Storage (ADLS) Gen2 source filesystems can only be used for one-time migrations.

Use the following CLI commands to add source filesystems:

filesystem add adls2 oauthAdd an ADLS Gen 2 filesystem resource using a service principal and oauth credentials
filesystem add adls2 sharedKeyAdd an ADLS Gen 2 filesystem resource using access key credentials
filesystem add hdfsAdd a HDFS resource
filesystem add s3aAdd an S3 filesystem resource. You can choose this when using Amazon S3, Oracle, and IBM Cloud Object Storage. If you want to specify a required filesystem, use --s3type parameter. See s3a optional parameters.
filesystem add localAdd a local or mounted NAS filesystem resource.

Validate your source filesystem

Verify that the correct source filesystem is registered or delete the existing one (you define a new source in the step Add a source filesystem.

If Kerberos is enabled or your Hadoop configuration does not contain the information needed to connect to the Hadoop filesystem, use the filesystem auto-discover-source hdfs command to enter your Kerberos credentials and auto-discover your source HDFS configuration.


If Kerberos is disabled, and Hadoop configuration is on the host, Data Migrator will detect the source filesystem automatically on startup.

Manage your source filesystem

Manage the source filesystem with the following commands:

source clearDelete all sources
source deleteDelete one source
source showView the source filesystem configuration
filesystem auto-discover-source hdfsEnter your Kerberos credentials to access your source HDFS configuration

To update existing filesystems, first stop all migrations associated with them. After saving updates to your configuration, you'll need to restart the Data Migrator service for your updates to take effect. In most supported Linux distributions, run the command service livedata-migrator restart.