Enterprise Vault Migrating Data Using the Microsoft Azure Blob Storage Migrator or later

Transcription

1 Enterprise Vault Migrating Data Using the Microsoft Azure Blob Storage Migrator 12.2 or later

2 Enterprise Vault : Migrating Data Using the Microsoft Azure Blob Storage Migrator Last updated: Legal Notice Copyright 2018 Veritas Technologies LLC. All rights reserved. Veritas, the Veritas Logo, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This product may contain third-party software for which Veritas is required to provide attribution to the third party ("Third-party Programs"). Some of the Third-party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Refer to the Third-party Legal Notices document accompanying this Veritas product or available at: The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Veritas as on-premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

3 Veritas Technologies LLC 500 E Middlefield Road Mountain View, CA Technical Support Technical Support maintains support centers globally. All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policies. For information about our support offerings and how to contact Technical Support, visit our website: You can manage your Veritas account information at the following URL: If you have questions regarding an existing support agreement, please the support agreement administration team for your region as follows: Worldwide (except Japan) Japan CustomerCare@veritas.com CustomerCare_Japan@veritas.com Before you contact Technical Support, run the Veritas Quick Assist (VQA) tool to make sure that you have satisfied the system requirements that are listed in your product documentation. You can download VQA from the following article on the Veritas Support website: Documentation Make sure that you have the current version of the documentation. Each document displays the date of the last update on page 2. The latest documentation is available on the Veritas website: Documentation feedback Your feedback is important to us. Suggest improvements or report errors or omissions to the documentation. Include the document title, document version, chapter title, and section title of the text on which you are reporting. Send feedback to: evdocs@veritas.com You can also see documentation information or ask a question on the Veritas community site:

4 Contents Chapter 1 Chapter 2 Introducing the Enterprise Vault Azure Blob Storage migrator... 5 About the Microsoft Azure Blob Storage migrator... 5 Requirements for using the Microsoft Azure Blob Storage migrator... 6 Configuring the Microsoft Azure Blob Storage migrator... 6 Configuring Microsoft Azure Blob Storage as secondary storage... 7 Getting the Microsoft Azure Blob Storage access credentials... 7 Configuring Microsoft Azure Blob Storage as secondary storage... 7 Microsoft Azure Blob Storage server properties... 8 Appendix A Troubleshooting Using DTrace to view diagnostic logs... 13

5 Chapter 1 Introducing the Enterprise Vault Azure Blob Storage migrator This chapter includes the following topics: About the Microsoft Azure Blob Storage migrator Requirements for using the Microsoft Azure Blob Storage migrator Configuring the Microsoft Azure Blob Storage migrator About the Microsoft Azure Blob Storage migrator The Microsoft Azure Blob Storage migrator lets you migrate archived data to and retrieve it from Azure Blob storage. You can use Azure Blob storage as a secondary storage location to store archived data in the cloud. The Microsoft Azure Blob Storage migrator is installed automatically when you install Enterprise Vault 12.2 or later. This guide shows how to configure the Microsoft Azure Blob Storage migrator to migrate data to the cloud. Caution: Using Azure Blob storage as a secondary storage can make some Enterprise Vault operations, such as retrieval, take a long time to process.

6 Introducing the Enterprise Vault Azure Blob Storage migrator Requirements for using the Microsoft Azure Blob Storage migrator 6 Requirements for using the Microsoft Azure Blob Storage migrator The following are the requirements for using the Microsoft Azure Blob Storage migrator: Veritas Enterprise Vault 12.2 or later. Azure Blob storage server name. Azure Blob storage account. Azure Blob storage account primary access key. Configuring the Microsoft Azure Blob Storage migrator The following table outlines the steps to configure the Microsoft Azure Blob Storage migrator. Table 1-1 Step Action Configuring the Microsoft Azure Blob Storage migrator Description Step 1 Step 2 Get the access credentials. For each vault store partition, configure Microsoft Azure Blob Storage as secondary storage. See Getting the Microsoft Azure Blob Storage access credentials on page 7. See Configuring Microsoft Azure Blob Storage as secondary storage on page 7.

7 Chapter 2 Configuring Microsoft Azure Blob Storage as secondary storage This chapter includes the following topics: Getting the Microsoft Azure Blob Storage access credentials Configuring Microsoft Azure Blob Storage as secondary storage Microsoft Azure Blob Storage server properties Getting the Microsoft Azure Blob Storage access credentials Before you configure Microsoft Azure Blob Storage as a secondary storage migrator, you must have an Azure Blob storage account to store data. Sign in to to create a storage account and get the storage access key. Configuring Microsoft Azure Blob Storage as secondary storage Use the Enterprise Vault Administration Console to enable and configure Microsoft Azure Blob Storage as secondary storage. For each vault store partition for which you want to configure Microsoft Azure Blob Storage as secondary storage, follow these steps.

8 Configuring Microsoft Azure Blob Storage as secondary storage Microsoft Azure Blob Storage server properties 8 To configure Microsoft Azure Blob Storage as secondary storage 1 Start the Enterprise Vault Administration Console. 2 In the left pane of the Administration Console, expand the Enterprise Vault site hierarchy until the vault store partition from which you want to migrate data is visible. 3 Right-click the vault store partition and click Properties. You can also double-click the vault store partition to open the vault store partition properties page. 4 In the Collection tab, do the following: Select Use collection files to enable collection. Select Enterprise Vault as the file collection software. Specify the daily collection times and the amount of time that must elapse since items were archived before they are eligible for collection. Note: For optimal performance, do not change the default collection file size. You can also enable and configure collection when creating a new vault store partition using the New Partition wizard. 5 In the Migration tab, do the following: Select Migrate files to enable migration. Select Microsoft Azure Blob Storage as the migrator software. Specify the amount of time that must elapse since a collection file was created before it is eligible for migration. Choose whether to remove the collection files from primary storage after they have been migrated. Specify the amount of time that must elapse since the migration before the files are deleted. You can also enable and configure migration when creating a new vault store partition using the New Partition wizard. 6 In the Advanced tab, configure the Microsoft Azure Blob Storage server properties. 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

9 Configuring Microsoft Azure Blob Storage as secondary storage Microsoft Azure Blob Storage server properties 9 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 2-1 Microsoft Azure Blob storage server properties Option Azure storage server name Azure storage account Azure storage account primary access key Azure container name Write Buffer size Description The name of the Azure storage server. You can choose from the following options: Default: if the storage server is located in any of the supported regions, except China. China: if the storage server is located in China. 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. The Azure storage account primary access key to access the storage account. The name of the Azure container. Note that the container name must be lowercase. 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. Default value Default None None None 20

10 Configuring Microsoft Azure Blob Storage as secondary storage Microsoft Azure Blob Storage server properties 10 Table 2-1 Microsoft Azure Blob storage server properties (continued) Option Read Buffer size Log level Description The buffer size, in megabytes, that Enterprise Vault uses for data downloads. 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. Default value 20 Errors, Warnings Use SSL for control Use SSL for data r/w Log CURL messages CURL connect timeout When set to Yes, Enterprise Vault uses the TLS 1.2 protocol to establish a secure connection to the Azure Blob storage cloud server. When set to Yes, 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. 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. 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. Yes Yes No 300

11 Configuring Microsoft Azure Blob Storage as secondary storage Microsoft Azure Blob Storage server properties 11 Table 2-1 Microsoft Azure Blob storage server properties (continued) Option CURL operation timeout CURL proxy type CURL proxy IP CURL proxy port User wait timeout System wait timeout Description 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. The curl proxy types. Proxy types are HTTP, SOCKS, SOCKS4, SOCKS5, SOCKS4A. The curl proxy IP. By default, no proxy is used. The curl proxy port number. 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. 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. Default value 900 None None

12 Configuring Microsoft Azure Blob Storage as secondary storage Microsoft Azure Blob Storage server properties 12 Table 2-1 Microsoft Azure Blob storage server properties (continued) Option Recalled file cache period Migrate all files Description 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. 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. Default value 7 No

13 Appendix A Troubleshooting This appendix includes the following topics: Using DTrace to view diagnostic logs Using DTrace to view diagnostic logs If you encounter problems when you store or retrieve archived data with the Microsoft Azure Blob Storage migrator, you can run the DTrace utility to help you identify the cause. DTrace let you monitor multiple services simultaneously, write the trace to a file, filter for specific words, and trigger tracing based on filters. The following table lists the migrator processes for which you can get diagnostic logs with DTrace. Note: We recommend that you set the monitoring level to Verbose in all cases. Table A-1 Monitor this process Troubleshooting with DTrace logs To do this EVStgOfflineOpns.exe StorageFileWatch.exe To get diagnostic logs for the restore or recall of the archived files that are located in the cloud. To get diagnostic logs for the following operations: The upload of data to the cloud through the Enterprise Vault collection and migration processes. The deletion of empty collection files from the primary storage.

14 Troubleshooting Using DTrace to view diagnostic logs 14 Table A-1 Monitor this process Troubleshooting with DTrace logs (continued) To do this StorageManagement.exe To view the information that is logged when Enterprise Vault checks whether the migrator software is installed and registered correctly and validates the configured settings. Enterprise Vault logs this information when you click the Test button on the Advanced tab of the vault store properties page. You can set a filter on the OST Streamer keyword to view logs specific to the Microsoft Azure Blob Storage migrator. For more information on DTrace, see the Utilities guide.