Enterprise Vault™ Migrating Data Using the Microsoft Azure Blob Storage Migrator
Microsoft Azure Blob Storage server properties
After you select Microsoft Azure Blob Storage as the secondary storage for a vault store partition, configure the properties for your Azure Blob 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:
Azure storage server name
Azure storage account
Azure storage account primary access key
Table: Microsoft Azure Blob storage server properties
Option | Description | Default value |
|---|---|---|
Azure storage server name | The name of the Azure storage server. You can choose from the following options:
| Default |
Azure storage account | The Azure storage account. This storage account can be a General-purpose storage account or a Blob storage account. The Microsoft Azure Blob Storage migrator supports the hot and cool storage tiers at the storage account level. | None |
Azure storage account primary access key | The Azure storage account primary access key to access the storage account. | None |
Azure container name | The name of the Azure container. Note that the container name must be lowercase. | None |
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: Note: If you choose , Enterprise Vault does not log cURL messages even if Log CURL messages is set to . | Errors, Warnings |
Use SSL for control | When set to , Enterprise Vault uses the TLS 1.2 protocol to establish a secure connection to the Azure Blob storage cloud server. | Yes |
Use SSL for data r/w | When set to , Enterprise Vault uses the TLS 1.2 protocol to establish a secure connection for read and write operations to the Azure Blob storage cloud server. | Yes |
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 Azure Blob storage cloud. | No |
CURL connect timeout | The maximum amount of time, in seconds, that the Microsoft Azure Blob Storage migrator waits to connect to the Azure Blob 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 Microsoft Azure Blob Storage migrator waits to transfer data to and retrieve data from the Azure Blob 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. | None |
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 Azure Blob 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 Azure Blob 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 , 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 , Enterprise Vault may leave some saveset files uncollected and thus unmigrated. | No |