Veritas Information Studio Deployment Guide · Components Description...

Veritas™ Information StudioDeployment Guide

Information Studio 1.1

September 2019

Information Studio 1.1Documentation version: .0

PN:

Legal NoticeCopyright © 2019 Veritas Technologies LLC. All rights reserved.

Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas TechnologiesLLC or its affiliates in the U.S. and other countries. Other names may be trademarks of theirrespective owners.

This product may contain third-party software for which Veritas is required to provide attributionto the third party (“Third-party Programs”). Some of the Third-party Programs are availableunder open source or free software licenses. The License Agreement accompanying theSoftware does not alter any rights or obligations you may have under those open source orfree software licenses. Refer to the Third-party Legal Notices document accompanying thisVeritas product or available at:

https://www.veritas.com/about/legal/license-agreements

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 bereproduced in any form by anymeans without prior written authorization of Veritas TechnologiesLLC and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIEDWARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ORNON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCHDISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLCSHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES INCONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THISDOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION ISSUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq."Commercial Computer Software and Commercial Computer Software Documentation," asapplicable, and any successor regulations, whether delivered by Veritas as on premises orhosted services. Any use, modification, reproduction release, performance, display or disclosureof the Licensed Software and Documentation by the U.S. Government shall be solely inaccordance with the terms of this Agreement.

https://www.veritas.com/about/legal/license-agreements

Veritas Technologies LLC2625 Augustine Drive.Santa Clara, CA 95054

http://www.veritas.com

.

http://www.veritas.com

Technical SupportTechnical Support maintains support centers globally. Technical Support’s primaryrole is to respond to specific queries about product features and functionality. TheTechnical Support group also creates content for our online Knowledge Base. TheTechnical Support group works collaboratively with the other functional areas withinthe company to answer your questions in a timely fashion.

Our support offerings include the following:

■ A range of support options that give you the flexibility to select the right amountof service for any size organization

■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about our support offerings, you can visit our website at the followingURL:

www.veritas.com/support

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should be atthe computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

www.veritas.com/supportwww.veritas.com/support

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Technical Support

■ Recent software configuration changes and network changes

Licensing and registrationIf your product requires registration or a license key, access our technical supportWeb page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Advice about technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs, DVDs, or manuals

www.veritas.com/supportwww.veritas.com/support

Support agreement resourcesIf you want to contact us regarding an existing support agreement, please contactthe support agreement administration team for your region as follows:

[email protected] (except Japan)

[email protected]

mailto:[email protected]:[email protected]

Technical Support ............................................................................................. 4

Chapter 1 Before you begin ................................................................. 9About Information Studio deployment ................................................. 9System requirements for Information Studio Hub ................................ 12System requirements for Remote Data Engine ................................... 13System requirements for Information Studio Windows Connectors

........................................................................................... 15Prerequisites for deploying an Information Studio Hub ......................... 15Prerequisites for deploying a Remote Data Engine .............................. 16

Downloading the on-premises remote Data Engine installer kit..................................................................................... 16

Prerequisites for installing Windows Connectors Node ......................... 18Viewing the Data Engine Nodes screen ...................................... 19

Network requirements ................................................................... 19

Chapter 2 Deploying the Information Studio Hub and DataEngine ............................................................................. 21

Setting up a virtual machine environment for deploying InformationStudio Hub and additional Remote Data Engines .......................... 21

Deploying Information Studio Hub using the wizard ............................. 30Performing post-deployment tasks ............................................. 34

Deploying a remote Data Engine using the wizard ............................... 35Installing the Information Studio Windows Connectors ......................... 39Viewing the Data Engines screen .................................................... 40

Chapter 3 Upgrading Information Studio v1.1 onwards ............. 41Upgrading the Information Studio Hub and Remote Data Engine ............ 41

Chapter 4 Disk management ............................................................. 43About disk management ................................................................ 43Viewing Disks screen .................................................................... 44Managing additional disks .............................................................. 45

Contents

Chapter 5 Getting help ......................................................................... 52Displaying the online help .............................................................. 52Using the Veritas™ Information Studio product documentation .............. 52

8Contents

Before you beginThis chapter includes the following topics:

■ About Information Studio deployment

■ System requirements for Information Studio Hub

■ System requirements for Remote Data Engine

■ System requirements for Information Studio Windows Connectors

■ Prerequisites for deploying an Information Studio Hub

■ Prerequisites for deploying a Remote Data Engine

■ Prerequisites for installing Windows Connectors Node

■ Network requirements

About Information Studio deploymentVeritas™ Information Studio comprises an Information Studio Hub and DataEngine(s) required for intelligently monitoring your data.

The Information Studio Hub allows you to visualize data collected from variouscontent sources such as Native file servers and Veritas NetBackup (NBU), andstore information about that data. The Information Studio Hub also makes this dataavailable for various tasks such as creating and running reports related to complianceand data governance.

The Remote Data Engine is set up to connect to various data sources in the datacenter including File Servers, NBU Servers and others. It uses unique connectorslike CIFS, NBU and others to connect to these sources through Veritas DataConnector Framework

1Chapter

If you are installing Veritas™ Information Studio for the first time, you will first needto deploy the Information Studio Hub. Information Studio Hub deployment includesthe installation of the Information Studio Hub and a default Data Engine (as youcan see in Use case 1 in Figure 1-1). You can eventually add more Remote DataEngines andWindows Connectors as per requirement (as you can see in Use case2, 3, and 4 in Figure 1-1).

Figure 1-1 Veritas™ Information Studio deployment use cases

DescriptionComponents

Provides information insights, decision support, businessprocess workflow management, and internal systemorchestration in a centralized big data repository. Itmanages and schedules jobs on Remote Data Enginesand stores and analyses the metadata collected fromcontent sources.

Information Studio Hub

10Before you beginAbout Information Studio deployment

DescriptionComponents

Interacts with the content sources such as MicrosoftSharePoint online, cloud connectors, and file servers, toinitiate scan and discovery, collect metadata, performcontent classification, and transmit it to Information StudioHub.

Remote Data Engine

The Windows Connectors is deployed on a WindowsServer and is solely used for discovering and scanningmetadata on CIFS-based Native File Servers, MicrosoftSharePoint on-premises, Microsoft Exchange on-premises,, Oracle, and Microsoft SQL Server.

Windows Connectors

Note: Ensure that you install the Remote Data Engines and Windows Connectorsto support the content sources mentioned above.

Supported connectorsThe following table lists the connectors that support the Information Studio Hub andData Engine, separate Remote Data Engine, and the Windows Connectors.

Table 1-1 Supported connectors

Supported byConnectors

Information Studio Hub's default Data Engine withoutthe Windows Connectors configured

Veritas NetBackup version 7.6.x,7.7.x, 8.0, 8.1, 8.1.1, 8.1.2, and 8.2

Information Studio Hub's default Data Engine withWindows Connectors configured

Veritas NetBackup version 7.6.x,7.7.x, 8.0, 8.1, 8.1.1, 8.1.2, and 8.2,Native File Server, MicrosoftSharePoint On-premises, MicrosoftExchange On-premises, MicrosoftSQL Server, Oracle Database

Remote Data Engine without Windows Connectorsconfigured

Veritas NetBackup version 7.6.x,7.7.x, 8.0, 8.1, 8.1.1, 8.1.2, and 8.2,Box for Enterprise, Google Drive,Google Cloud Storage, Gmail,Microsoft OneDrive, MicrosoftAzure, Microsoft SharePoint Online,Microsoft Exchange Online, CMIS(OpenText Documentum, OpentextLiveLink, IBM FileNet)

11Before you beginAbout Information Studio deployment

Table 1-1 Supported connectors (continued)

Supported byConnectors

Remote Data Engine with Windows Connectorsconfigured

Veritas NetBackup version 7.6.x,7.7.x, 8.0, 8.1, 8.1.1, 8.1.2, and 8.2,Box for Enterprise, Google Drive,Google Cloud Storage, Gmail,Microsoft OneDrive, MicrosoftAzure, Microsoft SharePoint Online,Microsoft Exchange Online, NativeFile Server, Microsoft SharePointOn-Prem, Microsoft ExchangeOn-Prem, Microsoft SQL Server,Oracle Database, CMIS (OpenTextDocumentum, Opentext LiveLink,IBM FileNet)

System requirements for Information Studio HubTo deploy the Information Studio Hub in your environment, carefully review theminimum requirements:

■ Deploy the Information Studio Hub on virtual machines hosted on VMware ESXServer having minimum ESX version 6.

■ The virtual machine for Information Studio Hub requires minimum 16 CPUs, 80GB RAM, and 1TB disk space in addition to 500 GB OS space.

Note: Information Studio Hub requires a minimum of a single disk of 1TB forapplication data. While importing the OVA, 1 TB of disk is automatically addedto the VM. If you need more than 1 TB disk, see Managing additional disks foradding additional disks.

Table 1-2 ESX version support in Information Studio

VCenter 6.7 (Web Client)VCenter 6.5 (Web Client)VCenter6.0(ThickClient/WebClient)

ESX 6.7ESX 6.5ESX 6.0ESX 6.5ESX 6.0ESX 6.0

HTML/ FlexHTML/ FlexHTML/ FlexHTMLHTML

12Before you beginSystem requirements for Information Studio Hub

Table 1-3 Minimum virtual machine requirements

SpecificationsVirtual Machines

■ One Network Interface Card (NIC)■ 1 node■ 16 CPUs and 80 GB RAM■ 500 GB for OS■ Additional data disks - 1TB or more for

product data■ Hard Disk Drive (HDD): Suitable for

Information Studio Hub OS Disk and DataDisk■ Separate Hypervisor and datastore disks

on different physical HDDs■ At least 4 disks configured as RAID 10

(RAID 1+0).RAID 0 can be used, but loss of a disk willresult in data loss. A Backup and Restoremechanism must be in place to recoverfrom such an event. Refer to the chapter,Back-up and restore Information Studioin Administering Veritas™ InformationStudio.

■ 15K RPM Disks■ Minimum 350 IOPS

■ Solid State Disk (SSD): Recommended forInformation Studio Hub Data Disk for highestperformance.At least 4 disks configured as RAID 10 (RAID1+0).RAID 0 can be used, but loss of a disk willresult in data loss. A Backup and Restoremechanism must be in place to recover fromsuch an event. Refer to the chapter, Back-upand restore Information Studio inAdministering Veritas™ Information Studio.

Virtual machine for deploying InformationStudio Hub

System requirements for Remote Data EngineTo deploy the Remote Data Engine in your environment, carefully review theminimum requirements.

13Before you beginSystem requirements for Remote Data Engine

Note: Remote Data Engine requires a minimum of a single disk of 500 GB forapplication data. While importing the OVA, 500 GB of disk is automatically addedto the VM. If you need more than 500 GB disk, see Managing additional disks foradding additional disks.



■ One Network Interface Card (NIC)■ 1 node■ 16 CPUs and 32 GB RAM■ 500 GB for OS■ Additional data disks - 500 GB for Remote

Data Engine data■ Hard Disk Drive (HDD): Suitable for Remote

Data Engine OS Disk and Data Disk■ Separate Hypervisor and datastore disks

on different physical HDDs■ At least 4 disks configured as RAID 10

(RAID 1+0).RAID 0 can be used, but loss of a disk willresult in data loss. A Backup and Restoremechanism must be in place to recoverfrom such an event. Refer to the chapter,Back-up and restore Information Studioin Administering Veritas™ InformationStudio.

■ 15K RPM Disks

Note: Remote Data Engines benefit from theuse of SSD, but this is typically not a large factorin overall system performance.

Virtual machine for deploying RemoteData Engines

Table 1-5 ESX version support in Information Studio

VCenter 6.7 (Web Client)VCenter 6.5 (Web Client)VCenter6.0(ThickClient/WebClient)

ESX 6.7ESX 6.5ESX 6.0ESX 6.5ESX 6.0ESX 6.0

HTML/ FlexHTML/ FlexHTML/ FlexHTMLHTML

14Before you beginSystem requirements for Remote Data Engine

System requirements for Information StudioWindows Connectors

The operating system for Windows Connectors must be 64-bit with Windows 2012R2 or Windows 2016. To deploy the Information Studio Windows Connectors inyour environment, carefully review the minimum requirements:



■ One Network Interface Card (NIC)■ 4 CPUs and 8 GB RAM■ Free disk space - 100 GB■ Operating system - Windows 2012R2 or

Windows 2016

Virtual machine for Windows Connectors

Prerequisites for deploying an Information StudioHub

The Information Studio Hub is deployed on a virtual machine running on a VMwareESX Server. For successful deployment of the Information Studio Hub, ensure thatthe following prerequisites are satisfied:

■ You need sufficient privileges on the vCenter Server to deploy OVF template.Consult the VMware vSphere documentation for more information about theprivileges.

■ You need temporary free space of approximately 16 GB to store the systemimage on a local server close to the VMware ESX Server fromwhere the systemimage (OVA template) can be uploaded to the ESX server.

■ You need following network configuration for the virtual machine:

■ IPv4 address

■ Netmask

■ Gateway

■ DNS Server

■ DNS Domain Name

■ Make sure that FQDN of all Connections configured in Information Studio areresolvable from the corresponding Data Engine and Information StudioWindowsConnectors.

15Before you beginSystem requirements for Information Studio Windows Connectors

Note: You can get the network configuration details from your network or systemadministrator.

Prerequisites for deploying a Remote Data EngineThe Remote Data Engine is deployed on a virtual machine running on a VMwareESX Server. For successful deployment of the Data Engine, ensure that the followingprerequisites are satisfied:

■ The Information Studio Hub must be deployed before you begin deploying theData Engine.

■ You need temporary free space of approximately 16 GB to store the systemimage on a local server close to the VMware ESX Server fromwhere the systemimage (OVA template) can be uploaded to the ESX server.

■ You need sufficient privileges on the vCenter Server to deploy OVF template.Consult the VMware vSphere documentation for more information about theprivileges. You need the following network configuration for the virtual machine:

■ IPv4 address

■ Netmask

■ Gateway

■ DNS Server

■ DNS Domain Name

■ You need to create a user with the role of IT Admin who can add a Remote DataEngine. Refer to Organizations in Administering Veritas™ Information Studiofor more information.

■ Download the starter.zip for the remote Data Engine. See Downloading theon-premises remote Data Engine installer kit.

Downloading the on-premises remote Data Engine installer kitFrom the Information Studio administration console, download the installation kitfor the on-premises remote Data Engine. Users with the IT Admin role can performthis action.

16Before you beginPrerequisites for deploying a Remote Data Engine

To download the installer kit

1 Sign in to the Information Studio administration console with IT Admincredentials.

2 In the left navigation pane of the Information Studio administration console,click Data Engines. The list of configured Remote Data Engines is displayed.

3 Click New Data Engine.4 On the Data Engine Installation dialog box, click VMWare On-Premise, and

click Next.

5 In the Setup Data Engine dialog box, perform the following:■ In the Register Data Engine panel, enter a unique name for your engine.

A valid Data Engine name should:

■ Include a minimum of five characters and a maximum of 20 characters.

■ Begin and end with a letter, include only lowercase letters, and hyphen(-)among special characters.

The name can include numbers.

■ Enter the location details for your on-premises Data Engine cluster.

■ ClickRegister Data Engine to register the Data Engine with the InformationStudio Hub. In this step, a starter.zip file containing the registration(starter) file, certificates, and private key is downloaded.

6 After you have created the starter.zip file, proceed to setting up a virtualmachine environment for deploying the Information Studio Hub (see Settingup a virtual machine environment for deploying Information Studio Hub andadditional Remote Data Engines), followed by deploying a Remote Data Engineusing the wizard. See “Deploying a remote Data Engine using the wizard”on page 35.

Note: Veritas™ Information Studio encrypts all the data flowing between theInformation Studio Hub and Remote Data Engine(s) using the Transport LayerSecurity (TLS) protocol.

If you encounter errors when downloading the starter.zip file or the VMwareinstaller, you can download them from the Data Engines list page on theInformation Studio administration console. Click the vertical ellipses at theright-end of the unregistered Remote Data Engine, and select Downloadstarter.zip.

17Before you beginPrerequisites for deploying a Remote Data Engine

Prerequisites for installing Windows ConnectorsNode

Note: You need to install the Information Studio Windows Connectors only if youwant to monitor Microsoft SharePoint On-premises, Microsoft ExchangeOn-premises, Microsoft SQL Server, Oracle Database, and Native File SystemServers.

To make a secure communication between a Data Engine (default or remote) nodeand Information Studio Windows Connector node, download the installation kit forthe Information Studio Windows Connector from the Information Studioadministration console. Users with the IT Admin role can perform this action.

To add and set up a Windows Connector Node

1 Navigate to the Data Engines screen in the Information Studio administrationconsole.

2 Click the vertical ellipses at the right-end of the Data Engine to which you wantto add the Windows Connector, and select NewWindows Connectors Nodefrom the drop-down.

3 In the Setup New Windows Connector Node modal, enter a name for thenode in the Register your Windows Connectors Node Name field.

The Country and City fields are auto-populated by the options set for thecorresponding Data Engine.

4 Click Register Windows Connector.A starter.zip file containing the registration (starter) file, certificates, andprivate key is downloaded. Use this file to upload during the WindowsConnectors installation. See “Installing the Information Studio WindowsConnectors” on page 39. for instructions.

If you encounter errors when downloading the starter.zip file, you canre-attempt download from theData Engines list page on the Information Studioadministration console. Click the vertical ellipses at the right-end of the DataEngine, and select View Data Engines Node. This takes you to the WindowsConnector Nodes list page. Click the vertical ellipses at the right-end of therelevant Windows Connector Node, and select Registration file.

Note: If a Windows Connector Node is uninstalled, the name of the node isautomatically removed from the Node Name column in the Data Engine Nodesscreen.

18Before you beginPrerequisites for installing Windows Connectors Node

Viewing the Data Engine Nodes screenClick the vertical ellipses in the right-end of theData Engines list screen, and selectShow Data Engine Nodes from the drop-down to display the Data Engine Nodesscreen.

Table 1-7 Data Engine Nodes table

DescriptionColumn

Name of the newly added node. Click on theNode Name to display the right-hand-paneland view the node details.

Node Name

Type of the node. For example, WindowsConnector, Master, and so on

Type

IP address of the nodeIP Address

Status of the deployment at which the nodeis currently in. For example, Registered orPending

Registered Status

The Details Panel displays the pending andregistered Nodes. All the fields in this panelare non-editable.

Details Panel on the right-hand side

Click +New Windows Connectors Node to set up a new Windows ConnectorsNode. See “Prerequisites for installing Windows Connectors Node” on page 18. formore information.

Network requirementsThe connectivity requirements for Veritas™ Information Studio are as follows:

Table 1-8 Connectivity requirements for Information Studio

Default portDestinationSource

TCP port 8443 (HTTPS)Information Studio HubRemote Data Engine

TCP port 8443 (HTTPS)Information Studio Hub

Information Studio RemoteData Engine

Information Studio WindowsConnectors

Port 1556NBU MasterRemote Data Engine

19Before you beginNetwork requirements

Table 1-8 Connectivity requirements for Information Studio (continued)

Default portDestinationSource

UDP ports 137 and 138, andTCP ports 139 and 445

Native FSInformation Studio WindowsConnectors

TCP port 443 (HTTPS)■ Information Studio Hub■ Information Studio

Remote Data Engine

Browser used by theInformation Studio user

20Before you beginNetwork requirements

Deploying the InformationStudio Hub and DataEngine

This chapter includes the following topics:

■ Setting up a virtual machine environment for deploying Information Studio Huband additional Remote Data Engines

■ Deploying Information Studio Hub using the wizard

■ Deploying a remote Data Engine using the wizard

■ Installing the Information Studio Windows Connectors

■ Viewing the Data Engines screen

Setting up a virtual machine environment fordeploying Information Studio Hub and additionalRemote Data Engines

A virtual machine is configured through a client, such as VMware vSphere Client.

This section describes the steps for creating a virtual machine using VMwarevSphere Client. If you plan to use any other client service, refer to the correspondingdocumentation.

Review the system requirements for the VMware ESX Server before creating thevirtual machines. See System requirements for Information Studio Hub and System

2Chapter

requirements for Remote Data Engine for more information on the version and typeof VMware vSphere Client.

Note: The instructions and screenshots provided in this section are representativeand vary as per the version of the VMware vSphere Client version.

To set up VMware environment

1 Download Infostudio-1.1.0.ova from the Veritas Entitlement ManagementSystem.

2 Sign in to the VMware vSphere Client, select and right-click the host whereyou want the VM to be deployed, and select Deploy OVF Template... fromthe drop-down.

22Deploying the Information Studio Hub and Data EngineSetting up a virtual machine environment for deploying Information Studio Hub and additional Remote Data

Engines

3 Browse to the location on your local machine where you have downloaded theOVA file and click Next.

4 Specify or select the following details■ A name and location for the OVA to be deployed.

■ The destination resource pool within which you want to deploy the OVA.


Engines

5 Review and verify the specified OVA template details.

Note: During Information Studio deployment, the Ova shows the disk size asunknown for thick provision for vcenter 6.5 and vcenter 6.7 versions.


Engines

6 Accept the end user license agreements.


Engines

7 Select the deployment configuration, Hub or Remote Data Engine.


Engines

8 Select the storage for the configuration and disk files.

Note: Ensure that you select Thick Provision as the virtual disk format.

9 Select a destination network for each source network.


Engines

10 If required, customize the deployment properties. These include:

DescriptionDeployment property

The host name of the Information StudioVirtual Appliance

Host name

The DNS domain where you are addingthe Information Studio Virtual Appliance

DNS domain name

IPv4 address for the Information StudioVirtual Appliance

IP Address

IPv4 netmask for the Information StudioVirtual Appliance

Netmask

Gateway for the Information Studio VirtualAppliance

Gateway

DNS server for the Information StudioVirtual Appliance

DNS server

Optional DNS server for the InformationStudio Virtual Appliance

Optional DNS server

Note:While deploying Information Studio, for ESX 6.7, you cannot see thenetwork details on the ova deployment summary.


Engines

11 After you specify and confirm the configurations, click Finish. The virtualmachine gets deployed.

Note: You can get the network configuration details from your network orsystem administrator.

Note: Make sure that the format of the Host name contains alpha-numericcharacters, along with the special character, hyphen (-). The host name shouldnot start with a hyphen. For example, samplehost, sample-host, sample-host-1.

In the absence of DNS Server values in theDeploy OVF Template dialog box,the OVF file is imported but you receive an error on starting your VM after thedeployment is complete.

To resolve the error:

■ In VMware vSphere Client, select the VM you are using, then go to EditSettings > Options tab.

■ In Settings, click Properties, and under vApp Property Configuration,enter the corresponding details in the fields underHost Configuration andIPv4 Network Configuration.

■ Power on the VM.


Engines

Note: To add additional disks to the newly-created virtual machine, seeManaging additional disks.

12 On the left pane, right-click the newly added virtual machine and select PowerOn. In this step, the contents of the OVA file get extracted. Usually, it takesseveral minutes to complete the extraction.

Note: This step is applicable only to VMware Client version 6.7.

13 Wait for the virtual machine to start up completely. The process takes around10-15 minutes due to boot-up scripts being executed.

Note: During first-time boot-up, the unzipping of the application binaries takessome time. You can see the logon prompt appear after the process is complete.

Deploying Information Studio Hub using thewizard

After the OVA file is extracted and the virtual machine is powered on, you mustcomplete the deployment procedure by following the deployment wizard inInformation Studio.

30Deploying the Information Studio Hub and Data EngineDeploying Information Studio Hub using the wizard

To run the Information Studio Hub deployment wizard

1 On the web browser, enter https://:8080 which is the IP address of the Information Studio Hub that youcreated in the Setting up a virtual machine environment for deployingInformation Studio Hub and additional Remote Data Engines step. This opensthe Veritas software license agreement page.

2 Review and accept the license agreement to proceed.


http://:8080http://:8080

3 In the Information Studio Hub deployment screen, click Next.

4 Select the Country and City from the respective drop-downs, which indicatesthe geographic location of the Information Studio Hub, and click Next.


5 Enter and confirm the Administrator password, then click Deploy.

Note:Use this password to later log into the Information Studio UI and completethe post-installation configuration tasks.

The administrator password you enter here is of the [email protected] of the Information Studio product and not theadministrator password of the virtual machine.

Note: The deployment process may take up to 30 minutes.


6 After successful installation of the Information Studio Hub, click LaunchVeritas™ Information Studio to sign into the Information Studio administrationconsole.

Note: Click Download Logs to download and view detailed logs of thedeployment.

Note: If the deployment fails, click Retry to re-attempt deployment.

Performing post-deployment tasksAfter you have deployed the Information Studio Hub, perform the following tasks:

■ Launch the Information Studio UI using https://.

■ Make sure you configure the Active Directory to be able to use InformationStudio. For more information and instructions on configuring the Active Directory,refer to the section on Editing a customer account in the Organizations chapterof Administering Veritas™ Information Studio.Optionally, upload your own Certificate Authority-signed transport layer security(TLS) certificate for the web server. Refer to the section on Certificatemanagement in theOrganizations chapter of Administering Veritas™ InformationStudio for more information.

■ Create users in the Information Studio administration console with the role ofIT Admin. Refer to the section on Granting access to Information Studio usersin the Organizations chapter of Administering Veritas™ Information Studio formore information.

■ (Optional) You can monitor Information Studio services using tools such asNagios.


Note: You can access Administering Veritas™ Information Studio and Veritas™Information Studio User Guide from the Veritas Support page.

Deploying a remote Data Engine using the wizardAfter successful installation of the Information Studio Hub, launch the InformationStudio administration console. The Information Studio Hub already includes a defaultData Engine, which can be used for certain Connector types. To configure otherConnector types, to get better scale, or to cater to remote geographic locations,you can configure one or more additional remote Data Engines.

To run the Data Engine deployment wizard

1 Set up a virtual machine using the procedure described in Setting up a virtualmachine environment for deploying Information Studio Hub and additionalRemote Data Engines.

2 On the web browser, enter the IP address (https://:8080) of the virtual machine that you had created in Step 1. Thisopens the Veritas software license agreement page.

35Deploying the Information Studio Hub and Data EngineDeploying a remote Data Engine using the wizard

http://:8080http://:8080

3 Review and accept the license agreement.


4 In the Information Studio Remote Data Engine deployment screen, clickNext.


5 Click Upload registration file, and browse to the starter.zip file that youdownloaded from the Information Studio administration console, then clickDeploy.

Click I don't have a configuration file if you have not already downloadedthe starter.zip and proceed to downloading one using instructions inDownloading the on-premises remote Data Engine installer kit.


Note: The deployment process takes up to 20 minutes

Installing the Information Studio WindowsConnectors

You can download theWindows Connectors installer from the same location whereyou downloaded the OVA. You must provision a Windows virtual machine tocomplete the installation. See “Prerequisites for installing Windows ConnectorsNode” on page 18. for instructions.

See “System requirements for Remote Data Engine” on page 13.

To install the Windows Connectors on a Windows virtual machine

1 Sign in to the machine intended to serve as the Connectors server with theadministrator credentials.

Note: The Windows Connector machine time (UTC) should be the same asthe one with the Information Studio Hub node.

2 Double-click Veritas_InformationStudio_windows__x64.exe tolaunch the installer. If you are not signed in to the computer as Administrator,you are prompted to enter the administrator credentials.

3 TheWelcome to the Setup Wizard window appears. Click Next.4 In the License Agreement panel, select I accept the agreement and click

Next.

5 On the Configuration details panel, enter the following details:

39Deploying the Information Studio Hub and Data EngineInstalling the Information Studio Windows Connectors

■ Data Directory: Browse to the location where you want to store the productdata before it is sent to the Data Engine. By default, the destination directoryis C:\Program Files\InformationStudio\data. You can configure it ina separate directory. The data directory should reside on a volume that hassufficient space and high-performance disk.

■ starter.zip file location: Browse to the location of the Windows Connectorstarter.zip you downloaded in the Information Studio administration console.See “Prerequisites for installing Windows Connectors Node” on page 18.for instructions.

6 Click Next to begin the installation.7 Click Finish.

Note:After the installation of the Information StudioWindows Connector is complete,ensure that you block the port 3000 using a firewall.

Viewing the Data Engines screenThe remote Data Engines list page displays details of deployed data engines.

Table 2-1 Remote Data Engines table

DescriptionColumn

Name of the Data Engine given duringregistration

Data Engine

Date on which the Data Engine is deployedDeployed On

Version of the Data Engine is deployedDeployed Version

Status of the deployment at which the DataEngine is currently in. For example,Registered or Pending

Registered Status

Number ofWindows Connectors NodesWindows Connectors Nodes

Windows Connectors machine detailsassociated with the deployed Data Engine

Right-hand side panel

40Deploying the Information Studio Hub and Data EngineViewing the Data Engines screen

Upgrading InformationStudio v1.1 onwards

This chapter includes the following topics:

■ Upgrading the Information Studio Hub and Remote Data Engine

Upgrading the InformationStudioHub andRemoteData Engine

You can upgrade to the next version of Information Studio Hub and Remote DataEngine from the same UI of the Veritas™ Information Studio.

Note: The Upgrade option is visible on the Information Studio UI only after youhave enabled upgrade from the Information Studio CLI. Refer to AdministeringVeritas™ Information Studio for instructions.

Note: Ensure that you take a backup of your system before performing an upgrade.

To upgrade Information Studio Hub and Remote Data Engine

1 Log into the virtual machine using the host admin credentials.2 Execute the command manage upgrade-ui application-start.

3Chapter

3 To access the Upgrade UI, go to https://:8080 which is the IP address of the starter virtualmachine that you created in the Setting up a virtual machine environment fordeploying Information Studio Hub and additional Remote Data Engines step..

4 Click Upgrade in the left navigation pane.

5 Follow the instructions on the UI.■ Download the upgrade package from Veritas SORT (Services and

Operations Readiness Tools) and save that to a location on your computer.

■ Click Upload to upload the .tar fileThe upload process take approximately an hour.

Note: You can cancel the upload process at any stage (during or even afterthe upload process) and you can choose to upload the .tar file at anotherlocation. You can also delete the upgrade package by selecting anotherlocation for the package.

■ After the package is uploaded, click Start Upgrade to upgrade InformationStudio.

Note: Make sure you back-up your system before you start the upgradeprocess.

6 If upgrade fails, click Retry to attempt the upgrade process again.Alternatively, click Download Logs to download and view detailed logs of thedeployment at any point.

42Upgrading Information Studio v1.1 onwardsUpgrading the Information Studio Hub and Remote Data Engine

https://:8080https://:8080

Disk managementThis chapter includes the following topics:

■ About disk management

■ Viewing Disks screen

■ Managing additional disks

About disk managementThe Disks screen is enabled after successful deployment of Information StudioHub (in case of first-time deployment) or Remote Data Engine. To access theDisksscreen, enter https://:8080/ in the web browser, and clickDisksin the left navigation pane.

Disk sizingInformation Studio Hub requires approximately 1TB of data disk per 150 TB of datascanned. The 150 TB refers to the total logical size of the items on disk. If youintend using more data than this, more storage capacity can be specified duringinitial configuration of the Information Studio Hub Virtual Machine, or added later.See “Prerequisites for deploying an Information Studio Hub” on page 15. andPrerequisites for deploying a Remote Data Engine for information on thepre-requisites while deploying an Information Studio Hub or Remote Data Engine,respectively.

The sizing is an approximation and varies based on the following:

■ The amount of classification data generated

■ The average logical item size on disk

The above calculation assumes an average logical item size of 500KB, based onreal-world observations. For example, if your environment has a lower average itemsize then you can expect to store more than 150 logical TBs per 1TB of data disk.

4Chapter

See “Viewing Disks screen” on page 44. to view disk utilization and Managingadditional disks for instructions on how to add additional storage to InformationStudio Hub.

Viewing Disks screenTo access the Disks screen, enter https://:8080/ in the webbrowser, and click Disks in the left navigation pane.

The Disks screen is divided into two panes. The upper pane includes the Storagesummary and the lower pane displays the Physical disks.

Figure 4-1 Disks screen for Information Studio Hub

Figure 4-2 Disks screen for Remote Data Engine

Storage summaryThe Storage summary displays the logical partitions of the data disk. The partitionsinclude:

■ Assets db (displayed only for Information Studio Hub)

■ Asset Search db (displayed only for Information Studio Hub)

44Disk managementViewing Disks screen

■ Application db (displayed only for Information Studio Hub)

■ Messaging

■ Scan db

■ Connector db (displayed only for Information Studio Hub)

■ Classification

■ System logs

Note: For Remote Data Engine, only four of the eight logical partitions are availableand displayed.

Each partition tile displays total space, used space, and free space available onthat logical partition.

Physical disksThe Physical disks pane displays the existing and newly-added data disks alongwith its configuration status. You can view the following:

DescriptionColumn name

Name of the diskName

Total disk sizeTotal

The configuration status of the disk. Thedifferent status include Not Configured, InProgress, Configured

Status

The vertical ellipses button to configurenewly-added disks

Note: The Actions column is not visible ifall the disks in the Physical disks pane areconfigured.

Action

Managing additional disksWhile viewing the Storage Summary of the Information Studio Hub or RemoteData Engine on the Disks screen, if you observe the disks are filling up, you canextend the disk. This section describes the steps for adding additional disks in theVMware vSphere Client. The steps are applicable to both, Information Studio Huband Remote Data Engine VM.

45Disk managementManaging additional disks

To add additional disks

1 Select the newly created virtual machine, and in its Properties dialog box, goto the Hardware tab and click Add to add a new hard disk.

2 In the Add Hardware dialog box:■ Select Hard Disk as the Device Type, then click Next.


■ Select Create a new virtual disk.

■ Select the virtual disk size and provisioning policy.

■ Enter the Disk Size

Note: Ensure that you enter the disk space either in TB or GB. You caneither add a single disk or multiple disks. However, ensure that you adda minimum 10 GB of disk size. There is no maximum limit for the disk.

■ Select Thick Provision for Disk Provisioning


■ Select Store with the virtual machine as the Location for the virtualdisk

■ Specify the Advanced Options.


■ Review the selected options, then click Finish.


A new hard disk of the specified size is added.

After you have added a new disk in VMware vSphere Client, you need to refreshthe Disks screen for the newly-added disk to appear in the Physical disks pane.Proceed to configuring the newly-added disk.


To configure the newly-added disk

◆ In the Physical disks pane of the Disks screen, click the vertical ellipsesbutton in the Actions column, and select Configure.

The configuration status of the disk changes from Not configured to Inprogress, and then Configured.

To re-enable read-only indexes for write for ElasticSearch

1 Log into the virtual machine as the host admin using the command:ssh hostadmin@

2 Run the command, manage index enablewrite.

3 At the prompt, Do you want to continue?, select yes or no.

4 Select yes, and hit enter.

You will see, All indexes have been successfully re-enabled.

The read-only indexes for write operation are re-enabled successfully.


Getting helpThis chapter includes the following topics:

■ Displaying the online help

■ Using the Veritas™ Information Studio product documentation

Displaying the online helpYou can access the online help through the management console of Veritas™Information Studio by clicking the question mark icon.

Using the Veritas™ Information Studio productdocumentation

The latest version of the Veritas™ Information Studio product documentation isavailable on the Veritas Services and Operations Readiness Tools (SORT) website.

https://sort.veritas.com/documents

You must specify the product and the platform and apply other filters for finding theappropriate document. Make sure that you are using the current version ofdocumentation. The document version appears on page 2 of each guide. Thepublication date appears on the title page of each document. The documents areupdated periodically for errors or corrections.

The following documents are available on the SORT site:

■ Veritas™ Information Studio Release Notes

■ Veritas™ Information Studio Deployment Guide

■ Veritas™ Information Studio Administration Guide

■ Veritas™ Information Studio User Guide

5Chapter

https://sort.veritas.com/documents

■ Veritas™ Information Studio Software Compatibility List

■ Veritas™ Information Studio Third-party Software Licence Agreements

53Getting helpUsing the Veritas™ Information Studio product documentation

Veritas™ Information Studio Deployment GuideTechnical SupportContents1. Before you beginAbout Information Studio deploymentSystem requirements for Information Studio HubSystem requirements for Remote Data EngineSystem requirements for Information Studio Windows ConnectorsPrerequisites for deploying an Information Studio HubPrerequisites for deploying a Remote Data EngineDownloading the on-premises remote Data Engine installer kit

Prerequisites for installing Windows Connectors NodeViewing the Data Engine Nodes screen

Network requirements

2. Deploying the Information Studio Hub and Data EngineSetting up a virtual machine environment for deploying Information Studio Hub and additional Remote Data EnginesDeploying Information Studio Hub using the wizardPerforming post-deployment tasks

Deploying a remote Data Engine using the wizardInstalling the Information Studio Windows ConnectorsViewing the Data Engines screen

3. Upgrading Information Studio v1.1 onwardsUpgrading the Information Studio Hub and Remote Data Engine

4. Disk managementAbout disk managementViewing Disks screenManaging additional disks

5. Getting helpDisplaying the online helpUsing the Veritas™ Information Studio product documentation

Date post:	12-Mar-2020
Category:	Documents
Upload:	others
View:	5 times
Download:	0 times

Veritas Information Studio Deployment Guide · Components Description...

Documents