About Veritas Resiliency Platform - I am Healthy! tus3slfwebpex01

About Veritas Resiliency Platform - I am Healthy! tus3slfwebpex01
Veritas™ Resiliency
Platform 1.2: Deployment
Guide
April 2016
Veritas Resiliency Platform: Deployment Guide
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Product version: 1.2
Document version: 1.2 Rev 0
Legal Notice
Copyright © 2016 Veritas Technologies LLC. All rights reserved.
Veritas and the Veritas Logo 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. Please see the Third Party Legal Notice Appendix to this Documentation
or TPIP ReadMe File accompanying this product for more information on the Third Party
Programs.
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 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," 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.
Veritas Technologies LLC
500 E Middlefield Road
Mountain View, CA 94043
http://www.veritas.com
Technical Support
Technical Support maintains support centers globally. Technical Support’s primary
role is to respond to specific queries about product features and functionality. The
Technical Support group also creates content for our online Knowledge Base. The
Technical Support group works collaboratively with the other functional areas within
the 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 amount
of service for any size organization
■
Telephone and/or Web-based support that provides rapid response and
up-to-the-minute information
■
Upgrade assurance that delivers software upgrades
■
Global support purchased on a regional business hours or 24 hours a day, 7
days a week basis
■
Premium service offerings that include Account Management Services
For information about our support offerings, you can visit our website at the following
URL:
www.veritas.com/support
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.
Contacting Technical Support
Customers with a current support agreement may access Technical Support
information at the following URL:
www.veritas.com/support
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be at
the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■
Product release level
■
Hardware information
■
Available memory, disk space, and NIC information
■
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 registration
If your product requires registration or a license key, access our technical support
Web page at the following URL:
www.veritas.com/support
Customer service
Customer service information is available at the following URL:
www.veritas.com/support
Customer Service is available to assist with non-technical questions, such as the
following 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
Support agreement resources
If you want to contact us regarding an existing support agreement, please contact
the support agreement administration team for your region as follows:
Worldwide (except Japan)
[email protected]
Japan
[email protected]
Contents
Technical Support
Chapter 1
............................................................................................ 4
Overview of Resiliency Platform deployment
.......... 13
About Veritas Resiliency Platform ....................................................
About Resiliency Platform features and components ............................
Veritas Resiliency Platform deployment infrastructure ....................
Resiliency Platform component diagram ......................................
Resiliency domain ..................................................................
Resiliency Manager ................................................................
Infrastructure Management Server (IMS) .....................................
Replication in a Resiliency Platform deployment ...........................
Planning a resiliency domain for efficiency and fault tolerance ...............
Deployment process overview .........................................................
Chapter 2
System requirements
13
14
15
16
18
18
19
20
21
22
....................................................... 24
Supported hypervisors for Resiliency Platform virtual appliance ............. 24
System resource requirements for Resiliency Platform ......................... 25
Network and firewall requirements ................................................... 25
Chapter 3
Deploying the Resiliency Platform virtual
appliance ........................................................................ 28
About deploying the Resiliency Platform virtual appliance .....................
Downloading the Resiliency Platform virtual appliance .........................
Deploying the virtual appliance through VMware vSphere Client ............
Deploying the virtual appliance through Hyper-V Manager ....................
Chapter 4
28
29
29
30
Configuring the Resiliency Platform virtual
appliance ........................................................................ 32
About configuring the Resiliency Platform components ......................... 32
Prerequisites for configuring Resiliency Platform components ................ 33
Configuring the Resiliency Platform component through the product
bootstrap .............................................................................. 33
Contents
Chapter 5
Chapter 6
Chapter 7
Setting up the resiliency domain ................................... 35
About the web console ..................................................................
Connecting to the Resiliency Platform web console .............................
Getting started with a new Resiliency Platform configuration .................
Adding a Resiliency Manager to an existing resiliency domain ...............
Removing a Resiliency Manager from a resiliency domain ....................
Viewing the status of a Resiliency Manager in a data center ..................
35
36
37
39
40
42
Managing Infrastructure Management
Servers ...........................................................................
44
How Infrastructure Management Servers relate to data centers ..............
Adding an IMS ............................................................................
Removing an IMS .........................................................................
Modifying an IMS .........................................................................
Reconnecting the IMS to a Resiliency Manager ..................................
Managing data centers ..................................................................
Configuring network settings for data centers .....................................
Configuring DNS server settings for a data center .........................
Configuring subnet information for a data center ...........................
Configuring V-Switch information for a data center ........................
44
45
46
47
48
49
51
51
53
53
Managing Veritas InfoScale Operations Manager
Server .............................................................................
55
About Veritas InfoScale Operations Manager .....................................
Resiliency Platform support for InfoScale applications .........................
Managing InfoScale applications using Resiliency Platform ...................
Prerequisites for managing Veritas InfoScale Operations Manager
server using Resiliency Platform ...............................................
Adding a Veritas InfoScale Operations Manager server ........................
Removing a Veritas InfoScale Operations Manager server ....................
Modifying a Veritas InfoScale Operations Manager server ....................
Chapter 8
Adding the asset infrastructure
55
56
57
57
58
59
60
..................................... 62
About the asset infrastructure .........................................................
Configuring IMS asset infrastructure for Hyper-V virtual machines ..........
Configuring IMS asset infrastructure for VMware virtual machines ..........
Configuring IMS asset infrastructure for application discovery on
Hyper-V virtual machines .........................................................
Configuring IMS asset infrastructure for application discovery on
VMware virtual machines .........................................................
63
64
65
67
68
8
Contents
Configuring IMS asset infrastructure for application discovery on
physical systems .................................................................... 70
Adding the asset infrastructure to an Infrastructure Management Server
(IMS) ................................................................................... 72
Managing host assets for an IMS ..................................................... 73
About adding host assets to an IMS ........................................... 73
Prerequisites for adding hosts to an IMS ..................................... 74
Installing the host package on a Windows host ............................. 75
About using a CSV file for adding hosts to an IMS ......................... 76
Adding hosts to an IMS ............................................................ 76
Removing hosts from an IMS ................................................... 78
Uninstalling the host package from a Linux host ............................ 79
Uninstalling the host package from a Windows host ....................... 80
Refreshing host discovery information for an IMS .......................... 80
Managing Hyper-V assets for an IMS ............................................... 81
About Microsoft Hyper-V virtualization discovery ........................... 81
Prerequisites for Microsoft Hyper-V virtualization discovery by the
IMS ............................................................................... 81
Managing VMware virtualization servers for an IMS ............................. 82
Prerequisites for adding VMware servers for discovery by the
IMS ............................................................................... 83
About using a separate Control Host for discovery of VMware
servers ........................................................................... 84
About near real-time discovery of VMware events ......................... 84
Setting up near real-time discovery of VMware events ................... 86
Configuring the VMware vCenter Server to generate SNMP
traps .............................................................................. 87
Adding virtualization servers for VMware discovery by the
IMS ............................................................................... 88
Editing a VMware virtualization discovery configuration in the
IMS ............................................................................... 90
Removing a virtualization discovery configuration from the
IMS ............................................................................... 91
Refreshing a VMware virtualization discovery configuration ............. 91
Refreshing an ESX Server discovery .......................................... 91
Managing enclosure assets for an IMS ............................................. 92
About the discovery host .......................................................... 93
Configuration prerequisites for adding storage enclosures to an
IMS ............................................................................... 93
Adding storage enclosures for discovery by the IMS .................... 104
Configuration prerequisites for adding replication appliances ......... 111
Adding RecoverPoint appliance for replication ............................ 112
Editing the discovery configuration for an enclosure ..................... 113
9
Contents
Removing the discovery configuration for an enclosure .................
Refreshing enclosure discovery information for an IMS .................
Managing add-ons for the hosts .....................................................
Installing add-ons on the hosts ................................................
Uninstalling add-ons from the hosts ..........................................
Managing solutions for the hosts ....................................................
Installing a solution on the hosts ..............................................
Uninstalling a solution from the hosts ........................................
Chapter 9
Managing users and global settings
114
114
115
115
117
118
118
119
.......................... 120
Managing licenses ......................................................................
About licenses .....................................................................
Viewing and managing licenses ...............................................
Viewing the License Entitlement report ......................................
Managing user authentication and permissions .................................
About user authentication in the web console .............................
About user permissions in the web console ................................
Predefined personas .............................................................
About limiting object scope for personas ....................................
Configuring authentication domains .........................................
Unconfiguring authentication domains .......................................
Showing domains on login screen ...........................................
Configuring user groups and users ...........................................
Assigning permissions to user groups and users .........................
Adding custom personas ........................................................
Predefined jobs that can be used for custom personas .................
Managing reports .......................................................................
About reports .......................................................................
Managing report preferences ..................................................
Scheduling a report ...............................................................
Running a report ..................................................................
Viewing and managing report schedules ....................................
Managing settings for alerts and notifications and general product
settings ...............................................................................
Adding, modifying, or deleting email settings ..............................
Adding, modifying, or deleting SNMP settings .............................
Setting up rules for event notifications .......................................
Modifying purge settings for logs and SNMP traps .......................
Enabling or disabling telemetry collection ........................................
120
120
121
122
122
123
124
125
128
128
132
133
133
134
136
137
139
139
139
142
144
145
147
147
149
149
150
151
10
Contents
Chapter 10
Updating Resiliency Platform ....................................... 152
About updating Resiliency Platform ...............................................
About applying updates to Resiliency Platform ..................................
Prerequisites for a repository server ...............................................
Setting up the repository server and downloading updates ..................
Adding a repository server in Resiliency Platform ..............................
Assigning a repository server in Resiliency Platform ...........................
Applying updates to virtual appliances using the console ....................
Applying updates to virtual appliance using CLISH menu ....................
Refreshing the information about applicable updates .........................
Removing an update from the repository server ................................
Chapter 11
152
153
154
155
156
157
157
159
159
160
Uninstalling Resiliency Platform .................................. 161
About uninstalling Resiliency Platform ............................................. 161
Chapter 12
Troubleshooting and maintenance
............................. 162
Viewing events and logs in the console ...........................................
Accessing Resiliency Platform log files ............................................
Displaying risk information ............................................................
Predefined risks in Resiliency Platform ......................................
About the Resiliency Manager services ..........................................
Components of Resiliency Platform virtual appliance ..........................
Troubleshooting discovery of assets ...............................................
About the frequency of asset information discovery ............................
Troubleshooting the connection between Resiliency Managers in a
resiliency domain ..................................................................
Troubleshooting removing a Resiliency Manager from a resiliency
domain ...............................................................................
Using Veritas Services and Operations Readiness Tools to find a
Unique Message Identifier description and solution ......................
Appendix A
162
163
164
165
167
168
169
171
172
173
174
Virtual appliance security features .............................. 176
Operating system security ............................................................
Management Security ..................................................................
Network security .........................................................................
Access control security ................................................................
Physical security .........................................................................
176
176
177
177
177
11
Contents
Appendix B
Using CLISH menu in Resiliency Platform ............... 178
About CLISH ............................................................................. 178
Using CLISH .............................................................................. 179
Appendix C
Tips on using the web console
.................................... 187
Tour of the Resiliency Platform web console screen ...........................
Menu bar options ..................................................................
Navigation pane options .........................................................
Using Quick Actions for shortcuts to common tasks ...........................
Filtering and searching for objects in the web console ........................
About settings in the web console ..................................................
About the Resiliency Platform Dashboard ........................................
Web console icons ......................................................................
Glossary
Index
187
188
190
190
191
191
193
194
........................................................................................................... 196
.................................................................................................................. 198
12
Chapter
1
Overview of Resiliency
Platform deployment
This chapter includes the following topics:
■
About Veritas Resiliency Platform
■
About Resiliency Platform features and components
■
Planning a resiliency domain for efficiency and fault tolerance
■
Deployment process overview
About Veritas Resiliency Platform
Veritas Resiliency Platform offers a unified approach for visibility and control of IT
service continuity for applications, virtual machines, and complex, multi-tier business
services across a global landscape.
Resiliency Platform has the following core capabilities:
Recovery
Resiliency Platform provides a disaster recovery (DR) solution
using data centers on premises in different geographical
locations. The management console simplifies recovery, with
single-click rehearsal and recovery operations.
Visibility
The console Dashboard provides visibility into the health of
applications, virtual machines, and multi-tier business
services.
Orchestration
Resiliency Platform can assist in data center day-to-day
workload automation activities. For instance, virtual machines
or IT services can be started and stopped for maintenance.
Overview of Resiliency Platform deployment
About Resiliency Platform features and components
About Resiliency Platform features and
components
The following is a brief introduction to Veritas Resiliency Platform key components
and features. Administrators responsible for deploying and configuring the product
need to understand these in more detail.
resiliency domain
The logical scope of a Resiliency Platform deployment.
It can extend across multiple data centers.
See “Resiliency domain” on page 18.
Resiliency Manager
The component that provides resiliency capabilities within a
resiliency domain. It is composed of loosely coupled services,
a distributed data repository, and a management console.
The Resiliency Manager is deployed as a virtual appliance.
See “Resiliency Manager” on page 18.
Infrastructure Management
Server (IMS)
The component that discovers, monitors, and manages the
asset infrastructure within a data center. The IMS transmits
information about the asset infrastructure to the Resiliency
Manager. The IMS is deployed as a virtual appliance.
To achieve scale, multiple IMSs can be deployed in the same
data center.
See “Infrastructure Management Server (IMS)” on page 19.
Veritas InfoScale Operations The component that allows discovery of InfoScale applications
Manager Management Server that are already configured in Veritas InfoScale Operations
Manager. Also referred to as Veritas InfoScale Operations
Manager server.
See “Managing InfoScale applications using Resiliency
Platform” on page 57.
data center
For a disaster recovery use case, the resiliency domain must
contain at least two data centers in different locations, a
production data center and recovery data center. Each data
center has a Resiliency Manager and one or more IMSs.
14
Overview of Resiliency Platform deployment
About Resiliency Platform features and components
asset infrastructure
The data center assets that you add to Resiliency Platform
for discovery and monitoring by the IMS.
The asset infrastructure can include hosts (Windows or Linux
servers), virtualization servers for Hyper-V and VMware, and
enclosures (storage arrays). Once the asset infrastructure is
discovered by the IMS, the discovered virtual machines or
applications are listed in the console as assets to manage
or protect.
resiliency group
The unit of management and control in Resiliency Platform.
You organize related assets into a resiliency group and
manage and monitor them as a single entity.
Virtual Business Service
(VBS)
A multi-tier business service where each VBS tier hosts one
or more resiliency groups. A VBS lets you group multiple
services as a single unit for visualization, automation, and
controlled start and stop in the desired order. VBS uses the
vertical grouping mechanism to group the multiple
services.You can also migrate or takeover the entire VBS.
See “Resiliency Platform component diagram” on page 16.
Veritas Resiliency Platform deployment infrastructure
A typical deployment consists of an Infrastructure Management Server (IMS)
reporting to a Resiliency Manager. Various physical and virtual assets are associated
with the IMS. For a disaster recovery deployment, this arrangement of various
components and assets exists in the recovery data center as well as in the
production data center.
The following diagram depicts the deployment infrastructure and how Resiliency
Manager, IMS, and various assets associated with the IMS interact with each other.
15
Overview of Resiliency Platform deployment
About Resiliency Platform features and components
Figure 1-1
Deployment infrastructure
Resiliency Platform component diagram
The diagram shows a simple overview of the main components of Resiliency
Platform - the Resiliency Manager, Infrastructure Management Server (IMS), and
resiliency domain - and their relationships to data centers and the data center asset
infrastructure.
For disaster recovery, the resiliency domain must contain at least two data centers,
a production data center and recovery data center. Each data center has a Resiliency
Manager and one or more Infrastructure Management Servers.
Resiliency Platform can also be implemented at a single data center for automation
of workload tasks.
The asset infrastructure includes the data center assets that you add to the IMS
for IMS discovery and monitoring. The asset infrastructure can include hosts
16
Overview of Resiliency Platform deployment
About Resiliency Platform features and components
(Windows or Linux servers), virtualization servers for Hyper-V and VMware, and
enclosures (storage arrays).
See “Veritas Resiliency Platform deployment infrastructure” on page 15.
This diagram does not show the replication details for the asset infrastructure.
See “Replication in a Resiliency Platform deployment” on page 20.
Replication, disaster recovery configuration, and disaster recovery operations are
described in the solutions guides.
Figure 1-2
Resiliency Platform components
17
Overview of Resiliency Platform deployment
About Resiliency Platform features and components
Resiliency domain
A resiliency domain is the management domain of a Veritas Resiliency Platform
deployment. It represents the scope of the deployment, which can spread across
multiple data centers and can include multiple Resiliency Managers and other
components, along with the infrastructure that is being managed and protected.
Within the resiliency domain, Resiliency Platform can protect assets, for example,
virtual machines and applications, and orchestrate automation of workload tasks
for the assets.
The resiliency domain is a logical object that you create from the web console after
you deploy the Resiliency Manager.
Note: For disaster recovery, the resiliency domain must contain at least two data
centers, a production data center and recovery data center. Each data center has
a Resiliency Manager and one or more IMSs. A resiliency domain can optionally
be implemented at a single data center for automation of workload tasks.
See “Resiliency Platform component diagram” on page 16.
See “Resiliency Manager” on page 18.
See “Infrastructure Management Server (IMS)” on page 19.
Resiliency Manager
The Resiliency Manager includes a set of loosely coupled services, a distributed
data repository, and a management web console. The Resiliency Manager provides
the services required for protecting assets, such as virtual machines, within a
resiliency domain. It also provides workload automation services.
In a typical deployment, one Resiliency Manager is deployed in the production data
center. You deploy another Resiliency Manager in a recovery data center in another
geographical location.
When you deploy the first Resiliency Manager, you create the resiliency domain.
When you deploy the second Resiliency Manager, you add it to the same resiliency
domain (also referred to as joining the existing resiliency domain).
The Resiliency Manager discovers and manages information about data center
assets from an Infrastructure Management Server (IMS), which is another required
Resiliency Platform component. The Resiliency Manager stores the asset information
in its data repository and displays the information in its management console.
Multiple Resiliency Managers that are part of the same domain synchronize their
databases using built-in replication. Each Resiliency Manager has its own web
console but because the data is synchronized, all consoles show the same data.
18
Overview of Resiliency Platform deployment
About Resiliency Platform features and components
Operations can be performed from any console and the results show in all the
consoles in the resiliency domain.
See “Resiliency Platform component diagram” on page 16.
See “Resiliency domain” on page 18.
See “Infrastructure Management Server (IMS)” on page 19.
Infrastructure Management Server (IMS)
Each Resiliency Manager requires one or more Infrastructure Management Servers
(IMSs). An IMS discovers and monitors assets within a data center. You use the
web console to add the asset infrastructure to the IMS so that assets can be
discovered and monitored.
The asset infrastructure can include objects such as hosts, virtualization servers,
and enclosures (storage arrays).
The IMS sends information about the assets to the Resiliency Manager so that the
Resiliency Manager can manage the assets. Management operations on assets
(for example, starting or stopping virtual machines) that you initiate from the web
console are carried out by the IMS.
If there are multiple data centers in different geographical locations, a separate IMS
is deployed and configured for each geographical data center location.
Each IMS connects to only one Resiliency Manager at a time. If a Resiliency
Manager failure occurs, an IMS can automatically connect to another Resiliency
Manager within the same domain.
You can also configure multiple Infrastructure Management Servers in the same
data center. For example, to achieve scale, you can add a separate IMS for a
separate business unit such as Human Resources or Finance. More than one IMS
can be managed by the same Resiliency Manager.
19
Overview of Resiliency Platform deployment
About Resiliency Platform features and components
Figure 1-3
Multiple Infrastructure Management Servers in a data center
See “Resiliency domain” on page 18.
See “Resiliency Manager” on page 18.
Replication in a Resiliency Platform deployment
Veritas Resiliency Platform provides data recovery from your production data center
to your recovery data center using two forms of replication: array-based replication
(block-based replication) and hypervisor-based replication. Figure 1-4 depicts how
replication is performed.
20
Overview of Resiliency Platform deployment
Planning a resiliency domain for efficiency and fault tolerance
For details on supported replication hardware and software, refer to the Hardware
and Software Compatibility List.
Figure 1-4
Replication in a Resiliency Platform deployment
More information on configuring replication for use with Resiliency Platform is
available in the solutions guides:
Solutions for Microsoft Hyper-V.
Solutions for VMware.
Solutions for Applications
Planning a resiliency domain for efficiency and
fault tolerance
Before you deploy Veritas Resiliency Platform, you should plan how to scale the
deployment for efficiency and fault tolerance.
You can deploy a Resiliency Manager and Infrastructure Management Server (IMS)
on the same virtual appliance. However, to meet performance requirements,
production environments typically require using separate virtual appliances for the
Resiliency Manager and IMS.
Therefore, the recommended minimum deployment for disaster recovery would be
four virtual appliances: a Resiliency Manager and IMS in the production data center
and a Resiliency Manager and IMS in the recovery data center.
21
Overview of Resiliency Platform deployment
Deployment process overview
The production and recovery data centers do not require a one-on-one mapping of
IMSs. For example, you can have two IMSs in the production data center and one
IMS in the recovery data center.
See “Resiliency domain” on page 18.
See “Resiliency Manager” on page 18.
See “Infrastructure Management Server (IMS)” on page 19.
Deployment process overview
The following steps must be completed before you can start managing and
monitoring your assets and performing disaster recovery operations with Veritas
Resiliency Platform.
Table 1-1
Deployment process overview
Step Description
More information
1
Deploy the Resiliency Platform virtual
appliances
Deployment Guide
Configure the virtual appliances as
Resiliency Platform components
Deployment Guide
2
See “About deploying the Resiliency
Platform virtual appliance” on page 28.
See “About configuring the Resiliency
Platform components” on page 32.
3
Set up the resiliency domain using the
Deployment Guide
Getting Started wizard in the web console
See “Getting started with a new Resiliency
Platform configuration” on page 37.
4
Finish configuring the settings for the
resiliency domain
Deployment Guide
See “Adding an IMS ” on page 45.
See “Managing user authentication and
permissions” on page 122.
See “Managing settings for alerts and
notifications and general product settings”
on page 147.
5
Add the asset infrastructure to the
Deployment Guide
Infrastructure Management Server (IMS)
See “Adding the asset infrastructure to an
Infrastructure Management Server (IMS)”
on page 72.
22
Overview of Resiliency Platform deployment
Deployment process overview
Table 1-1
Deployment process overview (continued)
Step Description
6
More information
Create resiliency groups for the virtual
Solutions Guides:
machines or applications to be managed
VMware
Hyper-V
Applications
7
(Optional) Implement custom resiliency
plans
Solutions Guides:
VMware
Hyper-V
Applications
8
(Optional) Configure virtual business
services
Solutions for Virtual Business Services
23
Chapter
2
System requirements
This chapter includes the following topics:
■
Supported hypervisors for Resiliency Platform virtual appliance
■
System resource requirements for Resiliency Platform
■
Network and firewall requirements
Supported hypervisors for Resiliency Platform
virtual appliance
This section lists the hypervisor versions that are supported for Resiliency Platform
virtual appliance.
Microsoft Hyper-V:
■
Windows Server 2012 with Hyper-V
■
Windows Server 2012 R2 with Hyper-V
VMware:
■
ESX 5.1, 5.5, 6.0
■
vCenter Server 5.1, 5.5, 6.0
Note: The lists of supported platforms for deployment of virtual appliance and for
disaster recovery of virtual machines are different. For information on platform
support for disaster recovery of virtual machines, see the Veritas Resiliency Platform
Hardware and Software Compatibility List.
See “About deploying the Resiliency Platform virtual appliance” on page 28.
System requirements
System resource requirements for Resiliency Platform
System resource requirements for Resiliency
Platform
The amount of virtual CPUs, memory, and disk space that Veritas Resiliency
Platform requires are listed in this section.
The minimum configuration that is recommended for a virtual appliance for Resiliency
Manager and Infrastructure Management Server (IMS):
Disk space
60 GB
RAM
16 GB
Virtual CPU
8
If the virtual appliance does not meet the minimum configuration, you get a warning
and you are required to confirm if you want to continue with the current configuration.
In addition to the above mentioned resources, you need a Linux server with a
minimum of 50-GB disk space, to be configured as the repository server. Provisioning
for the repository server is optional, it is required to install the Veritas Resiliency
Platform patches or updates in the future.
If you want to enable dynamic memory on Hyper-V, make sure that the following
prerequisites are met:
■
Startup memory and minimal memory should be equal to or greater than the
amount of memory that the distribution vendor recommends.
■
If you are using dynamic memory on a Windows Server 2012 operating system,
specify Startup memory, Minimum memory, and Maximum memory parameters
in multiples of 128 megabytes (MB). Failure to do so can lead to dynamic memory
failures, and you may not see any memory increase in a guest operating system.
See “About deploying the Resiliency Platform virtual appliance” on page 28.
Network and firewall requirements
The following are the network requirements for Veritas Resiliency Platform:
■
Before you use the hostname and the IP address in the Network settings, you
need to register them with the DNS server.
■
The hostname or the IP address which is used for product configuration, should
not have multiple entries in the DNS server. For example, the IP address should
not be associated with multiple hostnames, or the hostname should not be
associated with multiple IP addresses.
25
System requirements
Network and firewall requirements
■
Veritas Resiliency Platform supports only Internet protocol version (IPV) 4.
■
If you plan to use the DHCP server, the DHCP server should be in the same
subnet where you plan to deploy the product.
The following ports are used for Veritas Resiliency Platform:
Table 2-1
Ports used for Resiliency Manager
Ports
used
Purpose
For
communication
between
Direction
443
Used for SSL
communication
Resiliency Manager
and web browser
Browser to
TCP
Resiliency Manager
14176
Used for communication
between the Resiliency
Manager and
Infrastructure
Management Server
(IMS)
Resiliency Manager
and IMS
Bi-directional
TCP
7000
Used for database
replication
Resiliency Managers Bi-directional
of the two data centers
TCP
7001
Used for database
replication
Resiliency Managers Bi-directional
of the two data centers
TCP
22
Used for communication Appliance and the
between remote host to hosts
the appliance CLISH
access
Bi-directional
TCP
123
Used for NTP
synchronization
Bi-directional
TCP
Table 2-2
Protocol
Resiliency Managers
of the two data centers
Appliance and the
NTP server
Ports used for IMS
Ports
used
Description
For
communication
between
Direction
Protocol
14176
Used for communication
between the Resiliency
Manager and
Infrastructure
Management Server
(IMS)
Resiliency Manager
and IMS
Bi-directional
TCP
Resiliency Managers
of the two data centers
26
System requirements
Network and firewall requirements
Table 2-2
Ports used for IMS (continued)
Ports
used
Description
For
communication
between
Direction
Protocol
5634
Used for IMS
configuration
IMS and the hosts
Bi-directional
TCP
14161
Used for running the IMS Resiliency Manager
console
and IMS
Resiliency Manager TCP
to IMS
22
Used for communication IMS and the hosts
between remote host to
the appliance CLISH
access
Bi-directional
TCP
Used for remote
deployment of the
packages on remote Unix
host from IMS
135
Used for remote
deployment on client
computer (inbound)
Host and remote
Windows hosts
Bi-directional
TCP
123
Used for NTP
synchronization
Appliance and the
NTP server
Bi-directional
TCP
See “About deploying the Resiliency Platform virtual appliance” on page 28.
27
Chapter
3
Deploying the Resiliency
Platform virtual appliance
This chapter includes the following topics:
■
About deploying the Resiliency Platform virtual appliance
■
Downloading the Resiliency Platform virtual appliance
■
Deploying the virtual appliance through VMware vSphere Client
■
Deploying the virtual appliance through Hyper-V Manager
About deploying the Resiliency Platform virtual
appliance
Veritas Resiliency Platform is installed as a virtual appliance. A virtual appliance is
a virtual machine image consisting of a pre-configured operating system environment
with a software application installed on it. This virtual machine image can be
deployed on a hypervisor.
You typically deploy and configure at least one Resiliency Manager and one
Infrastructure Management Server (IMS) in the production data center and at least
one Resiliency Manager and one Infrastructure Management Server (IMS) in the
recovery data center.
You can deploy a Resiliency Platform virtual appliance using Hyper-V Manager as
well as using VMware vSphere Client.
Once the Resiliency Platform virtual appliances are deployed, you are required to
configure the Resiliency Platform component through the product bootstrap.
See “Deploying the virtual appliance through Hyper-V Manager” on page 30.
Deploying the Resiliency Platform virtual appliance
Downloading the Resiliency Platform virtual appliance
See “Deploying the virtual appliance through VMware vSphere Client” on page 29.
Downloading the Resiliency Platform virtual
appliance
You can download a licenced copy of Veritas Resiliency Platform virtual appliance
from MyVeritas portal.
To download the Resiliency Platform virtual appliance
1
Log in to MyVeritas portal:
https://my.veritas.com
2
Select Licensing tab, select the account and the entitlement ID that you want
to use for downloading the Resiliency Platform virtual appliance.
3
in the list of products, click Download button next to Resiliency Platform.
■
To deploy Resiliency Platform virtual appliance through Hyper-V, you need
to download a .zip file. The .zip file contains the Virtual Hard disk (VHD)
image file using which you can deploy the virtual appliance. The names of
the .zip file and the VHD file for Hyper-V are as follows:
■
Download file name:
Veritas_Resiliency_Platform_Hyper-V_Virtual_Appliance_1.2.0.0_IE.zip
■
VHD file names:
itrp-ra-disk1
itrp-ra-disk2
■
To deploy Resiliency Platform virtual appliance through VMware, you need
to download an Open Virtualization Archive (OVA) file. The name of the
OVA file for VMware is as follows:
Veritas_Resiliency_Platform_VMWare_Virtual_Appliance_1.2.0.0_IE.ova
You can also download a trial version of the product from the following URL:
go.veritas.com/try-vrp
Deploying the virtual appliance through VMware
vSphere Client
You can deploy Veritas Resiliency Platform virtual appliance through VMware
vSphere Desktop Client or VMware vSphere Web Client using the Open
Virtualization Archive (OVA) file that you have downloaded.
29
Deploying the Resiliency Platform virtual appliance
Deploying the virtual appliance through Hyper-V Manager
To deploy Resiliency Platform through VMware vSphere Desktop Client
1
In the VMware vSphere Desktop Client, click File and select Deploy OVF
Template.
2
Select the source location of the Resiliency Platform virtual appliance OVA file.
3
Specify a name for the virtual machine and location for the deployed template.
4
Select the host or cluster on which you want to deploy the template.
5
Select a destination where you want to store the virtual machine files.
6
Select the format in which you want to store the virtual disks.
7
If you have multiple networks configured, select the appropriate destination
network.
8
Review the virtual machine configuration and click Finish.
9
Power on the virtual machine.
To deploy Resiliency Platform through VMware vSphere Web Client
1
In the VMware vSphere Web Client, click vCenter Servers and select a vCenter
Server. Click Actions > Deploy OVF template.
2
Select the source location of the Resiliency Platform virtual appliance OVA file.
3
Specify a name and location for the deployed template.
4
Select a cluster, host, vApp, or resource pool in which to run the deployed
template.
5
Select a location to store the files for the deployed template.
6
Configure the networks the deployed template should use.
7
Review the virtual machine configuration and click Finish.
8
Power on the virtual machine.
You can now configure the Resiliency Platform component.
See “About configuring the Resiliency Platform components” on page 32.
Deploying the virtual appliance through Hyper-V
Manager
You can deploy Veritas Resiliency Platform virtual appliance through Hyper-V
Manager using the Virtual Hard Disk (VHD) files that you have downloaded. There
are two VHD files used for deploying the Resiliency Platform virtual appliance.
30
Deploying the Resiliency Platform virtual appliance
Deploying the virtual appliance through Hyper-V Manager
To deploy Resiliency Platform through Hyper-V Manager
1
Download the Hyper-V supported VHD file for the Resiliency Platform virtual
appliance on a system where Hyper-V Manager is installed.
See “Downloading the Resiliency Platform virtual appliance” on page 29.
2
In the Hyper-V Manager console, right-click the Hyper-V server and select New
Virtual Machine.
3
Provide a name for the virtual machine.
4
Select Generation 1 while specifying generation.
5
Assign minimum 16 GB RAM.
6
Select a network adapter for the virtual machine.
7
Select the option Attach a virtual hard disk later while specifying option to
connect virtual hard disk.
8
Review the virtual machine configuration details and click Finish.
9
Go to Settings, and increase the number of virtual processors as 8.
10 Add both the VHD files of the Resiliency Platform virtual appliance as IDE
Controller 0.
11 Click Apply, and then click OK.
12 Right-click the name of the virtual machine and select Start to power on the
virtual machine.
You can now configure the Resiliency Platform component.
See “About configuring the Resiliency Platform components” on page 32.
31
Chapter
4
Configuring the Resiliency
Platform virtual appliance
This chapter includes the following topics:
■
About configuring the Resiliency Platform components
■
Prerequisites for configuring Resiliency Platform components
■
Configuring the Resiliency Platform component through the product bootstrap
About configuring the Resiliency Platform
components
After the Veritas Resiliency Platform virtual appliance deployment, the virtual
appliance bootstrap process requires you to configure the Resiliency Platform
component that you have deployed. The following settings are configured as part
of this process to set up the component:
■
Network settings: Settings such as hostname, IP address, subnet mask, default
gateway, and DNS server.
■
System settings: Settings such as NTP server.
■
Product settings: Whether you want to configure a Resiliency Manager,
Infrastructure Management Server (IMS), or Resiliency Manager and IMS both.
Note: Before using the hostname and the IP address in the Network settings, you
need to register them with the DNS server. The hostname and the IP address that
you use for product configuration, cannot be changed later.
Configuring the Resiliency Platform virtual appliance
Prerequisites for configuring Resiliency Platform components
This configuration is done through the bootstrap process only for the first time. After
the successful configuration, the bootstrap process is disabled. If you want to change
these settings later, you need to use the Command Line Interface SHell (CLISH)
menu for changing these settings.
See “Configuring the Resiliency Platform component through the product bootstrap”
on page 33.
Prerequisites for configuring Resiliency Platform
components
Before configuring the component through product bootstrap, make sure that
following prerequisites are met:
■
In case of multiple Resiliency Managers, make sure that the NTP servers that
are used for configuration of Resiliency Managers are properly synchronized.
■
Make sure that you have disabled the dynamic or automatic MAC address
change for your hypervisor. Follow the documentation of your hypervisor to set
the MAC address manually or to disable the setting for automatic MAC address
change.
Configuring the Resiliency Platform component
through the product bootstrap
After Veritas Resiliency Platform (Resiliency Platform) deployment, you need to set
up the Resiliency Platform component during the product bootstrap. The bootstrap
script is used to set up the Resiliency Platform component only for the first time.
Later, if you want to reconfigure the Resiliency Platform component, you need to
use the CLISH menu.
To configure the Resiliency Platform node through the product bootstrap
1
Log in to the virtual appliance console for the first time using the following
credentials:
■
Username: admin
■
Password: [email protected]
33
Configuring the Resiliency Platform virtual appliance
Configuring the Resiliency Platform component through the product bootstrap
After a successful login, you need to change the password of the admin user.
The new password that you enter must not be a dictionary word, and must be
at least six characters long.
2
The bootstrap process is automatically invoked once you change the admin
password after deploying the virtual appliance. The first step in the bootstrap
process is to display the End User License Agreement (EULA). Accept the
EULA to proceed with the configuration.
3
In the Network Settings section, you need to enter your choice for the network
type. Type 1 for selecting static IP or 2 for selecting static DHCP.
In case of static DHCP, you need to ensure that a Dynamic Host Configuration
Protocol (DHCP) server is working in the subnet where the virtual appliance
is deployed. In case of static IP, you need to respond to the following additional
prompts:
4
■
Enter the fully qualified hostname:
■
Enter the IP address:
■
Enter the Subnet mask:
■
Enter the Default Gateway:
■
Enter the DNS server (space separated if more than one DNS, maximum
2 DNS entries):
In the System Settings section, do the following:
■
Press the Enter key to confirm the use of an NTP server for configuring the
date and time.
■
You are required to select the timezone. Select the appropriate options to
set your timezone and verify the displayed information.
■
Enter the FQDN or IP address of the NTP server.
5
In the Product Settings section, enter your choice for configuring the virtual
appliance as a Resiliency Manager, Infrastructure Management Server (IMS),
or both. Type 1 for configuring the role of Resiliency Manager, 2 for configuring
the role of IMS, and 3 for both. For test or evaluation purposes, you can deploy
a Resiliency Manager and Infrastructure Management Server (IMS) on the
same virtual appliance.
6
After a successful product configuration, a message is displayed. If you have
configured Resiliency Manager on the virtual appliance, a URL for the Resiliency
Platform web console login is provided. You can type the URL in a web browser
and log in to the web console.
See “About configuring the Resiliency Platform components” on page 32.
34
Chapter
5
Setting up the resiliency
domain
This chapter includes the following topics:
■
About the web console
■
Connecting to the Resiliency Platform web console
■
Getting started with a new Resiliency Platform configuration
■
Adding a Resiliency Manager to an existing resiliency domain
■
Removing a Resiliency Manager from a resiliency domain
■
Viewing the status of a Resiliency Manager in a data center
About the web console
Once you have finished configuring the virtual appliance settings for the Resiliency
Manager on the bootstrap menu, you log in to the Veritas Resiliency Platform web
console to continue with setting up the resiliency domain.
See “Connecting to the Resiliency Platform web console” on page 36.
Note: For the best console experience, use a minimum resolution of 1280x1040.
You must complete the basic configuration of the Resiliency Manager and the
resiliency domain using the Getting Started wizard before you have access to the
remainder of the web console.
See “Getting started with a new Resiliency Platform configuration” on page 37.
Setting up the resiliency domain
Connecting to the Resiliency Platform web console
From that point, any time you log in, you can view the full web console screen and
menus.
See “Tour of the Resiliency Platform web console screen” on page 187.
Connecting to the Resiliency Platform web
console
Once the Resiliency Manager virtual appliance is deployed and configured, you
can connect to the web console.
To connect to the Resiliency Platform web console
1
2
Prerequisites
■
A supported web browser on a system that has a network connection to
the Resiliency Manager
For information on web browser requirements, refer to the Hardware and
Software Compatibility List (HSCL).
Your browser must be configured to accept cookies and enabled for
JavaScript. If you use pop-up blockers, either disable them or configure
them to accept pop-ups from the Resiliency Manager or Infrastructure
Management Server (IMS) host.
■
Login credentials, including the domain
The initial credentials that are required are for the Admin user of the
Resiliency Manager.
The default domain for the Admin user is vrp.local.
Once the Admin user configures Resiliency Platform to use an LDAP or
Active Directory authentication broker and configures user access, users
can login with their credentials for that authentication domain.
Type the URL as follows:
https://hostname
Example: https://myhost.example.com
3
Enter your login credentials, including the domain, and click Login.
A configurable setting determines whether the login screen shows a list of
domains for user selection. By default, domains are not listed and users must
enter a fully qualified username as [email protected] or domain\username.
For example, for the Admin login, enter:
[email protected]
See “Getting started with a new Resiliency Platform configuration” on page 37.
36
Setting up the resiliency domain
Getting started with a new Resiliency Platform configuration
See “Showing domains on login screen ” on page 133.
Getting started with a new Resiliency Platform
configuration
When you first log in to the web console on a new Resiliency Manager, a Getting
Started wizard helps you to set up a basic Resiliency Platform configuration.
The following table shows the steps involved in getting started with the first
Resiliency Manager and creating a new resiliency domain.
The procedure for adding a Resiliency Manager to an existing resiliency domain is
covered in a separate topic.
See “Adding a Resiliency Manager to an existing resiliency domain” on page 39.
Prerequisites:
■
The basic configuration includes the Resiliency Manager and Infrastructure
Management Server (IMS).
See “About Resiliency Platform features and components” on page 14.
■
If the IMS is on a separate virtual appliance from the Resiliency Manager, ensure
that you have the fully qualified host name and login credentials for the IMS
virtual appliance. Optionally, you can add the IMS later.
Getting Started wizard
Table 5-1
Wizard step
Details
1. Set up Resiliency Manager
Specify the data center location of the Resiliency Manager, the data center friendly
name, and the Resiliency Manager name. Default entries are shown if the
Resiliency Manager has external Internet access to determine the geographical
location.
Click Confirm & Continue.
2. Create or Join a Resiliency
Domain
For a new Resiliency Platform deployment, select the option to create a resiliency
domain and supply a name for the domain.
You can choose whether to allow collection of product usage information.
Click Create.
Wait for the message showing that the domain is successfully created. This
process may take several minutes.
More information is available about telemetry collection.
See “Enabling or disabling telemetry collection ” on page 151.
37
Setting up the resiliency domain
Getting started with a new Resiliency Platform configuration
Getting Started wizard (continued)
Table 5-1
Wizard step
Details
3. Enable Solutions Licenses
You can select a license file to apply or enable the trial license.
See “About licenses” on page 120.
4. Set up Authentication Domain Optional.
By default the Admin user on the virtual appliance has the Super admin persona.
Personas are user roles with access to a predefined set of operations. The Super
admin persona has full access to all operations in the console.
If you want to assign a different user as Super admin you must first set up an
LDAP or Active Directory authentication domain.
Then, on the next step, you can add a user or group from that identity provider
as Super admin and optionally reassign the virtual appliance Admin user to a
more limited persona.
Otherwise, you can skip this step and set up authentication and assign personas
later using the console Settings page.
5. Set up Users and Personas
Optional.
If you set up an authentication domain in the previous step, you can specify the
user or user group to which you want to assign the Super admin persona.
Optionally, you can also reassign the virtual appliance Admin to the more limited
Resiliency Platform Deployment admin persona, with permission to perform
deployments and updates only.
The user with the Super Admin persona can add other users and groups and
assign them personas later using the Settings page.
See “Managing user authentication and permissions” on page 122.
38
Setting up the resiliency domain
Adding a Resiliency Manager to an existing resiliency domain
Getting Started wizard (continued)
Table 5-1
Wizard step
Details
6. Add Infrastructure
Management Servers
Optional.
Add an Infrastructure Management Server (IMS). Optionally you can add more
than one.
You can also add an IMS later from the Settings page.
■
■
Choose one of the following
■ To add an IMS co-located with the Resiliency Manager, choose Enable
internal IMS.
■ If you deployed an IMS separate from the Resiliency Manager, choose
Connect to IMS.
Fill in the following information and click Add:
Data Center Select the data center location, for example, the city.
Location
To specify a new data center, select New and then specify the
location and name. For the location, enter location identifier, such
as city, and the location list populates with potential matches for
you to select.
Server
Name
If you are adding an IMS separate from the Resiliency Manager,
enter the fully qualified host name.
For the login, use the Admin login credentials for the IMS virtual
appliance.
Friendly
Name
Enter a user-friendly name for the IMS. This name helps identify
the IMS in the console.
When you are done adding IMSs, you can exit the wizard. You can complete any
steps you skipped from the Settings page.
See “About settings in the web console” on page 191.
Adding a Resiliency Manager to an existing
resiliency domain
If you are using Resiliency Platform for disaster recovery, you deploy a Resiliency
Manager on both a production data center and a recovery data center. When adding
the first Resiliency Manager, you create a resiliency domain. You must add the
second Resiliency Manager to the existing resiliency domain.
39
Setting up the resiliency domain
Removing a Resiliency Manager from a resiliency domain
To add a Resiliency Manager to an existing resiliency domain
1
Prerequisites:
■
Deploy a new Resiliency Platform virtual appliance node. During deployment,
specify the node as either Resiliency Manager only or both Resiliency
Manager and Infrastructure Management Server (IMS).
■
Ensure that you have the fully qualified host name/IP address and the Admin
login credentials for an existing Resiliency Manager virtual appliance in the
resiliency domain.
2
Log in to the web console on the new Resiliency Manager. The Getting Started
wizard is displayed.
3
In Set up Resiliency Manager, specify the data center location, the data center
friendly name, and Resiliency Manager friendly name. Click Confirm &
Continue.
4
In Create or Join a Resiliency Domain, select Join resiliency domain.
Enter the fully qualified host name or IP address of a Resiliency Manager in
the domain you want to join, and click Verify.
5
Once the name or address has been verified as a Resiliency Manager, the
login fields are available. Enter the credentials for that Resiliency Manager and
click Join.
A confirmation message shows the name of the resiliency domain that you are
joining. Wait for the message that shows that the domain has been joined.
6
You have completed the Getting Started steps that are required for the new
Resiliency Manager. Optionally you can add an Infrastructure Management
Server, or you can do so later from the Settings page.
See “Adding an IMS ” on page 45.
7
If you refresh the page in the web console of the new Resiliency Manager, the
information for the domain that you joined is shown in the Dashboard
Each Resiliency Manager in the domain has its own web console but the data
that is shown is synchronized with other Resiliency Managers in the domain.
Removing a Resiliency Manager from a resiliency
domain
A Veritas Resiliency Platform resiliency domain typically contains two Resiliency
Managers. You can remove a Resiliency Manager from the domain as long as
another remains online.
40
Setting up the resiliency domain
Removing a Resiliency Manager from a resiliency domain
Removing a Resiliency Manager is necessary, for example, if you need to do the
following:
■
Change the host name or IP address of the Resiliency Manager virtual appliance.
■
Change a virtual appliance that is both a Resiliency Manager and Infrastructure
Management Server (IMS) so that it is used only as an IMS.
Caution: Ensure that you meet the prerequisites listed in the procedure.
For example, if you want to decommission a Resiliency Manager virtual appliance
node, you do the following steps:
■
If the virtual appliance node that you want to decommission is configured as
both a Resiliency Manager and Infrastructure Management Server (IMS), first
remove the IMS from the resiliency domain.
See “Removing an IMS” on page 46.
■
Remove the Resiliency Manager from the resiliency domain using the Leave
Domain procedure below.
Completing this operation ensures that the Resiliency Manager is cleanly
decommissioned and that all references to it are removed from the Resiliency
Manager database and no longer appear in the web console user interface.
■
If there is an IMS on a separate node that was reporting to the Resiliency
Manager, ensure that it is reconnected to another Resiliency Manager.
To remove a Resiliency Manager from a resiliency domain
1
2
Prerequisites
■
Both Resiliency Managers must be online.
■
Perform the operation from the Resiliency Manager that is remaining in the
resiliency domain, not from the Resiliency Manager that is being removed.
■
You should perform the operation during a maintenance window and send
appropriate notifications in advance.
■
Ensure that no activity is occurring on the Resiliency Manager that you plan
to remove. For example, ensure that no workflow is in progress.
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
41
Setting up the resiliency domain
Viewing the status of a Resiliency Manager in a data center
3
Under the data center, locate the Resiliency Manager and do the following:
Click the vertical ellipsis icon next to the Resiliency Manager and select Leave
Domain.
The operation can take over five minutes to complete as it is a multistep process.
4
Once the operation is successfully completed, you can remove the Resiliency
Manager virtual appliance node using the appropriate hypervisor manager.
See “Troubleshooting removing a Resiliency Manager from a resiliency domain”
on page 173.
Viewing the status of a Resiliency Manager in a
data center
In the web console, you can view a list of data centers and any associated Resiliency
Manager and IMS. Under the Resiliency Manager you can view the status, as
follows:
Connected
The Resiliency Manager is up and healthy, and if there is
another Resiliency Manager node in the domain, they are
connected.
Disconnected
The Resiliency Manager node is down, the Resiliency
Manager services are not running, or there is a connection
issue between the Resiliency Manager nodes.
See “Troubleshooting the connection between Resiliency
Managers in a resiliency domain” on page 172.
Leaving Domain
The Leave Domain operation has been initiated and is in
progress.
See “Removing a Resiliency Manager from a resiliency
domain” on page 40.
Leave domain failure
The Leave Domain operation did not complete successfully.
42
Setting up the resiliency domain
Viewing the status of a Resiliency Manager in a data center
To view the status of a Resiliency Manager in a data center
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
You can expand or contract each data center listed. Click the arrow to the right
of a data center to expand the data center and view the information about the
Resiliency Manager.
43
Chapter
6
Managing Infrastructure
Management Servers
This chapter includes the following topics:
■
How Infrastructure Management Servers relate to data centers
■
Adding an IMS
■
Removing an IMS
■
Modifying an IMS
■
Reconnecting the IMS to a Resiliency Manager
■
Managing data centers
■
Configuring network settings for data centers
How Infrastructure Management Servers relate to
data centers
Veritas Resiliency Platform provides for the resiliency management of virtual
machines or applications by data center. Virtual machines and applications are
associated with other infrastructure, such as physical hosts, virtualization servers,
and storage arrays. Resiliency Platform includes an Infrastructure Management
Server (IMS) to discover, monitor, and manage assets in a data center.
See “Infrastructure Management Server (IMS)” on page 19.
A Resiliency Platform domain can extend across data centers in different locations.
Each data center has at least one IMS. A data center can also have more than one
IMS. You determine which infrastructure assets to add to each IMS.
Managing Infrastructure Management Servers
Adding an IMS
In the Resiliency Platform web console, you associate each IMS with a data center
location and a data center name (friendly name). If a data center has more than
one IMS, the best practice is to associate each IMS with the same data center
location and name.
Adding an IMS
Veritas Resiliency Platform includes an Infrastructure Management Server (IMS)
to discover and monitor assets. When you first configure Resiliency Platform in the
web console, you set up the Resiliency Manager and resiliency domain with the
Getting Started wizard. Optionally, you can also add one or more IMSs. You can
also add IMSs later, after you exit the Getting Started wizard. This procedure
describes how to add IMSs later.
To add an IMS
1
2
Prerequisites
■
A Resiliency Manager and resiliency domain must be set up using the
Getting Started wizard.
See “Getting started with a new Resiliency Platform configuration”
on page 37.
■
The virtual appliance for the IMS must be deployed and configured.
■
Information needed for adding the IMS:
The fully qualified domain name (FQDN) or IP address plus the Admin
credentials for the IMS virtual appliance.
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
You can also access this page from the Quick Actions menu > Manage Asset
Infrastructure.
Click Infrastructure Management Server +.
45
Managing Infrastructure Management Servers
Removing an IMS
3
In Add Infrastructure Management Server, enter the information for the IMS
and submit.
Tips:
You can select from a list of existing data centers or add a new data center.
See “How Infrastructure Management Servers relate to data centers”
on page 44.
To specify a new data center, select New in the Data Center field, then specify
the location and name. When entering the location, enter a form of location
identifier, such as city, and the location list will populate with potential matches
for you to select.
4
Verify that the IMS is successfully added.
Once the IMS is successfully added, you can add the asset infrastructure to
the IMS.
See “Adding the asset infrastructure to an Infrastructure Management Server
(IMS)” on page 72.
5
If you add an IMS to an existing data center after the DNS settings for the data
center have been configured, go to the DNS settings for the data center, select
the modify option for the DNS server, enter a test host name and IP address,
and run a test. This ensures that this newly added IMS can be used to perform
DNS updates.
See “Configuring DNS server settings for a data center” on page 51.
Removing an IMS
In the web console, you can remove an Infrastructure Management Server (IMS)
from a resiliency domain. Removing an IMS removes the information about the IMS
in the Resiliency Manager repository for the resiliency domain.
Caution: Removing an IMS also removes the Resiliency Manager repository records
of the asset infrastructure that was added to that IMS. Assets managed by that IMS
that were added to Resiliency Platform resiliency groups are removed from the
resiliency groups. You may want to edit the resiliency groups before removing the
IMS to remove the assets managed by this IMS. If the resiliency group contains
only assets from this IMS, you can remove the resiliency group.
More information on resiliency groups is available in the Solutions guide.
46
Managing Infrastructure Management Servers
Modifying an IMS
To remove an IMS
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
Under the data center, locate the IMS and do the following:
Click the vertical ellipsis for the IMS > Remove. Confirm the deletion.
3
Verify that the IMS is removed.
Note: Additional cleanup is optional. If resiliency groups were created for the
assets managed by the IMS, and they are no longer needed, you can remove
them.
Modifying an IMS
In the web console, you can modify the friendly name associated with an
Infrastructure Management Server (IMS) that has been added to a resiliency domain
or change the data center name for the IMS. You cannot change the information
about the virtual appliance that hosts the IMS.
Modifying an IMS is a separate operation from configuring or modifying assets for
an IMS.
See “Adding the asset infrastructure to an Infrastructure Management Server (IMS)”
on page 72.
47
Managing Infrastructure Management Servers
Reconnecting the IMS to a Resiliency Manager
To modify an IMS
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure.
2
Under the data center, locate the IMS and do the following:
Click the vertical ellipsis for the IMS > Modify.
Tips:
You can select from a list of existing data centers or add a new data center.
See “How Infrastructure Management Servers relate to data centers”
on page 44.
To specify a new data center, select New in the Data Center field, then specify
the location and name. When entering the location, enter a location identifier,
such as city, and the location list will populate with potential matches for you
to select.
3
Verify the change.
Reconnecting the IMS to a Resiliency Manager
You can use the web console to reconnect an Infrastructure Management Server
(IMS) to a Resiliency Manager. The operation disconnects any existing connection
and the IMS then reinitiates the connection. This operation can be useful when
troubleshooting or repairing a connection between an IMS and a Resiliency Manager.
For example, say the connection between an IMS and the Resiliency Manager
located in the same data center (data center A) fails. Another Resiliency Manager
in the same resiliency domain is online in another data center (data center B). In
such a case, the IMS can automatically connect itself to the Resiliency Manager in
data center B.
However, once the issue with the first Resiliency Manager is fixed, the administrator
may want to reconnect the IMS back with the first Resiliency Manager. The
Reconnect operation will accomplish this as follows: If there is an existing connection,
the Reconnect operation disconnects it. The IMS then reconnects to a Resiliency
Manager in the resiliency domain based on priority. A Resiliency Manager in the
same data center as the IMS has a higher priority than a Resiliency Manager in a
48
Managing Infrastructure Management Servers
Managing data centers
different data center. Therefore, in the above scenario, the IMS reconnects to the
Resiliency Manager in data center A.
To reconnect an IMS to a Resiliency Manager
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
Under the data center, locate the IMS and do the following:
Click the vertical ellipsis for the IMS > Reconnect.
Managing data centers
Resiliency Managers and Infrastructure Management Servers (IMSs) must always
be associated with a data center location and name. You specify the data center
information while setting up the Resiliency Manager and while adding an IMS.
See “How Infrastructure Management Servers relate to data centers” on page 44.
In the web console, you can view a list of data centers and any associated Resiliency
Manager and IMS. You can edit the data center information. You can also add data
centers separately for use later or delete a data center if it has no Resiliency
Manager or IMS associated with it.
Details about configuring network settings for data centers are covered in a separate
topic.
See “Configuring network settings for data centers” on page 51.
To view data centers
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
You can expand or contract each data center listed. Click the arrow to the right
of a data center to expand the data center and view the information about any
associated Resiliency Manager and IMS, including status of connections.
49
Managing Infrastructure Management Servers
Managing data centers
To add a data center
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
Click Data Center +.
3
Specify the location and a friendly name for the data center. When entering
the location, enter a form of location identifier, such as city, and the location
list will populate with potential matches for you to select.
To modify a data center
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
3
Click the vertical ellipsis next to the data center name, then click Edit Data
Center.
Edit the data center information and submit the changes.
To delete a data center
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
3
Click the arrow to the right of a data center to expand the data center and verify
there is no associated Resiliency Manager and IMS. You cannot delete a data
center that is associated with a Resiliency Manager or IMS. You can edit an
IMS to change its data center; however you cannot change the data center
associated with a Resiliency Manager.
Click the vertical ellipsis next to the data center name, then click Delete Data
Center.
50
Managing Infrastructure Management Servers
Configuring network settings for data centers
Configuring network settings for data centers
In the web console, you can configure DNS and subnet settings for data centers.
These settings are used for disaster recovery operations between data centers.
To configure network settings for data centers
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
Click the vertical ellipsis next to the data center name, then click DNS & Network
Settings.
2
(For application disaster recovery only) On the DNS tab, add, modify, or remove
information about the DNS server.
See “Configuring DNS server settings for a data center” on page 51.
3
On the Subnets tab, add, modify, or remove information about subnets.
See “Configuring subnet information for a data center” on page 53.
See “Managing data centers” on page 49.
Configuring DNS server settings for a data center
In the web console, you can configure the DNS server settings for the data center.
These settings are used for performing DNS updates at the time of application
migration between the data centers for application disaster recovery. They must
be configured on both data centers.
You can add DNS servers for the data center or modify or remove the settings for
servers that were added previously.
Note: If you add an IMS to an existing data center after you add a DNS server for
the data center, select the modify option for the DNS server, enter a test host name
and IP address, and run a test. This test confirms that the newly added IMS can
be used to perform DNS updates.
To configure DNS server settings for a data center
1
Prerequisites
You must have the following information:
51
Managing Infrastructure Management Servers
Configuring network settings for data centers
2
■
The IP address of the DNS server
■
The name of the domain, and associated credentials. For TSIG
authentication, you need the TSIG key and TSIG private files. For GSSAPI
authentication, you need the user name and keytab file.
■
A test host name and IP address for performing a test operation by updating
the DNS server for validating the specified DNS configuration.
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
Click the vertical ellipsis next to the data center name, then click DNS & Network
Settings > DNS tab.
Any DNS servers already added for the data center are listed. You can modify
or remove them, or add a new DNS server.
3
To add a new DNS server for the data center, click Add DNS and select Add
New DNS.
Or select Add Existing DNS Server if the DNS server has already been added
to Resiliency Platform for another data center.
4
Specify the IP address for the DNS server.
5
Add one or more domains to the DNS server:
■
Fill in the domain name and the authentication type. For TSIG, browse to
the key and private files. For GSSAPI, enter the user name and browse to
the keytab file.
■
Enter a test host name and IP address and click Test. If the test is
successful, the Add button is enabled.
■
Click Add to add the domain to the DNS server.
6
If you are done adding domains, click Save.
7
To modify or remove a DNS server, go to the DNS tab and select Modify or
Remove for that DNS server.
See “Configuring subnet information for a data center” on page 53.
See “Managing data centers” on page 49.
52
Managing Infrastructure Management Servers
Configuring network settings for data centers
Configuring subnet information for a data center
To configure subnet information for a data center
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
Click the vertical ellipsis next to the data center name, then click DNS & Network
Settings > Subnets tab.
Any subnets already added for the data center are listed. You can modify or
remove them, or add a new subnet.
You can optionally specify if a subnet should be used for the purpose of rehearsal
or for production.
2
To add a new subnet, click Add and specify the IP address for the subnet and
gateway. Optionally, select the virtualization servers that are part of the subnet.
3
Click Add at the bottom of the form.
See “Configuring DNS server settings for a data center” on page 51.
See “Managing data centers” on page 49.
See “Configuring V-Switch information for a data center” on page 53.
Configuring V-Switch information for a data center
Veritas Resiliency Platform 1.2 allows you to perform disaster recovery rehearsal
for a virtual machine in a private network. For any virtualization server, you can
specify an alternate virtual switch (V-Switch) that is connected to a private network.
53
Managing Infrastructure Management Servers
Configuring network settings for data centers
To configure virtual switch information for a data center
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
Click the vertical ellipsis next to the data center name, then click DNS & Network
Settings > V-Switches tab.
2
You can see a list of virtualization servers and their corresponding list of virtual
switches. Select the virtualization server for which you want to edit the settings
of the virtual switch, and expand Edit next to the virtual switch.
3
Select your option for using the virtual switch for rehearsal or for production
(migrate and takeover operations). You can also specify an option to use any
virtual local area network (VLAN) network for rehearsal or for production
(migrate and takeover operations). The default behaviour is using a virtual
switch or VLAN for production.
4
Click Close to save the settings and exit the wizard.
See “Configuring DNS server settings for a data center” on page 51.
See “Managing data centers” on page 49.
See “Configuring subnet information for a data center” on page 53.
54
Chapter
7
Managing Veritas
InfoScale Operations
Manager Server
This chapter includes the following topics:
■
About Veritas InfoScale Operations Manager
■
Resiliency Platform support for InfoScale applications
■
Managing InfoScale applications using Resiliency Platform
■
Prerequisites for managing Veritas InfoScale Operations Manager server using
Resiliency Platform
■
Adding a Veritas InfoScale Operations Manager server
■
Removing a Veritas InfoScale Operations Manager server
■
Modifying a Veritas InfoScale Operations Manager server
About Veritas InfoScale Operations Manager
Veritas InfoScale Operations Manager gives you a single, centralized management
console for the Veritas InfoScale products. You can use it to monitor, visualize, and
manage storage and cluster resources, and generate reports about these
components in the Management Server domain. Veritas InfoScale Operations
Manager helps administrators centrally manage diverse data center environments.
Managing Veritas InfoScale Operations Manager Server
Resiliency Platform support for InfoScale applications
Resiliency Platform support for InfoScale
applications
A typical workflow of Veritas Resiliency Platform for InfoScale applications consists
of a Veritas InfoScale Operation Manager server reporting to a Resiliency Manager.
The InfoScale applications should be already configured in Veritas InfoScale
Operations Management server. You can group the InfoScale applications into
resiliency groups or VBSs to recover, monitor, visualize, and generate reports about
these applications in the Resiliency Platform.
Note: Applications that are only managed by InfoScale Availability (VCS) are
supported in Veritas Resiliency Platform.
The following diagram depicts the general workflow of configuring the InfoScale
applications for recovery using Resiliency Platform.
Figure 7-1
A typical workflow for recovering managed InfoScale applications
56
Managing Veritas InfoScale Operations Manager Server
Managing InfoScale applications using Resiliency Platform
Managing InfoScale applications using Resiliency
Platform
Veritas Resiliency Platform lets you manage the InfoScale applications that are
already configured in Veritas InfoScale Operations Manager Management Server.
The InfoScale applications are automatically discovered in the Resiliency Platform
when the Veritas InfoScale Operations Manager server is added to the resiliency
domain. They are listed on the Assets page under the Unmanaged tab. You can
filter the InfoScale applications using the InfoScale applications check box under
the More Options drop-down menu.
Veritas InfoScale Operations Manager users must download and install Veritas
Resiliency Platform Enablement add-on to automatically discover the InfoScale
applications. You can download the add-on from Veritas Services and Operations
Readiness Tools (SORT). You cannot add or modify InfoScale applications through
Resiliency Platform. They can be added or modified only by an administrator through
Veritas InfoScale Operations Manager.
For information on configuring resiliency groups with InfoScale applications, refer
to the Veritas Resiliency Platform 1.2: Solutions for Applications guide.
Prerequisites for managing Veritas InfoScale
Operations Manager server using Resiliency
Platform
The following prerequisites are required for managing InfoScale applications in
Veritas Resiliency Platform:
■
Veritas Resiliency Platform requires Veritas InfoScale Operations Manager
Management Server version 7.0 or later.
■
You need to download and install the Veritas Resiliency Platform Enablement
add-on on the Veritas InfoScale Operations Manager Management Server and
then on the intended managed host nodes.
Note: You need to restart the Veritas InfoScale Operations Manager server
after installing the add-on.
■
Veritas Resiliency Platform supports Veritas Cluster Servers (6.0 onwards).
■
Global Cluster Option (GCO) must be enabled for performing DR operations.
57
Managing Veritas InfoScale Operations Manager Server
Adding a Veritas InfoScale Operations Manager server
■
InfoScale applications must be configured along with replication in VCS for
performing DR operations.
■
Make sure the managed hosts in the GCO pair are not cross attached between
Production and Recovery Veritas InfoScale Operations Manager server.
■
Make sure that the same vCenter Server is not added to both Veritas InfoScale
Operations Manager and Infrastructure Management Server (IMS).
■
Make sure you plumb the IP of the application on both the production and
recovery sites, while configuring disaster recovery for an InfoScale resiliency
group. Once the disaster recovery configuration of the resiliency group is
complete, you can remove the plumbing of the application IP at recovery site.
Adding a Veritas InfoScale Operations Manager
server
Veritas Resiliency Platform includes Veritas InfoScale Operations Manager
Management Server to discover and monitor InfoScale applications.
To add a Veritas InfoScale Operations Manager server in Resiliency Platform
1
Prerequisites
See “Prerequisites for managing Veritas InfoScale Operations Manager server
using Resiliency Platform ” on page 57.
2
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
You can also access this page from the Quick Actions menu > Manage Asset
Infrastructure.
Click Veritas InfoScale Operations Manager server +.
58
Managing Veritas InfoScale Operations Manager Server
Removing a Veritas InfoScale Operations Manager server
3
In Add Veritas InfoScale Operations Manager window, enter the information
for the Veritas InfoScale Operations Manager, and click Submit.
Tips:
You can select from a list of existing data centers or add a new data center.
To specify a new data center, select New in the data center field, then specify
the location and name. When entering the location, enter a form of location
identifier, such as city, and the location list will populate with potential matches
for you to select.
4
Verify that the Veritas InfoScale Operations Manager server is successfully
added. Once the server is successfully added, the applications that are already
added in the Veritas InfoScale Operations Manager are shown in the
Unmanaged tab under Assets.
Note: You can add or manage the asset infrastructure related to the InfoScale
applications only through Veritas InfoScale Operations Manager console. For
managing applications in Veritas InfoScale Operations Manager, you need to
log in using administrator credentials.
If you want to manage the InfoScale assets after you have successfully added
the Veritas InfoScale Operations Manager server, you can click the vertical
ellipsis and select Manage Asset Infrastructure to launch the Veritas InfoScale
Operations Manager console.
Removing a Veritas InfoScale Operations Manager
server
In the web console, you can remove a Veritas InfoScale Operations Manager server
from a resiliency domain by performing the following steps:
59
Managing Veritas InfoScale Operations Manager Server
Modifying a Veritas InfoScale Operations Manager server
To remove a Veritas InfoScale Operations Manager server
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
Under the data center, locate the Veritas InfoScale Operations Manager server
and do the following:
Click the vertical ellipsis for the Veritas InfoScale Operations Manager server
> Remove. Confirm the deletion.
3
Verify that the Veritas InfoScale Operations Manager server is removed.
Note: Additional cleanup is optional. If resiliency groups were created for the
assets managed by the Veritas InfoScale Operations Manager server and VBS,
and they are no longer needed, you can remove them.
Modifying a Veritas InfoScale Operations Manager
server
In the web console, you can modify the friendly name associated with a Veritas
InfoScale Operations Manager server that has been added to a resiliency domain
or change the data center name.
60
Managing Veritas InfoScale Operations Manager Server
Modifying a Veritas InfoScale Operations Manager server
To modify a Veritas InfoScale Operations Manager server
1
Navigate
Settings (menu bar)
Under Infrastructure Settings, click Infrastructure
2
Under the data center, locate the Veritas InfoScale Operations Manager server
and do the following:
Click the vertical ellipsis for the Veritas InfoScale Operations Manager server
> Edit.
3
In the Edit Veritas InfoScale Operations Manager server window, make the
required changed and click Submit.
61
Chapter
8
Adding the asset
infrastructure
This chapter includes the following topics:
■
About the asset infrastructure
■
Configuring IMS asset infrastructure for Hyper-V virtual machines
■
Configuring IMS asset infrastructure for VMware virtual machines
■
Configuring IMS asset infrastructure for application discovery on Hyper-V virtual
machines
■
Configuring IMS asset infrastructure for application discovery on VMware virtual
machines
■
Configuring IMS asset infrastructure for application discovery on physical systems
■
Adding the asset infrastructure to an Infrastructure Management Server (IMS)
■
Managing host assets for an IMS
■
Managing Hyper-V assets for an IMS
■
Managing VMware virtualization servers for an IMS
■
Managing enclosure assets for an IMS
■
Managing add-ons for the hosts
■
Managing solutions for the hosts
Adding the asset infrastructure
About the asset infrastructure
About the asset infrastructure
The data center assets that you add to the Infrastructure Management Server (IMS)
for IMS discovery and monitoring are referred to as the asset infrastructure.
The asset infrastructure can include hosts (Windows or Linux servers) and
virtualization servers for Hyper-V and VMware. For configuring disaster recovery,
if you are using enclosures (storage arrays) for replication, you also add the
information about the storage arrays to the IMS. See the following use cases for
the recommended sequence in which to add assets. Once the asset infrastructure
is discovered by the IMS, the discovered virtual machines or applications are listed
in the console as assets to manage or protect.
Note: Replication appliances are added in a different way from other types of asset
infrastructure.
See “Adding RecoverPoint appliance for replication” on page 112.
Table 8-1
Use cases for adding asset infrastructure
Use case
More information
Virtual machine discovery in Hyper-V
environment
See “Configuring IMS asset infrastructure for
Hyper-V virtual machines” on page 64.
Virtual machine discovery in VMware
environment
See “Configuring IMS asset infrastructure for
VMware virtual machines” on page 65.
Application discovery on Hyper-V virtual
machines
See “Configuring IMS asset infrastructure for
application discovery on Hyper-V virtual
machines” on page 67.
Application discovery on VMware virtual
machines
See “Configuring IMS asset infrastructure for
application discovery on VMware virtual
machines” on page 68.
Application discovery on physical systems
See “Configuring IMS asset infrastructure for
application discovery on physical systems”
on page 70.
See “Adding the asset infrastructure to an Infrastructure Management Server (IMS)”
on page 72.
63
Adding the asset infrastructure
Configuring IMS asset infrastructure for Hyper-V virtual machines
Configuring IMS asset infrastructure for Hyper-V
virtual machines
The following table describes the asset infrastructure to be added to the
Infrastructure Management Server (IMS) for discovery and management of Hyper-V
virtual machines and for discovery of storage arrays used for replication for disaster
recovery.
Note: Replication appliances are added in a different way from other types of asset
infrastructure.
See “Adding RecoverPoint appliance for replication” on page 112.
Table 8-2
Task
Configuring IMS asset infrastructure for Hyper-V virtual machines
Details
Add the Hyper-V
See “Managing Hyper-V assets for an IMS”
virtualization server to on page 81.
the IMS
See “Managing host assets for an IMS”
on page 73.
For storage
array-based
replication
IMS wizard
Add Hosts
Configure a discovery host with the
not applicable
vendor-specific array management tools and
connect it to the enclosure
Configure a discovery See “About the discovery host” on page 93.
host for the storage
See “Configuration prerequisites for adding
array
storage enclosures to an IMS” on page 93.
Not applicable for
Hyper-V Replica
Add the array
See “Managing host assets for an IMS”
discovery host to the on page 73.
IMS
Add Hosts
Add the storage array See “Managing enclosure assets for an IMS” Add Enclosures
to the IMS
on page 92.
64
Adding the asset infrastructure
Configuring IMS asset infrastructure for VMware virtual machines
Configuring IMS asset infrastructure for VMware
virtual machines
The following tables describe the asset infrastructure to be added to the
Infrastructure Management Server (IMS) for discovery and management of VMware
virtual machines. They include information on adding the storage arrays used for
replication for disaster recovery.
Note: The tables also show the recommended sequence for adding the assets so
that the IMS completes discovery most quickly.
Refer to the appropriate table depending on the type of array-based replication you
are using.
Note: Replication appliances are added in a different way from other types of asset
infrastructure.
See “Adding RecoverPoint appliance for replication” on page 112.
Table 8-3
Task
Configuring IMS asset infrastructure for VMware virtual machines
(EMC SRDF, Hitachi TrueCopy, HPE 3PAR Remote Copy)
Details
IMS wizard
Configure a discovery Configure a discovery host with the
not applicable
host for the storage
vendor-specific array management tools and
array to be used for connect it to the enclosure
replication
See “About the discovery host” on page 93.
See “EMC Symmetrix configuration
prerequisites” on page 94.
See “Hitachi configuration prerequisites”
on page 100.
See “3PAR configuration prerequisites”
on page 104.
Add the storage array See “Managing host assets for an IMS”
discovery host to the on page 73.
IMS
Add Hosts
Add the storage array See “Managing enclosure assets for an IMS” Add Enclosures
to the IMS
on page 92.
65
Adding the asset infrastructure
Configuring IMS asset infrastructure for VMware virtual machines
Table 8-3
Task
Configuring IMS asset infrastructure for VMware virtual machines
(EMC SRDF, Hitachi TrueCopy, HPE 3PAR Remote Copy)
(continued)
Details
IMS wizard
Add the VMware
If you added a storage array for replication, Add Virtualization
vCenter Server to the for IMS discovery to proceed most quickly,
Server
IMS
ensure that the enclosure discovery is
complete before you add the vCenter Server
to the IMS.
Optionally, you can add a separate host to
act as the Control Host for the vCenter
Server.
See “About using a separate Control Host for
discovery of VMware servers” on page 84.
See “Managing VMware virtualization servers
for an IMS” on page 82.
Table 8-4
Task
Configuring IMS asset infrastructure for VMware virtual machines
(NetApp SnapMirror replication)
Details
Add the VMware
Optionally, you can add a separate host to
vCenter Server to the act as the Control Host for the vCenter
IMS
Server.
IMS wizard
Add Virtualization
Server
See “About using a separate Control Host for
discovery of VMware servers” on page 84.
See “Managing VMware virtualization servers
for an IMS” on page 82.
For NetApp
SnapMirror
replication:
For IMS discovery to proceed most quickly,
ensure that the vCenter Server discovery is
complete before you add the storage array
to the IMS.
Add the storage array
or NetApp cluster to When you enter the array information in the
the IMS
IMS wizard, you must specify the IMS as the
discovery host.
See “Managing enclosure assets for an IMS”
on page 92.
Add Enclosures
66
Adding the asset infrastructure
Configuring IMS asset infrastructure for application discovery on Hyper-V virtual machines
Configuring IMS asset infrastructure for
application discovery on Hyper-V virtual machines
The following table describes the asset infrastructure to be added to the
Infrastructure Management Server (IMS) for discovery and management of
applications on Hyper-V virtual machines. It includes information on adding the
storage arrays used for replication for disaster recovery.
Table 8-5
Task
Configuring IMS asset infrastructure for application discovery on
Hyper-V virtual machines
Details
IMS wizard
Add the Hyper-V
See “Managing Hyper-V assets for an IMS”
virtualization server to on page 81.
the IMS
See “Managing host assets for an IMS”
on page 73.
Add Hosts
Add the Hyper-V
virtual machines to
the IMS as hosts
Add Hosts
See “Managing host assets for an IMS”
on page 73.
Note: Discovery of custom applications
requires an additional step after adding the
hosts. You must also add the applications on
the Assets page.
More information is available on adding
custom applications.
See Veritas Resiliency Platform Solutions
for Applications.
For array-based
Configure a discovery host with the
not applicable
replication, configure vendor-specific array management tools and
a discovery host for connect it to the enclosure
the storage array
See “About the discovery host” on page 93.
See “Configuration prerequisites for adding
storage enclosures to an IMS” on page 93.
Add the storage array See “Managing host assets for an IMS”
discovery host to the on page 73.
IMS
Add Hosts
Add the storage array See “Managing enclosure assets for an IMS” Add Enclosures
to the IMS
on page 92.
67
Adding the asset infrastructure
Configuring IMS asset infrastructure for application discovery on VMware virtual machines
Configuring IMS asset infrastructure for
application discovery on VMware virtual machines
The following table describes the asset infrastructure to be added to the
Infrastructure Management Server (IMS) for discovery and management of
applications on VMware virtual machines. It includes information on adding the
storage arrays used for replication for disaster recovery.
Table 8-6
Configuring IMS asset infrastructure for application discovery on
VMware virtual machines (EMC SRDF replication)
Task
Details
IMS wizard
For EMC SRDF
replication:
Configure a discovery host with the
not applicable
vendor-specific array management tools and
connect it to the enclosure
Configure a discovery
host for the storage
See “About the discovery host” on page 93.
array to be used for
See “EMC Symmetrix configuration
replication
prerequisites” on page 94.
Add the storage array See “Managing host assets for an IMS”
discovery host to the on page 73.
IMS
Add Hosts
Add the storage array See “Managing enclosure assets for an IMS” Add Enclosures
to the IMS
on page 92.
Add the VMware
See “Managing VMware virtualization servers Add Virtualization
vCenter Server to the for an IMS” on page 82.
Server
IMS
Optionally, you can add a separate host to
act as the Control Host for the vCenter
Server.
See “About using a separate Control Host for
discovery of VMware servers” on page 84.
68
Adding the asset infrastructure
Configuring IMS asset infrastructure for application discovery on VMware virtual machines
Table 8-6
Configuring IMS asset infrastructure for application discovery on
VMware virtual machines (EMC SRDF replication) (continued)
Task
Details
IMS wizard
Add the VMware
virtual machines to
the IMS as hosts
See “Managing host assets for an IMS”
on page 73.
Add Hosts
Note: Discovery of custom applications
requires an additional step after adding the
hosts. You must also add the applications on
the Assets page.
More information is available on adding
custom applications.
See Veritas Resiliency Platform Solutions
for Applications.
Table 8-7
Task
Configuring IMS asset infrastructure for VMware virtual machines
(NetApp SnapMirror replication)
Details
IMS wizard
Add the VMware
See “Managing VMware virtualization servers Add Virtualization
vCenter Server to the for an IMS” on page 82.
Server
IMS
Add the VMware
virtual machines to
the IMS as hosts
See “Managing host assets for an IMS”
on page 73.
Optionally, you can add a separate host to
act as the Control Host for the vCenter
Server.
See “About using a separate Control Host for
discovery of VMware servers” on page 84.
Note: Discovery of custom applications
requires an additional step after adding the
hosts. You must also add the applications on
the Assets page.
More information is available on adding
custom applications.
See Veritas Resiliency Platform Solutions
for Applications.
Add Hosts
69
Adding the asset infrastructure
Configuring IMS asset infrastructure for application discovery on physical systems
Table 8-7
Configuring IMS asset infrastructure for VMware virtual machines
(NetApp SnapMirror replication) (continued)
Task
Details
IMS wizard
For NetApp
SnapMirror
replication:
For IMS discovery to proceed most quickly, Add Enclosures
ensure that the vCenter Server discovery and
virtual machine discovery is complete before
you add the storage array to the IMS.
Add the storage array
to the IMS
When you enter the array information in the
IMS wizard, you must specify the IMS as the
discovery host.
See “Managing enclosure assets for an IMS”
on page 92.
Configuring IMS asset infrastructure for
application discovery on physical systems
The following table describes the asset infrastructure to be added to the
Infrastructure Management Server (IMS) for discovery and management of
applications on physical systems. It includes information on adding the storage
arrays used for replication for disaster recovery.
Table 8-8
Task
Configuring IMS asset infrastructure for application discovery on
physical systems (EMC SRDF replication)
Details
IMS wizard
Add the physical
See “Managing host assets for an IMS”
Add Hosts
servers on which the on page 73.
applications are
Note: Discovery of custom applications
running to the IMS
requires an additional step after adding the
hosts. You must also add the applications on
the Assets page.
More information is available on adding
custom applications.
See Veritas Resiliency Platform Solutions
for Applications.
70
Adding the asset infrastructure
Configuring IMS asset infrastructure for application discovery on physical systems
Table 8-8
Configuring IMS asset infrastructure for application discovery on
physical systems (EMC SRDF replication) (continued)
Task
Details
IMS wizard
For EMC SRDF
replication: Configure
a discovery host for
the storage array to
be used for
replication
Configure a discovery host with the
not applicable
vendor-specific array management tools and
connect it to the enclosure
See “About the discovery host” on page 93.
See “Configuration prerequisites for adding
storage enclosures to an IMS” on page 93.
Add the array
See “Managing host assets for an IMS”
discovery host to the on page 73.
IMS
Add Hosts
Add the storage array See “Managing enclosure assets for an IMS” Add Enclosures
to the IMS
on page 92.
Table 8-9
Task
Configuring IMS asset infrastructure for application discovery on
physical systems (NetApp SnapMirror replication)
Details
IMS wizard
Add the physical
See “Managing host assets for an IMS”
Add Hosts
servers on which the on page 73.
applications are
Note: Discovery of custom applications
running to the IMS
requires an additional step after adding the
hosts. You must also add the applications on
the Assets page.
More information is available on adding
custom applications.
See Veritas Resiliency Platform Solutions
for Applications.
For NetApp
SnapMirror
replication:
When adding or refreshing a configuration, Add Enclosures
ensure that host discovery is complete before
adding/refreshing the NetApp enclosure.
Add the storage array When you enter the array information in the
to the IMS
IMS wizard, you must specify the IMS as the
discovery host.
See “Managing enclosure assets for an IMS”
on page 92.
71
Adding the asset infrastructure
Adding the asset infrastructure to an Infrastructure Management Server (IMS)
Adding the asset infrastructure to an
Infrastructure Management Server (IMS)
After you add an Infrastructure Management Server (IMS) to the resiliency domain,
you add the asset infrastructure to the IMS.
The asset infrastructure can include hosts, virtualization servers, and enclosures
(storage arrays used for replication). The assets you must add depend on the use
case and environment.
See “About the asset infrastructure” on page 63.
Note: Replication appliances are added in a different way from other types of asset
infrastructure.
See “Adding RecoverPoint appliance for replication” on page 112.
To add the asset infrastructure to an IMS
1
Prerequisites
To verify supported assets, refer to the Hardware and Software Compatibility
List (HSCL).
2
Navigate
Settings (menu bar) > Infrastructure
You can also access this page from the Quick Actions menu > Manage Asset
Infrastructure.
3
Under the data center, locate the IMS and click Manage Asset Infrastructure.
The Settings page for the IMS is displayed. You can add, edit, or remove
assets.
Tip: You must add Hyper-V servers as hosts rather than as virtualization
servers.
See “Managing host assets for an IMS” on page 73.
See “Managing Hyper-V assets for an IMS” on page 81.
See “Managing VMware virtualization servers for an IMS” on page 82.
See “Managing enclosure assets for an IMS” on page 92.
72
Adding the asset infrastructure
Managing host assets for an IMS
Managing host assets for an IMS
The asset infrastructure that you must add to an Infrastructure Management Server
(IMS) can include assets that you add as hosts. The following topics describe the
types of assets you add as hosts, the prerequisites, and how to add and remove
host assets.
See “About adding host assets to an IMS” on page 73.
See “Prerequisites for adding hosts to an IMS” on page 74.
See “Adding hosts to an IMS” on page 76.
See “About using a CSV file for adding hosts to an IMS” on page 76.
See “Removing hosts from an IMS ” on page 78.
See “Uninstalling the host package from a Linux host” on page 79.
See “Uninstalling the host package from a Windows host” on page 80.
See “Refreshing host discovery information for an IMS” on page 80.
About adding host assets to an IMS
You add several types of assets as hosts to an Infrastructure Management Server
(IMS). Host assets that you add to an IMS can include physical systems, virtual
machines, and Hyper-V servers, depending on the use case, as described in the
table.
Note: You must add a host to only one IMS.
Table 8-10
Use cases for adding host assets to an IMS
Use case
Details
Application discovery and
management
For discovery of supported applications on either physical
systems or virtual machines, you must add the physical
system or virtual machine as a host.
Note: For the use case of discovering and managing virtual
machines rather than applications, you do not need to add
the virtual machines as hosts.
For discovery of a custom application, after you add the hosts,
you must also add the application on the Assets page.
More information is available on adding custom applications.
See Veritas Resiliency Platform Solutions for Applications.
73
Adding the asset infrastructure
Managing host assets for an IMS
Table 8-10
Use cases for adding host assets to an IMS (continued)
Use case
Details
Hyper-V virtualization server Hyper-V servers used for virtualization must be added as
host assets, rather than as virtualization servers.
Control Host for VMware
vCenter Server (optional)
You can add a host to the IMS to be used as the Control Host
by the IMS for discovery of a VMware vCenter Server.
See “About using a separate Control Host for discovery of
VMware servers” on page 84.
Hardware replication
For storage array-based replication, you may need to install
array-specific software on a host and add the host to the IMS
to use as a discovery host.
See “About the discovery host” on page 93.
More information is available on requirements for adding
enclosures for array-based replication.
See “Managing enclosure assets for an IMS” on page 92.
When you add hosts to an IMS, the IMS installs the host package (VRTSsfmh) on
the host. On Linux hosts, the VRTSsfmh package is installed in the /opt directory.
On Windows hosts, the VRTSsfmh package is installed in the system drive.
The IMS also installs several add-on packages on the host for use by the IMS
discovery:
■
Veritas Resiliency Platform Enablement add-on
■
Applications Enablement add-on
Before you add hosts to the IMS, ensure that all prerequisites are met.
See “Prerequisites for adding hosts to an IMS” on page 74.
Prerequisites for adding hosts to an IMS
Before you add hosts to an Infrastructure Management Server (IMS), ensure that
the following prerequisites are met. Prerequisites include general prerequisites for
all hosts and additional prerequisites for Linux or Windows systems.
General prerequisites for adding host assets to an IMS:
■
Ensure that the IMS can communicate with the host.
See “Network and firewall requirements” on page 25.
74
Adding the asset infrastructure
Managing host assets for an IMS
■
Ensure that the time difference between the system clocks on the IMS and host
is no more than 90 minutes. The managed hosts must report synchronized
universal time clock time (UC/UTC).
■
If a CSV file is used to add hosts, ensure that it uses the correct syntax.
See “About using a CSV file for adding hosts to an IMS” on page 76.
Additional prerequisites for Linux systems:
■
In order to install the host package while adding the Linux host, ensure that the
PasswordAuthentication field is set to yes in the /etc/ssh/sshd_config file
on the host.
■
Ensure that the following Linux packages are installed: glibc (32-bit), libstdc++
(32-bit), and NetworkManager.
Additional prerequisites for Windows systems:
■
You must manually install the VRTSsfmh host package on one Windows host
before you can add the Windows host to the IMS using the web console. You
can then add any remaining Windows hosts from the same domain using the
console, and the IMS installs the host package on the subsequent Windows
hosts.
See “Installing the host package on a Windows host” on page 75.
■
If you install the host package using the web console, you should be a domain
user having administrative privileges on the host. If you install the host package
manually, then you need to be a local user having administrative privileges on
the host.
■
The Windows Management Instrumentation (WMI) service must be running.
More information is available about the add host operation.
See “About adding host assets to an IMS” on page 73.
Installing the host package on a Windows host
Before you can use the wizard in the web console to add Windows hosts to an
Infrastructure Management Server, you must first manually install the VRTSsfmh
host package on at least one Windows host.
Note: By default, the VRTSsfmh package is installed in the system drive. You cannot
specify a different location to install the package.
75
Adding the asset infrastructure
Managing host assets for an IMS
To install the host package on a Windows host
1
Log on to the target host as a user with administrator privileges.
2
Make sure that the value for environment variable PATHEXT on the target host
includes the extensions .exe, .bat, and .vbs.
3
Download the host installation files bundle, and unzip it.
See “Downloading the Resiliency Platform virtual appliance” on page 29.
4
From the directory to which you unzipped the installation files bundle, open an
elevated command prompt and run
VRTSsfmh_7.0.3.0_Windows_arch_x64.msi.
5
On the welcome screen of the Installation Wizard, click Next.
6
On the Ready to Install the Program screen, click Install to start the
installation.
7
Click Finish to exit the Installation Wizard.
See “Managing host assets for an IMS” on page 73.
About using a CSV file for adding hosts to an IMS
When adding hosts to an Infrastructure Management Server (IMS), you have the
option to import the information from a comma-separated (.csv) file. The CSV file
must include the “.csv” extension. The following is an example of a CSV file:
Host,User,Password
host1.abc.com,username1,password1
host2.abc.com,username2,password2
The first line in the CSV file must appear as above. You replace the subsequent
lines with your hosts, user names, and passwords.
See “Adding hosts to an IMS” on page 76.
Adding hosts to an IMS
After adding an Infrastructure Management Server (IMS) to the resiliency domain,
you can add host assets to the IMS.
76
Adding the asset infrastructure
Managing host assets for an IMS
To add hosts to an IMS
1
Prerequisites
Ensure that you understand the use cases and prerequisites for adding hosts
to an IMS.
See “About adding host assets to an IMS” on page 73.
See “Prerequisites for adding hosts to an IMS” on page 74.
2
Navigate
Settings (menu bar) > Infrastructure
You can also access this page from the Quick Actions menu.
3
Under the data center, locate the IMS and click Manage Asset Infrastructure.
4
On the IMS Settings page, click Host to view information on already added
hosts, then click Add Hosts.
Or to go directly to the Add Hosts wizard, click Add Hosts in the Settings page
menu bar.
5
6
In the wizard, select the installation option that corresponds to the platform of
the hosts. The appropriate host package is automatically installed on the hosts
by the IMS if you continue with the Add Host operation.
■
If the host package is already present on the host that is being added, select
None.
■
If you select Install managed host package on Linux/Unix, the Use root
password option is enabled. Select this option if you want to install the
host package on a Linux/Unix host as a non-root user. Provide the non-root
username, non-root password, and root password for the specified host.
You can use this option if the Secure Shell (SSH) access is disabled for
the root login on the host where you want to install the host package.
■
Before you can add the first Windows host to the IMS, you must manually
install the host package on the host. Then add the host using the None
option in this wizard.
See “Installing the host package on a Windows host” on page 75.
After the first Windows host is added, to add more Windows hosts, run the
wizard again and select Install managed host package on Windows.
Then, for Select Windows Managed Host, select the host added previously.
If there are multiple Windows hosts listed, you can select any one.
Choose from the following methods of adding a host:
77
Adding the asset infrastructure
Managing host assets for an IMS
■
Type the information on the table row. To add a blank table row, click Add.
■
Click Clone to clone the selected table row, and then edit the clone.
■
To import the information from a CSV file, click Import.
7
Verify that the host has been added successfully.
8
In the Recent tasks pane, verify that the Install add-on tasks for the Veritas
Resiliency Platform Enablement add-on, and Veritas Resiliency Platform
Applications Enablement add-on are successfully completed on the host.
If the add-ons are not successfully installed, then you need to manually install them
on the host.
See “Installing add-ons on the hosts” on page 115.
If installation of the Veritas Resiliency Platform Applications Enablement add-on
fails and an error message to run the cleanup script is displayed, you need to run
the following script on the managed host:
C:\ProgramData\Symantec\VRTSsfmh\spool\addons\store
\VRTSitrpappdr-1.0.0.0\CleanUp_Scripts\cleanup.bat
See “Managing host assets for an IMS” on page 73.
Removing hosts from an IMS
You can remove one or more hosts that were added to an Infrastructure
Management Server (IMS).
If the hosts contain assets that were added to a Resiliency Platform resiliency group,
after you remove the hosts, the assets are no longer shown as part of the resiliency
group in the console. However, removing a resiliency group does not remove related
hosts from the IMS. Removing hosts and removing resiliency groups are separate
operations and can be performed in either sequence.
If Control Host add-on is installed on the host then you need to uninstall the add-on
and then remove the host from the IMS.
See “Uninstalling add-ons from the hosts” on page 117.
For more information about resiliency groups, see the Solutions guides.
78
Adding the asset infrastructure
Managing host assets for an IMS
To remove hosts from an IMS
1
Prerequisites
Before removing a host, you need to uninstall all the add-ons that were installed
on the host.
See “Uninstalling add-ons from the hosts” on page 117.
2
Navigate
Settings (menu bar) > Infrastructure
3
Under the data center, locate the IMS and click Manage Asset Infrastructure.
4
On the IMS Settings page, click Host.
5
Right-click the host and select Remove.
To remove more than one host, hold down Ctrl as you select hosts from the
list.
6
Confirm that you want to remove the host.
Removing a host from the IMS does not uninstall the host package (VRTSsfmh)
from the host. More information is available on uninstalling the host package.
See “Uninstalling the host package from a Linux host” on page 79.
See “Uninstalling the host package from a Windows host” on page 80.
See “Managing host assets for an IMS” on page 73.
Uninstalling the host package from a Linux host
You can use an operating system command to remove the VRTSsfmh package
from a Linux host. Before you uninstall the host package, remove the host from the
Infrastructure Management Server (IMS).
See “Removing hosts from an IMS ” on page 78.
To uninstall the host package from a Linux host
1
Open an operating system console.
2
On the managed host where you plan to uninstall the host package, log on as
root.
3
At the command prompt, enter the following command to uninstall the package:
rpm -e VRTSsfmh
79
Adding the asset infrastructure
Managing host assets for an IMS
Uninstalling the host package from a Windows host
You can use an operating system command to remove the VRTSsfmh package
from a Windows host. Before you uninstall the host package, remove the host from
the Infrastructure Management Server (IMS).
See “Removing hosts from an IMS ” on page 78.
To uninstall the host package from a Windows host
1
Log in to the target host as a user with administrator privileges.
2
Go to the Windows Control Panel, and click Programs and Features.
3
From the list of installed programs, select Veritas InfoScale Operations
Manager (Host Component).
4
Do one of the following:
■
Select Uninstall at the top of the list.
■
Right click and select Uninstall. Click Yes to confirm.
Refreshing host discovery information for an IMS
You can submit a refresh request to update the information displayed for the hosts
that have been added to the Infrastructure Management Server (IMS). Once the
refresh operation is complete, the Assets page in the console is also updated.
To refresh a host discovery for the IMS
1
Navigate
Settings (menu bar) > Infrastructure
2
Under the data center, locate the IMS and click Manage Asset Infrastructure.
3
On the IMS Settings page, click Host.
4
Right-click the host (press CRTL to select multiple hosts) and select Refresh.
5
Click OK.
The refresh operation is asynchronous. The wizard displays that the operation
has triggered the refresh, but the discovery operation is in progress in the
background. The Discovery State column shows a status of Refreshing. When
it is complete, you can view the status change reflected in the Discovery State
column.
See “Managing host assets for an IMS” on page 73.
80
Adding the asset infrastructure
Managing Hyper-V assets for an IMS
Managing Hyper-V assets for an IMS
You can add Hyper-V servers to an Infrastructure Management Server (IMS) for
discovery of Hyper-V virtual machines. Hyper-V servers are added as hosts.
See “About Microsoft Hyper-V virtualization discovery” on page 81.
See “Prerequisites for Microsoft Hyper-V virtualization discovery by the IMS”
on page 81.
See “Adding hosts to an IMS” on page 76.
See “Managing host assets for an IMS” on page 73.
About Microsoft Hyper-V virtualization discovery
Hyper-V is a hypervisor-based virtualization technology from Microsoft. The
Infrastructure Management Server (IMS) can discover Hyper-V host and virtual
machine-related information if the Hyper-V role is enabled on the host. The Hyper-V
WMI API and Windows PowerShell commandlets are used for the discovery.
Hyper-V discovery can be grouped into the following categories:
■
Virtual machine discovery: Discovery of the Hyper-V virtual machines and its
correlation with the Hyper-V server.
When you add the Hyper-V server to the IMS, IMS discovers all virtual machines
including the virtual machines without the guest operating system installed.
■
Exported storage discovery: Discovery of storage that is provisioned to the
guests and its correlation with the virtual machine and Hyper-V server.
IMS discovers the storage provisioned to the guests from the host's local storage,
or storage area network (SAN). The Hyper-V guest, when added to the IMS
domain, provides storage mapping discovery.
See “Managing Hyper-V assets for an IMS” on page 81.
Prerequisites for Microsoft Hyper-V virtualization discovery by the
IMS
You can add Microsoft Hyper-V servers to an Infrastructure Management Server
(IMS) for virtualization discovery.
Note: When adding Hyper-V servers to the IMS in the console, you choose the
option to add hosts rather than to add virtualization servers.
For information on supported operating system versions for the Hyper-V Server,
refer to the Hardware and Software Compatibility List (HSCL).
81
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
Table 8-11
Requirements for Microsoft Hyper-V virtualization discovery
Type of discovery
Requirements
Virtual machine discovery
■
■
■
The VRTSsfmh package must be installed on the
Hyper-V Server (parent partition). This is done
automatically by the IMS when you add the Hyper-V
server to the IMS as a host.
The Hyper-V role must be enabled.
The Windows Management Instrumentation (WMI)
service must be running on the Hyper-V Server.
There are additional prerequisites for adding hosts to
an IMS.
See “Prerequisites for adding hosts to an IMS”
on page 74.
Exported storage discovery
■
The Windows Management Instrumentation (WMI)
service must be running on the guest.
See “Managing Hyper-V assets for an IMS” on page 81.
See “Managing host assets for an IMS” on page 73.
Managing VMware virtualization servers for an
IMS
You can add VMware vCenter servers to an Infrastructure Management Server
(IMS) for VMware discovery.
The VMware discovery provides the following the vCenter server information:
■
Information on vCenter servers
■
Information on the ESX servers managed by the vCenter servers
■
Information on the virtual machines that are configured on the ESX servers
See “Prerequisites for adding VMware servers for discovery by the IMS” on page 83.
See “About using a separate Control Host for discovery of VMware servers”
on page 84.
See “Adding virtualization servers for VMware discovery by the IMS” on page 88.
See “Editing a VMware virtualization discovery configuration in the IMS” on page 90.
See “Removing a virtualization discovery configuration from the IMS” on page 91.
See “Refreshing a VMware virtualization discovery configuration” on page 91.
82
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
See “Refreshing an ESX Server discovery” on page 91.
Prerequisites for adding VMware servers for discovery by the IMS
Ensure that the following requirements are met to add the VMware vCenter or ESX
servers to the Infrastructure Management Server (IMS):
■
Ensure that the IMS server can ping the vCenter servers or the ESX servers
from which it can discover the information on VMware Infrastructure.
Optionally, you can add a separate host to act as the Control Host for the vCenter
Server.
See “About using a separate Control Host for discovery of VMware servers”
on page 84.
■
Ensure that you have configured near real-time discovery of VMware events.
See “About near real-time discovery of VMware events” on page 84.
See “Setting up near real-time discovery of VMware events” on page 86.
See “Configuring the VMware vCenter Server to generate SNMP traps”
on page 87.
■
Ensure that the vCenter Server user account that is used to add the servers to
IMS has the following privileges assigned:
■
System.Anonymous
■
System.View
■
System.Read
■
Datastore.AllocateSpace
■
Datastore.Rename
■
Host.Config.Storage
■
Host.Config.Settings
■
Host.Config.Network
■
VirtualMachine.Config.AddNewDisk
■
VirtualMachine.Config.RemoveDisk
■
VirtualMachine.Config.DiskExtend
■
VirtualMachine.Interact.PowerOff
■
VirtualMachine.Interact.PowerOn
■
VirtualMachine.Inventory.Register
■
VirtualMachine.Inventory.Unregister
83
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
■
VirtualMachine.Provisioning.Customize
There are additional requirements for virtual machines if added to the IMS,
depending on the use case.
See “Prerequisites for adding hosts to an IMS” on page 74.
About using a separate Control Host for discovery of VMware servers
Resiliency Platform uses a designated Control Host to discover a VMware vCenter
Server. This discovery displays those ESX servers that the VMware vCenter Server
manages and the virtual machines that are configured on the ESX servers.
You can use the Infrastructure Management Server (IMS) as the Control Host, or
you can designate a separate host as a Control Host.
For example, you may want to designate a separate host from the IMS as Control
Host to address the following situations:
■
To discover a vCenter server that is behind a firewall and you do not want to
install the IMS inside the firewall.
■
To reduce the discovery load on the IMS.
To designate a separate host as the Control Host for a vCenter Server:
■
Ensure that the Control Host can communicate with the vCenter server and with
the IMS.
■
Add the host to the IMS to make it a managed host.
See “Adding hosts to an IMS” on page 76.
■
Install the Control Host Add-on on the managed host.
See “Installing add-ons on the hosts” on page 115.
■
Select the Control Host when you add the vCenter Server to the IMS (or edit an
existing configuration).
See “Adding virtualization servers for VMware discovery by the IMS” on page 88.
About near real-time discovery of VMware events
The Infrastructure Management Server (IMS) uses VMware events to discover in
near real-time a change in the state of a virtual machine (for example, virtual machine
powered on) and changes occurring at the vCenter Server infrastructure level (for
example, virtual machine created).
To set up the near real-time discovery of VMware events by the IMS, you must
configure the vCenter Server to generate SNMP traps and send them to the IMS
address. The recommended sequence is to do this before adding the vCenter
Server to the IMS.
84
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
See “Setting up near real-time discovery of VMware events” on page 86.
The near real-time discovery of VMware infrastructure enables the partial discovery
of ESX servers managed under a vCenter Server. This discovery is triggered by
the event notification from the VMware vCenter Server to the IMS using SNMP
traps. For example, if an SNMP trap is received for a virtual machine (VM1) hosted
on ESX1, the IMS runs the discovery cycle only for ESX1. Other ESX servers under
that vCenter Server are not re-discovered.
The IMS component of near real-time discovery is xtrapd. After you configure a
vCenter Server to send the SNMP traps to the IMS, you add the vCenter Server to
the IMS. The xtrapd daemon now detects the SNMP traps that are sent from the
specified vCenter Server. The Resiliency Platform database and console are updated
with the latest state of the virtual machine or infrastructure changes.
Note: SNMP version 1 (SNMPv1) and version 2 (SNMPv2) are supported.
For details on supported events, see the following table.
Table 8-12
Supported events for near-real time discovery
Discovered state
Event as shown in VMware vCenter
Server
Virtual machine powered on
VM powered on
Virtual machine powered off
VM powered off
Virtual machine Distributed Resource
Scheduler (DRS) powered on
DRS VM powered on
Virtual machine suspended
VM suspended
Virtual machine created
VM created
Virtual machine migrated
VM migrated
Hot migration: A powered-on virtual machine
is migrated from one ESX server to another
ESX server.
Virtual machine relocated from one ESX
server to another
VM relocating
Cold migration: A powered-off virtual machine
is migrated from one ESX server to another
ESX server.
Virtual machine renamed
VM renamed
85
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
Table 8-12
Supported events for near-real time discovery (continued)
Discovered state
Event as shown in VMware vCenter
Server
Virtual machine migrated to another host by DRS VM migrated
VMware DRS (Distributed Resource
Scheduler)
Setting up near real-time discovery of VMware events
To set up the near real-time discovery of VMware events, complete the following
steps.
Table 8-13
Step
Setting up near real-time (NRT) discovery of VMware events
Action
Description
Using VMware vCenter Server console:
Step 1
In the vCenter Server
console, provide IMS
details and configure the
alarm for sending the
SNMP traps.
Configure the IMS address as the SNMP trap
receiver URL. Also configure the alarm to send
the SNMP traps when the state of the virtual
machine changes.
See “Configuring the VMware vCenter Server to
generate SNMP traps” on page 87.
Using the Resiliency Platform console:
Step 2
Add the vCenter Server to
the IMS as a virtualization
server.
See “Adding virtualization servers for VMware
discovery by the IMS” on page 88.
After you add the vCenter Server to the IMS, the
xtrapd daemon on the IMS starts accepting
SNMP traps from the specified vCenter Server.
Note: If you have not configured the vCenter
Server as in step 1 before adding it to the IMS, a
warning message is displayed. It does not affect
the vCenter Server discovery. However, near
real-time discovery of VMware events is not
functional. To enable the near real-time discovery
subsequently, first configure the vCenter Server.
Then refresh the vCenter Server configuration in
the IMS using the Resiliency Platform console.
See “Refreshing a VMware virtualization
discovery configuration” on page 91.
86
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
By default, near real-time discovery of VMware events is enabled. To disable it,
you need to remove the IMS as the SNMP receiver in the vCenter Server and
refresh the vCenter Server configuration in the IMS.
See “About near real-time discovery of VMware events” on page 84.
Configuring the VMware vCenter Server to generate SNMP traps
In the VMware vCenter Server console, provide the following information to configure
the vCenter Server to generate SNMP traps and send them to the IMS:
■
Configure the Infrastructure Management Server (IMS) as the SNMP trap
receiver, as follows:
Navigate to the SNMP configuration. Enable one of the SNMP receivers and
enter the following details:
Field
Description
Receiver URL
Provide the host name of the IMS which will be connected to
the vCenter Server. The vCenter Server sends the SNMP traps
to this IMS.
Also, configure port 162 as the SNMP port. Ensure that port
162 is not used by any other application in IMS.
Community String
■
Provide community string. SNMP versions v1 and v2 are
supported.
Configure an alarm for generating SNMP traps when a virtual machine state
changes or any virtual infrastructure-related change occurs.
This step includes adding an alarm to monitor the changes related to virtual
machine state and vCenter Server infrastructure, and then adding the appropriate
action (for example, send a notification trap).
■
You can set the alarm at an individual virtual machine level, at the data center
level, or at the entire VMware vCenter Server level. It is recommended to
set it at the vCenter Server level.
■
For the alarm type details, make sure to specify the following
■
■
Set the alarm type to monitor virtual machines
■
Set the alarm to monitor for specific events occurring on this object, for
example, VM powered on
■
Enable the alarm
Add the required triggers to monitor the states of the virtual machine. For
example, VM created, VM migrated, VM powered on, VM powered off, VM
87
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
suspended, DRS VM powered on (for clustered environment with DRS
enabled) and so on. The values of the fields are as follows:
■
For the following value of an
event...
Select the following status...
VM powered on
Unset
VM powered off
Unset
DRS VM powered on
Unset
VM suspended
Unset
VM created
Unset
VM migrated
Unset
VM relocating
Unset
VM renamed
Unset
DRS VM migrated
Unset
Add the required triggers to monitor the states of the hosts. The values of the
fields are as follows:
For the following value of an event... Select the following status...
■
Host disconnected
Unset
Host connected
Unset
Add a new action to send a notification trap. Specify to send the notification trap
as in the following example:
See “About near real-time discovery of VMware events” on page 84.
See “Setting up near real-time discovery of VMware events” on page 86.
Adding virtualization servers for VMware discovery by the IMS
You can add VMware vCenter servers to an Infrastructure Management Server
(IMS) for VMware discovery.
88
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
The VMware discovery provides the following information:
■
Information on vCenter servers
■
Information on the ESX servers that the vCenter Server manages
When adding a vCenter Server, you have the option to automatically discover
all ESX servers registered to the vCenter Server or manually specify names of
selected ESX servers to discover.
■
Information on the virtual machines that are configured on the ESX servers
Optionally, you can add a separate host to act as the Control Host for the vCenter
Server, and then select that host while adding the virtualization server.
See “About using a separate Control Host for discovery of VMware servers”
on page 84.
To add a virtualization server for VMware discovery by the IMS
1
Prerequisites:
See “Prerequisites for adding VMware servers for discovery by the IMS”
on page 83.
2
Navigate
Settings (menu bar) > Infrastructure
You can also access this page from the Quick Actions menu.
3
Under the data center, locate the IMS and click Manage Asset Infrastructure.
4
On the IMS Settings page, click Virtualization to view information on existing
virtualization servers, then click Add Virtualization Server.
Or to go directly to the Add Virtualization Server wizard, click Add Virtualization
Server in the Settings page menu bar.
5
In the wizard, specify the information for the vCenter Server and click Next.
Tips:
■
For Configuration Name, specify a name that will help you identify this
configuration
■
Specify the fully-qualified name of the vCenter Server that you want to
discover along with its port number, separated by a colon. If the vCenter
Web service is running on a default port, you do not need to specify the
port number.
89
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
■
When entering login credentials, an administrative vCenter Server user
account is required.
6
Choose to automatically discover all ESX servers or manually specify names
of ESX servers to discover. Click Finish.
7
In the Result panel, view the progress of the configuration. After the
configuration is complete, click OK.
8
After you add a vCenter Server, to view all ESX servers that the vCenter Server
manages, click vCenter under Data Center.
If any changes are made on the virtualization server after adding it to the IMS, you
need to refresh the server discovery configuration.
See “Refreshing a VMware virtualization discovery configuration” on page 91.
Editing a VMware virtualization discovery configuration in the IMS
You can edit a virtualization discovery configuration in the Infrastructure Management
Server (IMS) to modify the following information:
■
Name of the configuration.
■
Credentials to log on to the vCenter.
When entering the username, you must enter in the format
[email protected], not domainname\username.
To edit a virtualization discovery configuration in the IMS
1
Navigate
Settings (menu bar) > Infrastructure
2
Under the data center, locate the IMS and click Manage Asset Infrastructure.
3
On the IMS Settings page, click Virtualization.
4
In the Virtualization Configurations details list, right-click the configuration
that you want to edit.
5
In the Edit Configuration wizard panel, modify the required information, click
Next.
6
In the Edit Configuration wizard panel, edit the method for virtualization
discovery of the servers, click Finish.
7
In the Result panel, view the progress of the configuration, click OK.
See “Managing VMware virtualization servers for an IMS” on page 82.
90
Adding the asset infrastructure
Managing VMware virtualization servers for an IMS
Removing a virtualization discovery configuration from the IMS
To remove a virtualization discovery configuration from the IMS
1
Navigate
Settings (menu bar) > Infrastructure
2
Under the data center, locate the IMS and click Manage Asset Infrastructure.
3
On the IMS Settings page, click Virtualization.
4
Right-click the virtualization server and select Remove Configuration.
5
In the Remove Virtualization Configuration wizard panel, click Remove.
6
In the Result panel, click OK.
See “Managing VMware virtualization servers for an IMS” on page 82.
Refreshing a VMware virtualization discovery configuration
You can submit a refresh request to update the information displayed on the table
of virtualization servers that have been added to the Infrastructure Management
Server (IMS).
To refresh a virtualization discovery configuration
1
Navigate
Settings (menu bar) > Infrastructure
2
Under the data center, locate the IMS and click Manage Asset Infrastructure.
3
On the IMS Settings page, click Virtualization.
4
Right-click the virtualization configuration and select Refresh Configuration.
5
In the Refresh Virtualization Configuration wizard panel, click Refresh.
6
In the Result panel, click OK.
See “Managing VMware virtualization servers for an IMS” on page 82.
Refreshing an ESX Server discovery
You can refresh the Infrastructure Management Server (IMS) discovery of one or
more ESX servers that are configured under a selected VMware vCenter Server.
91
Adding the asset infrastructure
Managing enclosure assets for an IMS
To refresh the discovery of an ESX server
1
Navigate
Settings (menu bar) > Infrastructure
2
Under the data center, locate the IMS and click Manage Asset Infrastructure.
3
On the IMS Settings page, click Virtualization.
4
Under the Virtualization Configurations tab, you can view the details of
virtualization configuration. For example, the name of the virtualization server
(vCenter Server) used in the configuration, its type, and other parameters.
Select the desired virtualization configuration.
5
The Configured Virtualization Servers tab lists the ESX servers managed
under the vCenter Server that is part of the selected virtualization configuration.
6
Right-click the required ESX server and click Refresh. Press Ctrl or Shift for
the selection of multiple ESX servers.
7
In the Refresh Virtualization Server wizard panel, click Refresh.
8
In the Result panel, click OK.
See “Managing VMware virtualization servers for an IMS” on page 82.
Managing enclosure assets for an IMS
You can add storage enclosures (arrays) to an Infrastructure Management Server
(IMS) for discovery of storage information to monitor array-based replication.
This does not apply for environments that are using Hyper-V Replica.
See “About the discovery host” on page 93.
See “Configuration prerequisites for adding storage enclosures to an IMS”
on page 93.
See “Adding storage enclosures for discovery by the IMS” on page 104.
See “Adding RecoverPoint appliance for replication” on page 112.
See “Editing the discovery configuration for an enclosure” on page 113.
See “Removing the discovery configuration for an enclosure” on page 114.
92
Adding the asset infrastructure
Managing enclosure assets for an IMS
About the discovery host
A discovery host is a Windows or Linux host on which are installed vendor-specific
array management tools that the Infrastructure Management Server (IMS) uses for
discovery and monitoring the enclosure (storage array). When you add the enclosure
to the IMS, you specify a discovery host in the Add Enclosure wizard. The discovery
host must also be added to the IMS.
In the case of NetApp, you specify the IMS as a discovery host when you add the
enclosure. You do not add a separate discovery host.
Replication appliances are added in a different way from other types of asset
infrastructure. For the RecoverPoint appliance, the IMS can be used as a discovery
host or you can specify a separate discovery host.
See “Adding RecoverPoint appliance for replication” on page 112.
For 3PAR the discovery host could be Windows or Linux host or the IMS.
Vendor-specific array management tools installation is not required.
See “Adding hosts to an IMS” on page 76.
See “EMC Symmetrix configuration prerequisites” on page 94.
See “NetApp configuration prerequisites” on page 99.
See “Hitachi configuration prerequisites” on page 100.
See “EMC CLARiiON configuration prerequisites” on page 101.
See “EMC VNX configuration prerequisites” on page 104.
See “Managing enclosure assets for an IMS” on page 92.
Configuration prerequisites for adding storage enclosures to an IMS
For array-based replication environments, the asset infrastructure that you add to
the Infrastructure Management Server (IMS) includes storage enclosures and the
discovery host.
For Resiliency Platform to discover replication-related device groups, you must also
add the hosts that contain those device groups to the IMS.
For more on replication requirements, refer to the Solutions guides.
See “About the discovery host” on page 93.
See “EMC Symmetrix configuration prerequisites” on page 94.
See “NetApp configuration prerequisites” on page 99.
See “Hitachi configuration prerequisites” on page 100.
See “EMC CLARiiON configuration prerequisites” on page 101.
93
Adding the asset infrastructure
Managing enclosure assets for an IMS
See “EMC VNX configuration prerequisites” on page 104.
See “3PAR configuration prerequisites” on page 104.
See “Adding the asset infrastructure to an Infrastructure Management Server (IMS)”
on page 72.
See “Adding hosts to an IMS” on page 76.
EMC Symmetrix configuration prerequisites
For the Infrastructure Management Server (IMS) to discover EMC Symmetrix storage
arrays, ensure that your storage network’s physical connections and device settings
are properly configured.
Physical connection requirements
The physical connection requirements are as follows:
■
Fibre Channel connection between each Symmetrix array and the SAN fabric.
Device setup requirements
The device setup requirements include the following:
You configure an array for discovery using the EMC Symmetrix Command Line
Interface (SYMCLI). The SymCLI utilities must be configured on a discovery host.
Install EMC Solutions Enabler (SYMCLI) on the discovery host.
IMS can also use the EMC Symmetrix Remote Data Facility (SRDF).
Veritas Resiliency Platform supports SYMCLI 7.x for IMS discovery of the EMC
Symmetrix storage enclosures.
For the complete information on supported hardware and software, see the
Hardware and Software Compatibility List (HSCL).
The IMS discovers all in-band Symmetrix storage arrays with a Fibre Channel or
SCSI connection to a discovery host where SYMCLI is installed.
The IMS also supports discovery of EMC Symmetrix storage arrays through remote
SYMAPI servers. This discovery method does not require in-band array connectivity
to the discovery host specified in the array configuration. However, the host on
which the SYMAPI server is running must have in-band connectivity with the
Symmetrix array.
For the IMS to discover EMC Symmetrix arrays using a remote SYMAPI server,
you must specify the remote SYMAPI server while configuring the enclosure in IMS.
See “Configuring the remote SYMAPI server for EMC Symmetrix array discovery”
on page 95.
94
Adding the asset infrastructure
Managing enclosure assets for an IMS
See “Verifying the configuration of a remote SYMAPI server” on page 98.
Replication requirements
To discover and manage EMC SRDF replication technology, you need to create
appropriate device groups on hosts which have EMC Symmetrix Gatekeeper devices
mapped. Device groups need to be defined on such hosts in both the production
and recovery data centers. You must add these hosts to the local IMSs so that
Resiliency Platform can discover the device groups.
See “Adding hosts to an IMS” on page 76.
For more information on requirements for array-based replication, see the Solutions
guides.
See “Managing enclosure assets for an IMS” on page 92.
Configuring the remote SYMAPI server for EMC Symmetrix array
discovery
The Infrastructure Management Server (IMS) supports the discovery of EMC
Symmetrix arrays with a remote SYMAPI server mechanism. This discovery method
does not require in-band array connectivity to the host from which the EMC
Symmetrix array is discovered.
For the IMS to discover EMC Symmetrix arrays using a remote SYMAPI server,
you need to configure the SYMAPI server. To configure the remote SYMAPI server
in your environment, you need to perform two tasks:
■
Ensure that the remote SYMAPI server daemon is running on the server where
the EMC Solutions Enabler is installed. See the following procedure:
To ensure that the remote SYMAPI server daemon is running on the server
where the EMC Solutions Enabler is installed
■
Ensure that the EMC Solutions Enabler on the discovery host can communicate
with the remote SYMAPI server. See the following procedure:
To ensure that the EMC Solutions Enabler can communicate with the remote
SYMAPI server
95
Adding the asset infrastructure
Managing enclosure assets for an IMS
To ensure that the remote SYMAPI server daemon is running on the server
where the EMC Solutions Enabler is installed
1
Log on with the administrative credentials to the host that you want to use as
the remote SYMAPI server and which has in-band connectivity to the EMC
Symmetrix array.
2
Type the following command on the host:
stordaemon list
An example of the daemon list appears.
Available Daemons
[*] storapid
storgnsd
storrdfd
storevntd
[*] storwatchd
storsrmd
storstpd
storsrvd
[*] storsrvdInst
('[*]': Currently Running):
EMC Solutions Enabler Base Daemon
EMC Solutions Enabler GNS Daemeon
EMC Solutions Enabler RDF Daemon
EMC Solutions Enabler Event Daemon
EMC Solutions Enabler Watchdog Daemon
EMC Solutions Enabler SRM Daemon
EMC Solutions Enabler STP Daemon
EMC Solutions Enabler SYMAPI Server Daemon
>>> Running Instance of storsrvd <<<
The name for the remote SYMAPI server daemon is storsrvd. If you see a
[*] for storsrvd, that means the remote SYMAPI server daemon is already
running on the host. If the daemon is running, proceed to the next procedure.
To ensure that the EMC Solutions Enabler can communicate with the remote
SYMAPI server
96
Adding the asset infrastructure
Managing enclosure assets for an IMS
3
Type the following commands to start the storsrvd daemon:
stordaemon start storsrvd
Waiting for daemon to start. This may take several seconds.
stordaemon list
An example of the daemon list appears.
Available Daemons
[*] storapid
storgnsd
storrdfd
storevntd
[*] storwatchd
storsrmd
storstpd
[*] storsrvd
4
('[*]': Currently Running):
EMC Solutions Enabler Base Daemon
EMC Solutions Enabler GNS Daemeon
EMC Solutions Enabler RDF Daemon
EMC Solutions Enabler Event Daemon
EMC Solutions Enabler Watchdog Daemon
EMC Solutions Enabler SRM Daemon
EMC Solutions Enabler STP Daemon
EMC Solutions Enabler SYMAPI Server Daemon
Perform steps 1 and 2 on each host in which you want to configure the remote
SYMAPI server.
To ensure that the EMC Solutions Enabler can communicate with the remote
SYMAPI server
1
Install EMC Solutions Enabler on the Discovery Host.
2
Change to the SYMAPI configuration directory. By default, the directory is:
3
■
Linux — /var/symapi/config
■
Windows — %PROGRAMFILES%\EMC\SYMAPI\config
Modify the file "netcnfg" in the SYMAPI configuration directory of the host where
the EMC Solutions Enabler is installed. Append the entry for the configured
SYMAPI server(s) to the end of the file. The following is an example of adding
entries for two SYMAPI servers:
#SYMAPI_SERVER - TCPIP node001 WWW.XXX.YYY.ZZZ 2707 DC1_SERVER - TCPIP ctrlhost_1 10.200.15.155 2707 DC2_SERVER - TCPIP ctrlhost_2 10.249.100.155 2707 -
See “EMC Symmetrix configuration prerequisites” on page 94.
97
Adding the asset infrastructure
Managing enclosure assets for an IMS
Verifying the configuration of a remote SYMAPI server
Verify the remote SYMAPI server configuration before you perform the device setup
requirements. Set environment variables to test if the SYMAPI server is configured
correctly.
To verify the configuration of a remote SYMAPI server
1
Open an operating system console and log on to the host as root (Linux) or as
a user with administrator-level privileges (Windows).
2
Ensure that the SYMCLI commands are in your PATH environment.
3
Do one of the following:
■
On Linux, run the following SYMCLI commands to set the server's
environment variables:
SYMCLI_CONNECT_TYPE=REMOTE; export SYMCLI_CONNECT_TYPE
SYMCLI_CONNECT=DC1_SERVER; export SYMCLI_CONNECT
symcfg list
■
On Windows, run the following SYMCLI commands to set the server's
environment variables:
set SYMCLI_CONNECT_TYPE=REMOTE
set SYMCLI_CONNECT=DC1_SERVER
symcfg list
4
Ensure that the arrays on different remote SYMAPI server hosts are discovered
correctly.
If you get an error in the output (instead of a list of the Symmetrix arrays), verify
that your EMC Solutions Enabler is configured properly. If it is not configured
properly, consult the EMC Solutions Enabler install guide for the commands.
The install guide provides the detailed instructions on configuring the SYMAPI
server and related commands.
5
To unset the environment variables, type the following commands:
unset SYMCLI_CONNECT_TYPE
unset SYMCLI_CONNECT
See “EMC Symmetrix configuration prerequisites” on page 94.
98
Adding the asset infrastructure
Managing enclosure assets for an IMS
NetApp configuration prerequisites
For the Infrastructure Management Server (IMS) to discover a NetApp enclosure
or cluster, ensure that the storage network physical connections and NetApp server
are properly configured.
The NetApp storage objects work on the Data ONTAP operating system, which
provides various interfaces to administer the NetApp storage objects. The IMS
communicates to the enclosures using the ONTAP SDK interface to get the NetApp
enclosure information. This communication occurs through the HTTP protocol (using
the port number 80) or through the HTTPS protocol (using the port number 443).
The IMS supports NetApp 7 mode enclosures that have Data ONTAP 1.4 or later
and NetApp cluster management interface that has Data ONTAP version 8.2.1. or
later.
Physical connection requirements
The physical connection requirements for NetApp enclosure discovery are as follows:
■
Network connectivity between the discovery host and NetApp enclosure or
cluster.
■
You should be able to connect from the discovery host to NetApp enclosure or
server using HTTP and HTTPS connections. Use the following URLs to access
the enclosure:
■
https://netapp_address/na_admin
Port 443 is used for HTTPS connection.
■
http://netapp_address/na_admin
Port 80 is used for HTTP connection.
■
netapp_address is the IP address or NetApp array name, registered with
the Domain Name System (DNS).
Device setup requirements
Setting up the device includes NetApp server configuration and enabling support
for MultiStore Virtual Systems on NetApp enclosure.
Configure the array with an IP address or name, and an administrator-level account
with valid user name and password. These credentials are used by IMS to access
the enclosure for discovery.
Ensure you turn on the following options in the NetApp 7 Mode enclosure. These
are required for NetApp SnapMirror operations.
■
httpd.admin.enable
■
httpd.enable
99
Adding the asset infrastructure
Managing enclosure assets for an IMS
Ensure that following licenses are installed and enabled for NetaApp 7 Mode
enclosure:
■
licensed_feature.multistore.enable (required for discovering IP addresses)
■
licensed_feature.flex_clone.enable (required for rehearsal operation)
Hitachi configuration prerequisites
For the Infrastructure Management Server (IMS) to discover Hitachi TrueCopy
storage arrays, ensure that your storage network’s physical connections and device
settings are properly configured.
Physical connection requirements
The physical connection requirements are as follows:
■
Fiber channel or Small Computer System Interface (SCSI) should directly attach
the hosts to the Hitachi TrueCopy array that contains the TrueCopy P-VOL /
S-VOL devices.
Device setup requirements
The device setup requirements include the following:
■
The host must be configured with Command Control Interface (CCI) provided
by Hitachi TrueCopy.
■
The IMS discovers all Hitachi storage arrays with a Fiber Channel or SCSI
connection to a discovery host where CCI is installed. It discovers TrueCopy as
well as Shadow Instances of Hitachi.
■
The IMS Supports TrueCopy on all microcode levels on all the arrays, only if
the host, HBA, and array combination is supported by Hitachi.
■
Veritas Resiliency Platform supports All Levels of CCI for IMS discovery of the
Hitachi TrueCopy storage enclosures.
Replication requirements
To discover and manage Hitachi TrueCopy/HUR replication technology, you need
to create appropriate HTC/HUR device groups on hosts which have Hitachi
Command Devices mapped. Device groups need to be defined on such hosts in
both the production and recovery data centers. You must add these hosts to the
local IMSs so that Resiliency Platform can discover the device groups.
See “Adding hosts to an IMS” on page 76.
For more information on requirements for array-based replication, see the Solutions
guides.
100
Adding the asset infrastructure
Managing enclosure assets for an IMS
EMC CLARiiON configuration prerequisites
The Infrastructure Management Server (IMS) communicates to the EMC CLARiiON
enclosures through the NaviSphere Secure CLI (NaviSecCLI) utility, which is the
secure CLI for communicating to the NaviSphere package on the enclosure. The
NaviSphere Secure CLI utility must be installed on a discovery host. A discovery
host can be a Windows or Linux host that you add as an asset to the IMS.
The IMS supports only the EMC CLARiiON CX series enclosures with a firmware
version 6.26 and later.
To discover EMC CLARiiON enclosures, ensure that network physical connections
and Navisphere CLI are properly configured.
For more information, refer to Hardware and Software Compatibility List (HSCL).
Physical connection requirements
The physical connection requirements for EMC CLARiiON enclosure are as follows:
■
Network connectivity between the enclosure and discovery host.
Device setup requirements
The device setup requirements for EMC CLARiiON enclosure include using
password security file and verifying NaviSecCLI communication with CLARiiON
enclosure.
See “Using Password Security file for CLARiiON enclosure” on page 101.
See “Verifying NaviSecCLI communication with CLARiiON enclosure” on page 102.
Using Password Security file for CLARiiON enclosure
To use Secure Sockets Layer for the discovery of CLARiiON array, you need to
use Password Security file on the discovery host.
101
Adding the asset infrastructure
Managing enclosure assets for an IMS
To put the password in a security file
1
Log on as root to the host that manages CLARiiON array.
2
Run the following NaviSecCLI command to create the security file:
naviseccli -user userName -password passWord -scope
userScope AddUserSecurity [-secfilepath
secFileFolderName]
Where:
userName is a valid user name for the account in the array.
passWord is the password for the userName.
userScope is the scope of the user that you specified when you created the
account in the array. It can be either local (userScope=1) or global
(userScope=0).
secFileFolderName is the directory where you want the security file to reside.
This directory is the path that you specify when you configure an array for the
discovery.
3
If some CLARiiON arrays have a different user name, repeat step 2 for each
user name, specifying a different secFileFolderName.
If the secFileFolderName was specified in step 2, use the same name when
configuring the corresponding arrays.
Verifying NaviSecCLI communication with CLARiiON enclosure
Use the following procedure to verify the communication of NaviSecCLI with the
CLARiiON enclosure.
102
Adding the asset infrastructure
Managing enclosure assets for an IMS
To verify that the NaviSecCLI can communicate with CLARiiON arrays
1
Enter the following command at the command prompt of CLARiiON
management host:
naviseccli -h arrayIPAddress -user userName -password
passWord -scope userScope networkadmin -get
Where:
arrayIPAddress is the IP address, the fully qualified domain name, or the name
of one of the storage processors in the array.
userName is a valid user name for the account in the array.
passWord is the password for userName.
userScope is the scope of the user that you specified when you created the
account in the array. It can be Local, Global, or LDAP.
2
Review the information that displays:
■
If NaviSecCLI can communicate with the arrays, the following information
is displayed:
Storage
Storage
Storage
Storage
Storage
Processor:
SP B
Processor Network Name:
cx500-2spb
Processor IP Address:
10.100.18.18
Processor Subnet Mask:
255.255.248.0
Processor Gateway Address: 10.100.16.1
If this command succeeds, the Management Server uses the credentials
to communicate with the array.
■
If NaviSecCLI cannot communicate with the array, the following information
is displayed:
Broken Pipe
Valid IP Address with Feature not installed:
naviseccli -h cx500a -user admin -password password -scope 0
networkadmin -get
Management Server - Feature software is not installed or the
command may have been typed incorrectly
usage:
metalun
migrate
connection
mirror
103
Adding the asset infrastructure
Managing enclosure assets for an IMS
snapview
analyzer
EMC VNX configuration prerequisites
Infrastructure Management Server (IMS) discovery can be performed on EMC VNX
(block) storage enclosures. You can specify the scope for VNX block as global
(value 0) or local (value 1) when you add the enclosure in the IMS.
Configuration steps for VNX block are similar to EMC CLARiiON.
See “EMC CLARiiON configuration prerequisites” on page 101.
3PAR configuration prerequisites
To discover 3PAR enclosure, ensure that the storage network connection between
the enclosure and the discovery host is properly configured. The discovery host
communicates directly with 3PAR enclosure using the IP address that is provided
on the Device Configuration panel. The discovery uses SSH communication.
Adding storage enclosures for discovery by the IMS
After adding Infrastructure Management Server (IMS), you add the asset
infrastructure. For array-based replication environments, the asset infrastructure
includes the storage enclosures. This does not apply for environments that are
using Hyper-V Replica.
To add storage enclosures for discovery
1
Prerequisites
Ensure that you have configured the storage array for discovery.
See “Configuration prerequisites for adding storage enclosures to an IMS”
on page 93.
Ensure that you have the name of the discovery host.
See “About the discovery host” on page 93.
2
Navigate
Settings (menu bar) > Infrastructure
You can also access this page from the Quick Actions menu.
3
Under the data center, locate the IMS and click Manage Asset Infrastructure.
104
Adding the asset infrastructure
Managing enclosure assets for an IMS
4
On the IMS Settings page, click Device to view information on existing
enclosures, then click Add Enclosure.
Or to go directly to the Add Enclosure wizard, click Add Enclosure in the
Settings page menu bar.
5
In the Add Enclosure wizard, select the vendor and the enclosure model.
Click Next.
See “Add Enclosure panel options for vendor and product selection” on page 105.
6
Specify the discovery details and click Next.
See “Add Enclosure panel options for configuration details” on page 106.
7
Choose the enclosures and enable the deep array discovery. Click Finish.
See “Add Enclosure panel options to enable or disable discovery for selected
enclosures” on page 110.
8
When the enclosure is successfully added, you can verify the information on
the Enclosure Configurations tab.
See “Managing enclosure assets for an IMS” on page 92.
Add Enclosure panel options for vendor and product
selection
Table 8-14
Add Enclosure panel for vendor and product selection
Field
Description
Enclosure Vendor
Select the enclosure vendor from the
drop-down list.
Select product with appropriate discovery method
Product
Select the array model for which you want to
enable the deep array discovery.
Discovery Method
Displays the discovery method that is used
for the discovery of the selected array model.
Additional Information
Provides the information about the discovered
objects, prerequisites, CLI version, and other
details about the enclosure discovery.
See “Adding storage enclosures for discovery by the IMS” on page 104.
105
Adding the asset infrastructure
Managing enclosure assets for an IMS
Add Enclosure panel options for configuration details
Use this wizard panel to specify the details of the devices and the server information
for adding the following enclosures for deep discovery.
Table 8-15 lists the options for EMC Symmetrix enclosures.
Table 8-16 lists the options for NetApp enclosures.
Table 8-17 lists the options for Hitachi enclosures.
Table 8-18 lists the options for EMC CLARiiON enclosures.
Table 8-19 lists the options for EMC VNX enclosures.
Table 8-20 lists the options for 3PAR enclosures.
Table 8-15
Add Enclosure panel options for EMC Symmetrix enclosure
Field
Description
Discovery Host
Enter the name of the discovery host. A host
that runs on Linux or Windows can be
designated as a discovery host. The
discovery host must be added as a host to
the IMS.
SYMAPI Server
Specify the SYMAPI Server name that is
configured on the discovery host to discover
the EMC Symmetrix enclosures. Use this
option if the discovery host does not have
visibility to gatekeeper devices for Symmetrix
enclosures.
SymCLI Location
Use Default
Choose this option if you have stored the
SymCLI binaries on the default location.
SymCLI must be functional to discover the
array details. Refer to the enclosure
configurations prerequisites section for more
details.
See “EMC Symmetrix configuration
prerequisites” on page 94.
Custom
Choose this option if you have stored the
SymCLI binaries on any other location. Enter
the path to the location in the field.
You must ensure that the SymCLI binaries
are available on the discovery host.
106
Adding the asset infrastructure
Managing enclosure assets for an IMS
Table 8-16
Add Enclosure panel options for NetApp enclosures
Field
Description
Discovery Host
Specify the name of the IMS.
NetApp Server
For NetApp 7 mode, enter the name or the
IP address.
NetApp Cluster
For NetApp cluster, enter the NetApp cluster
management interface name or the IP
address.
Port
Enter the port number.
Enter 80 for communicating over HTTP. For
communicating over HTTPS, enter 443.
Ensure the port that you specify here is
enabled on the enclosure.
Username
Enter the user name for the enclosure.
Password
Enter the password for the enclosure.
Table 8-17
Add Enclosure panel options for Hitachi enclosures
Field
Description
Discovery Host
Specify the name of the IMS.
HiCommand server
Enter the name of the HiCommand server.
Port
The port for the HiCommand server. The
default port number is 2001.
Username
Enter the user name for the HiCommand
server.
Password
Enter the password for the HiCommand
server.
Table 8-18
Discovery Host
Add Enclosure panel options for EMC CLARiiON enclosures
Enter the name of the discovery host. A host
that runs on Linux or Windows can be
designated as a discovery host. The
discovery host must be added as a host to
the IMS.
107
Adding the asset infrastructure
Managing enclosure assets for an IMS
Table 8-18
Add Enclosure panel options for EMC CLARiiON enclosures
(continued)
Storage Array Name/IP
Name or the IP address of the storage
enclosure.
Port
The port for communicating to the EMC
CLARiiON enclosure for getting the
information.
The default port number is 443.
Username
Enter the user name for the EMC CLARiiON
enclosure.
Password
Enter the password for the EMC CLARiiON
enclosure.
Scope
Specifies the type of the user account on the
storage system that you want to log on. The
available options are:
■
■
■
NAVISEC CLI Location
Global: Choose this option if your account
is effective throughout the domain. When
the administrator creates a global account,
the software copies the definition of this
account to the domain directory, which
makes it accessible on all storage systems
in the domain.
Local: Choose this option if your account
is effective only on the storage systems
for which the administrator creates the
account. Using the local account, you can
log on to only those storage systems on
which you have a local account.
LDAP: LDAP maps the user name and
the password entries to an external LDAP
or Active Directory server for
authentication. The user name and the
password pairs whose roles are not
mapped to the external directory are
denied access.
For authentication within the local security
directory, specify global or local scope.
The location of the NaviSecCLI binary in the
discovery host.
108
Adding the asset infrastructure
Managing enclosure assets for an IMS
Table 8-18
Add Enclosure panel options for EMC CLARiiON enclosures
(continued)
Use Default
Choose this option if you have stored the
NaviSecCLI binaries on the default location.
You must ensure that the NaviSecCLI
binaries are available on the discovery host.
Custom
Choose this option if you have stored the
NaviSecCLI binaries on any other location.
Enter the path to the location in the field.
You must ensure that the NaviSecCLI
binaries are available on the discovery host.
Use Secure Socket Layer
Select this check box to use the secure
socket layer for communicating to the
enclosure.
If you select this check box, you do not have
to enter the credentials again when you
perform deep discovery for the EMC
CLARiiON enclosures.
Table 8-19
Add Enclosure panel options for EMC VNX enclosure
Field
Description
Discovery Host
Enter the name of the managed host. A
managed host that runs on Linux or Windows
can be designated as a discovery host.
Control Station IP/Name
Ignore this field.
Block IP/Name:Scope
IP address or name and scope for VNX Block.
The IP address or name, and the scope must
be separated using colon.
For global scope, enter the value as 0.
For local scope, enter the value as 1.
User Name
Enter the user name for the enclosure.
Password
Enter the password for the enclosure.
CLI Location
Enter the Navisphere CLI location.
109
Adding the asset infrastructure
Managing enclosure assets for an IMS
Table 8-20
Add Enclosure panel options for 3PAR enclosure
Field
Description
Discovery Host
Enter the name of the managed host. A
managed host that runs on Linux or Windows
can be designated as a discovery host.
3PAR Enclosure IP/Name
Enter the name or the IP address for the
3PAR enclosure.
User Name
Enter the user name for the enclosure.
Password
Enter the password for the enclosure.
See “Adding storage enclosures for discovery by the IMS” on page 104.
Add Enclosure panel options to enable or disable
discovery for selected enclosures
Use this wizard panel to enable or disable deep discovery for selected enclosures.
Select the check box in the top row to select all the enclosures in the list. The check
box is selected by default.
For Discovery, choose Enable to perform the discovery; otherwise choose Disable.
Table 8-21
Add Enclosure panel to update the deep discovery information
for enclosures
Field
Description
Configuration Name
Enter a name for the deep discovery
operation that you want to perform.
Enclosures
Display Name
Displays the name of the enclosure.
Enclosure Vendor ID
Displays the ID that is generated for the
enclosure.
Serial
Displays the serial number of the enclosure.
Vendor
Displays manufacturer of the enclosure.
Model
Displays the enclosure model information.
Product
Displays the type of the enclosure.
110
Adding the asset infrastructure
Managing enclosure assets for an IMS
Table 8-21
Add Enclosure panel to update the deep discovery information
for enclosures (continued)
Field
Description
Connectivity
This field is displayed only for the EMC
Symmetrix enclosures. It indicates the
following:
■
■
Discovery
Local: Whether the enclosure is
connected to the host locally.
Remote: Whether the enclosure is
connected to another enclosure, using the
EMC Symmetrix Remote Data Facility
(SRDF), which might have been
connected to the host locally.
Choose Enable to perform the deep
discovery.
Choose Disable to disable the deep
discovery.
This field is not applicable for NetApp cluster
management interface.
Configured Name
If the enclosure was already added for deep
discovery, the configuration name that was
entered at that time is displayed in this field.
See “Adding storage enclosures for discovery by the IMS” on page 104.
Configuration prerequisites for adding replication appliances
For appliance based replication, you need to add the appliance to the Infrastructure
Management Server (IMS).
EMC RecoverPoint configuration prerequisites
For the Infrastructure Management Server (IMS) to discover EMC RecoverPoint
appliance, ensure that following prerequisites are met:
■
The IMS supports EMC RecoverPoint 4.1.
■
The discovery host should be able to communicate with RecoverPoint using
Secure Shell (SSH).
111
Adding the asset infrastructure
Managing enclosure assets for an IMS
Adding RecoverPoint appliance for replication
In Veritas Resiliency Platform console, you can add a RecoverPoint appliance to
provide continuous data protection with multiple recovery points to restore the
applications instantly to a specific point in time.
To add RecoverPoint appliance for replication
1
Prerequisites
Ensure that you have the name of the discovery host.
See “About the discovery host” on page 93.
2
Navigate
Settings (menu bar) > Infrastructure
You can also access this page from the Quick Actions menu.
3
Under the data center, click Details in Replication Appliances.
4
On the next page that displays the details of the replication appliances, click
Add.
5
In the Add RecoverPoint wizard, specify the details and click Next.
See “Add RecoverPoint panel options for configuration details for RecoverPoint”
on page 112.
6
Specify a name for the configuration. Click Finish.
7
When the appliance is successfully added, you can verify the information on
the Replication Appliances tab.
Add RecoverPoint panel options for configuration details
for RecoverPoint
Use this wizard panel to specify the details of the devices and the server information
for adding the RecoverPoint appliance for replicating a virtual machine.
Table 8-22
Add RecoverPoint panel options
Field
Description
Infrastructure Management Server
Specify the name of the Infrastructure
Management Server (IMS).
112
Adding the asset infrastructure
Managing enclosure assets for an IMS
Table 8-22
Add RecoverPoint panel options (continued)
Field
Description
Discovery Host Name
Enter the name of the discovery host. A host
that runs on Linux or Windows can be
designated as a discovery host. The
discovery host must be added as a host to
the IMS.
You can also designate your IMS as the
discovery host.
RecoverPoint Server
Enter the name of the RecoverPoint
appliance.
Username
Enter the user name for the RecoverPoint
appliance.
Password
Enter the password for the RecoverPoint
appliance.
See “Adding RecoverPoint appliance for replication” on page 112.
Editing the discovery configuration for an enclosure
You can edit details for enclosure configurations that were added previously to the
Infrastructure Management Server (IMS).
To edit the discovery configuration for an enclosure
1
Navigate
Settings (menu bar) > Infrastructure
2
Under the data center, locate the IMS and click Manage Asset Infrastructure.
3
On the IMS Settings page, click Device.
4
Expand Enclosures to locate the vendor.
5
In the vendor configurations list, right-click the enclosure and select Edit
Configuration.
113
Adding the asset infrastructure
Managing enclosure assets for an IMS
6
In the Edit Configuration wizard panel, edit the configuration details to change
the device discovery. Click Next.
Note: The configuration details are the same as when adding the enclosure.
See “Add Enclosure panel options for configuration details” on page 106.
7
In the next panel, select the check box for the enclosures for which you want
to perform the deep discovery configuration. Click Finish.
8
In the result panel review the information and click OK.
See “Managing enclosure assets for an IMS” on page 92.
Removing the discovery configuration for an enclosure
You can remove enclosure configurations that were added previously to the
Infrastructure Management Server (IMS).
To remove the discovery configuration for an enclosure
1
Navigate
Settings (menu bar) > Infrastructure
2
Under the data center, locate the IMS and click Manage Asset Infrastructure.
3
On the IMS Settings page, click Device.
4
Expand Enclosures to locate the vendor.
5
In the vendor configurations list, right-click the enclosure and select Remove
Configuration.
6
In the Unconfigure Device panel, click Yes.
See “Managing enclosure assets for an IMS” on page 92.
Refreshing enclosure discovery information for an IMS
You can submit a refresh request to update the information displayed on the table
of enclosures assets that have been added to the Infrastructure Management Server
(IMS).
114
Adding the asset infrastructure
Managing add-ons for the hosts
To refresh an enclosure configuration discovery
1
Navigate
Settings (menu bar) > Infrastructure
2
Under the data center, locate the IMS and clickManage Asset Infrastructure.
3
On the IMS Settings page, click Device and click the Enclosure
Configurations tab.
4
To refresh the configuration, right click and select Refresh Configuration. To
refresh an enclosure, right-click a configured enclosure and select Refresh
Enclosure.
5
Click OK.
Managing add-ons for the hosts
Infrastructure Management Server (IMS) installs a host package and the following
add-ons when you add hosts to the IMS.
■
Enablement add-on
■
Applications Enablement add-on
In some cases you may need to install add-ons manually. In addition, before
removing the host package from hosts, you must uninstall the add-ons.
See “Installing add-ons on the hosts” on page 115.
See “Uninstalling add-ons from the hosts” on page 117.
Installing add-ons on the hosts
You can install the add-ons on the hosts that are added to the Infrastructure
Management Server (IMS).
To install add-ons on the hosts
1
Navigate
Settings (menu bar) > Infrastructure
(Or, click Quick Actions (menu bar) > Add Assets)
2
Under the data center, locate the IMS and click Manage Assets.
115
Adding the asset infrastructure
Managing add-ons for the hosts
3
On the IMS Settings page, click Deployment.
4
Expand Add-ons to select the add-on that you want to install.
5
In the Add-ons tab, right-click the add-on, and select Install.
6
In the Install - Selects hosts wizard panel, select the hosts, and click Finish.
See “Install - Select hosts panel options for add-ons” on page 116.
7
In the Result panel, click Close
8
Those add-ons which require web server restart, click Restart Web server.
If installation of the Veritas Resiliency Platform Applications Enablement add-on
fails and an error message to run the cleanup script is displayed, you need to run
the following script on the managed host:
C:\ProgramData\Symantec\VRTSsfmh\spool\addons\store
\VRTSitrpappdr-1.0.0.0\CleanUp_Scripts\cleanup.bat
Install - Select hosts panel options for add-ons
Use this wizard panel to select the hosts on which you want to install the add-on.
You can do one of the following:
■
Select the hosts explicitly and install the add-on on the selected hosts.
■
Select the platform.
If you select a specific platform, the add-on is installed on all the hosts using that
platform. Also the add-on is installed on all the new hosts that are added to the IMS
in the future.
For example, if you select Windows, the add-on is installed on all the hosts that
use Windows platform. Also when a new Windows host is added to the IMS, the
add-on is installed on the host.
116
Adding the asset infrastructure
Managing add-ons for the hosts
Table 8-23
Select hosts panel options
Field
Description
Hosts
Select to view the list of all the hosts where
the add-on is not installed.
Select Show all applicable hosts
(Overwrites existing installation) to list all
the hosts on which you can install the add-on.
It includes:
■
■
Platform
Hosts on which the add-on is not installed
currently.
Hosts on which the add-on is installed
currently. In this case, the existing add-on
installation is overwritten.
Select to install the add-on on all the hosts
using the specific platform. This option is
useful for installing the add-on whenever a
new host using the specific platform is added
to the IMS.
Select Force install (Overwrites existing
installation) to overwrite existing add-on
installation on the hosts.
See “Installing add-ons on the hosts” on page 115.
Uninstalling add-ons from the hosts
You need to manually uninstall all the add-ons before you uninstall the host packages
from the Infrastructure Management Server (IMS).
Select Ignore checks (if any) before uninstalling if you want to remove all the
configurations of the add-on. For example, if vCenter is discovered using Control
Host add-on, then when you uninstall the add-on, the vCenter configuration is also
removed.
117
Adding the asset infrastructure
Managing solutions for the hosts
To uninstall add-ons from the hosts
1
Navigate
Settings (menu bar) > Infrastructure
(Or, click Quick Actions (menu bar) > Add Assets)
2
Under the data center, locate the IMS and click Manage Assets.
3
On the IMS Settings page, click Deployment.
4
Expand Add-ons to select the add-on that you want to uninstall.
5
In the Add-ons tab, right-click the add-on, and select Uninstall.
6
In the Uninstall panel, confirm the action of uninstalling the add-on from all
the hosts. Select Ignore checks (if any) before uninstalling to ignore the
checks before uninstalling.
7
Click Yes to uninstall the add-on from all the hosts.
If you try to uninstall the Veritas Resiliency Platform Applications Enablement
add-on using Windows Programs and Features, you are asked to reboot the system.
You can ignore this message.
If uninstallation of the Veritas Resiliency Platform Applications Enablement
add-on fails and an error message to run the cleanup script is displayed, you need
to run the following script on the managed host:
C:\ProgramData\Symantec\VRTSsfmh\spool\addons\store
\VRTSitrpappdr-1.0.0.0\CleanUp_Scripts\cleanup.bat
Managing solutions for the hosts
See “Installing a solution on the hosts” on page 118.
See “Uninstalling a solution from the hosts” on page 119.
Installing a solution on the hosts
Using the Resiliency Platform console, you can install a solution on the hosts that
are added to the Infrastructure Management Server (IMS).
118
Adding the asset infrastructure
Managing solutions for the hosts
To install a solution on the hosts
1
Navigate
Settings (menu bar) > Infrastructure
(Or, click Quick Actions (menu bar) > Add Assets)
2
Under the data center, locate the IMS and click Manage Assets.
3
On the IMS Settings page, click Deployment.
4
Expand and right-click the solution, click Install.
5
In the Install Select hosts wizard panel, select the hosts on which you want
to install the hot fix, package, or patch, and click Finish.
6
In the Result panel, click OK
Uninstalling a solution from the hosts
Using the Resiliency Platform console, you can uninstall a solution from the hosts.
To uninstall a solution from the hosts
1
Navigate
Settings (menu bar) > Infrastructure
(Or, click Quick Actions (menu bar) > Add Assets)
2
Under the data center, locate the IMS and click Manage Assets.
3
On the IMS Settings page, click Deployment.
4
Locate the solution, and right-click the solution that you want to uninstall, select
Uninstall.
5
In the Uninstall panel, review the information. If you want to uninstall the
solution from a specific host, select the host
Select Ignore checks (if any) before uninstalling to ignore the checks before
uninstalling. Click Yes.
See “Installing a solution on the hosts” on page 118.
119
Chapter
9
Managing users and
global settings
This chapter includes the following topics:
■
Managing licenses
■
Managing user authentication and permissions
■
Managing reports
■
Managing settings for alerts and notifications and general product settings
■
Enabling or disabling telemetry collection
Managing licenses
Using the Veritas Resiliency Platform console, you can install, view, and manage
the licenses. You can also view the report that provides details about the licenses
that are deployed for various Veritas Resiliency Platform solutions.
See “About licenses” on page 120.
See “Viewing and managing licenses” on page 121.
See “Viewing the License Entitlement report” on page 122.
About licenses
To create resiliency groups using virtual machines or applications, you need to
install a subscription license for Veritas Resiliency Platform. The license is provided
for a predefined number of virtual machines for a set duration of time. The license
for physical servers is provided for a predefined number of CPU cores for a set
Managing users and global settings
Managing licenses
duration of time. The extension of the license file is .slf. You can install the file using
the Resiliency Platform console.
During the initial setup, a demo license is made available. This demo license is
valid for 60 days, letting you evaluate the Resiliency Platform. Before the expiry
date, daily notifications are sent based on the warning period that is specified in
the license file. You need to purchase a subscription if you intend to use the
Resiliency Platform beyond the expiry date of the demo license.
After a subscription has expired, you can continue to perform operations on the
resiliency groups that are already created. However create new resiliency group
operation is disabled. Note that to be in compliance you are required to repurchase
the subscription to continue using Veritas Resiliency Platform.
See “Viewing and managing licenses” on page 121.
See “Viewing the License Entitlement report” on page 122.
Viewing and managing licenses
You can install and view the licenses using the Veritas Resiliency Platform console.
The extension of a license file is .slf.
You can view the following information about the installed licenses in a table:
■
Name: Name of the license.
■
Meter Type: Licenses for physical hosts are categorized under Per Core meter
type whereas licenses for virtual machines are categorized under Per Virtual
Machine meter type.
■
Type: Type of the license, demo or permanent.
■
Version: License version number.
■
Purchased Quantity: Number of meters purchased.
■
Start Date: The date on which the license is installed.
■
Expiry Date: Expiry date of the license.
■
Valid For (Days): Indicates the number of days the license is valid for.
To install a license
1
Navigate
Settings (menu bar) > Settings > Licenses
2
Click Browse to select the .slf file and click Install License.
See “About licenses” on page 120.
See “Viewing the License Entitlement report” on page 122.
121
Managing users and global settings
Managing user authentication and permissions
Viewing the License Entitlement report
This report provides details about the licenses that are deployed for various Veritas
Resiliency Platform solutions.
You can view the following information in the table for licenses deployed on physical
hosts and virtual machines:
■
Total number of subscriptions and expired subscriptions
■
Purchased, used, and available quantity
■
Number of unmanaged assets
In the Details table, you can view the additional information about all the licenses
deployed. Information such as the license type (demo or permanent), version,
purchased quantity, start and expiry date, and the status of the license.
To view the License Entitlement report
1
Navigation
Reports (menu bar) > Inventory Reports.
2
Click Run on the License Entitlement report to view the report in the HTML
format or save as a comma-separated (.csv) file.
Click Schedule on the License report to receive the report on the specified
email address.
See “About licenses” on page 120.
See “Viewing and managing licenses” on page 121.
Managing user authentication and permissions
Veritas Resiliency Platform provides a console for viewing information and
performing operations. Managing user authentication and permissions for the
console involves the following tasks.
Table 9-1
Task
Process for setting up user authentication and permissions
Details
Configure authentication domains You can add multiple authentication domains.
See “About user authentication in the web console”
on page 123.
See “Configuring authentication domains ” on page 128.
See “Unconfiguring authentication domains” on page 132.
122
Managing users and global settings
Managing user authentication and permissions
Table 9-1
Process for setting up user authentication and permissions
(continued)
Task
Details
Configure user groups and users
Once you configure an authentication domain, you can
configure user groups or users for Resiliency Platform
from that authentication domain.
See “Configuring user groups and users” on page 133.
Assign permissions to groups and When you configure user groups or users for Resiliency
users
Platform, they are by default assigned the Guest
persona, which gives permission to view information in
the web console.
Permission to perform operations in the console requires
assigning additional personas. For some personas, you
can also limit the scope of the operation to selected
objects, for example, resiliency groups.
See “About user permissions in the web console”
on page 124.
See “Predefined personas” on page 125.
See “About limiting object scope for personas”
on page 128.
See “Assigning permissions to user groups and users”
on page 134.
You can also create custom personas.
See “Adding custom personas” on page 136.
See “Predefined jobs that can be used for custom
personas” on page 137.
About user authentication in the web console
By default, the Admin user of the Veritas Resiliency Platform virtual appliance can
log in to the web console with access to all views and operations.
The Admin user can configure authentication domains from external identity
providers such as Active Directory (AD) and LDAP.
Once an authentication domain is configured, the Admin user can configure user
groups and users for Resiliency Platform from that domain. These users can log in
to the console with their domain login credentials.
123
Managing users and global settings
Managing user authentication and permissions
All users and groups that are configured for Resiliency Platform have permission
by default to view everything in the web console but not to perform any operations.
Permissions for operations must be assigned separately by assigning the appropriate
personas to users and groups.
See “Managing user authentication and permissions” on page 122.
About user permissions in the web console
Veritas Resiliency Platform uses the concepts of personas, job, and objects to
define permissions for users in the web console.
Persona
A role that has access to a predefined set of jobs (operations).
The product comes with a set of predefined personas.
See “Predefined personas” on page 125.
You can also add custom personas.
See “Adding custom personas” on page 136.
See “Predefined jobs that can be used for custom personas”
on page 137.
All users and groups that are added to Resiliency Platform
have the Guest persona by default. The Guest persona allows
users to view everything in the web console but not to perform
any operations.
Job
A type of task (operation) that a user can perform.
Examples:
Manage resiliency groups
Manage assets
Perform disaster recovery of resiliency groups
Object types and scope
Each job can be performed on certain types of Resiliency
Platform objects. Types of objects include data centers,
resiliency groups, and virtual business services.
See “About Resiliency Platform features and components”
on page 14.
When you assign a persona to a user or group, you define
the scope of some jobs by selecting from available objects.
For some jobs, the scope is the resiliency domain, which
would be the entire scope of the product deployment.
124
Managing users and global settings
Managing user authentication and permissions
If you want a user to have permissions that are different from the user group to
which they belong, you must add the user individually to Resiliency Platform.
Permissions assigned at the individual user level override the permissions that the
user has as a user group member.
If a user tries to perform an operation for which they do not have authorization, a
message is displayed to notify them of the fact; in addition an entry for "authorization
check failed" is available in the audit logs.
See “Managing user authentication and permissions” on page 122.
Predefined personas
The following table lists the predefined personas for Veritas Resiliency Platform
and their associated jobs and objects. You can assign one or more of these personas
to a user or user group to define permissions. Some jobs let you limit the scope by
specifying the assets (resiliency groups) on which permissions are assigned.
You can also create custom versions of these personas, except for the Guest and
Super admin persona.
Table 9-2
Predefined personas and jobs
Persona
Description and scope
Super admin
Can perform all operations on All jobs
all objects in resiliency
All objects in resiliency
domain.
domain
Resiliency Platform admin
Manage Resiliency Managers Manage assets
and Infrastructure
Manage user security settings
Management Servers (IMSs)
Manage product settings
and data centers.
Manage assets for the IMS.
Jobs
Manage product updates
Manage user security settings Manage server deployments
and other product settings.
Manage product updates.
Scope: Resiliency domain.
125
Managing users and global settings
Managing user authentication and permissions
Table 9-2
Predefined personas and jobs (continued)
Persona
Description and scope
Jobs
Resiliency Platform
Deployment admin
Manage Resiliency Managers Manage product updates
and Infrastructure
Manage server deployments
Management Servers (IMSs).
Can add an IMS to an
existing data center.
Manage product updates.
Scope: Resiliency domain.
Resiliency Domain admin
Create, update, and delete
resiliency groups, virtual
business services (VBSs),
and resiliency plans and
templates.
Manage resiliency groups
Start/stop resiliency groups
Manage virtual business
service (VBSs)
Start/stop all resiliency groups Manage resiliency plan
templates
and VBSs.
Scope: Resiliency domain.
Manage resiliency plans
Execute custom script
VBS admin
Create, update, and delete all Manage virtual business
virtual business services
services (VBSs)
(VBSs).
Start/stop resiliency groups
Start/stop all resiliency groups
and VBSs.
Scope: Resiliency domain.
DR admin
Configure all resiliency
groups for disaster recovery
(DR).
Manage disaster recovery of
resiliency groups
Perform disaster recovery of
Perform DR operations:
resiliency groups
migrate, takeover, rehearsal.
Manage resiliency plans
Create, update, and delete
Manage resiliency plan
resiliency plans and
templates
templates.
Manage disaster recovery
Manage disaster recovery
network settings
network settings.
Start/stop resiliency groups
Start/stop all resiliency
groups.
Scope: Resiliency domain.
126
Managing users and global settings
Managing user authentication and permissions
Table 9-2
Predefined personas and jobs (continued)
Persona
Description and scope
Jobs
Resiliency Group DR admin
Manage and perform disaster Start/stop resiliency groups
recovery of resiliency groups
Manage disaster recovery of
Start/stop specified resiliency resiliency groups
groups.
Perform disaster recovery of
Start/stop or perform DR
resiliency groups
operations on VBSs as long
as the VBS contains only the
specified resiliency groups.
Scope: Specified resiliency
groups.
Resiliency Group DR operator Start/stop specified resiliency Start/stop resiliency groups
groups.
Perform disaster recovery of
Perform disaster recovery on resiliency groups
specified resiliency groups.
Start/stop or perform DR
operations on VBSs as long
as the VBS contains only the
specified resiliency groups.
Scope: Specified resiliency
groups.
Resiliency Group admin
Update and delete specified
resiliency groups.
Manage resiliency groups
Start/stop resiliency groups
Start/stop specified resiliency
groups.
Start/stop VBSs as long as
the VBS contains only the
specified resiliency groups.
Scope: Specified resiliency
groups.
Resiliency Group operator
Start/stop specified resiliency Start/stop resiliency groups
groups.
Start/stop VBSs as long as
the VBS contains only the
specified resiliency groups.
Scope: Specified resiliency
groups.
127
Managing users and global settings
Managing user authentication and permissions
Table 9-2
Predefined personas and jobs (continued)
Persona
Description and scope
Jobs
Guest
View all information in
console.
No operations, only view
permission
Assigned by default when
user or group is configured
for Resiliency Platform.
See “Managing user authentication and permissions” on page 122.
About limiting object scope for personas
For some personas, Veritas Resiliency Platform lets you select a subset of objects
such as resiliency groups to limit the scope of operations.
See “Predefined personas” on page 125.
For example, you can assign one user the permission to perform operations on
resiliency group RG1 and assign another user the permission to perform operations
on RG2.
When planning persona assignments in which you select objects to limit the scope,
take the following into account:
■
Before you can select the objects such as resiliency groups to limit the scope
of operations for a persona, the objects must first be created in Resiliency
Platform.
■
You need to plan for future maintenance on such limited scope personas. If
more objects of that type are added later, you may need to edit existing personas
for users or user groups in order to add permissions for the new objects.
■
Keep in mind that operations on virtual business services (VBSs) that include
multiple resiliency groups will fail unless the user performing the operation has
permission for operations on all the resiliency groups in the VBS.
The same limitation applies for workflow or resiliency plan operations that include
multiple resiliency groups.
For example: a VBS is composed of RG1 and RG2. The operator has permission
to perform operations on RG1 but not RG2. If they try to perform operations on
the VBS, the operation will fail.
Configuring authentication domains
By default, the Admin user on the Veritas Resiliency Platform virtual appliance can
log in to the Resiliency Platform web console with access to all views and operations.
128
Managing users and global settings
Managing user authentication and permissions
The Admin user can configure authentication domains for Resiliency Platform from
external identity providers so that other users can be authenticated for access to
the console.
To configure authentication domains
To edit authentication domains
To configure authentication domains
1
Prerequisites
The fully qualified domain name (FQDN) or IP address and credentials for the
LDAP/AD servers in the authentication domain
2
Navigate
Settings (menu bar)
Under Product Settings, click User Management > Domains
Note: You can also configure an authentication domain from the Getting Started
wizard after setting up the Resiliency Manager and resiliency domain.
3
Click Configure Domain.
4
Select a data center and under Specify server information for each data
center, enter the information for the server at that data center.
Repeat this step for other data centers in the authentication domain. When
you select a different data center, the server information fields are cleared so
that you can enter information for a different server, but the entries for the
previous data center are remembered.
Note: If the same server is used for more than one data center, enter the same
server information for each data center.
The remaining fields on the page apply to all data centers; fill these in as
required.
See “Options for authentication domain configuration ” on page 130.
Once you have entered information for all data centers, click Next.
129
Managing users and global settings
Managing user authentication and permissions
5
Verify and complete the configuration:
In the Domain Name field, enter a friendly name for the authentication domain.
If you configure the login screen to list domains, this name is listed.
Verify that the applicable data centers are listed. To make any changes, click
Back to return to the previous screen. Once all is complete, click Submit.
6
Verify that the new domain is listed under Domains.
You can now configure user groups and users from that domain and assign
permissions.
To edit authentication domains
1
Navigate to the domain list as described in the procedure to configure
authentication domains.
2
Select the authentication domain you want to edit and select the Edit option.
Note the following guidelines when editing:
■
To add server information for a new data center, select the applicable data
center and fill in the server information.
■
To edit existing server information, select the applicable data center.
■
To edit other information, you do not need to select each data center; the
same information applies to all.
■
If a data center no longer uses a separate server, replace the server
information for that data center with the information for the server that is
being used.
■
To remove a data center from the authentication domain, use the
Unconfigure option instead of the Edit option.
See “Unconfiguring authentication domains” on page 132.
See “Managing user authentication and permissions” on page 122.
Options for authentication domain configuration
The first page of the authentication domain configuration wizard is divided into 2
areas.
Server information by data center
Configuration options applicable to all data centers
Server information by data center
You must specify the server information separately for each data center. When you
select a different data center the server information fields clear so you can enter
130
Managing users and global settings
Managing user authentication and permissions
the new information. If the same server is used for multiple data centers, enter the
same information for both data centers.
Table 9-3
Server information by data center
Option
Description
Server
Enter the fully-qualified host name or IP address of the LDAP
server. If a secure session is configured with the LDAP server
using SSL certificates, you must enter the fully-qualified host
name that matches with the fully-qualified host name in the
LDAP server certificate.
(Mandatory)
Port
Displays the number of the port on which the LDAP server
is configured to run. By default, this field displays the port
number as 389. You can edit this port number, if required.
(Mandatory)
Connect using SSL/TLS
Select this check box to use the Secure Sockets Layer (SSL)
or Transport Layer Security (TLS) certificates to establish a
secure channel between the authentication broker and the
LDAP server.
Certificate
Browse to the location of the trusted root CA certificate of the
vendor that issued the LDAP server certificate.
Configuration options applicable to all data centers
The remaining fields apply to all data centers; fill these in as required.
Table 9-4
Configuration options applicable to all data centers
Option
Description
The authentication servers
require me to log on.
Select this check box if the anonymous operations are
disabled on the LDAP server and a bind user ID is required
to proceed with configuring the LDAP-based authentication
131
Managing users and global settings
Managing user authentication and permissions
Table 9-4
Configuration options applicable to all data centers (continued)
Option
Description
Bind User Name/DN
Enter the complete Distinguished Name (DN) of the user that
is used to bind to the LDAP server.
If the LDAP server being used is Active Directory (AD), you
can provide the DN in the following formats:
[email protected] or domainname\username
For example, you can provide the DN as
[email protected]
ENTERPRISE\Administrator
For RFC 2307 compliant LDAP servers, specify complete
bind DN.
For example, cn=Manager,dc=vss,dc=veritas,dc=com
The LDAP or the AD administrator can provide you the bind
user name that you can use.
Password
Enter the password that is assigned to the bind user name
that you use.
Query Information:
User
(Mandatory)
Under Query Information, enter the user name based on
which the system detects the LDAP server-related settings.
Ensure that the user name does not contain any special
characters.
The system determines the search base based on the user
name that you specify in this field.
Group
Enter the name of the user group based on which the system
detects the LDAP server-related settings. Ensure that the
group name does not contain any special characters.
The system determines the search base based on the group
name along with the user name that you have specified.
See “Configuring authentication domains ” on page 128.
See “Getting started with a new Resiliency Platform configuration” on page 37.
Unconfiguring authentication domains
If an authentication domain is no longer applicable for a data center you can
unconfigure it (remove it from Resiliency Platform).
132
Managing users and global settings
Managing user authentication and permissions
Warning: Any users or user groups that you added from that domain are also
removed from Resiliency Platform when you unconfigure an authentication domain.
To unconfigure an authentication domain
1
Navigate
Settings (menu bar)
Under Product Settings, click User Management > Domains
2
Right-click the domain and select Unconfigure.
3
Select the data center. If you select all data centers, any users or user groups
that you added from that domain are removed from Resiliency Platform. Click
Submit.
4
Verify that the domain is removed under Domains.
See “Managing user authentication and permissions” on page 122.
Showing domains on login screen
You can set up the login screen to list the available authentication domains. By
default, the domains list is not shown and the user must enter a fully qualified
username, for example, [email protected] or domain\username.
To show domains on login
1
Navigate
Settings (menu bar)
Under General Settings, click General
2
Under Login Settings, select Show domains list and save the setting.
Configuring user groups and users
After you configure an authentication domain for Veritas Resiliency Platform, you
can configure user groups and users for Resiliency Platform from that domain.
If you want to assign permissions to a user that are different from the user group
as a whole, you must configure the user separately from the group.
133
Managing users and global settings
Managing user authentication and permissions
To configure user groups and users
1
Prerequisites
The names of the user groups or users that you want to configure, as configured
in the authentication domain.
2
Navigate
Settings (menu bar)
Under Product Settings, click User Management > Users & Groups
Note: To edit or remove an existing user or group, right-click the name in the
list and select the appropriate option.
3
Click Configure User or Group.
4
Select the authentication domain.
5
Type the name of the user group or user. Click Verify so that the wizard can
verify the name in the domain.
6
Click Submit and verify that the group or user is listed under Users & Groups.
All groups and users that are added have the default persona of Guest. You
can add other permissions.
See “Assigning permissions to user groups and users” on page 134.
See “Managing user authentication and permissions” on page 122.
Assigning permissions to user groups and users
In Veritas Resiliency Platform, permissions use the concept of personas and jobs.
When you first add user groups and users to Resiliency Platform, they are assigned
the Guest persona, which allows views but no operations. You can assign other
permissions. For each persona, there is a set of jobs (operations) and for some
jobs, you select objects.
See “About user permissions in the web console” on page 124.
134
Managing users and global settings
Managing user authentication and permissions
To assign permissions to user groups and users
1
Prerequisites
The users and groups must be added to Resiliency Platform before you can
assign personas.
See “Configuring user groups and users” on page 133.'
2
Navigate
Settings (menu bar)
Under Product Settings, click User Management > Users & Groups
3
Double-click the user group or user.
4
Click Assign Persona.
5
In the Assign Persona page, you can assign one persona at a time. Complete
the following steps:
6
■
Select a persona that you want to assign to that user group or user.
■
Verify that you want to assign the jobs that are listed for that persona.
■
Under Objects, view the available objects on which jobs can be performed.
To assign permission to selected objects, drag them from the left grid to
the left grid. If there are multiple object types, they are listed on separate
tabs. Click any remaining tab and select the objects.
■
Click Submit.
Verify that the correct persona name and associated objects are listed on the
user details page.
To edit permissions or unassign personas
1
Navigate
Settings (menu bar)
Under Product Settings, click User Management > Users & Groups
2
Double-click the user or group.
3
On the details page for the user or group, right-click the persona that you want
to unassign or edit, and select the appropriate option.
See “Managing user authentication and permissions” on page 122.
135
Managing users and global settings
Managing user authentication and permissions
Adding custom personas
Veritas Resiliency Platform provides a set of predefined personas with access to
predefined jobs.
You can add custom personas by selecting from the predefined jobs.
For example, the predefined persona Resiliency Platform Admin includes the jobs
for managing assets, managing security settings, and managing product settings.
You could create an "Asset Manager" persona that includes only the managing
assets job.
You cannot customize the Super admin persona, which has access to all jobs and
all objects in the resiliency domain. You also cannot customize the Guest persona,
which can view all information in the console.
To add custom personas
1
Navigate
Settings (menu bar)
Under Product Settings, click User Management > Persona & Jobs > Add
Persona
2
3
In the Add Persona page, complete the following steps and submit:
■
Assign a name and description to the custom persona.
■
Select one or more jobs that you want to assign to the persona. The jobs
are shown in categories depending on whether the scope is the entire
resiliency domain or whether the scope can be customized to specific data
centers or assets. Select the job from the appropriate category.
For example, if you want to assign a permission related to managing any
resiliency group in the resiliency domain, select Manage Resiliency Group
under the category of For entire Resiliency Domain. But if you want to
limit permissions to specific resiliency groups, select Manage Resiliency
Group under the category For specific resiliency groups.
See “Predefined jobs that can be used for custom personas” on page 137.
Verify that the correct persona name and associated jobs are listed.
You can now assign this persona to users or user groups.
See “Managing user authentication and permissions” on page 122.
136
Managing users and global settings
Managing user authentication and permissions
Predefined jobs that can be used for custom personas
The following table lists the predefined jobs that you can use to create custom
personas for Veritas Resiliency Platform. The jobs are categorized as to whether
they provide permissions for the entire resiliency domain or can be customized to
specific data centers or assets.
Table 9-5
Jobs for custom personas
Job
Description
Scope
View all information
View all information in
console.
Resiliency domain
Manage assets
Add assets to the IMS,
remove assets that were
added previously.
Resiliency domain or specific
data centers
Manage user security settings Manage authentication
domains, users and user
groups, personas.
Resiliency domain
Manage product settings
Resiliency domain
Manage general product
settings such as alerts and
notifications.
Manage server deployments Edit Resiliency Manager
information.
Resiliency domain
Join a Resiliency Manager to
a domain or leave a domain.
Manage IMSs, including add,
remove, edit, reconnect
operations.
Manage product updates
Perform the operations
Resiliency domain
available from the Product
Updates page of the console.
Manage resiliency groups
Create, update, and delete
resiliency groups.
Resiliency domain or specific
resiliency groups
Start/stop resiliency groups
Start/stop resiliency groups.
Resiliency domain or specific
resiliency groups
Manage virtual business
services (VBSs)
Create, update, and delete
virtual business services
(VBSs).
Resiliency domain or specific
VBSs
137
Managing users and global settings
Managing user authentication and permissions
Table 9-5
Jobs for custom personas (continued)
Job
Description
Scope
Manage resiliency plans
Create, update, and delete
resiliency plans.
Resiliency domain
Note: The permission to
execute a resiliency plan
depends on a cumulative
check on permissions for
individual resiliency groups
and VBSs in the plan.
See “About limiting object
scope for personas”
on page 128.
Manage resiliency plan
templates
Create, update, and delete
resiliency plan templates.
Resiliency domain
Execute custom script
Execute custom scripts as
part of resiliency plans.
Resiliency domain or specific
data centers
Manage disaster recovery of Configure resiliency groups
resiliency groups
for disaster recovery (DR).
Resiliency domain or specific
resiliency groups
Perform disaster recovery of Perform DR operations:
resiliency groups
migrate, takeover, rehearsal
Resiliency domain or specific
resiliency groups
Note: There is no separate
job to perform disaster
recovery of VBSs. If the
assigned scope of this job
includes all the resiliency
groups in a VBS, DR
operations can be performed
on that VBS.
See “About limiting object
scope for personas”
on page 128.
Manage disaster recovery
(DR) network settings
Configure disaster recovery Resiliency domain
network settings, for example,
mapping network settings for
disaster recovery.
See “Predefined personas” on page 125.
See “Adding custom personas” on page 136.
138
Managing users and global settings
Managing reports
Managing reports
Using the Veritas Resiliency Platform console you can view and generate various
reports. You can schedule periodic email updates.
See “About reports” on page 139.
See “Managing report preferences” on page 139.
See “Scheduling a report” on page 142.
See “Running a report” on page 144.
See “Viewing and managing report schedules” on page 145.
About reports
Using the Veritas Resiliency Platform console, you can generate a variety of reports.
The following are the broad categories under which the reports are grouped:
■
Inventory: Reports in this category provide information about the data centers
and applications, and the virtual machines that are deployed in the data centers.
■
Recovery Assessment: This category lists the reports that are related to the
disaster recovery operations such as the migrate and take over report, and the
rehearsal report.
■
Risk: This category has two reports; Current Risk and Risk History. These
reports show the summary and details of all the current and historical risks that
occurred in the environment.
Reports can be scoped on the data center or global. You can subscribe for a report
on a daily, weekly, monthly, quarterly, or yearly basis, or on predefined days of the
week, or run on demand. Reports are available in the HTML and PDF format, or
as a comma-separated file (CSV) file.
You can send a report to multiple recipients by entering the email addresses
separated by a comma (,) or a semicolon (;).
See “Managing report preferences” on page 139.
See “Scheduling a report” on page 142.
See “Running a report” on page 144.
Managing report preferences
Using the Veritas Resiliency Platform console, you can create, update, and view
your preferences for generating and receiving reports.
139
Managing users and global settings
Managing reports
To create report preferences
1
Navigate
Reports (menu bar) > Settings.
2
3
In the Report preferences wizard panel, specify the following information and
click Save.
Scope
Select the scope of the report such as
Global or specific data center.
From and To
Select the duration for which you want to
receive the report.
Format
Select the delivery format as HTML or
CSV.
Email
Enter an email address at which you want
to send the report.
You can enter multiple email addresses
that are separated by a comma (,) or a
semicolon (;).
140
Managing users and global settings
Managing reports
Frequency
Select the start and the end date and the
time at which you want to generate and
receive the report.
Select Daily to generate the report on a
daily basis.
Select Weekly to avail the following
options:
■
■
Select Every Weekday to receive the
report on all week days.
Select Recur every week on and
select one or more week days on which
you want to receive the report.
Select Monthly to avail the following
options:
■
■
■
Set the monthly recurrence. For
example every one month, or every 3
months.
Select the day of the month on which
you want to receive the report.
Or select every weekday of the month
on which you want to receive the report.
For example every first Monday of the
month or every fourth Saturday of the
month.
Select Yearly to avail the following options:
■
■
■
Set the yearly recurrence. For example
every one year, or every 3 years.
Select the day of the month on which
you want to receive the report.
Or select every weekday of a month on
which you want to receive the report.
For example every first Monday of
January or every fourth Saturday of
April.
Select Once to generate the report only
one time.
See “Scheduling a report” on page 142.
See “Running a report” on page 144.
141
Managing users and global settings
Managing reports
Scheduling a report
Using the Veritas Resiliency Platform console, you can update the report generation
schedule for a selected report. The schedule that is defined in the template is then
overwritten. You can also enable or disable the report schedule.
To schedule a report
1
Navigate
Reports (menu bar), and expand the report category.
2
In the report row, click on Schedule.
3
In the Schedule Report wizard panel, specify the following information and
click Schedule.
4
Name
Enter a name for the report schedule. Only
special character under score (_) is
allowed.
Description
Enter a description for the report schedule.
142
Managing users and global settings
Managing reports
Frequency
Select the start and the end date and the
time at which you want to generate and
receive the report.
Select Daily to generate the report on a
daily basis.
Select Weekly to avail the following
options:
■
■
Select Every Weekday to receive the
report on all week days.
Select Recur every week on and
select one or more week days on which
you want to receive the report.
Select Monthly to avail the following
options:
■
■
■
Set the monthly recurrence. For
example every one month, or every 3
months.
Select the day of the month on which
you want to receive the report.
Or select every weekday of the month
on which you want to receive the report.
For example every first Monday of the
month or every fourth Saturday of the
month.
Select Yearly to avail the following options:
■
■
■
Set the yearly recurrence. For example
every one year, or every 3 years.
Select the day of the month on which
you want to receive the report.
Or select every weekday of a month on
which you want to receive the report.
For example every first Monday of
January or every fourth Saturday of
April.
Select Once to generate the report only
one time.
Scope
Select the scope of the report such as
Global or specific data center.
From and To
Select the duration for which you want to
generate the report.
143
Managing users and global settings
Managing reports
Format
Select the delivery format as HTML or
CSV.
Email
Enter an email address at which you want
to send the report.
You can enter multiple email addresses
that are separated by a comma (,) or
semicolon (;).
See “Managing report preferences” on page 139.
See “Running a report” on page 144.
Running a report
On the Veritas Resiliency Platform console, you can run a report on demand. The
report is generated and sent to the specified email address. To view the generated
report in the browser, do one of the following:
■
Click on the report notification.
■
Click Saved to expand the table, and then double-click on the saved report row.
■
Click Saved to expand the table, click on the Action menu, and then click View.
144
Managing users and global settings
Managing reports
To run a report
1
Navigate
Reports (menu bar).
Click Inventory Reports or Risk Assessment Reports.
2
Click Run on the desired report, specify the following information in the wizard
panel, and click Run.
Scope
Select the scope of the report such as
Global or specific data center.
From and To
Select the duration for which you want to
generate the report.
Format
Select the delivery format as HTML or
CSV.
Email
Enter an email address at which you want
to send the report.
You can enter multiple email addresses
that are separated by a comma (,) or
semicolon (;).
See “Scheduling a report” on page 142.
Viewing and managing report schedules
You can use the Resiliency Platform console to view the details of all the reports
and manage the report schedules. You can view a brief description about the report
along with the following information:
■
Number of times the report is saved.
■
Number of times the report is scheduled to run.
■
Number of currently running instances of the report.
When a currently running instance of a report is complete, the number of saved
report count increases by one and the number of currently running instances count
decreases by one.
In each report row you can do the following:
145
Managing users and global settings
Managing reports
Saved
Click to view additional details such as the
generation time, format, status, scope, and
user information of all the saved instances of
the report.
Double-click on a saved report row to view
the report.
Click on the vertical ellipses to view or remove
the report.
Saved reports are purged depending on the
number of days defined in the Reports
Retention Policy Settings.
Schedules
Click to view the report generation schedules
such as the format, recipient email address,
recurrence, and whether the report is enabled
or disabled.
Click on the Actions column to enable,
disable, update, or delete the report schedule.
Running
Click to view the format, scope, and user
information.
You can abort the generation process.
Run
Click to run the report on demand.
Schedule
Click to update the report generation
schedule.
Last Run
Displays the last run date and time of the
report.
To view reports
◆
Navigate
Reports (menu bar)
Expand Inventory Reports or Risk Assessment Reports to view details of
all the reports.
See “Managing report preferences” on page 139.
See “Scheduling a report” on page 142.
See “Running a report” on page 144.
146
Managing users and global settings
Managing settings for alerts and notifications and general product settings
Managing settings for alerts and notifications and
general product settings
See the following topics for information on configuring email and SNMP settings
for notifications and reports, setting up rules for event notifications, and configuring
purge settings for logs and traps, and some general product settings.
See “Adding, modifying, or deleting email settings” on page 147.
See “Adding, modifying, or deleting SNMP settings” on page 149.
See “Setting up rules for event notifications” on page 149.
See “Modifying purge settings for logs and SNMP traps” on page 150.
See “Enabling or disabling telemetry collection ” on page 151.
Adding, modifying, or deleting email settings
You can configure email settings to be used for different features, such as sending
reports or receiving automatic email notifications of events. Veritas Resiliency
Platform manages email notifications via Resiliency Managers. When Resiliency
Managers are located in different geographical locations, the required email settings
are likely different for each location. In that case, you add a separate email
configuration for each location. You can send a test email to verify the settings. You
can also modify or delete existing email configurations.
147
Managing users and global settings
Managing settings for alerts and notifications and general product settings
To add, modify, or delete email settings
1
Navigate
Settings (menu bar)
Under Product Settings, select Alerts & Notifications > Email
To add a new email configuration, select Add Email Configuration.
To modify or delete an existing one, right-click it and select Modify or Delete.
2
To add or modify an email configuration, go through the wizard pages and
specify the options.
In Server Information, specify the following:
Name
Assign a unique name for the email configuration.
Email Server
Valid formats include: Fully Qualified Domain Name
(FQDN), IP address, or, if the network handles
DNS resolution for host names, a shortened host
name. Examples: Host123, Host123.example.com,
xxx.yyy.zzz.aaa.
SMTP Port
Enter the SMTP mail server port number. The
default is 25.
From Email Address
Enter the email address to be shown as the sender
of all the emails that are sent.
Friendly Email Name
Optionally, enter a name to be shown for the From
address.
3
In Security, if you want to implement secure SMTP, select the checkbox and
enter the user name and password.
4
In Select Resiliency Managers, select a Resiliency Manager in the data center
location where these email settings apply.
5
In Test Email Settings, enter a valid email address, and enter a subject and
message for the test email. Click Send Test Email to test your settings.
6
Review the information in the summary and submit
See “Managing settings for alerts and notifications and general product settings”
on page 147.
148
Managing users and global settings
Managing settings for alerts and notifications and general product settings
Adding, modifying, or deleting SNMP settings
When an event takes place, you can configure SNMP traps to be sent. You can
configure the SNMP settings in the web console.
To add, modify, or delete SNMP settings
1
Navigate
Settings (menu bar)
Under Product Settings, select Alerts & Notifications > SNMP
To add a new SNMP configuration, select Add SNMP Configuration.
To modify or delete an existing one, right-click it and select Modify or Delete.
2
To add or modify SNMP settings, specify the following:
Name
Assign a friendly name.
SNMP Server
Enter the IP Address or name of the host
where the SNMP trap console is located.
Example: Host123.example.com
SNMP Port
Enter the SNMP port number. The default
port for the trap is 162.
See “Managing settings for alerts and notifications and general product settings”
on page 147.
Setting up rules for event notifications
Logs of the type information, warning, or error generate an event. You can view
Veritas Resiliency Platform event logs in the web console and set up rules for
receiving notifications of events. You can also modify or delete existing rules.
149
Managing users and global settings
Managing settings for alerts and notifications and general product settings
To set up rules for event notifications
1
Prerequisite
Configure the email server for sending notifications. Optionally you can also
configure SNMP.
See “Adding, modifying, or deleting email settings” on page 147.
See “Adding, modifying, or deleting SNMP settings” on page 149.
2
Navigate
Settings (menu bar)
Under Product Settings, select Alerts & Notifications
To add a new rule: Click the Definition tab > New Rule.
To modify or delete an existing rule: Click the Rules tab, right-click the rule,
and select Modify or Delete.
3
4
In Configure Rule, enter or modify the following:
Name
Enter a unique name for this rule.
Send emails to
Enter one or more email addresses
separated by a comma
Send SNMP traps to
Optional
Select Events
Select one or more events that you want
to be notified about
Click Submit.
The rule is listed on the Rules tab.
Modifying purge settings for logs and SNMP traps
By default, logs and SNMP traps are retained for two years. You can modify this
purge setting.
150
Managing users and global settings
Enabling or disabling telemetry collection
To modify the purge setting for logs and SNMP traps
1
Navigate
Settings (menu bar)
Under General Settings, click General
2
Under Logs, enter the new value for the purge settings, in months.
3
Click Save.
See “Managing settings for alerts and notifications and general product settings”
on page 147.
Enabling or disabling telemetry collection
Veritas Resiliency Platform can collect usage information via telemetry for the
purpose of future product enhancements. You can enable or disable the collection.
The types of telemetry information collected include configuration information, mainly
inventory counts, and license information.
For example, information can include number of configured authentication domains,
resiliency plans and templates, virtual business services, virtual machines by platform
and virtualization technology, virtualization servers by type, resiliency groups by
replication type, distribution of hosts over physical and virtual, enclosures by type,
virtual machines and applications enabled or not enabled for disaster recovery.
You can view a file showing the collected information.
Telemetry collection requires that the Resiliency Manager have internet connectivity.
To enable or disable telemetry collection
1
Navigate
Settings (menu bar)
Under General Settings, click General
2
Under Telemetry, select the setting to turn it on or off. To download a file
showing the information that is collected, click Show what is collected.
151
Chapter
10
Updating Resiliency
Platform
This chapter includes the following topics:
■
About updating Resiliency Platform
■
About applying updates to Resiliency Platform
■
Prerequisites for a repository server
■
Setting up the repository server and downloading updates
■
Adding a repository server in Resiliency Platform
■
Assigning a repository server in Resiliency Platform
■
Applying updates to virtual appliances using the console
■
Applying updates to virtual appliance using CLISH menu
■
Refreshing the information about applicable updates
■
Removing an update from the repository server
About updating Resiliency Platform
This chapter covers common aspects of updating a Resiliency Platform deployment.
The topics in this chapter cover the process of applying updates (patches and
maintenance release) to the virtual appliance, add-ons, and host packages.
Note: Upgrade from Resiliency Platform 1.1 to 1.2 is not supported.
Updating Resiliency Platform
About applying updates to Resiliency Platform
About applying updates to Resiliency Platform
Updates to Veritas Resiliency Platform provide significant benefits, such as improved
functionality, performance, security, and reliability.
In Veritas Resiliency Platform, you can apply updates to the following:
■
Veritas Resiliency Platform virtual appliance
■
Veritas Resiliency Platform add-ons
■
Host packages on the assets that are added to the Infrastructure Management
Server (IMS) as a host
For applying updates to Resiliency Platform, you need to set up a repository server
and download the updates to the repository server. Then, you assign the repository
server to the Resiliency Platform virtual appliance, where you want to apply the
update. You can apply the updates using the web console or using the CLISH menu.
It is recommended to take a snapshot of the appliance before applying the updates.
The following figure shows how a repository server is used to apply the updates to
Resiliency Platform:
Note: While applying updates, ensure that the virtual appliance remains powered
on. Restarting the appliance during the process of applying updates may adversely
affect the functionality. In case the appliance gets restarted, you need to reassign
the repository to the appliance.
The following is an overview of the process of applying updates in Veritas Resiliency
Platform:
153
Updating Resiliency Platform
Prerequisites for a repository server
Applying updates to Resiliency Platform
Table 10-1
Step
Task
1
Make sure that the prerequisites for the See “Prerequisites for a repository
repository server are met.
server” on page 154.
2
Set up a repository server and download See “Setting up the repository server and
the updates from SORT
downloading updates” on page 155.
3
Add the repository server to Veritas
Resiliency Platform. There can be
multiple repository servers added to
Veritas Resiliency Platform at a time.
4
Assign a repository server to the virtual See “Assigning a repository server in
appliance where you want to apply the Resiliency Platform” on page 157.
update. A single repository server can
be assigned to multiple virtual
appliances but one virtual appliance can
be assigned only one repository server
at a time.
5
For a major upgrade:
■
Apply updates using CLISH menu
Description
See “Adding a repository server in
Resiliency Platform” on page 156.
See “Applying updates to virtual
appliances using the console”
on page 157.
For a minor upgrade:
■
See “Applying updates to virtual
Apply updates using web console or appliance using CLISH menu”
using CLISH menu
on page 159.
6
Refresh the information about applicable See “Refreshing the information about
updates
applicable updates” on page 159.
7
Remove an update from the repository See “Removing an update from the
server
repository server” on page 160.
Prerequisites for a repository server
To set up a repository server, make sure that the following prerequisites are met:
■
Repository server should be RHEL server version 6.5 with minimum yum version
3.2.29. Base server installation is recommended for the repository server.
■
Perl and Python should be installed on the server. Perl modules JSON.pm and
Config::Simple.pm need to be installed on the Linux server.
■
Web server (HTTP/HTTPS) should be configured on the server. Two-way SSL
configuration is recommended for HTTPS.
154
Updating Resiliency Platform
Setting up the repository server and downloading updates
Default ports are 80 for HTTP and 443 for HTTPS.
■
Repository server should have minimum 50 GB disk space available for
repository data.
■
Repository server should have connectivity with SORT as well as with the virtual
appliances.
See “About applying updates to Resiliency Platform” on page 153.
Setting up the repository server and downloading
updates
You need to set up a repository server in your environment, download the updates
from SORT, and make them available on your repository server.
You have following three options to set up a repository and download the updates
from SORT:
■
Download a specified update or download all the updates released after a
specified date.
■
Download a specified update on your local system and then update the repository
system with the downloaded updates. You can use this option if your repository
server does not have SORT connectivity. To use this option, you need to
download master.xml file from SORT.
■
Download the metadata of the applicable updates to your repository server.
Once you add the repository server using the Resiliency Manager console, you
can view the list of applicable updates in the Resiliency Manager console. You
can then decide which update you want to download.
Note: In case you plan to update the repository server with the updates or metadata
that you have saved on you local system, you need to always use the latest
master.xml file, irrespective of which update you plan to use.
To set up a repository server and download the updates
1
Create a repository path under root directory of the web server.
mkdir path_to_repository
2
Download the setup_conf_repo.pl file from SORT.
3
Do one of the following:
■
To download the updates and update the repository server with those
updates, do one of the following:
155
Updating Resiliency Platform
Adding a repository server in Resiliency Platform
■
To download a particular update to the repository server, and update
the repository:
./setup_conf_repo.pl --download-updates --repo-location
path_to_repository --product-version base_version --product
product_abbreviation --release-name release_name
■
To download multiple updates that are released after a particular date
or after a particular update version, and update the repository:
./setup_conf_repo.pl --download-updates --repo-location
path_to_repository product-version base_version --product
product_abbreviation --start-date yyyy-mm-dd
■
To update the repository server with the updates that you have saved on
your local system:
./setup_conf_repo.pl --add-local-updates --repo-location
path_to_repository --update-location path_to_tar
--metadata-location path_to_master.xml
■
To download the metadata of the applicable updates to your repository
server:
./setup_conf_repo.pl --refresh-metadata --repo-location
path_to_repository --product-version base_version --product
product_abbreviation
■
To update the repository server with the metadata file master.xml that you
have saved on your local system:
./setup_conf_repo.pl --refresh-metadata --repo-location
path_to_repository --metadata-location path_to_master.xml
See “About applying updates to Resiliency Platform” on page 153.
Adding a repository server in Resiliency Platform
After configuring a repository server, you need to add the repository server in Veritas
Resiliency Platform.
To add a repository server in Veritas Resiliency Platform
1
Navigate
Settings (menu bar) > Updates > Repository Servers
2
Click Add.
3
In the Add Repository Wizard panel, do the following:
156
Updating Resiliency Platform
Assigning a repository server in Resiliency Platform
■
Select the protocol for adding the repository server.
■
Enter the fully qualified hostname (FQDN) or IP address of the server that
you want to configure as the repository server.
■
If you want to modify the default port, enter the port number.
■
Enter the repository path that is created under root directory of web server.
■
Click Submit.
See “About applying updates to Resiliency Platform” on page 153.
Assigning a repository server in Resiliency
Platform
You need to assign a repository server to every virtual appliance where you want
to apply the updates. You can store all the available updates on this server and
apply it on the virtual appliance whenever required.
Note: Before assigning a repository server to a virtual appliance, make sure that
the path where repository server is configured has read permissions.
To assign a repository server to a virtual appliance
1
Navigate
Settings (menu bar) > Updates
2
Select the server names (virtual appliances) to which you want to assign a
repository server.
3
Click Assign Repository. Select the repository server that you want to assign
to the virtual appliances.
Click Submit.
See “About applying updates to Resiliency Platform” on page 153.
Applying updates to virtual appliances using the
console
You can apply updates to the virtual appliances using the console.
157
Updating Resiliency Platform
Applying updates to virtual appliances using the console
Replication gateway updates must be applied on the cloud replication gateway first
and then on the on-premises gateway.
To apply updates to the virtual appliances using the console
1
Prerequisites:
All the Resiliency Managers in the domain should have same version of update
installed on them.
Ensure that following services are running on the local as well as remote
Resiliency Manager:
2
■
User Interface service
■
Database service
■
Messaging service
■
Core service
■
Task service
■
Event service
Navigate
Settings (menu bar) > Updates
3
Select the server name or virtual appliance on which you want to apply the
update.
4
Select the update that you want to apply from New Updates.
5
Click Upgrade.
6
Verify the details of the update and click Submit.
Note: If the process of applying updates on the appliance takes more than 30
minutes, the session times out and you need to confirm if you want to continue the
session and refresh the page. The progress of the task of applying updates can be
tracked from Recent Activities.
See “About applying updates to Resiliency Platform” on page 153.
158
Updating Resiliency Platform
Applying updates to virtual appliance using CLISH menu
Applying updates to virtual appliance using CLISH
menu
You can use the CLISH menu to perform the upgrade related tasks in Resiliency
Platform.
Replication gateway updates must be applied on the cloud replication gateway first
and then on the on-premises gateway.
You need to log into the virtual appliance as admin and go to the updates sub-menu.
Following is a list of commands that you can run to perform the operations that are
related to the updates:
■
To configure the repository:
config-repository FQDN_or_IP_of_the _repository_server protocol
port_number Repository _path_on_repository_server
If you enter HTTPS as protocol, you are required to copy the content from the
SSL certificate, paste it on prompt, and press enter key.
■
To view the current configuration of the repository:
show-repo
■
To view the current version of the appliance or the version of the update installed
on the appliance:
list-updates
■
To show the readme file for the specified update:
show-readme version_of_the_update
■
To apply the specified update:
apply-update version_of_the_update
■
To remove the current repository configuration:
remove_repo
See “Using CLISH” on page 179. for a complete list of options available with Updates
command.
See “About applying updates to Resiliency Platform” on page 153.
Refreshing the information about applicable
updates
After applying updates, you may want to refresh the information about the applicable
updates on each of the virtual appliances or servers. If you apply the updates using
159
Updating Resiliency Platform
Removing an update from the repository server
CLISH, you need to refresh the information to reflect the current status of the updates
in the Resiliency Manager web console.
To refresh the information about applicable updates
1
Navigate
Settings (menu bar) > Updates > Available Updates
2
Click Refresh.
See “About applying updates to Resiliency Platform” on page 153.
Removing an update from the repository server
You can remove a particular update from the repository server.
To remove an update from the repository server
1
Go to the ITRP/RM directory on the repository server. This directory is created
under the repository path that you had provided while setting up the repository.
2
Run the following commands:
■
To remove the directory created for a particular update:
rm -rf patch_version_dir
■
To clear the older data, and then refresh and build the repository with the
existing patches in the RM directory:
createrepo --update RM
160
Chapter
11
Uninstalling Resiliency
Platform
This chapter includes the following topics:
■
About uninstalling Resiliency Platform
About uninstalling Resiliency Platform
In the current version, there is no provision for uninstalling Resiliency Platform. If
you do not want to use the Resiliency Platform product any longer, you can remove
the Resiliency Platform virtual appliance node using the appropriate hypervisor
manager in your environment.
If you want to decommision a Resiliency Platform virtual appliance node while
continuing to use the product on other nodes in the resiliency domain, you should
first use the web console to remove the node from the Resiliency Manager database.
For example, you can remove a Resiliency Manager node from the domain if another
Resiliency Manager node is active.
See “Removing a Resiliency Manager from a resiliency domain” on page 40.
Chapter
12
Troubleshooting and
maintenance
This chapter includes the following topics:
■
Viewing events and logs in the console
■
Accessing Resiliency Platform log files
■
Displaying risk information
■
About the Resiliency Manager services
■
Components of Resiliency Platform virtual appliance
■
Troubleshooting discovery of assets
■
About the frequency of asset information discovery
■
Troubleshooting the connection between Resiliency Managers in a resiliency
domain
■
Troubleshooting removing a Resiliency Manager from a resiliency domain
■
Using Veritas Services and Operations Readiness Tools to find a Unique
Message Identifier description and solution
Viewing events and logs in the console
Veritas Resiliency Platform maintains the following types of logs that can be viewed
in the web console:
System logs: System logs are typically the result of a user performing an operation
in the console.
Troubleshooting and maintenance
Accessing Resiliency Platform log files
Audit logs: Audit logs are primarily used for security audits. They leave a
chronological trail of activities performed on the system. They identify user, activity,
affected objects, etc. They help track the individuals responsible for activities and
detect security violations.
Event and notification logs: Event and notification logs are not necessarily related
to user activity; they can include information such as a server going down. Events
can be public or private. Rules can be configured to notify users by email of selected
public events. Private events are typically unrelated to user-initiated operations.
Private events are displayed in the console for troubleshooting but are not available
to include in rules for notification.
See “Setting up rules for event notifications” on page 149.
By default, logs and SNMP traps are retained for 2 years. This retention period can
be modified in the product settings in the console.
See “Modifying purge settings for logs and SNMP traps” on page 150.
To view events and logs
1
Navigate
More Views (menu bar) > Logs
You can also view new notifications from the Notifications icon.
2
To view logs by type (System, Audit, or Notification) select the appropriate tab.
You can filter by the product service and by severity (information, warning, or
errors) or type (public, private), depending on the tab.
Accessing Resiliency Platform log files
You can use logs-gather option available with support command of CLISH menu
to access the Resiliency Platform log files.
To access Resiliency Platform log files
1
Log in to the Resiliency Platform virtual appliance console as an admin user.
2
Go to the support under main menu.
163
Troubleshooting and maintenance
Displaying risk information
3
Run the logs-gather command with any of the log collection options that are
available.
See “Using CLISH” on page 179.
The command collects the logs according to the option that you use with the
command.
4
Once the logs are collected, a URL for downloading the log zip file is provided
to you. You can enter the URL in a browser on any host connected to the virtual
appliance. Log in as an admin user and download the zip file.
Displaying risk information
Resiliency Platform identifies and flags several risks that may occur during data
center operations. Some of these risks are transient. They are temporary and resolve
themselves without your intervention. Other risks require intervention and
troubleshooting to resolve.
You can display risks in the following ways:
Table 12-1
Ways to display risks
To display ...
Do the following:
A complete list of risks across the resiliency 1
domain
On the menu bar, select
More Views > Risks
Risks that are associated with a specific
resiliency group or virtual business service
2
On the Risk page, double-click a risk in
the table to display detailed information.
1
On the navigation pane, select
(Assets) and the tab for either
Resiliency Groups or Virtual Business
Services.
2
On the tab, double-click a resiliency
group or virtual business service to
display detailed information.
3
On the details page, note any risks that
are listed in the At Risk area, and
double-click the risk for details.
In addition to the above mentioned views, the More views > Logs > All view and
the More views > Logs > Notification view also includes the notification about
164
Troubleshooting and maintenance
Displaying risk information
the risks in your environment. You can double-click any row to view the detailed
description of the error and suggested resolution for the error.
Predefined risks in Resiliency Platform
Table 12-2 lists the predefined risks available in Resiliency Platform. These risks
are reflected in the current risk report and the historical risk report.
Predefined risks
Table 12-2
Risks
Description
Risk
detection
time
New VM
added to
replication
storage
Checks if a virtual machine 5 minutes
that is added to a
consistency group on a
primary site, is not a part
of the resiliency group.
Risk type
Affected
operation
Error
■
Migrate
■
Takeover
■
Rehearse
■
Migrate
■
Takeover
■
Migrate
■
Takeover
■
Migrate
■
Takeover
Replication
Checks if the replication
5 minutes
lag exceeding lag exceeds the thresholds
threshold
that are defined by the
user for each resiliency
group.
Warning
Replication
Checks if the replication is 5 minutes
state
not working or is in a
broken/critical critical condition for each
resiliency group.
Error
Remote
mount point
already
mounted
Checks if the mount point ■
is not available for
mounting on target site for
any of the following
■
reasons:
■
■
Mount point is already
mounted.
Mount point is being
used by other assets.
Native (ext3, Warning
ext4,NTFS ):
30 minutes
Virtualization
(VMFS,
NFS): 6
hours
Fix if violated
Add the virtual machine
to the resiliency group.
Contact the appropriate
administrator
Contact the enclosure
vendor.
Unmount the mount
point that is already
mounted or is being
used by other assets.
165
Troubleshooting and maintenance
Displaying risk information
Predefined risks (continued)
Table 12-2
Risks
Description
Risk
detection
time
Disk
utilization
critical
Checks if at least 80% of
the disk capacity is being
utilized. The risk is
generated for all the
resiliency groups
associated with that
particular file system.
■
Control host Checks if the discovery
not reachable daemon is down on the
Control Host.
ESX not
reachable
■
Risk type
Native (ext3, Warning
ext4,NTFS ):
30 minutes
Virtualization
(VMFS,
NFS): 6
hours
15 minutes
Checks if the ESX server 5 minutes
is in a disconnected state.
Affected
operation
■
Migrate
■
Takeover
■
Rehearse
Error
■
Migrate
Error
■
On primary Resolve the ESX server
site: start or connection issue.
stop
operations
On
secondary
site:
migrate or
takeover
operations
■
vCenter
Server not
reachable
Insufficient
compute
resources on
failover target
Fix if violated
Checks if the virtualization 5 minutes
server is unreachable or if
the password for the
virtualization server has
changed.
Error
Checks if there are
6 hours
insufficient CPU resources
on failover target in a
virtual environment.
Warning
Delete or move some
files or uninstall some
non-critical applications
to free up some disk
space.
Resolve the discovery
daemon issue.
On primary
site: start or
stop
operations
On
secondary
site:
migrate or
takeover
operations
Resolve the
virtualization server
connection issue.
■
Migrate
■
Takeover
Reduce the number of
CPUs assigned to the
virtual machines on the
primary site to match the
available CPU
resources on failover
target.
■
■
In case of a password
change, resolve the
password issue.
166
Troubleshooting and maintenance
About the Resiliency Manager services
Table 12-3 describes some risks that are displayed in Resiliency Platform console,
but these risks are not reflected in the risk reports.
Other risks
Table 12-3
Risk
Description
HOST_SFMH_REINSTALLED
The host is disconnected. The probable cause is that the
host has been reinstalled. Changes you make after this
condition are not reflected on the Resiliency Manager. To
correct this issue, remove and re-add this host to the
Infrastructure Management Server (IMS).
HOST_DISCONNECTED_MAC_CHANGED
The host is disconnected. The probable cause is that the
media access code (MAC) address of host has changed.
Changes you make after this condition are not reflected
on the Resiliency Manager. To correct this issue, remove
and re-add this host to the Infrastructure Management
Server (IMS).
VMWARE_DISCOVERY_FAILED
VMware discovery failed.
FS_FILESYSTEM_FULL
The file system is at 100% usage.
About the Resiliency Manager services
The Resiliency Manager is a server that includes a set of loosely coupled services,
a data repository, and a management console. The following is a list of services
that can be started or stopped via CLISH on the Resiliency Platform virtual appliance.
See “Using CLISH” on page 179.
Table 12-4
Resiliency Manager services
Service or Description
component
name
Database
service (DB)
Supports the main data repository.
Core service
Provides the default platform functionality. Also includes critical capabilities
such as security management, data repository access and external systems
communication.
Licensing
service
Provides the licensing capability.
167
Troubleshooting and maintenance
Components of Resiliency Platform virtual appliance
Resiliency Manager services (continued)
Table 12-4
Service or Description
component
name
Workflow
Service (WF)
Provides the platform-level capability to deploy and execute workflows for
other services in the platform.
Reporting
Service
Provides the platform-level capability to deploy and run reports for other
services in the platform.
Messaging
Service (MQ)
The Messaging Service is the backbone of internal communication between
all services in a Resiliency Manager.
Authentication Provides consistent tokens and certificates across identity providers that
Service (AT)
can be used by Resiliency Platform authorization and rule-based access
control (RBAC).
Scheduler
Service
Provides the platform-level capability to schedule execution of a job (report,
workflow, API, etc.) for other services in the platform.
Though schedule settings are maintained at the main data repository and
available consistently to all Resiliency Managers, the schedule runs at only
one Resiliency Manager instance.
User Interface Provides the web-based user interface for the product.
Service (UI)
Recovery
Automation
Service (RA)
Provides disaster recovery capability for virtual machines and applications.
Components of Resiliency Platform virtual
appliance
Following components are deployed while deploying the Resiliency Platform virtual
appliance:
Table 12-5
Components
Description
Operating System
Hardened CentOS 6.7 Minimal operating system. The operating
system is hardened or customized to contain only those packages
that are required to run the application.
168
Troubleshooting and maintenance
Troubleshooting discovery of assets
Table 12-5
(continued)
Components
Description
Veritas Resiliency
Platform
Veritas Resiliency Platform provides core and standard services
framework for the solution.
Resiliency Manager
Serves as the management console for Resiliency Platform. It also
includes the database and the Resiliency Platform services.
Infrastructure
Management Server
(IMS)
Serves as the infrastructure manager or asset manager for
Resiliency Platform.
Command Line
Command Line Interface Shell (CLISH) is used to provide the user
Interface Shell (CLISH) a limited menu-based access to the operating system and the
application.
See “About deploying the Resiliency Platform virtual appliance” on page 28.
Troubleshooting discovery of assets
When asset infrastructure is added to the Infrastructure Management Server (IMS),
or when changes are made to the infrastructure, the IMS discovers and correlates
the asset information and displays the information on the Assets page of the
Resiliency Platform console. The discovery can take some time before the
information is updated on the console. Until discovery is complete, some information
needed to configure resiliency groups may be missing from the Assets page on the
console.
See “About the frequency of asset information discovery” on page 171.
If changes have been made to the asset infrastructure, you can use the Refresh
operation on assets in the IMS to speed up discovery so that updated asset
information is displayed more quickly in the console. To use the Refresh operation,
display the asset infrastructure page for the IMS, select the asset type, right-click
the asset and select Refresh.
Note: Occasionally, the data discovered from the Infrastructure Management server
(IMS) may not be updated properly in the Resiliency Manager database. This
situation may result in displaying incorrect information about the resiliency group
state, replication state, and replication type. In such a case, refresh the appropriate
assets on the IMS in both the data centers.
169
Troubleshooting and maintenance
Troubleshooting discovery of assets
If you are configuring replication using storage arrays in a VMware vCenter Server
environment, you can use the following guidelines to speed up discovery or to
troubleshoot information that is not being updated:
Table 12-6
Configuring asset infrastructure in IMS for storage arrays in
VMware environment
Situation
Troubleshooting/best practices
Adding storage arrays as
enclosures to IMS
Ensure that the storage arrays that are added to the
IMS are the ones that provide storage to the ESX
servers managed by the vCenter Server that is added
to the IMS.
More than one IMS in data center Ensure that the vCenter Server that is managing the
ESX servers, and the enclosure providing storage to
those servers, are added to the same IMS.
Refreshing the IMS after a change Ensure that you use the Refresh operation on the correct
in infrastructure
vCenter Servers and enclosures where the change was
made.
Refreshing the IMS after a change Ensure that you use the Refresh operation in the correct
in infrastructure, where there is
IMS.
more than one IMS
In the VMware and EMC SRDF and RecoverPoint environment, the general guideline
is to add/refresh the enclosure before adding/refreshing the VMware vCenter Server.
Table 12-7
Configuring or refreshing asset infrastructure in IMS for VMware
and EMC SRDF and RecoverPoint environment
Situation
Recommended sequence
You have not yet added the asset
infrastructure.
Add the enclosure information in the IMS and
let the discovery complete before adding the
vCenter Server to the IMS.
You later provision new storage from an
enclosure that is already configured in the
IMS and mount datastores from the new
storage.
Refresh the enclosure in the IMS, let the
refresh task on the enclosure complete, and
then refresh the vCenter Server in the IMS.
You provision storage from a new enclosure. Add the new enclosure in the IMS and then
refresh the vCenter Server after the enclosure
discovery completes.
170
Troubleshooting and maintenance
About the frequency of asset information discovery
Table 12-7
Configuring or refreshing asset infrastructure in IMS for VMware
and EMC SRDF and RecoverPoint environment (continued)
Situation
Recommended sequence
You are provisioning storage from an
enclosure that is already configured in the
IMS to new ESX servers managed by a
vCenter Server.
Refresh the enclosure first, than add the
vCenter Server to the IMS or refresh it if it is
already added to the IMS.
In the VMware and NetApp SnapMirror environment, the general guideline is
add/refresh the vCenter Server first, then add/refresh the NetApp enclosure.
Table 12-8
Configuring or refreshing asset infrastructure in IMS for storage
arrays in VMware and NetApp SnapMirror environment
Situation
Recommended sequence
You have not yet added the asset
infrastructure.
Add the vCenter Server to the IMS first and
let the discovery complete before you add the
NetApp enclosure.
You later provision storage from an existing Refresh the vCenter Server first in the IMS,
NetApp enclosure and mount NFS datastores let the discovery complete and then refresh
on ESX servers.
the NetApp enclosure.
You later provision storage from a new
Refresh the vCenter Server first in the IMS,
NetApp enclosure and mount NFS datastores wait for the vCenter Server discovery to
on that ESX servers.
complete, and then add the new NetApp
enclosure.
The recommended sequence for adding or modifying asset infrastructure for
application discovery in the NetApp SnapMirror replication environment is as follows:
Ensure that discovery of the hosts is complete before you add or refresh the NetApp
enclosures.
See “Adding the asset infrastructure to an Infrastructure Management Server (IMS)”
on page 72.
About the frequency of asset information
discovery
After you add the asset infrastructure, for example virtualization servers, to the
Infrastructure Management Server (IMS), the IMS discovers information about the
assets and the information is displayed in the console. Thereafter, the IMS continues
171
Troubleshooting and maintenance
Troubleshooting the connection between Resiliency Managers in a resiliency domain
to discover and update the information. The following table describes how often
the IMS performs discovery.
If you make changes to the asset infrastructure, such as adding or removing virtual
machines, you can use the Refresh operation on assets in the IMS to manually
initiate the discovery.
Note: The discovery is triggered when configuration changes occur on the hosts.
If configuration changes are not detected on the managed hosts, the communication
between the host and IMS is restricted to the heartbeat communication that occurs
every five minutes.
Asset type
Discovery
interval in
minutes
Discovered information
Host
1440
The operating system and
networking for the host.
Typically, this information does not
change frequently.
Applications
360
Supported applications and their
storage dependencies.
Hyper-V
120
Virtual machines and storage
discovery.
VMware
360
ESX servers, virtual machines, and
their storage dependencies.
Enclosures
360
Logical devices, physical devices,
host associations, replications, and
other storage array-specific
properties.
Replication Appliance
360
Replication and storage
dependencies
Troubleshooting the connection between
Resiliency Managers in a resiliency domain
Multiple Resiliency Managers that are part of the same domain synchronize their
databases using built-in replication. Each Resiliency Manager has its own web
console but because the data is synchronized, all consoles show the same data.
172
Troubleshooting and maintenance
Troubleshooting removing a Resiliency Manager from a resiliency domain
Operations can be performed from any console and the results show in all the
consoles in the resiliency domain.
In some cases the connection is lost between Resiliency Managers. In such a case,
if you login to the console, a message is displayed to warn you about this and
request that you confirm whether the other Resiliency Manager is down (outage).
If the Resiliency Manager administrator confirms that the other Resiliency Manager
is down, you can click the confirmation on the message box and continue working
on the console. When the other Resiliency Manager is brought up, the changes are
synchronized.
However, if you check and the other Resiliency Manager is not down, the problem
is in the network connection. In this case, you should not attempt to work in the
Resiliency Manager console until the network connection is restored.
Troubleshooting removing a Resiliency Manager
from a resiliency domain
In some cases you may want to remove a Resiliency Manager node from a resiliency
domain.
Before removing a Resiliency Manager node, you should first remove the Resiliency
Manager from the resiliency domain using the Leave Domain operation in the Veritas
Resiliency Platform web console. Completing this operation ensures that the
Resiliency Manager is cleanly decommissioned and that all references to it are
removed from the Resiliency Manager database and no longer appear in the web
console user interface. The Leave Domain operation has prerequisites that are
documented in the procedure topic.
See “Removing a Resiliency Manager from a resiliency domain” on page 40.
The following gives more details for trouble scenarios, for example, if the Resiliency
Manager you want to remove is not online or if the operation does not complete
successfully.
173
Troubleshooting and maintenance
Using Veritas Services and Operations Readiness Tools to find a Unique Message Identifier description and
solution
Unable to bring the Resiliency
Manager online
The Leave Domain operation requires that both
Resiliency Managers be online. However, if you are
unable to bring the Resiliency Manager you want to
remove online, there is no problem with leaving it in a
down state. The resiliency domain and other
infrastructure components continue to function. If an
Infrastructure Management Server (IMS) was connected
to the Resiliency Manager that was down, the IMS will
automatically reconnect itself to another Resiliency
Manager in the same domain. In addition, you can add
another Resiliency Manager and join it to the domain.
Unable to complete Leave Domain The Leave Domain operation is a multistep process.
operation
First the Resiliency Manager decommissions itself. Then
all references to it are removed from the Resiliency
Manager database. Finally any IMS connected to the
decommissioned Resiliency Manager is rerouted to
another Resiliency Manager.
You can use the Activities pane to verify that the Leave
Domain operation completes.
If the process fails before all steps are complete, the
partially removed Resiliency Manager no longer
operates. However, the resiliency domain continues to
function.
Using Veritas Services and Operations Readiness
Tools to find a Unique Message Identifier
description and solution
You can use Veritas Services and Operations Readiness Tools (SORT) to find a
Unique Message Identifier (UMI) description and solution.
To find a Unique Message Identifier description and solution
1
Point your Web browser to the following URL:
http://sort.veritas.com
2
In the search field on the top right of any SORT page, enter the UMI code, and
then click the search icon.
174
Troubleshooting and maintenance
Using Veritas Services and Operations Readiness Tools to find a Unique Message Identifier description and
solution
3
On the Search Result page, in the Error codes pane, click the link to your
message code. If you have a large number of search results, use the check
boxes at the top of the page to display only error codes to find your code more
easily.
The Error Code details page for the UMI code displays, which provides the
description and any possible solutions.
4
If the information on the page does not provide an adequate solution to your
issue, you can click one of the links on the page to do one of the following
things:
■
Comment on the UMI or its solution.
■
Request a solution.
■
Add a solution of your own.
175
Appendix
A
Virtual appliance security
features
This appendix includes the following topics:
■
Operating system security
■
Management Security
■
Network security
■
Access control security
■
Physical security
Operating system security
Veritas Resiliency Platform appliance operating system is hardened against potential
security exploitation by removing the operating system packages that are not used
by the Resiliency Platform. All the default yum repository files that are shipped with
the operating system are removed.
The Control + Alt + Delete key combination has been disabled to avoid any
accidental reboot of the virtual appliance. Exec-shied is enabled to protect the virtual
appliance from stack, heap, and integer overflows.
Management Security
Only two users are available on the appliance: admin user and support user. These
two user accounts are used to access the appliance based on the requirement.
Only admin login is available for the appliance. The password policy of admin login
is modified to prompt the user to change the password on the first login. The new
Virtual appliance security features
Network security
password must not be a Dictionary word and must be at least six characters long.
If the admin user password is lost, Veritas may access the root using the grub
access, and reset the admin user password.
On successful completion of the product bootstrap, admin user can only access a
limited menu of commands through CLISH. Besides admin user, support user is
also supported in the appliance but remote login of support user is disabled. To
access the support user, one need to login as an admin and go through CLISH. An
option support > shell is provided in the CLISH menu to switch the user to support
and access the bash shell of support. After selecting this option, the support user
is given superuser privileges. Using this option is not recommended and it should
be used only with the assistance of technical support.
Timeout of the bash shells of all users is set to 900 seconds.
Network security
The TCP timestamp responses are disabled in Resiliency Platform virtual appliance.
Another network security feature of the appliance is that during the product bootstrap
process, only those ports that are used by the product for communication and data
transfer, are opened through the firewall and all the other communications are
blocked.
Uncommon network protocols such as DCCP, SCTP, RDC, TIPC have been disabled
so that any process cannot load them dynamically.
See “Network and firewall requirements” on page 25.
Access control security
Resiliency Platform virtual appliance implements certain access control measures.
The umask is set to 0700 across the appliance. The access permissions of some
of the files such as home folder of root, the log directory etc. is restricted. All the
security and the authorization messages are logged into the appliance.
Physical security
In the Resiliency Platform virtual appliance, the USB storage access is disabled.
177
Appendix
B
Using CLISH menu in
Resiliency Platform
This appendix includes the following topics:
■
About CLISH
■
Using CLISH
About CLISH
Once the Veritas Resiliency Platform virtual appliance is deployed and configured,
you are given limited, menu-based access to the operating system and the product.
You need to use Command Line Interface Shell (CLISH) menu to manage the
configuration-related changes to the product.
You can use CLISH menu to do the following:
■
Manage the Veritas Resiliency Platform appliance
■
Monitor the Veritas Resiliency Platform appliance activities
■
Change some of the network configurations
■
Change the system settings
■
Access the Veritas Resiliency Platform logs
■
Manage Veritas Resiliency Platform updates and patches
See “Using CLISH” on page 179.
Using CLISH menu in Resiliency Platform
Using CLISH
Using CLISH
After the product configuration, when you log in to the Resiliency Platform appliance,
you get the main menu of CLISH. This menu is the starting point, from which you
can configure, manage, monitor, and support your application using the command
line.
You can reconfigure or modify some of the appliance settings that are configured
through the product bootstrap. Following are the settings that you can reconfigure
using CLISH:
■
Network settings: You can reconfigure the subnet mask, default gateway, DNS
server, and search domains using the CLISH menu.
You cannot reconfigure the hostname that you had configured through the
bootstrap process. In case of static DHCP, you cannot change the network
settings using the CLISH menu. You cannot change the network settings for
any component that is configured in the cloud environment.
■
System settings: You can reset the timezone and NTP server using CLISH
menu. Changing the system settings can affect the product functionality if
incorrect values are set.
You can press the tab or space key to display the menu options. Press ? key to
display detailed help.
Table B-1
Options available in the main menu
Menu option
Description
back
Return to the previous menu
exit
Log out from the current CLI session
help
Display an overview of the CLI syntax
manage
Manage appliance
Table B-2
monitor
Monitor appliance activities
Table B-5
network
Network configuration
Table B-6
settings
Appliance settings
Table B-12
179
Using CLISH menu in Resiliency Platform
Using CLISH
Table B-1
Options available in the main menu (continued)
Menu option
Description
support
Access logs
Table B-16
updates
Manage updates and patches
Table B-18
Table B-2
Options available with manage command
Menu option
Description
back
Return to the previous menu
configure
Configure Resiliency Platform component or show the configured
component
Table B-3
exit
Log out from the current CLI session
help
Display an overview of the CLI syntax
services
Manage the appliance services
■
Table B-3
If the appliance has been configured as a Resiliency Manager or
IMS, use rm or ims as first parameter and options available in the
services menu as second parameter.
Table B-4
See “About the Resiliency Manager services ” on page 167.
Options available with configure command
Menu option
Description
ims
Configure Infrastructure Management Server
rm
Configure Resiliency Manager
show
Show the configured component
Table B-4
Options available with services command
Menu option
Description
show
Show Resiliency Platform services
180
Using CLISH menu in Resiliency Platform
Using CLISH
Table B-4
Options available with services command (continued)
Menu option
Description
restart
Restart Resiliency Platform services
Two options available are:
restart all where, all means all the services.
restart service name where, service name is the name of a
particular service. You can provide multiple service names (comma
separated).
start
Start Resiliency Platform services
Two options available are:
start all where, all means all the services.
start service name where, service name is the name of a
particular service. You can provide multiple service names (comma
separated).
status
Check the status of Resiliency Platform services
Two options available are:
status all where, all means all the services.
status service name where, service name is the name of a
particular service. You can provide multiple service names (comma
separated).
stop
Stop Resiliency Platform services
Two options available are:
stop all where, all means all the services.
stop service name where, service name is the name of a
particular service. You can provide multiple service names (comma
separated).
Table B-5
Options available with monitor command
Menu option
Description
back
Return to the previous menu
exit
Log out from the current CLI session
FSusage
Display filesystem usage
help
Display an overview of the CLI syntax
181
Using CLISH menu in Resiliency Platform
Using CLISH
Table B-5
Options available with monitor command (continued)
Menu option
Description
top
Display the top process information
uptime
Display the uptime statistics for the appliance
who
Display who is currently logged into the appliance
Table B-6
Options available with network command
Menu option
Description
back
Return to the previous menu
dns
Show or change the DNS
Table B-7
exit
Log out from the current CLI session
gateway
Show or change the Gateway
Table B-8
help
Display an overview of the CLI syntax
hostname
Show the hostname
ip
Show or change the IP address
Table B-9
netmask
Show or change the netmask
Table B-10
search-domain
Show or change the domain
Table B-11
Table B-7
Options available with dns command
Menu option
Description
set
Configure Domain Name Server
show
Show the current Domain Name Server
182
Using CLISH menu in Resiliency Platform
Using CLISH
Table B-8
Options available with gateway command
Menu option
Description
set
Configure Gateway
show
Show the current Gateway
Table B-9
Options available with ip command
Menu option
Description
set
Configure the IP address
show
Show the current IP address
Table B-10
Options available with netmask command
Menu option
Description
set
Configure the netmask
show
Show the current netmask
Table B-11
Options available with search-domain command
Menu option
Description
add
Add search-domain
remove
Remove the search domain name
show
Show the search domain settings
Table B-12
Options available with settings command
Menu option
Description
back
Return to the previous menu
change-password
Change the admin user password for the appliance
date
Display the current date and time for the appliance
Table B-13
exit
Log out from the current CLI session
help
Display an overview of the CLI syntax
183
Using CLISH menu in Resiliency Platform
Using CLISH
Table B-12
Options available with settings command (continued)
Menu option
Description
lvm
Perform operations related to logical volume manager on the appliance
See Table B-14 on page 184.
ntp
Perform operations related to NTP server
poweroff
Shut down the appliance
reboot
Restart the appliance
timezone
Show or change the timezone for the appliance
See Table B-15 on page 184.
Table B-13
Options available with date command
Menu option
Description
show
Show the time and date
Table B-14
Options available with lvm command
Menu option
Description
add-disk
Add disk to the data volume. You need to attach a disk before adding
it.
list-free-disk
List the free disks
initialize-free-disk
Initialize the newly attached free disk
list-used-disk
List the disks used by the data volume
remove-disk
Remove disk from the data volume. Make sure that you have an extra
disk to migrate the data before removing a disk.
Note: In case you initialize the newely-added disk during add-disk or remove-disk
operation, the existing data on the new disk is deleted.
Table B-15
Options available with timezone command
Menu option
Description
set
Set the timezone for the appliance
show
Show the current timezone for the appliance
184
Using CLISH menu in Resiliency Platform
Using CLISH
Table B-16
Options available with support command
Menu option
Description
back
Return to the previous menu
exit
Log out from the current CLI session
help
Display an overview of the CLI syntax
loggather
■
shell
Open the bash shell prompt for support user
Table B-17
If the appliance has been configured as a Resiliency Manager or
an IMS, then various options will be available for collecting the
Resiliency Manager and IMS logs.
Table B-17
Options available with loggather command
Menu option
Description
basic
Gather logs of Resiliency Manager and IMS without database
full
Gather logs of Resiliency Manager and IMS with database
fullims
Gather logs of IMS with database
fullrm
Gather logs of Resiliency Manager with database
ims
Gather logs of IMS
rm
Gather logs of Resiliency Manager
Table B-18
Options available with updates command
Menu option
Description
apply-update
Apply the specified update
back
Return to the previous menu
config-repository
Configure the repository
Table B-19
exit
Log out from the current CLI session
help
Display an overview of the CLI syntax
list-updates
List the applicable updates
remove-repository
Remove current repository configuration
185
Using CLISH menu in Resiliency Platform
Using CLISH
Table B-18
Options available with updates command (continued)
Menu option
Description
show-readme
Show readme for the specified update
show-repository
Show current repository configuration
show-version
Show appliance version
Table B-19
Options available with config-repository command
Menu option
Description
hostname
hostname of the repository server
protocol
Protocol on which the repository server is configured
port
Port on which the repository server is configured
RepoPath
Path on which the repository server is configured
See “About CLISH” on page 178.
See “Accessing Resiliency Platform log files” on page 163.
186
Appendix
C
Tips on using the web
console
This appendix includes the following topics:
■
Tour of the Resiliency Platform web console screen
■
Using Quick Actions for shortcuts to common tasks
■
Filtering and searching for objects in the web console
■
About settings in the web console
■
About the Resiliency Platform Dashboard
■
Web console icons
Tour of the Resiliency Platform web console
screen
The numbered screen areas are illustrated below the table.
Table C-1
Overview of the web console screen areas
Screen areas
Description
1 - Menu bar
Menu options for reports, resiliency plans, views,
settings, notifications, inbox, and online help.
See “Menu bar options” on page 188.
2 - Navigation pane
Icons to open pages for configuring and implementing
start/stop and disaster recovery operations.
See “Navigation pane options” on page 190.
Tips on using the web console
Tour of the Resiliency Platform web console screen
Table C-1
Overview of the web console screen areas (continued)
Screen areas
Description
3 - Dashboard
The console home page - clicking the Home icon in the
navigation pane returns to the Dashboard.
View an overview of assets in the resiliency domain and
their current status. Drill down for details.
See “About the Resiliency Platform Dashboard”
on page 193.
Menu bar options
The menu bar is located at the top of the console window.
188
Tips on using the web console
Tour of the Resiliency Platform web console screen
Table C-2
Menu bar options for the Veritas Resiliency Platform web console
Options
Description
Open drop-down selection of shortcuts to common
tasks.
See “Using Quick Actions for shortcuts to common
tasks” on page 190.
Schedule and run reports. View reports showing data
center and asset status.
See “About reports” on page 139.
Create and run custom resiliency plans for starting,
stopping, and migrating resiliency groups.
See the Solutions guide for details on resiliency plans.
More views
View activities, risks, and logs.
Settings
Open Settings page for configuring and maintaining
product infrastructure and other settings.
See “About settings in the web console” on page 191.
Notifications
Display most recent notifications.
Requires alerts and notifications to be enabled using
Settings page.
See “Viewing events and logs in the console”
on page 162.
See “Managing settings for alerts and notifications and
general product settings” on page 147.
Inbox
View actions to be completed.
Help
Open Help window where you can search all help or
filter by category.
189
Tips on using the web console
Using Quick Actions for shortcuts to common tasks
Menu bar options for the Veritas Resiliency Platform web console
(continued)
Table C-2
Options
Description
Log out of console.
Shows Resiliency Manager, resiliency domain, and data
center.
Navigation pane options
The navigation pane is located on the left side of the console window.
Note: Click the arrow on the top of the navigation pane to expand or contract the
pane and view labels for icons.
Table C-3
Left navigation pane options for the Veritas Resiliency Platform
web console
Options Description
Returns to Home page Dashboard
Opens Assets page for configuring and viewing resiliency groups and performing
start/stop operations or disaster recovery
Opens configuration page for disaster recovery settings
Using Quick Actions for shortcuts to common
tasks
In the Veritas Resiliency Platform web console, you can use the Quick Actions
pull-down menu for shortcuts to go to common tasks.
To use Quick Actions for shortcuts to common tasks
1
Navigate
On the top menu bar, click Quick Actions to
display available shortcuts.
190
Tips on using the web console
Filtering and searching for objects in the web console
2
The menu of available shortcuts is displayed. Click the desired shortcut.
Filtering and searching for objects in the web
console
On pages that list multiple objects, for example, virtual machines listed on the Assets
page, the web console lets you select object types as a filter or search by first letters
of a name. To see the full list again, clear the filter or search field.
You can also double-click to drill down to a more detailed view. For example, you
can drill down from a row of a table that lists virtual machines, or from a Dashboard
graphic showing information on virtual machine status.
About settings in the web console
With appropriate permissions you can configure Veritas Resiliency Platform
infrastructure and other general settings. You access the Settings page from the
menu bar.
191
Tips on using the web console
About settings in the web console
Settings
Table C-4
Settings page options
Type of setting
Description
More information
Infrastructure
Add and manage
Infrastructure Management
Servers (IMS) and add the
asset infrastructure to the
IMS
See “Managing data
centers” on page 49.
Manage data centers and
their network settings
See “Removing a
Resiliency Manager from a
resiliency domain”
on page 40.
Manage Resiliency
Managers and resiliency
domains
Updates
View and deploy product
updates
See “About applying
updates to Resiliency
Platform” on page 153.
User Management
Configure authentication
See “Managing user
domains, users and user authentication and
groups, and user personas permissions” on page 122.
(roles)
Licenses
View and manage product See “Managing licenses”
licenses
on page 120.
Alerts and Notifications
Configure email and SNMP
for alerts and notifications,
configure rules for
notification
General
Configure general product See “Managing settings for
settings such as purge
alerts and notifications and
intervals and telemetry
general product settings”
on page 147.
See “Managing settings for
alerts and notifications and
general product settings”
on page 147.
Note: Additional settings that relate to disaster recovery configuration are available
from the navigation pane.
See “Tour of the Resiliency Platform web console screen” on page 187.
192
Tips on using the web console
About the Resiliency Platform Dashboard
About the Resiliency Platform Dashboard
The Resiliency Platform Dashboard gives you an overview of your resiliency domain.
Use the Dashboard to answer questions such as the following:
■
Which of my data centers have Resiliency Platform managed assets?
■
What is the mix of my assets by type and platform?
■
Which assets are configured for disaster recovery?
The Dashboard has the following areas:
Global View
A world map that identifies the data centers
that contain Resiliency Platform managed
assets.
Lines between data centers indicate that
replication takes place between the locations.
Mouse over an icon for basic Resiliency
Platform platform configuration and asset
configuration information for that data center.
Click More for detailed information and recent
activity.
Resiliency Groups and Virtual Business
Services summaries
The upper right section of the dashboard
displays total number of resiliency groups and
virtual business services in the resiliency
domain, as well as those at risk and normal.
Click a square in either the Resiliency
Groups or Virtual Business Services
summary to display a tab of detailed
information.
Virtual Machines by Type and Platform
Displays a summary of virtual machines in all
data centers or information on a single data
center. Use the drop-down list to filter your
results. The summary lists the virtual machine
types by percentage and the platform types
by number.
Application environment
Displays the number of applications and the
application types. The chart shows the
number of applications that are managed by
InfoScale and those that are not managed by
InfoScale.
193
Tips on using the web console
Web console icons
Applications by Type
Displays a summary of application types in
all data centers or in a single data center. Use
the drop-down list to filter your results.
Top Resiliency Groups by Replication Lag Ranks the resiliency groups according to how
long it takes the recovery data center to be
in sync with the active data center.
Virtual Machines and Applications by
Recovery Readiness
Displays the percentage of virtual machines
and applications that are unprotected or
unmanaged.
Use the drop-down list to filter your results.
Web console icons
The following is a summary of icons that appear on the Veritas Resiliency Platform
web console.
Table C-5
Web console icons
Icon Description
More views
Location
Menu bar
Menu options for Activities, Logs, Risks
Settings
Menu bar
Opens Settings page
Notifications
Menu bar
Displays notifications
Requires alerts and notifications to be enabled using
Settings page
Inbox
Menu bar
View actions to be completed.
Help
Menu bar
Opens Help window where you can search all help
or filter by category
Log out of console
Shows user login and information about Resiliency
Manager, resiliency domain, and data center
Menu bar
194
Tips on using the web console
Web console icons
Table C-5
Web console icons (continued)
Icon Description
Home
Location
Navigation pane
Returns to the Home page Dashboard
Assets
Navigation pane
Opens the Assets page for configuring and viewing
resiliency groups and performing start/stop operations
or disaster recovery
Recovery Automation
Navigation pane
Opens configuration page for disaster recovery
settings
Vertical ellipsis
Displays list of actions for selected object
To the right of a selected
object in a list
195
Glossary
activity
A task or an operation performed on a resiliency group.
add-on
An additional software package that can be installed on hosts by the Infrastructure
Management Server (IMS) for specialized uses.
asset infrastructure
The data center assets that can be added to the Infrastructure Management Server
(IMS) for IMS discovery and monitoring. For example, virtual machines or
virtualization servers.
assets
In Veritas Resiliency Platform, the virtual machines or applications that have been
discovered by the Infrastructure Management Server (IMS) and that can be grouped
into resiliency groups.
CLISH
Command Line Interface SHell. Provides the command line menu on the virtual
appliance for use after the initial bootstrap configuration.
data center
A location that contains asset infrastructure to be managed by Veritas Resiliency
Platform.
For the disaster recovery use case, the resiliency domain must contain at least two
data centers in different locations, a production data center and recovery data
center. Each data center has a Resiliency Manager and one or more IMSs.
host
Physical servers, virtual machines, or Hyper-V servers that are added to the
Infrastructure Management Server (IMS) as hosts.
Adding the assets as hosts installs the host package that is used by the IMS for
discovery and monitoring.
Infrastructure
Management Server
(IMS)
The Veritas Resiliency Platform component that discovers, monitors, and manages
the asset infrastructure within a data center. The IMS transmits information about
the asset infrastructure to the Resiliency Manager.
migrate
A planned activity involving graceful shutdown of virtual machines at the production
data center and starting them at the recovery data center. In this process, replication
ensures that consistent virtual machine data is made available at the recovery data
center.
persona
A user role that has access to a predefined set of jobs (operations). Used to assign
permissions to users and groups for Veritas Resiliency Platform web console
operations.
product role
The function configured for a Veritas Resiliency Platform virtual appliance.
Glossary
For example, a virtual appliance can be configured as a Resiliency Manager,
Infrastructure Management Server (IMS) or both.
production data center The data center that is normally used for business. See also recovery data center.
recovery data center
The data center that is used if a disaster scenario occurs. See also production data
center.
rehearsal
A zero-downtime test that mimics the configuration, application data, storage, and
the failover behavior of the resiliency group.
Rehearsal verifies the ability of the resiliency group to fail over to the recovery data
center during a disaster.
resiliency domain
The logical scope of a Resiliency Platform deployment. It can extend across multiple
data centers.
resiliency group
The unit of management and control in Veritas Resiliency Platform. Related assets
are organized into a resiliency group and managed and monitored as a single entity.
Resiliency Manager
The Veritas Resiliency Platform component that provides resiliency capabilities
within a resiliency domain. It is composed of loosely coupled services, a distributed
data repository, and a management console.
resiliency plan
A collection of tasks or operations, along with the relevant assets, which are
performed in a predefined sequence.
resiliency plan
A template defining the execution sequence of a collection of tasks or operations.
template
takeover
An activity initiated by a user when the production data center is down due to a
disaster and the virtual machines need to be restored at the recovery data center
to provide business continuity.
tier
Within a virtual business service (VBS), resiliency groups are arranged as tiers.
Tiers represent the logical dependencies between the resiliency groups and
determine the relative order in which the resiliency groups start and stop.
virtual appliance
An appliance that includes the operating system environment and the software
application which are deployed together as a virtual machine.
The Veritas Resiliency Platform virtual appliance is deployed as a virtual machine
and then configured with basic settings and a role (for example, Resiliency Manager).
virtual business
service (VBS)
web console
A multi-tier IT service where each VBS tier hosts one or more resiliency groups. A
VBS groups multiple services as a single unit for visualization, automation, and
controlled start and stop in the desired order. You can also migrate/takeover the
entire VBS.
The web-based management console on the Resiliency Manager that is used to
configure the settings for the resiliency domain and perform operations.
197
Index
A
alert settings
email 147
SNMP 149
asset infrastructure
about adding assets as hosts 73
adding hosts 76
adding storage enclosures 104
adding to IMS 72
adding VMware virtualization servers 88
CSV file for adding hosts 76
editing storage enclosures 113
editing VMware virtualization servers in IMS 90
prerequisites for hosts 74
prerequisites for Hyper-V virtualization
discovery 81
prerequisites for VMware discovery 83
RecoverPoint appliance 112
refreshing ESX Servers in IMS 91
refreshing hosts 80
refreshing storage enclosures 114
refreshing VMware virtualization servers 91
removing hosts 78
removing storage enclosures 114
removing VMware virtualization servers 91
troubleshooting discovery of assets 169
Windows host installation 75
authentication domains
configuring 128
unconfiguring 132
C
components
configuring 33
Control Host 84
CSV file for adding hosts to IMS 76
D
dashboard 193
data centers
managing 49
deploying
Hyper-V Manager 30
VA 28
VMware vSphere Client 29
deployment
infrastructure 15
replication 20
discovery host 93
DNS server settings for data center 51
domains on login 133
downloading
virtual appliance 29
E
email settings 147
EMC Symmetrix configuration prerequisites 94–95,
98
events 162
F
firewall 25
G
Getting Started wizard 37
H
Hitachi configuration prerequisites 100
hosts
adding to IMS 76
installing host package on Windows host 75
refreshing in IMS 80
removing in IMS 78
hot fix
installing 118
uninstalling 119
Hyper-V servers
discovery in IMS 81
prerequisites for IMS discovery 81
Index
I
M
icons 194
Infrastructure Management Server
about adding assets as hosts 73
adding 45
adding asset infrastructure 72
adding hosts 76
adding storage enclosures 104
adding VMware virtualization servers 88
CSV file for adding hosts 76
editing storage enclosures 113
editing VMware virtualization servers in IMS 90
modifying 47
overview 19
prerequisites for adding hosts 74
prerequisites for adding VMware vCenter
servers 83
prerequisites for Hyper-V virtualization
discovery 81
reconnecting to Resiliency Manager 48
refreshing ESX Servers 91
refreshing hosts 80
refreshing storage enclosures 114
refreshing VMware virtualization servers 91
removing 46
removing hosts 78
removing storage enclosures 114
removing VMware virtualization servers 91
troubleshooting discovery of assets 169
Windows host installation 75
IPV 25
menu bar 188
J
jobs for custom personas 137
L
licenses
about 120
managing 121
report 122
viewing 121
login 133
login to web console 36
logs
purge settings 150
viewing in console 162
N
NetApp configuration prerequisites 99
network settings
configuring for data centers 51
notification settings
email 147
rules 149
SNMP 149
P
package
installing 118
patch
installing 118
permissions 122
assigning to users 134
overview 124
personas
custom 136–137
limiting object scope for operations 128
predefined 125
ports 25
purge settings for logs and SNMP traps 150
Q
Quick Actions menu 190
R
RecoverPoint configuration prerequisites 111
reports
about 139
inventory 139
managing preferences 139
managing schedule 145
risk assessment 139
running 144
scheduling 142
viewing 145
resiliency domain
creating 37
joining 39
overview 18
removing Resiliency Manager 40
199
Index
Resiliency Manager
configuring on web console 37
joining existing resiliency domain 39
overview 18
removing from resiliency domain 40, 173
services 167
troubleshooting connections 172
viewing status 42
Resiliency Platform
features and components 14
risk information
view 164
risks
description 165
rules for event notifications 149
S
SNMP
configuring settings 149
purge settings for traps 150
storage enclosures
adding to IMS 104
editing in IMS 113
refreshing in IMS 114
removing in IMS 114
subnet information for data center 53
supported hypervisors 24
system requirements 25
T
telemetry collection 151
U
Update
refresh 159
remove 160
virtual appliance 157
update
about 152–153
Updating
virtual appliance 159
upgrade
adding repository server 156
assigning repository server 157
downloading updates 155
prerequisites of repository server 154
setting up repository server 155
user authentication 122–123
user permissions
overview 124
users
assigning permissions 134
configuring 133
V
V-Switch information for data center 53
Veritas Resiliency Platform
configuring 32
virtual appliance
components 168
downloading 29
VMware virtualization server
adding to IMS 88
configuring the VMware vCenter Server to
generate SNMP traps 87
editing configuration in IMS 90
near real-time update in IMS 84
refreshing configuration in IMS 91
refreshing ESX Servers in IMS 91
removing configuration in IMS 91
requirements for IMS discovery 83
setting up near real-time update of virtual machine
states 86
200
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement