Receive Management Information settings

Setting for receive file name

When uploading receive files to the object storage, specify a path in the following format for File Name of the Receive Management Information according to the object storage that is the upload destination.

Table 3.12 Path specification for uploads to object storage

Type of Object Storage

Path

Amazon S3

s3://bucketname/objectname

Azure Blob Storage

bs://containername/objectname

Google Cloud Storage

gs://bucketname/objectname
Note

  • The "s3://," "bs://," and "gs://" at the beginning of the path are fixed strings corresponding to each type of object storage. Be sure to specify lowercase characters only.

  • Even if the receiving-side host is Windows, use a "/" (slash) as the path delimiter when you specify the path for the upload to object storage, not a "\" (backslash).

  • If the corresponding HULFT Cloud Storage Option is not installed, the object storage path will not be recognized, even if the path is specified as shown in Table 3.12 . In such cases, a file open error occurs when the receiving-side host tries to receive the file on the disk.

  • For the bucket name or container name, specify the name of a bucket or container that exists in the object storage. If a bucket or container with the specified name does not exist, the upload ends in an error.

  • You cannot specify multibyte characters for the bucket name or container name due to object storage specifications. For the object name, you can specify multibyte characters.

    However, for HULFT8 for Linux, you cannot register multibyte characters for File Name for the Receive Management Information.

  • A "/" cannot be specified at the end of the object name. If specified, a transfer error occurs.

= Remarks =

  • A "/" can be included in the object name.

    For example, the path "s3://sales/kanto/tokyo/akasaka.dat" is handled as follows:

    Bucket Name

    :

    sales

    Object Name

    :

    kanto/tokyo/akasaka.dat

  • There is no hierarchical structure in object storage. All objects in the bucket are stored flat. However, if the object name includes a "/," the object is displayed on the management console of each object storage as though it has a folder hierarchy.

Settings for the handling of receive files

Objects in object storage cannot be handled in the same way as files on the disk.

Therefore, there are some restrictions on the values that can be set for the following items related to the handling of receive files:

Registration Mode

When you update an object in object storage, the old object is overwritten with the new object. You cannot append a new object to an old object.

Therefore, you can specify only "New Creation" or "Replace" for Registration Mode, and you cannot specify "Append".

Error Handling

When you update an object in object storage, the old object is overwritten with the new object if the upload succeeds, and the old object remains if the upload fails. Therefore, you cannot specify "Delete" and "Keep" for Error Handling.

You can specify "Restore", but this does not indicate that HULFT performs a backup before receiving or performs error recovery. Rather, HULFT takes actions based on object storage specifications.

Receive Mode

Because a new object cannot be appended to an old object, you can specify only "Single Receive" (for HULFT for Windows) or "Single" (for HULFT for Linux) for Receive Mode.

Generational Management

HULFT Cloud Storage Option does not support the Generational Management function. Therefore, specify "No" for Generational Management.

 

For items other than the above, check HULFT functional restrictions for uploads to object storage, and then set them according to actual operations.

For details on upload operations, refer to Parallel uploads.