Help Center> Cloud Data Migration> User Guide> Job Management> Destination Job Parameters> To FTP/SFTP/NAS/SFS
View PDF

To FTP/SFTP/NAS/SFS

If the destination link of a job is the Link to an FTP or SFTP Server or Link to NAS/SFS, configure the destination job parameters based on Table 1.

Table 1 Parameter description

Category

Parameter

Description

Example Value

Basic parameters

Write Directory

Directory to which data will be written.

This parameter can be configured as a macro variable of date and time and a path name can contain multiple macro variables. When the macro variable of date and time works with a scheduled job, the incremental data can be synchronized periodically. For details, see Incremental Synchronization Using the Macro Variables of Date and Time.

/opt/ftp/

File Format
Format in which data is written. The options are as follows:
  • CSV: Data is written in CSV format, which is used for migrating data tables to files.
  • Binary: Files will be transferred directly. CDM writes the files without changing their format. This setting is suitable for file migration.

If data is migrated between file-related data sources, such as FTP, SFTP, NAS, HDFS, and OBS, the value of File Format must the same as the source file format.

CSV

Duplicate File Processing Method
Files with the same name and size are identified as duplicate files. If there are duplicate files during data writing, the following methods are available:
  • Replace
  • Skip
  • Stop job

Skip

Advanced attributes

Line Separator

Lind feed character in a file. By default, the system automatically identifies \n, \r, and \r\n. This parameter is not used when File Format is set to Binary.

\n

Field Delimiter

Field delimiter in the file. This parameter is not used when File Format is set to Binary.

,

File Size

This parameter is displayed only when the migration source is a database. Files are partitioned as multiple files by size so that they can be exported in proper size. The unit is MB.

1024

Encoding Type

Encoding type, for example, UTF-8 or GBK. This parameter is not used when File Format is set to Binary.

GBK

Use Quote Character

This parameter is displayed only when File Format is CSV. It is used when database tables are migrated to file systems.

If you set this parameter to Yes and a field in the source data table contains a field delimiter or line separator, CDM uses double quotation marks (") as the quote character to quote the field content as a whole to prevent a field delimiter from dividing a field into two fields, or a line separator from dividing a field into different lines. For example, if the hello,world field in the database is quoted, it will be exported to the CSV file as a whole.

No

Write to Temporary File

Whether to write the binary file to a .tmp file first. After the migration is successful, run the rename or move command at the migration destination to restore the file.

No

Generate MD5 Hash Value

This parameter is displayed only when the migration source is a file system (OBS/FTP/SFTP/NAS/HDFS), the migration destination is FTP/SFP/NAS, and File Format is Binary.

An MD5 hash value is generated for each transferred file, and the value is recorded in a new .md5 file. You can specify the directory where the MD5 value is generated.

No

Directory of MD5 Hash Value

Directory for storing MD5 values

/md5

Use First Row as Header

This parameter is displayed only when File Format is set to CSV. When a table is migrated to a CSV file, CDM does not migrate the heading line of the table by default. If you set this parameter to Yes, CDM writes the heading line of the table to the file.

No

Job Success Marker File

Whether to generate a marker file with a custom name in the destination directory after a job is executed successfully. If you do not specify a file name, this function is disabled by default.

finish.txt

Encryption
Whether to encrypt the uploaded data. The options are as follows:
  • None: Data is written without encryption.
  • AES-256-GCM: The AES 256-bit encryption algorithm is used to encrypt data. Currently, only the AES-256-GCM (NoPadding) encryption algorithm is supported. This parameter is used for encryption at the migration destination and decryption at the migration source.

For details, see Encryption and Decryption During File Migration.

AES-256-GCM

DEK

This parameter is displayed only when Encryption is set to AES-256-GCM. The key consists of 64 hexadecimal numbers.

Remember the key configured here because the decryption key must be the same as that configured here. If the encryption and decryption keys are inconsistent, the system does not report an exception, but the decrypted data is incorrect.

DD0AE00DFECD78BF051BCFDA25BD4E320DB0A7AC75A1F3FC3D3C56A457DCDC1B

IV

This parameter is displayed only when Encryption is set to AES-256-GCM. The initialization vector consists of 32 hexadecimal numbers.

Remember the initialization vector configured here because the initialization vector used for decryption must be the same as that configured here. If the initialization vectors are inconsistent, the system does not report an exception, but the decrypted data is incorrect.

5C91687BA886EDCD12ACBC3FF19A3C3F