Enterprise Vault™ Migrating Data Using the Google Cloud Storage Migrator

Last Published:
Product(s): Enterprise Vault (14.1, 14.0, 12.5, 12.4, 12.3, 12.2)

Google Cloud Storage server properties

After you select Google Cloud Storage as the secondary storage for a vault store partition, configure the properties for your Google Cloud Storage. Use the Advanced tab of the vault store partition properties page to configure the storage server properties.

Most of the configuration parameters are populated with their default values. You need to set the following parameters:

  • Google Cloud Storage server name

  • Google Cloud Storage Access Key

  • Google Cloud Storage Secret Key

Table: Google Cloud Storage server properties

Option

Description

Default value

Storage server name

The name of the Google Cloud Storage server.

None

Http port

The HTTP port number.

80

Https port

The HTTPS port number.

443

Use SSL for control

When set to Yes, Enterprise Vault uses the TLS 1.2 protocol to establish a secure connection to the Google Cloud Storage server.

Note that the S3 API does not support self-signed certificates.

Yes

Use SSL for data r/w

When set to Yes, Enterprise Vault uses the TLS 1.2 protocol to establish a secure connection for read and write operations to the Google Cloud Storage server.

Yes

Google Storage Access Key

The user ID for the Google Storage account.

None

Google Storage Secret Key

The password for the Google Storage account.

None

Supported regions

The geographical regions that Google Cloud Storage supports to store data. Specify regions in the format identifer, displayname, servicehostname. Use semicolons to separate region names. For example, us-west-1,US West,s3-us-west-1.googleapis.com; eu-west-1,EU West,s3-eu-west-1.googleapis.com.

Note the following:

  • Each region should contain three parts: identifier, display name, and service host.

    The identifier must be a location constraint of the region in Google Cloud Storage.

  • Specify the default region for the cloud storage first. The first region that is specified in the supported region list is treated as the default region.

  • If Google Cloud Storage has region support you must specify all regions.

 
 

  • Do not add whitespace in the identifier and the service host.

  • None of the fields of the region list should be blank.

  • Multiple regions should be separated with semicolon.

  • Each field in the region details should be separated with a comma.

  • The S3 API supports Signature V2 for authentication.

  • The region list should end with a semicolon.

  • You can specify only English characters in the region list.

  • Do not specify duplicate region names.

  • All regions should have similar SSL configuration, either enabled or disabled. Mixed SSL configuration is not supported.

 

Bucket name

The name of the bucket.

The bucket name must be unique across all existing bucket names in Google Cloud Storage. To ensure that you use a unique name you can prefix your bucket names with your company's name.

Refer to the Google Cloud Storage documentation for bucket naming requirements and guidelines.

None

Bucket region

The geographical location where the bucket is created.

None

Bucket access type

Specifies whether the URL is virtual-hosted-style URL or path-style URL.

Path

Write Buffer size

The buffer size, in megabytes, that Enterprise Vault uses for data uploads. Ensure that this value is greater than the Maximum collection file size setting on the Collections tab of the vault store partitions page.

Set this option to zero (0) to disable the use of buffers.

20

Read Buffer size

The buffer size, in megabytes, that Enterprise Vault uses for data downloads.

20

Log level

The amount of detail to include in the log file. You can select from the following:

  • No logging

  • Errors only

  • Errors, Warnings

  • Errors, Warnings, Info

  • Everything

Note:

If you choose No logging, Enterprise Vault does not log cURL messages even if Log CURL messages is set to Yes.

Errors, Warnings

Log CURL messages

Specifies whether to log cURL activity.

cURL is a command line tool for sending or receiving files using URL syntax. Enterprise Vault uses the cURL library to transfer data to the Google Cloud Storage cloud.

No

CURL connect timeout

The maximum amount of time, in seconds, that the Enterprise Vault Google Cloud Storage migrator waits to connect to the Google Cloud Storage cloud server. This only limits the connection phase, not the session time.

300

CURL operation timeout

The maximum amount of time, in seconds, that the Enterprise Vault Google Cloud Storage migrator waits to transfer data to and retrieve data from the Google Cloud Storage cloud server.

900

CURL proxy type

The cURL proxy types. Proxy types are HTTP, SOCKS, SOCKS4, SOCKS5, SOCKS4A.

None

CURL proxy IP

The cURL proxy IP. By default, no proxy is used.

your_proxy_ip

CURL proxy port

The cURL proxy port number.

70000

User wait timeout

If an Enterprise Vault user's request to retrieve an archived item from the Google Cloud Storage cloud server takes time, specifies the number of seconds after which to present the user with the following message:

The archived item is being retrieved from a slow device. Try again later.

Enterprise Vault continues to retrieve the item in the background until the System wait timeout period has elapsed. Enterprise Vault then abandons the attempt to retrieve the item, and the user must submit the retrieval request again.

The recommended value is 40 seconds.

40

System wait timeout

If an attempt to retrieve an archived item from the Google Cloud Storage cloud server takes time, specifies the number of seconds after which to abandon the attempt and remove the requested item from the retrieval queue.

The recommended value is 900 seconds.

900

Recalled file cache period

The number of days, since the last accessed date, that Enterprise Vault should retain recalled files in the cache. The collection process deletes the recalled files when the cache period has elapsed.

7

Migrate all files

If the value is set to Yes, Enterprise Vault forces all eligible files to be collected and migrated. Setting this value to Yes may cause Enterprise Vault to create a large number of collection files.

If the value is set to No, Enterprise Vault may leave some saveset files uncollected and thus unmigrated.

No