Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On This Page

...

  1. Select Connections > Add connection.

  2. Select Hitachi Object Storage as the platform on the Add connection modal.

  3. Enter the connection information. Reference the table below for details about each field.

  4. Test the connection to ensure DryvIQ can connect using the information entered.

  5. You will see a "Connection test succeeded" message on the Add connection modal when DryvIQ establishes connection. (If you don't see this message, verify the information you entered.)

  6. Select Done to finish creating the connection.

Add connection modal for Hitachi Object Storage

...

Field

Description

Required

Display as

Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists.

If you do not add a display name, the connection will automatically be named, “Hitachi Object Storage.” DryvIQ recommends you enter a name that more readily identifies the connection, especially if you will be creating multiple connections.

Optional

Access Key

Enter the access key ID required to access the account.

Required

Secret Key

Enter the secret key required to access the account.

Required

Service URL

If you have a custom Amazon S3 implementation, enter the service URL that needs to be used. You must enter the full URL including https:// at the the beginning. The URL will override the Region value.

Required

Use Server-Side Encryption

Select if the account uses server side encryption.

 Optional

Storage Class

Select the storage class: Standard, Standard-Infrequent Access, Reduced Frequency, or Glacier.

 Optional

Skip SSL Verification Check

Indicate if you want to skip the SSL verification check.

Optional

Features and Limitations

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. The information below is platform specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations. 

Supported Features (tick)

Unsupported Features (error)

Other Features/Limitations (warning)

Version preservation

Timestamp preservation

File size maximum: 5 TB

Metadata map

Author/Owner preservation

Path length maximum: No maximum

File lock propagation

Restricted types: none

Mirror lock ownership

 Segment path length: No maximum

Account map

Invalid characters:
DryvIQ restricts the use of / to prevent nesting in buckets.

Amazon doesn’t restrict characters but provides Object Key and Metadata guidelines you should follow.

Group map

Permission preservation

User impersonation

Tags map